> For the complete documentation index, see [llms.txt](https://help.intangible.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.intangible.ai/learn-more/reference/supported-file-formats.md).

# Supported file formats

Which file formats Intangible accepts for import and exports for download. Plus what's not supported and what to do about it.

Bring in GLB, GLTF, FBX, OBJ, DAE and PLY models, SOG and SPZ splats, and JPEG, PNG or WebP reference images. Take out PNG and JPEG renders, MP4 video, and GLTF/GLB or USD scenes.

## Imports

### 3D models (Smart Import)

Smart Import accepts: `.glb`, `.gltf`, `.dae`, `.fbx`, `.ply`, `.obj`, `.sog`, `.spz`.

| Format         | Notes                                                                                                                                                               |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **GLB / GLTF** | Web-optimized format. The most reliable path in, and the smallest file for a given model.                                                                           |
| **FBX**        | The most common interchange format from Maya, 3ds Max and Blender. A rigged FBX keeps its skeleton.                                                                 |
| **OBJ**        | Clean meshes from CAD tools.                                                                                                                                        |
| **DAE**        | COLLADA interchange. Older pipelines that still publish DAE.                                                                                                        |
| **PLY**        | Used by two different things. A mesh or scan PLY imports as geometry; a Gaussian splat PLY imports as a splat. The file header decides which, so you don't have to. |
| **SOG / SPZ**  | Compressed Gaussian splat formats. See [Import Gaussian splats](/build/import-gaussian-splats.md).                                                                  |

Every format comes in as geometry. Import removes textures, except alpha masks, and makes every material plain white, so colour is lost too; attach an [image reference](/learn-more/concepts/image-reference.md) to bring the look back. Animation clips are dropped. See [What import keeps](/build/import-your-own-models.md#what-import-keeps).

USD is an **export** format only; it is not accepted on import. STL and DXF are not accepted either.

### Import size limits

| What                                | Limit                          |
| ----------------------------------- | ------------------------------ |
| 3D model, any supported mesh format | 512 MB, and 2 million vertices |
| Gaussian splat, `.PLY`              | 2 GB                           |
| Gaussian splat, `.SPZ` or `.SOG`    | 512 MB                         |
| Gaussian splat, any format          | 10 million splats              |
| Files per upload                    | 10                             |

Each limit is a hard one: a file over it is rejected during import rather than failing silently later. Splats take longer to process than meshes of the same size, since they are voxelised as well as compressed.

See [Smart Import](/build/import-your-own-models.md) for the mesh workflow and [Import Gaussian splats](/build/import-gaussian-splats.md) for splats.

### Reference images (image reference, custom styles)

| Format   | Notes                                                  |
| -------- | ------------------------------------------------------ |
| **JPEG** | Compressed raster. Common photographic format.         |
| **PNG**  | Lossless raster. Better for clean images and graphics. |
| **WebP** | Compressed raster. Accepted as a reference image.      |

Image reference and custom styles accept JPEG, PNG and WebP, up to 20 MB. GIFs are not accepted. Larger images are downsampled internally; sub-megapixel resolution is fine.

### LoRA files

| Format             | Notes                                              |
| ------------------ | -------------------------------------------------- |
| **`.safetensors`** | The standard format for fine-tuned models.         |
| **`.pt`**          | Older PyTorch format. Supported but not preferred. |

See [LoRAs](/build/loras.md) for the upload flow.

### Audio

You can't import audio. Intangible generates audio as part of video output where the chosen model supports it; you can't upload an audio track and sync it to a render.

**Start from what's already on your drive.**

<a href="https://studio.intangible.ai/?utm_source=help.intangible.ai&#x26;utm_medium=docs&#x26;utm_campaign=page-cta&#x26;utm_content=supported-file-formats" class="button primary" data-icon="arrow-up-right">Import a file into Intangible</a>

## Exports

### Renders

| Format   | Used for                                                                             |
| -------- | ------------------------------------------------------------------------------------ |
| **PNG**  | Lossless raster for print and downstream design tools. Renders have no transparency. |
| **JPEG** | Compressed raster. Web, social, email.                                               |

### Video

| Format                  | Used for                                              |
| ----------------------- | ----------------------------------------------------- |
| **MP4 (H.264, 30 fps)** | The default video container. Universal compatibility. |

Other video codecs (H.265, ProRes) aren't exposed. For specialized codecs, transcode externally.

### 3D scene

| Format         | Used for                                                                                                       |
| -------------- | -------------------------------------------------------------------------------------------------------------- |
| **GLTF / GLB** | Open 3D scene format (GLB is the binary variant). Web handoff (Three.js, Babylon), some Unity flows, archival. |
| **USD**        | Virtual production handoffs, Unreal Engine, Maya / Houdini round-trips.                                        |

Scene exports preserve hierarchy, transforms, and cameras. Owned library assets export at full fidelity; licensed assets get smart stand-ins. See [Export formats](/publish/export-formats.md).

## What's not supported and what to do

| Want                                     | Workaround                                                                    |
| ---------------------------------------- | ----------------------------------------------------------------------------- |
| **FBX export**                           | GLTF or USD. Or render to PNG and import the still into the downstream tool.  |
| **TIFF for high-bit-depth print**        | PNG covers most print cases at lower bit depth. Convert externally if needed. |
| **HDR formats (.exr)** for VFX pipelines | Not supported; no equivalent workaround.                                      |
| **Stereo or 360 video**                  | Not supported.                                                                |
| **Lottie or motion-graphics formats**    | Not supported. Render as MP4 and re-encode externally.                        |

## Can I import STEP, STL, SketchUp or Revit files?

Yes, once you convert the file to a format Intangible accepts: GLB, GLTF, DAE, FBX, PLY, OBJ, SOG or SPZ. Export it from the tool it came from, or convert it for free in FreeCAD or Blender, then import the result.

| You have               | Convert to | How                                                                                                         |
| ---------------------- | ---------- | ----------------------------------------------------------------------------------------------------------- |
| **SketchUp** (.skp)    | FBX or OBJ | **File > Export > 3D Model** in SketchUp Go, Pro or Studio.                                                 |
| **Revit** (.rvt)       | FBX or OBJ | Open a 3D view, then **File > Export > FBX**, or **File > Export > CAD Formats > OBJ**.                     |
| **STEP** (.step, .stp) | GLB or OBJ | In FreeCAD (free), **File > Import**, select the parts, then **File > Export**.                             |
| **STL** (.stl)         | GLB        | In Blender (free), **File > Import > Stl (.stl)**, then **File > Export > glTF 2.0** as glTF Binary (.glb). |

## Limits and known issues

* **Big files import slowly.** A model near the 512 MB or 2 million vertex limit takes longer to import and to work with. Run a decimation pass in your modeling tool before import.
* **Audio in MP4 exports is per-shot.** No cross-shot audio mixing in [Export Video](/publish/export-video.md). Mix in editorial.
* **A joined cut takes the size of its first video.** In a scene or sequence export, each shot's own file keeps the resolution it was rendered at. The joined video uses the resolution of the first video in the export, and the other shots are scaled to fit it.

## Related

* [Smart Import](/build/import-your-own-models.md)
* [Render a CAD file with AI](/learn-more/how-to/render-a-cad-file-with-ai.md)
* [Image reference](/learn-more/concepts/image-reference.md)
* [LoRAs](/build/loras.md)
* [Export formats](/publish/export-formats.md)
* [Generate image](/visualize/generate-image.md)
* [Generate video](/visualize/generate-video.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.intangible.ai/learn-more/reference/supported-file-formats.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.