> For the complete documentation index, see [llms.txt](https://help.vectary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.vectary.com/documentation/sharing-exporting-embedding/export-options.md).

# Export options

Vectary supports exporting projects to a range of widely used 3D file formats. Each format serves different use cases — whether it's for 3D printing, AR, web, or other platforms.

To export a file, go to the **Menu** ➞ **Export**:

<figure><img src="https://2973737105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAXNLyKVZ2tvtyDr8sVES%2Fuploads%2FgxGIXh1YZtS96TX80dJw%2Fimage.png?alt=media&amp;token=e2e10fb1-5ef2-42a8-b44d-8131c5d288bf" alt="" width="375"><figcaption></figcaption></figure>

<table><thead><tr><th width="187.84375">Formats</th><th>Details</th></tr></thead><tbody><tr><td><strong>OBJ</strong> (.obj + .mtl)</td><td><ul><li><strong>Content:</strong> Geometry, basic materials</li><li><strong>Textures:</strong> Separate files</li><li><strong>Best for:</strong> compatibility with most 3D software</li><li><strong>Note:</strong> Does not support animation or lights</li></ul></td></tr><tr><td><strong>DAE</strong></td><td><ul><li><strong>Content:</strong> Geometry, basic materials</li><li><strong>Note:</strong> Can be complex and inconsistent between software</li></ul></td></tr><tr><td><strong>USDZ</strong></td><td><ul><li><strong>Content:</strong> All-in-one AR-ready 3D scene</li><li><strong>Textures:</strong> Embedded</li><li><strong>Supports:</strong> Geometry, materials, animations, lights</li><li><strong>Best for:</strong> Apple AR experiences (iOS, Safari, RealityKit)</li><li><strong>Note:</strong> Single file, lightweight and optimized for AR<br><br>⚠️ USDZ export settings include an option to choose the file type — ASCII or Binary.<br><br>- <strong>ASCII</strong> format saves the data in a human-readable text form, which is useful for debugging and version control. <br><br>- <strong>Binary</strong> format creates smaller files and loads faster, making it more suitable for production and distribution.</li></ul></td></tr><tr><td><strong>GLTF</strong> (.gltf + .bin + textures folder)</td><td><ul><li><strong>Content:</strong> Scene description in JSON</li><li><strong>Textures:</strong> External folder</li><li><strong>Supports:</strong> Geometry, materials, animations, lights, cameras</li><li><strong>Best for:</strong> Web and modern 3D workflows</li><li><strong>Note:</strong> Folder-based format, not ideal for sending as a single file</li></ul></td></tr><tr><td><strong>GLB</strong> (binary glTF)</td><td><ul><li><strong>Content:</strong> All assets packed into a single binary file</li><li><strong>Textures:</strong> Embedded</li><li><strong>Supports:</strong> Geometry, materials, animations, lights, cameras</li><li><strong>Best for:</strong> Web, AR, game engines, and when a single file is needed</li><li><strong>Note:</strong> Compact and easy to share, widely supported</li></ul></td></tr><tr><td><strong>FBX</strong></td><td><ul><li><strong>Content:</strong> Complex scenes with hierarchy</li><li><strong>Textures:</strong> Separate files</li><li><strong>Supports:</strong> Geometry, cameras, lights</li><li><strong>Best for:</strong> Game engines</li><li><strong>Note:</strong> Proprietary format by Autodesk, large file sizes possible</li></ul></td></tr><tr><td><strong>STL</strong></td><td><ul><li><strong>Content:</strong> Pure geometry</li><li><strong>Textures:</strong> Not supported</li><li><strong>Supports:</strong> Geometry data only (triangles)</li><li><strong>Best for:</strong> 3D printing</li><li><strong>Note:</strong> No color, no texture, no animation — just shape</li></ul></td></tr></tbody></table>

Related topics:

[Sharing](/documentation/sharing-exporting-embedding/sharing.md)

[Augmented Reality (WebAR)](/documentation/project-settings/augmented-reality-webar.md)

[Download image](/documentation/design-process/control-bar/download-image.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.vectary.com/documentation/sharing-exporting-embedding/export-options.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.