Skip to content
Tutorials

glTF and USD workflow guide

Choose glTF, GLB, USD or USDZ for the next handoff in your 3D project. Check textures, scale and animation before you deliver an asset.

aukimi4 min read
On this page

A useful glTF and USD workflow starts with the next person who will open your asset. A browser preview needs an efficient model that loads with its textures. A team assembling a scene needs to keep references and edits organised. Plan the handoff around that job, then test a small representative asset before exporting the whole project.

Choose the format for the next handoff

Khronos describes glTF as a format for efficient delivery and loading of 3D scenes. OpenUSD provides scene description and composition, allowing applications to assemble assets and apply edits across layers. A studio can use both in the same production, publishing a glTF asset from an authoring scene when a viewer needs it. Khronos glTF overview · Introduction to OpenUSD

HandoffStarting pointCheck first
Model for a browser or gameGLB with embedded resourcesViewer extensions and texture support
Asset with separate texture filesglTF and its resource folderRelative paths and complete dependencies
Scene assembled across departmentsUSD layers and referencesComposition, variants and asset resolution
Packaged USD deliveryUSDZThe receiving application’s supported content

Package glTF and GLB resources deliberately

A .gltf document describes the asset in JSON. Buffers and images may be separate files or embedded resources. The .glb container can carry JSON and binary data together. A self-contained GLB is convenient for a single-file handoff, so inspect the exported asset for any remaining external references. Renaming a file changes its name, while packaging requires an exporter or conversion tool. glTF 2.0 specification

Make a delivery folder containing only the files you intend to share. Copy it to another location and reopen the model there. This catches a texture path that accidentally points to your working directory. Record the exporter version and settings beside the asset so a teammate can repeat the export after a revision.

Keep USD composition and USDZ packaging understandable

USD layers, references, payloads and variants organise contributions into a composed stage. Agree on a root layer and a folder structure before several people begin editing. The Alliance for OpenUSD Core Specification defines the composition model and the USDA, USDC, USD and USDZ formats. AOUSD Core Specification overview

A USDZ package uses an uncompressed ZIP layout with specific packaging requirements. It can carry USD content and supporting files. Validate it in the receiving viewer, including its material and animation capabilities. Keep the editable source scene and package a delivery copy when required. OpenUSD USDZ specification

Check geometry, materials and motion after conversion

Choose an asset that exercises your real work, such as a painted prop with a moving hinge. Compare its silhouette, UV seams, normals and material assignments after export. A second model with a skin or morph target is useful if characters are part of the project. Save reference images under the same lighting for each revision.

glTF’s material model includes metallic-roughness PBR channels, and additional properties may use extensions. An authoring shader graph can require baking or approximation. Check roughness, metallic values, normal direction, transparency and emissive surfaces in the target renderer. A change in lighting or tone mapping can also change the appearance. Khronos glTF exporter documentation

Compare animation duration and intermediate poses. glTF animation channels can target node transforms, while skinning and morph targets carry other motion data. USD’s skeletal animation schema carries joint transforms and blend-shape weights. Confirm the particular exporter and importer support the channels you need. Khronos animation tutorial · OpenUSD skeletal animation reference

Use one measurable acceptance checklist

  1. Include a reference object of known size and measure it after import. glTF uses metres. Check USD’s metersPerUnit metadata for the source stage. OpenUSD unit guidance
  2. Check the ground plane and forward direction. glTF is Y-up. USD records its upAxis, which the handoff should interpret consistently. OpenUSD axis guidance
  3. Reopen the asset with its delivery files, play each required animation and inspect a close view of each material.
  4. Run the Khronos glTF Validator on a glTF delivery, resolve errors and review warnings, then test the real destination.

In aukimi, a practical starting point is to bring a prepared GLB into Engine and inspect its size, materials and animation in the scene where it will be used. Sculpt also supports glTF and GLB interchange. For a USD deliverable, prepare and validate that branch in the USD-capable authoring and viewing tools chosen by your team. The Sculpt documentation lists its supported interchange formats.

  • #gltf
  • #glb
  • #openusd
  • #usdz
  • #3d-workflow
  • #game-assets

Enjoyed this article?

ShareHN

Related Articles

Help Build the Future of Creative Software

Support aukimi development and get exclusive early access to the complete creative suite.

Back the Project