> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tilebox.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Assets in Tilebox
> Understand how Tilebox datapoints reference files in external storage.
Assets connect searchable Tilebox datapoints to files such as images and previews. Tilebox stores those references with the datapoint, while the files remain in their original storage.
## Reusable file access model
A structured asset model lets the Tilebox storage client access files through one interface. The same client reads assets from Tilebox open data datasets and from datasets you create that reference files in private buckets.
## Assets belong to datapoints
A datapoint can reference named assets such as `red`, `nir`, or `thumbnail`. Each asset contains a primary location, optional alternate locations, and metadata such as its media type, roles, or bands.
Asset locations can reference storage and authentication schemes. These describe provider settings such as region and requester-pays behavior and how access is authenticated, allowing the storage client to select and configure a compatible location.
Assets can also include metadata compatible with common STAC extensions, including [Electro-Optical](https://github.com/stac-extensions/eo), [Projection](https://github.com/stac-extensions/projection), and [Raster](https://github.com/stac-extensions/raster).
In Python, [`AssetCollection`](/api-reference/python/tilebox.datasets.assets/AssetCollection) provides read-only, key-based access to the assets of one datapoint.
## Work with assets
Query an asset-enabled dataset, then read, stream, download, or open its files.
Add references to your own files when ingesting datapoints.