Which 3D model file format should you deliver for WebAR or WebXR? Begin with the target viewer and the content features it must support. A model opening in a desktop authoring tool does not establish that it will load quickly, look correct or interact properly in the final experience. This guide explains the delivery decisions using primary documentation checked on 5 October 2026.
Cover photograph: Unsplash. Illustrative stock photograph; it does not depict a tested device comparison or a Mimic XR client project.
In this guide
glTF and GLB for runtime delivery
Khronos describes glTF as a format for efficient transmission and loading of 3D scenes and models. The glTF 2.0 specification defines the format and its binary container. In a typical delivery, .gltf uses a JSON description with referenced resources, while .glb can package the content in a binary file.
Choose the packaging around the application pipeline and caching needs. A single file can simplify delivery, but its extension does not guarantee a small download. Texture resolution, geometry and the features included in the model still determine the workload.
USDZ for the Apple viewing route
Apple’s Quick Look documentation describes its supported AR viewing workflow. Plan the corresponding asset delivery when that route is part of the project. Do not assume renaming or mechanically converting a file preserves every material, animation or interaction.
Test the exported asset in the actual viewer. Check scale, orientation, transparency and the intended animation. If the experience also uses a browser 3D viewer, keep the two outputs traceable to the same approved source so catalogue updates remain consistent.
Keep editable source assets
Separate the source package from the runtime deliverable. The source should preserve the material references, textures, naming and ownership information needed to maintain the content. The runtime package should contain what the target experience requires.
Agree who owns the editable files and who can regenerate exports. This matters when a product finish changes or a platform update exposes an incompatibility. A delivery containing only an optimised final file may be difficult to update reliably.
Validate appearance and performance
Use a representative asset early. Check dimensions, origin, orientation, materials, textures, animation and behaviour under the final lighting. Test compression support and fallback behaviour before applying a pipeline to the entire catalogue.
Measure transfer size and performance on target hardware. Optimise the parts that dominate the real workload rather than chasing an arbitrary polygon count. A modest mesh with oversized textures can still be expensive. Keep essential product information available outside the 3D view.
Write an asset delivery specification
List target viewers, output formats, units, naming, material requirements, supported animations, size budgets and acceptance tests. Include a version identifier and a way to report defects. Validate the exported outputs, not just the authoring scene.
For production support, explore 3D modelling and asset creation, AR product visualisation and WebXR development. Contact Mimic XR with the target devices and a representative source asset.
Frequently asked questions
Are glTF and GLB unrelated formats?
No. GLB is the binary container defined by the glTF specification.
Does GLB automatically mean a small file?
No. Geometry, textures and included features still determine the delivery size.
Should we retain editable source files?
Yes. They support corrections, new outputs and future content maintenance.
Is conversion enough to guarantee visual parity?
No. Validate the exported materials, scale and animation in the target viewer.
Does WebXR require one universal file format?
No. The application and rendering pipeline determine how content is loaded.
What should be tested first?
A representative asset with the most important materials and interactions.
Is polygon count the only performance measure?
No. Texture memory, materials, scene complexity and device limits also matter.
What belongs in an asset specification?
Formats, units, naming, supported features, budgets, ownership and acceptance checks.
