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