Free online USDZ to GLB converter

Many WebGL viewers, game engines, 3D editors, and asset libraries require GLB instead of Apple’s USDZ format. Conversion creates a portable single file for sharing, archiving, and real-time rendering outside Apple’s AR Quick Look ecosystem.

What the USDZ format is

USDZ is a ZIP-based package built around Pixar’s Universal Scene Description (OpenUSD) format and developed for Apple and Pixar workflows. Its package can contain USD scene files, meshes, materials, animations, and referenced image textures without a separate asset folder. USDZ packages normally store their members without ZIP compression, so “compressed” does not accurately describe the container.

Apple uses USDZ for AR Quick Look on iPhone, iPad, and macOS, and for content created with Reality Composer, Reality Composer Pro, and Apple’s Reality Converter. OpenUSD tools and applications such as Houdini, Cinema 4D, Autodesk products, and other digital-content-creation software can also create or process USD and USDZ files. USDZ may include composition layers, variants, custom schemas, renderer-specific materials, cameras, lights, physics, or AR-related metadata that do not have direct GLB equivalents.

What the GLB format is

GLB is the binary, single-file form of glTF 2.0, a real-time 3D transmission format maintained by the Khronos Group. It can contain a scene hierarchy, meshes, materials, embedded textures, and supported animations in one file.

GLB is accepted by many browser viewers and engines, including Three.js, Babylon.js, Unity, Unreal Engine, and Blender. Compared with a JSON glTF file accompanied by separate binary and texture files, GLB reduces missing-asset and path problems and simplifies uploads, downloads, and version control. It is intended for runtime rendering, not for preserving the complete authoring structure of a USD scene.

Convert the file on 101convert.com

You can convert a file on 101convert.com for free without installing software:

1. Open the USDZ-to-GLB converter and upload the .usdz file.
2. Choose GLB as the output format and start the conversion.
3. Download the resulting .glb file.
4. Open the GLB in the destination viewer or application and check its geometry, textures, materials, scale, orientation, and animations.

Do not distribute the converted file without checking it in the application that will use it; a successful conversion does not guarantee that every USD feature survived the format change.

Convert with Blender

Recent Blender versions include USD import and glTF 2.0 export. Menu names and supported USD features vary by release.

1. Keep a backup of the original model.usdz file.
2. In Blender, choose File → Import → Universal Scene Description and select the USDZ file. If the version does not import USDZ directly, extract the package with a ZIP utility, preserve the relative locations of all textures, and import its root .usd, .usda, or .usdc scene file instead.
3. Inspect the imported scene in Material Preview or Rendered view. Check mesh visibility, texture paths, object transforms, cameras, lights, and animation data.
4. Select the objects to include, then choose File → Export → glTF 2.0.
5. Set Format to GLB. Enable Selected Objects for a partial export and Animation when supported animation data must be included.
6. Choose a destination such as model.glb, export the file, and reopen it in Blender or the target glTF viewer for verification.

If Blender’s USD importer is unavailable or fails on the package, use a current Blender release or OpenUSD-compatible desktop tooling to unpack or convert the source first. A USDZ archive can contain multiple layers, so importing only a texture or secondary layer can produce an incomplete scene.

Quality and compatibility limitations

USD and glTF use different scene models, so conversion is not always lossless. Meshes, UVs, basic transforms, and ordinary animation tracks often transfer, while USD composition arcs, variants, custom schemas, AR anchors, physics, particles, application-specific metadata, and some lights or cameras may be discarded.

Materials need particular inspection. GLB commonly uses glTF’s metallic-roughness physically based material model, while USDZ may use UsdPreviewSurface or renderer-specific shader graphs. Unsupported node networks can become flat-colored or partially configured materials. Verify texture color space, opacity mode, normal-map orientation, UV transforms, and transparency in the destination application.

Check units, axis orientation, and transforms before export. Differences in conventions can make a model appear too large, too small, rotated, or mirrored. Embedded textures can make the GLB large; resizing textures or enabling a mesh-compression option can reduce size, but compressed output must be tested in the target viewer because decoder support varies.

Retain the original USDZ when Apple AR placement data, USD variants, editability, or full-fidelity scene reconstruction may be needed. The GLB normally preserves only the visible geometry and the USD features supported by the importer and glTF exporter.