# Supported file formats

Lookup table. Imports for 3D models and reference images, exports for renders and 3D scene downloads.

## Imports

### 3D models (Smart Import)

Smart Import accepts: `.glb`, `.gltf`, `.dae`, `.fbx`, `.ply`, `.obj`, `.stl`, `.usd`.

| Format         | Notes                                                                                                                  |
| -------------- | ---------------------------------------------------------------------------------------------------------------------- |
| **GLB / GLTF** | Web-optimized format with embedded textures and materials. The smallest file size for the most complete asset.         |
| **FBX**        | Geometry plus materials when authored as standard PBR. The most common interchange format from Maya, 3ds Max, Blender. |
| **OBJ**        | Geometry only, no materials. Clean meshes from CAD tools.                                                              |
| **DAE**        | COLLADA interchange. Older pipelines that still publish DAE.                                                           |
| **PLY**        | Point-cloud and scan format. Geometry only.                                                                            |
| **STL**        | Mesh-only format common to CAD and 3D-print pipelines.                                                                 |
| **USD**        | Pixar's universal scene description. Round-trip with Maya, Houdini, and Unreal.                                        |

See [Smart Import](/build/import-your-own-models.md) for the import workflow.

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

| Format   | Notes                                                       |
| -------- | ----------------------------------------------------------- |
| **JPEG** | Compressed raster. Common photographic format.              |
| **PNG**  | Lossless raster. Better for clean images with transparency. |

Image reference and custom styles accept JPEG and PNG. 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

User-supplied audio import isn't exposed in any flow today. The product 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.

## Exports

### Renders

| Format   | Used for                                                                     |
| -------- | ---------------------------------------------------------------------------- |
| **PNG**  | Lossless raster. Print, downstream design tools, anything with 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 in v1.                                                          |
| **Lottie or motion-graphics formats**    | Not supported. Render as MP4 and re-encode externally.                        |

## Limits and known issues

* **Browser-based rendering imposes a soft cap.** Multi-gigabyte FBX files with millions of triangles will struggle. Run a decimation pass externally before import.
* **Audio in MP4 exports is per-shot.** No cross-shot audio mixing in [Export Video](/publish/export-video.md). Mix in editorial.
* **Video export resolution is limited by the lowest-resolution shot.** A sequence with mixed resolutions exports at the lowest common one.

## Related

* [Smart Import](/build/import-your-own-models.md)
* [Image reference](/overview/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: 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:

```
GET https://help.intangible.ai/overview/reference/supported-file-formats.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.