VertexModelerLoading environment
Loading environment
3D File Formats
Choose a format by delivery target, material support, hierarchy, animation, and ecosystem—not by file extension alone.
Continue learning
3D File FormatsPrepare Principled materials, normal maps, transforms, and packages for a reliable round trip.
Read guideNo 3D format is best for every destination. glTF is strong for real-time delivery, USD for composed scenes, USDZ for Apple distribution, FBX for legacy DCC exchange, and OBJ for simple static geometry. This handbook keeps action, mechanism, and acceptance evidence on one production path. The aim is not to memorize menus. It is to let another artist reach the same conclusion from the same inputs, identify a version boundary, locate a failure, and recover without damaging the source.
Checked with Blender 5.2.0 LTS exporters, Khronos glTF 2.0.1, OpenUSD USDZ specification 1.3, and Apple Quick Look documentation current on 2026-07-31. FBX behavior remains implementation-specific. “Verified” means the written condition was checked against that version, repository behavior, primary specification, or named target. It does not promise that an arbitrary third-party exporter or viewer preserves the same capability. Easy-series statements are constrained by manifests, implementation, unit tests, and Blender 5.2 smoke evidence.
No 3D format is best for every destination. glTF is strong for real-time delivery, USD for composed scenes, USDZ for Apple distribution, FBX for legacy DCC exchange, and OBJ for simple static geometry. The deliverable is more than a good render or a file that opens once. It includes replayable steps, stage gates, diagnostic notes, a dependency inventory, and target-side evidence. Success that cannot be reproduced in a clean environment remains a possible cache or workstation artifact.
Representative input with units, dimensions, provenance, and one known failing control
An untouched high-quality source plus separate diagnostic, interchange, and delivery copies
Full Blender, Easy extension, exporter, and target-viewer version records
A writable staging root, dependency inventory, acceptance matrix, and rollback points
A neutral light rig, close diagnostic camera, and final delivery camera
Before starting glTF, FBX, OBJ, USD, USDC, and USDZ Compared, duplicate the source and hash critical inputs. Record the operating system, build, target format, viewer, and case budget together. When results diverge, that evidence separates content, tool, and environment changes instead of asking the team to reason across moving variables.
Principle 1: Choose the target application before choosing the format. Bind it to an observable signal and rollback point. A claim that only says the result “looks better,” without measurement or controlled comparison, is not a production gate.
Principle 2: Separate geometry fidelity from material fidelity. Bind it to an observable signal and rollback point. A claim that only says the result “looks better,” without measurement or controlled comparison, is not a production gate.
Principle 3: Check whether the target needs hierarchy, instancing, animation, or variants. Bind it to an observable signal and rollback point. A claim that only says the result “looks better,” without measurement or controlled comparison, is not a production gate.
Principle 4: Treat USDZ as a packaged USD delivery, not a universal authoring format. Bind it to an observable signal and rollback point. A claim that only says the result “looks better,” without measurement or controlled comparison, is not a production gate.
Principle 5: Prefer binary formats when reducing file count matters. Bind it to an observable signal and rollback point. A claim that only says the result “looks better,” without measurement or controlled comparison, is not a production gate.
Principle 6: Always validate with the actual target importer. Bind it to an observable signal and rollback point. A claim that only says the result “looks better,” without measurement or controlled comparison, is not a production gate.
One configurator asset has a five-part hierarchy, four metallic-roughness materials, one 3.2-second animation, two reusable fasteners, and 2K textures. GLB serves web, USDC enters a USD pipeline, USDZ serves Quick Look, FBX is retained for one partner DCC, and OBJ is only a static fallback. The case retains a failing control so the team can distinguish a genuinely correct workflow from a result that merely happens to work. Its values are case acceptance targets, not universal standards; a different camera, device, license, or delivery format requires a new budget.
The diagram connects the eight glTF, FBX, OBJ, USD, USDC, and USDZ Compared stages to explicit gates. Arrows describe dependencies, not a ban on iteration. When diagnosis disproves an upstream assumption, return to the earliest stage that owns that variable, correct it, and replay every dependent gate.
Action. Freeze the acceptance target: No 3D format is best for every destination. glTF is strong for real-time delivery, USD for composed scenes, USDZ for Apple distribution, FBX for legacy DCC exchange, and OBJ for simple static geometry. Give this stage one owner and one observable output. Work on the smallest representative part first; expanding an unverified operation across the project only multiplies uncertainty. Save a checkpoint before changing topology, file paths, color interpretation, hierarchy, or exporter state.
Control the variables. GLB/glTF is the runtime delivery for specified metallic-roughness PBR. The governing principle is: Choose the target application before choosing the format. In glTF, FBX, OBJ, USD, USDC, and USDZ Compared, treat it as a measurable production rule rather than general advice. Record the relevant dimension, path, data-block, material channel, object count, or target result beside the file so another artist can reproduce the decision without memory.
Understand the mechanism. Establish the input baseline before judging processing. “GLB/glTF is the runtime delivery for specified metallic-roughness PBR” is the factual anchor for this stage. Compare an untouched sample with the working copy under identical conditions and attribute only the change introduced here.
Stage gate. Acceptance is Target importer is known. Capture evidence appropriate to the claim: a measurement, Outliner snapshot, path inventory, neutral render, validator report, re-import, or target-viewer comparison. The known trap is: USDC can preserve rich USD data but is not as universally previewable as glTF. If the gate fails, return to the earliest stage that owns the fault instead of compensating downstream.
Action. List the required target viewers, engines, DCC tools, and devices. Give this stage one owner and one observable output. Work on the smallest representative part first; expanding an unverified operation across the project only multiplies uncertainty. Save a checkpoint before changing topology, file paths, color interpretation, hierarchy, or exporter state.
Control the variables. FBX is chosen only when a partner pipeline explicitly requires it. The governing principle is: Separate geometry fidelity from material fidelity. In glTF, FBX, OBJ, USD, USDC, and USDZ Compared, treat it as a measurable production rule rather than general advice. Record the relevant dimension, path, data-block, material channel, object count, or target result beside the file so another artist can reproduce the decision without memory.
Understand the mechanism. Structure can remain wrong while the beauty view looks plausible. “FBX is chosen only when a partner pipeline explicitly requires it” turns ownership into an inspectable condition. Verify it in the hierarchy, data-block graph, or directory layer before visual refinement expands the cost of correction.
Stage gate. Acceptance is Required PBR channels survive. Capture evidence appropriate to the claim: a measurement, Outliner snapshot, path inventory, neutral render, validator report, re-import, or target-viewer comparison. The known trap is: USDZ support varies by tool and material network. If the gate fails, return to the earliest stage that owns the fault instead of compensating downstream.
Action. Record required features: PBR maps, animation, cameras, lights, instancing, and custom metadata. Give this stage one owner and one observable output. Work on the smallest representative part first; expanding an unverified operation across the project only multiplies uncertainty. Save a checkpoint before changing topology, file paths, color interpretation, hierarchy, or exporter state.
Control the variables. OBJ carries simple static geometry and limited MTL, not scene fidelity. The governing principle is: Check whether the target needs hierarchy, instancing, animation, or variants. In glTF, FBX, OBJ, USD, USDC, and USDZ Compared, treat it as a measurable production rule rather than general advice. Record the relevant dimension, path, data-block, material channel, object count, or target result beside the file so another artist can reproduce the decision without memory.
Understand the mechanism. Preparation converts hidden state into recorded state. “OBJ carries simple static geometry and limited MTL, not scene fidelity” defines the coordinate, path, or interpretation that later operations consume. Preserve before-and-after values and reproduce the premise in a clean representative sample.
Stage gate. Acceptance is Hierarchy and transforms match. Capture evidence appropriate to the claim: a measurement, Outliner snapshot, path inventory, neutral render, validator report, re-import, or target-viewer comparison. The known trap is: OBJ has no modern standard PBR model. If the gate fails, return to the earliest stage that owns the fault instead of compensating downstream.
Action. Use glTF/GLB for broad web and real-time PBR delivery. Give this stage one owner and one observable output. Work on the smallest representative part first; expanding an unverified operation across the project only multiplies uncertainty. Save a checkpoint before changing topology, file paths, color interpretation, hierarchy, or exporter state.
Control the variables. USD is selected for composition, layers, variants, and references. The governing principle is: Treat USDZ as a packaged USD delivery, not a universal authoring format. In glTF, FBX, OBJ, USD, USDC, and USDZ Compared, treat it as a measurable production rule rather than general advice. Record the relevant dimension, path, data-block, material channel, object count, or target result beside the file so another artist can reproduce the decision without memory.
Understand the mechanism. Keep the core operation single-variable. “USD is selected for composition, layers, variants, and references” is the only control allowed to move in this comparison; camera, exposure, caches, and unrelated branches remain fixed. A repeatable response establishes causality.
Stage gate. Acceptance is Animation plays at correct timing. Capture evidence appropriate to the claim: a measurement, Outliner snapshot, path inventory, neutral render, validator report, re-import, or target-viewer comparison. The known trap is: FBX behavior can vary between exporter and importer versions. If the gate fails, return to the earliest stage that owns the fault instead of compensating downstream.
Action. Use USD/USDC for scene composition and USD pipelines; use USDZ for Apple Quick Look delivery. Give this stage one owner and one observable output. Work on the smallest representative part first; expanding an unverified operation across the project only multiplies uncertainty. Save a checkpoint before changing topology, file paths, color interpretation, hierarchy, or exporter state.
Control the variables. USDC is a binary USD crate, not a different scene model. The governing principle is: Prefer binary formats when reducing file count matters. In glTF, FBX, OBJ, USD, USDC, and USDZ Compared, treat it as a measurable production rule rather than general advice. Record the relevant dimension, path, data-block, material channel, object count, or target result beside the file so another artist can reproduce the decision without memory.
Understand the mechanism. Critical detail usually fails at boundaries rather than in a front view. Inspect “USDC is a binary USD crate, not a different scene model” close up, at a grazing angle, or across a hierarchy boundary, then compare that evidence with the approved delivery camera.
Stage gate. Acceptance is Textures are embedded or packaged. Capture evidence appropriate to the claim: a measurement, Outliner snapshot, path inventory, neutral render, validator report, re-import, or target-viewer comparison. The known trap is: USDC can preserve rich USD data but is not as universally previewable as glTF. If the gate fails, return to the earliest stage that owns the fault instead of compensating downstream.
Action. Use FBX only when a legacy pipeline requires it, and OBJ for simple geometry plus basic MTL exchange. Give this stage one owner and one observable output. Work on the smallest representative part first; expanding an unverified operation across the project only multiplies uncertainty. Save a checkpoint before changing topology, file paths, color interpretation, hierarchy, or exporter state.
Control the variables. USDZ is zero-compression with 64-byte file alignment and a default layer. The governing principle is: Always validate with the actual target importer. In glTF, FBX, OBJ, USD, USDC, and USDZ Compared, treat it as a measurable production rule rather than general advice. Record the relevant dimension, path, data-block, material channel, object count, or target result beside the file so another artist can reproduce the decision without memory.
Understand the mechanism. A correct/error pair must share its inputs. Lock every condition except “USDZ is zero-compression with 64-byte file alignment and a default layer” and save the same camera, exposure, and target-viewer result. The comparison then demonstrates the rule instead of two unrelated scene states.
Stage gate. Acceptance is File opens on a second device. Capture evidence appropriate to the claim: a measurement, Outliner snapshot, path inventory, neutral render, validator report, re-import, or target-viewer comparison. The known trap is: USDZ support varies by tool and material network. If the gate fails, return to the earliest stage that owns the fault instead of compensating downstream.
Action. Create a format matrix, export a representative asset, and compare geometry, normals, materials, hierarchy, and file size. Give this stage one owner and one observable output. Work on the smallest representative part first; expanding an unverified operation across the project only multiplies uncertainty. Save a checkpoint before changing topology, file paths, color interpretation, hierarchy, or exporter state.
Control the variables. Quick Look is tested on an actual supported Apple path. The governing principle is: Choose the target application before choosing the format. In glTF, FBX, OBJ, USD, USDC, and USDZ Compared, treat it as a measurable production rule rather than general advice. Record the relevant dimension, path, data-block, material channel, object count, or target result beside the file so another artist can reproduce the decision without memory.
Understand the mechanism. Diagnosis starts at the earliest stage that owns the variable. Use “Quick Look is tested on an actual supported Apple path” as the smallest falsifiable test; if it fails, move upstream, and if it passes, restore materials, lights, modifiers, paths, and export settings one at a time.
Stage gate. Acceptance is Target importer is known. Capture evidence appropriate to the claim: a measurement, Outliner snapshot, path inventory, neutral render, validator report, re-import, or target-viewer comparison. The known trap is: OBJ has no modern standard PBR model. If the gate fails, return to the earliest stage that owns the fault instead of compensating downstream.
Action. Run the final glTF, FBX, OBJ, USD, USDC, and USDZ Compared validation from the delivery package and archive the evidence. Give this stage one owner and one observable output. Work on the smallest representative part first; expanding an unverified operation across the project only multiplies uncertainty. Save a checkpoint before changing topology, file paths, color interpretation, hierarchy, or exporter state.
Control the variables. Separate delivery copies replace the idea of one universal master. The governing principle is: Separate geometry fidelity from material fidelity. In glTF, FBX, OBJ, USD, USDC, and USDZ Compared, treat it as a measurable production rule rather than general advice. Record the relevant dimension, path, data-block, material channel, object count, or target result beside the file so another artist can reproduce the decision without memory.
Understand the mechanism. The final gate validates the deliverable rather than the authoring workstation. Evidence for “Separate delivery copies replace the idea of one universal master” must come from the final root, a re-imported file, or the named target while source paths, caches, and temporary copies are unavailable.
Stage gate. Acceptance is Required PBR channels survive. Capture evidence appropriate to the claim: a measurement, Outliner snapshot, path inventory, neutral render, validator report, re-import, or target-viewer comparison. The known trap is: FBX behavior can vary between exporter and importer versions. If the gate fails, return to the earliest stage that owns the fault instead of compensating downstream.
Stage | Acceptance | Evidence |
|---|---|---|
1 | Target importer is known | Reproducible evidence saved |
2 | Required PBR channels survive | Reproducible evidence saved |
3 | Hierarchy and transforms match | Reproducible evidence saved |
4 | Animation plays at correct timing | Reproducible evidence saved |
5 | Textures are embedded or packaged | Reproducible evidence saved |
6 | File opens on a second device | Reproducible evidence saved |
7 | Target importer is known | Reproducible evidence saved |
8 | Required PBR channels survive | Reproducible evidence saved |
A glTF, FBX, OBJ, USD, USDC, and USDZ Compared reviewer must locate each item without asking the author and determine which source, version, and target it represents. Screenshots need diagnostic context, numbers need units, and export evidence must come from the final package rather than a temporary directory.
The glTF, FBX, OBJ, USD, USDC, and USDZ Compared method follows an “earliest responsible stage” rule. Scale errors are not camera problems, origin errors should not require a manual offset on every placement, color-space errors should not be disguised with lighting, and unsupported shader graphs should not be left for a viewer to guess. Reducing a symptom to one variable minimizes repair and regression scope.
For glTF, FBX, OBJ, USD, USDC, and USDZ Compared, assets still need distinct authoring, interchange, and delivery states. The authoring state preserves editability. The interchange state narrows expression to what the target understands. The delivery state optimizes size, dependencies, and device constraints. Distinct copies prevent portability work from permanently degrading the master.
Failure 1: USDC can preserve rich USD data but is not as universally previewable as glTF. Reproduce the smallest failure, disable unrelated lights, shader branches, modifiers, caches, or external paths, and change one condition. Save a same-camera, same-exposure, same-target comparison before accepting the explanation.
Failure 2: USDZ support varies by tool and material network. Reproduce the smallest failure, disable unrelated lights, shader branches, modifiers, caches, or external paths, and change one condition. Save a same-camera, same-exposure, same-target comparison before accepting the explanation.
Failure 3: OBJ has no modern standard PBR model. Reproduce the smallest failure, disable unrelated lights, shader branches, modifiers, caches, or external paths, and change one condition. Save a same-camera, same-exposure, same-target comparison before accepting the explanation.
Failure 4: FBX behavior can vary between exporter and importer versions. Reproduce the smallest failure, disable unrelated lights, shader branches, modifiers, caches, or external paths, and change one condition. Save a same-camera, same-exposure, same-target comparison before accepting the explanation.
Symptom | Most likely cause | Minimum test | Correction |
|---|---|---|---|
USDC can preserve rich USD data but is not as universally previewable as glTF. | Choose the target application before choosing the format. | Target importer is known | List the required target viewers, engines, DCC tools, and devices. |
USDZ support varies by tool and material network. | Separate geometry fidelity from material fidelity. | Required PBR channels survive | Record required features: PBR maps, animation, cameras, lights, instancing, and custom metadata. |
OBJ has no modern standard PBR model. | Check whether the target needs hierarchy, instancing, animation, or variants. | Hierarchy and transforms match | Use glTF/GLB for broad web and real-time PBR delivery. |
FBX behavior can vary between exporter and importer versions. | Treat USDZ as a packaged USD delivery, not a universal authoring format. | Animation plays at correct timing | Use USD/USDC for scene composition and USD pipelines; use USDZ for Apple Quick Look delivery. |
Diagnose glTF, FBX, OBJ, USD, USDC, and USDZ Compared in this order: inputs, structure, transforms, mapping, shading, export boundary, and target. A minimum test that changes several variables is not falsifiable; reduce it. After repair, replay the critical path because local viewport success does not prove packaging, re-import, or the target viewer remains correct.
Validate the exact glTF, FBX, OBJ, USD, USDC, and USDZ Compared file from the delivery directory while the original source path is unavailable. Record byte size, SHA-256, object and material counts, missing-dependency scan, re-import result, and target-viewer result. Interactive targets also require loading, console, and stable-frame evidence; asset libraries require drag, save, close, and reopen.
Untouched source and clearly named delivery copy
Blender, Easy extension, exporter, and target-viewer versions
Scale, transform, origin, hierarchy, material-slot, normal, and dependency checks
Reopen or re-import evidence executed from the final package
Target screenshots, validator output, file checksums, and known limitations
A delivery root containing only intentional files, without caches, backups, or helpers
These primary sources define the factual boundary for glTF, FBX, OBJ, USD, USDC, and USDZ Compared. Blender operations point to the 5.2 manual, format guarantees point to specifications, and Easy behavior is constrained to repository version and smoke evidence.
Related tools & assets
MODEL / FREEMetalAdd a product description.
MODEL / PAIDChisel PBR Game AssetA PBR process supports chisel assets with 6 LOD grading Good wiring \ high-quality textures
MODEL / FREEKeyboard IQUNIXA Blender 4.2+ model of an IQUNIX mechanical keyboard with gray, white, and green keycaps, delivered as a .blend file for Cycles and Eevee.