Skip to content

Exporting

Click the Share button in the toolbar to export your model. Gantry offers two export modes — choose the one that matches how the file will be used next.

Writes the asset preserving its original USD composition — layers, references, payloads, and variants are kept intact. The resulting file can be re-imported into DCC tools and round-tripped without losing structure.

Use this when:

  • You plan to continue editing the file in another application
  • The asset uses USD variants or references you want to keep
  • You are passing the file to another person in the same pipeline

Collapses all USD composition into a single layer and embeds all referenced assets (textures, sub-layers) into one self-contained file. References and layer structure are removed.

Use this when:

  • You are delivering a final asset for distribution or deployment
  • The recipient doesn’t need to understand the internal structure
  • You want a single portable file with no external dependencies
FormatExtensionDescription
USDZ Archive.usdzSelf-contained ZIP-based archive. Best for Apple platforms, AR Quick Look, and Reality Composer Pro.
USD (auto).usdGantry chooses ASCII or binary encoding based on content.
USD ASCII.usdaHuman-readable text. Useful for inspection and version control.
USD Binary.usdcCompact binary (Crate format). Smaller file size, faster to load.

Before or during export you can optimize the textures embedded in your asset — controlling output format, compression quality, maximum resolution, and mipmap generation. See Optimizing Textures for the full workflow.

  • Use USDZ + Flattened for sharing with Apple users or deploying to AR workflows
  • Use USD + Preserve Authorship for continued editing in other 3D applications
  • Run texture optimization before a final USDZ export to reduce file size for RealityKit delivery