Separate a supporting prop from the hero product
A table, background object or studio scene can help stage a composition. The product being sold may need a different standard: geometry, labels, finish and dimensions must match the approved technical source. Do not use a visually similar stock object as if it were an accurate representation of a specific manufactured product.
Write the role before choosing the asset. A prop that occupies a small background area may need less surface detail than an object filling the frame. A close-up or moving camera can expose geometry and texture limitations that are invisible in a catalogue thumbnail.
Match the native file and the interchange file
A native scene can contain renderer-specific lighting, cameras and materials. An interchange export carries only the information its format and exporter support. Treat these as separate deliverables rather than interchangeable extensions.
For example, XO3D Shop lists BIP, KSP, OBJ, STL and FBX for Keyshot Product Scene #03. That listing does not promise a ready-made GLB or identical browser-rendered appearance. Check the product page, choose a supported export route and rebuild or adjust materials where the destination requires it.
Inspect geometry, scale and materials separately
Check a known physical dimension after import. Inspect pivots and orientation, then review the silhouette from the actual camera. A model that looks right from one angle can reveal open surfaces or unwanted detail when rotated.
Inspect material assignments and texture paths after export. Confirm which maps are base colour, normal, roughness or metallic data. A missing texture is a different problem from a wrong colour interpretation. Changing lighting until the image looks plausible can conceal the underlying error.
- Open the saved export in the intended application.
- Check normals, transparent surfaces and the silhouette.
- Compare a known dimension and the orientation.
- Review material regions at the final camera distance.
Treat the download budget and render budget differently
Compressed download bytes do not describe all the memory required after loading. Texture resolution, decoded formats, geometry and renderer allocations also matter. Use the Labs texture-memory guide to reason about a known RGBA8 example, then inspect the real workload on the destination device.
Optimise a delivery copy, keeping the original available. Reduce detail where it does not affect the intended result, then compare again. Do not approve a smaller file solely because it passes a byte threshold if the product surface or silhouette has visibly changed.
Check the licence and the handoff
Read the current licence linked from the product before choosing it. Establish who will use the asset, the project scope and whether the handoff contains final renders or source files. Resolve any mismatch with the supplier before relying on the asset.
Keep the product link, file version and relevant documentation in the handoff record. A studio brief should distinguish what is supplied, what must be rebuilt and what needs approval. For a bespoke hero product or complete campaign, the main XO3D site explains the modelling and creative-production routes.