Should I start from .gltf or .glb?

From GLB if you can: it packs everything into one file with no risk of a missing .bin or texture. If you only have the .gltf, load its companion files too.

Do animations come across?

No: the USDZ comes out in a static pose. Animated AR on iOS needs Apple's Reality Converter. Geometry, materials and textures are preserved.

What if the glTF uses Draco compression?

It's decompressed on load, so the conversion works fine. The resulting USDZ uses no mesh compression — it can weigh considerably more than the source glTF.

No file handy?

Convert toUSDZ

Coordinates and scale are preserved exactly as they are.

Convert glTF to USDZ

Drop your glTF files and download them as USDZ: free, in batch, and they never leave your device.

glTF → USDZ: what you should know

glTF to USDZ completes the pair of formats you need to publish AR across the whole web: glTF/GLB is the standard for Android and browsers; USDZ is what iOS understands through Quick Look. With both files, the "view in your space" button works for every visitor.

glTF arrives with PBR materials, so the conversion carries base colour, metalness, roughness and textures into the USD container — it's one of the conversions that loses the least along the way.

It runs in the browser with Three.js's USDZ exporter. If your glTF comes with .bin and loose texture files, load them alongside the .gltf so the conversion can find them.

Related conversions

STL → USDZ PLY → USDZ OBJ → USDZ glTF → STL glTF → PLY glTF → OBJ glTF → GLB glTF → 3MF

Analytics

I measure which tools get used and which ones fail, so I can fix them. Your files never leave your device.

If you decline, everything still works. If you answer a question, I only keep your answer. What I measure