What an asset is

An asset is a stored file attached to a project. Assets are what the Editor builds map layers from and what the export system draws on when generating game-ready output.

Each asset has a kind (terrain elevation, vector data, or raster image), a format, a size, a checksum, and metadata describing where it came from and how it was processed. Most assets are created automatically as the result of a completed task; others are created when you upload a file directly or when the Editor creates certain layer types.

Asset kinds

Assets come in three kinds:

• DTM (terrain elevation) — a processed height map representing the elevation of the project area, typically stored as a PNG image where pixel brightness encodes height. Used to drive the terrain layer in the Editor.
• Vector — a structured dataset of geographic features (roads, rivers, fields, buildings, and more) projected into the project's local coordinate space. Used to populate all vector layers in the Editor.
• Raster — a positioned image layer. Satellite imagery arrives as a raster asset, and any paint, mask, or custom image layers you create or edit in the Editor are stored as raster assets.

Where assets come from

An asset can originate from three sources:

• A completed task — when a download or processing task finishes, it automatically creates one or more assets and links them to the project. The task detail page shows which assets were produced.
• A direct upload — some workflows let you skip the download step and upload a prepared file directly. The file is stored as an asset and a processing step runs against it.
• Manual creation in the Editor — certain layer types (such as empty paint layers) create their own underlying assets when you add them to a project.

Viewing and managing assets

You can see the full list of assets for a project from the Assets tab in the project view. Each entry shows the kind, format, file size, and creation date. The list also indicates which task produced the asset, if applicable.

Assets are immutable — they are not edited in place. When something changes in the Editor (for example, a paint layer is modified), a new asset version is created.

Storage used by all assets across all projects in your team counts toward your team's total storage. You can check your current usage from the Usage page in the dashboard.