> For the complete documentation index, see [llms.txt](https://umber.gitbook.io/umber/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://umber.gitbook.io/umber/concepts/asset-types.md). # Asset Types Umber can, in principle, store and deliver any kind of file. To support better delivery, searching, and filtering, every asset is tagged with one of the following types. Each type has a **slug** and a numeric **ID**. The slug is the readable name and is what we recommend using; the ID is the stored value and is accepted everywhere the slug is. Both forms work in every API that takes an asset type, and always will — existing integrations that send IDs keep working. | Type | Slug | ID | Extensions | | ------------------ | --------------- | ---- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Image | `image` | 0001 | `.arw` `.avif` `.bmp` `.cr2` `.cr3` `.dng` `.emf` `.emz` `.gif` `.heic` `.heif` `.ico` `.jfif` `.jpe` `.jpeg` `.jpg` `.jxl` `.nef` `.orf` `.png` `.raf` `.rw2` `.svg` `.tif` `.tiff` `.webp` `.wmf` | | Audio | `audio` | 0002 | `.aac` `.aif` `.aiff` `.flac` `.m4a` `.mp3` `.oga` `.ogg` `.opus` `.wav` `.wma` | | Video | `video` | 0003 | `.avi` `.braw` `.m4v` `.mkv` `.mov` `.mp4` `.mpeg` `.mpg` `.mxf` `.ogv` `.r3d` `.webm` `.wmv` | | Unity Asset | `unity` | 0004 | `.bundle` `.unity3d` `.unitypackage` | | Unreal Asset | `unreal` | 0005 | `.pak` `.uasset` `.ucas` `.umap` `.utoc` | | PDF | `pdf` | 0006 | `.pdf` | | XML | `xml` | 0007 | `.xml` `.xsd` `.xsl` `.xslt` | | JSON | `json` | 0008 | `.geojson` `.json` `.jsonl` `.ndjson` | | 3D Model | `model-3d` | 0009 | `.3ds` `.abc` `.basis` `.blend` `.dae` `.drc` `.exr` `.fbx` `.glb` `.gltf` `.hdr` `.ktx2` `.mtl` `.obj` `.ply` `.stl` `.usd` `.usda` `.usdc` `.usdz` `.vrm` | | Document | `document` | 0010 | `.doc` `.docm` `.docx` `.dot` `.dotx` `.odt` `.rtf` | | Spreadsheet | `spreadsheet` | 0011 | `.csv` `.ods` `.tsv` `.xls` `.xlsb` `.xlsm` `.xlsx` | | Presentation | `presentation` | 0012 | `.key` `.odp` `.ppt` `.pptm` `.pptx` | | Font | `font` | 0013 | `.eot` `.otf` `.ttc` `.ttf` `.woff` `.woff2` | | Archive | `archive` | 0014 | `.7z` `.br` `.gz` `.rar` `.tar` `.tar.gz` `.tgz` `.zip` | | Data / Config | `config` | 0015 | `.avsc` `.gql` `.graphql` `.ics` `.ini` `.log` `.md` `.parquet` `.properties` `.proto` `.toml` `.txt` `.yaml` `.yml` | | Localization | `localization` | 0016 | `.arb` `.mo` `.po` `.resx` `.strings` `.xlf` `.xliff` | | Caption / Subtitle | `caption` | 0017 | `.dfxp` `.sbv` `.srt` `.ttml` `.vtt` | | Design Source | `design-source` | 0018 | `.afdesign` `.afphoto` `.ai` `.eps` `.fig` `.indd` `.psb` `.psd` `.sketch` `.xd` | | CAD / Engineering | `cad` | 0019 | `.dwg` `.dxf` `.ifc` `.iges` `.igs` `.sldasm` `.sldprt` `.step` `.stp` | | Web Asset | `web-asset` | 0020 | `.css` `.htm` `.html` `.js` `.map` `.mjs` `.wasm` | You'll provide the asset type when creating the definition of an Asset Version or Asset Collection. {% hint style="warning" %} **Fetch the type list, don't hard-code it.** `GET /assettypes` returns the current set, with both slug and ID for each. This table grows — nine types were added in September 2026 — and a copied list silently stops offering the newer ones. A workspace that hard-coded an older list had every spreadsheet and CAD drawing filed under the wrong type for months, because the types that fit them weren't in the copy. **Extensions are a different matter.** `/assettypes` does not return them, so this page is the published list. It also grows. Rather than copying it into your own client-side check, let the upload call decide: an unsupported file is rejected with a message naming the file's real type and what the target accepts. Your copy of the list can go stale; the API's cannot. {% endhint %} The table is the definitive list of what each type accepts. A few types are worth a word of explanation: * **Data / Config** (`config`) is for structured configuration shipped as an asset — YAML, TOML, `.properties`, Parquet, and plain `.txt` and `.md`. * **Image** (`image`) includes camera raw formats (`.cr3`, `.nef`, `.arw` and similar) and `.svg`. SVG is delivered with script execution disabled, so it still previews but cannot run code. * **Web Asset** (`web-asset`) splits by how the file is delivered: `.js`, `.css`, `.wasm` and `.map` are served inline for your own pages to load, while `.html` is always delivered as a download. * **Archive** (`archive`) covers the container formats; what is inside them is not inspected or indexed. If you need a format that isn't covered above, contact or raise a ticket from your account. {% hint style="info" %} The [Umber CLI](/umber/cli-tools/umber-cli.md)'s `assets migrate` command currently auto-discovers Image (`png jpg jpeg gif webp avif svg`), Video (`mp4 webm mov`), and Doc-family files (`pdf doc docx xls xlsx csv`). Audio is mapped internally but not yet enabled, and the remaining types aren't yet covered by CLI auto-discovery — those still need to go through the dashboard. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://umber.gitbook.io/umber/concepts/asset-types.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.