3D DELIVERY / 5 MINUTE READ
Fix missing OBJ and MTL textures before delivery
A converter cannot recreate an image that was not included. Find the source texture first; only then relink and export.
Why an OBJ loses its appearance
The mesh is in the OBJ, but material names and image paths may point to separate MTL and texture files. Moving only the OBJ—or changing folders and filename case—can break those references. A gray preview is a clue, not proof that the original texture is unrecoverable.
A safe handoff sequence
- Collect the OBJ, every referenced MTL, and the actual PNG, JPG, or WebP diffuse images into one source package. Keep a backup.
- Open the package in the 3D workbench. Inspect each reference. Resolve missing or ambiguous matches with an existing file; do not guess when two images have the same name.
- Confirm the source units and up axis. OBJ does not reliably tell a receiver whether a number means meters, centimeters, or another unit.
- Preview the result, export a GLB, and read the JSON report. The tool validates the GLB against glTF rules and reopens it; still inspect the model visually in the destination.
Destination review
The independent Khronos glTF Validator checks format rules and can report warnings. Neither it nor a successful browser preview can confirm that every storefront theme, AR viewer, or material will look identical.
Shopify and Android Scene Viewer have their own media requirements. Use the report as a preflight, then compare against current Shopify product-media guidance or Scene Viewer guidance. A checked GLB is not an acceptance guarantee, and a destination may need formats this tool does not produce.
Know the boundary
Handoff Desk relinks files you provide; it does not generate missing textures, repair damaged geometry, reproduce all MTL effects, export USDZ, or certify visual equivalence. If a referenced texture truly is absent, recover it from the source project or request it from the author.
Updated 13 October 2026