The One-Time Setup That Lets You Ship Every Asset to Every Buyer Without Rework Your character model is finished. You sold it to a buyer who wants FBX for Unity. Easy. The next buyer wants OBJ for a...
The One-Time Setup That Lets You Ship Every Asset to Every Buyer Without Rework
Your character model is finished. You sold it to a buyer who wants FBX for Unity. Easy. The next buyer wants OBJ for a print pipeline. Easy. The third buyer wants glTF for a WebGL project. You realize your FBX export does not convert cleanly. The fourth wants USD for a multi-app pipeline. You spend a half day fighting conversion bugs and finally lose the sale because the file does not work in their engine.
This is the format-pipeline problem that hits most indie 3D sellers in their first year of selling. The art is finished. The conversion work is endless and chronic. The fix is a one-time pipeline setup that ships every format from a single source, with the right material handling and the right pre-flight checks.
This guide expands on the pipeline approach from the Digital Asset Seller's Playbook. The pillar names the problem. This one walks through the format-by-format pipeline that solves it.
The core principle for asset format work is straightforward: keep your source file in your DCC's native format, and export to each delivery format directly from that source. Do not convert FBX to glTF to OBJ in a chain; each step loses data.
Sellers who get this right keep one source file (Maya .ma, Blender .blend, Houdini .hip, etc.) as the authoritative master, then maintain an export script or manual export checklist that produces the standard delivery formats from that source.
Industry guidance is consistent on this point: each format conversion is a chance for data loss, especially around materials, rigging, and animation. Native exports preserve the maximum quality. Chained conversions degrade it (3D format export strategy).
For 3D asset sales in 2026, five formats cover the overwhelming majority of buyer requirements. Cover all five from your source file and most buyer requests need no follow-up.
FBX
The workhorse for game engines (Unity, Unreal) and motion graphics applications. Supports geometry, materials, UVs, rigging, animation, and lights in a single file. Most buyers expect FBX as the primary delivery format for game-ready assets.
Export settings that matter:
Common buyer complaints when FBX export is wrong: incorrect scale (the model is the size of a building or the size of a fingernail), broken smoothing (faceted shading on smooth surfaces), missing textures (referenced but the buyer received only the FBX).
OBJ
The universal format for static geometry. No animation, no rigging, no embedded materials. Supports UVs and a separate MTL material file. Used by 3D printing pipelines, simple renderers, and engines that prefer minimal-feature input.
Export settings that matter:
OBJ is the easiest format to get right but the most limited in feature support. Treat it as the simplest fallback delivery format.
glTF / GLB
The format for web, mobile AR, and real-time WebGL applications. glTF (.gltf) is the text-based version with separate texture files; GLB (.glb) is the binary version that bundles textures inside the file.
For buyer delivery, GLB is usually the better choice because it ships as a single file with no missing-texture issues.
Export settings that matter:
glTF is the format with the most rapid evolution in 2025-2026 because of WebGL and AR demand. Stay current on the export tool's capability for the format.
USD / USDZ
The format gaining adoption for large-scale VFX, animation, multi-app pipelines, and Apple's AR ecosystem (USDZ is the iOS AR variant). Used by Pixar, major animation studios, and Apple Vision Pro content.
Export settings that matter:
USD's material conversion is the most common conversion friction point. Dedicated converter tools handle most cases; manual cleanup is sometimes needed for custom materials.
Source File (.blend, .ma, .max, .c4d)
Include the native source file when the buyer's license permits. Many buyers want the source so they can modify the asset for their specific use.
If you do not want to share the source (proprietary techniques, licensing concerns), state this clearly in the listing. Buyers who need a source-modifiable asset will move on to a listing that includes it.
The format that handles materials best is FBX or glTF. The format that handles them worst is OBJ (which uses a separate MTL file that is often dropped during transfer).
Best practices:
Format-specific conversion tools that handle the common cases without manual cleanup.
Before any format goes to a buyer, run this checklist.
Running this checklist takes 10 to 15 minutes per format. It catches roughly 80 percent of the issues that produce refund requests later.
The first time you set up the multi-format pipeline takes a few hours. After that, exporting all five formats from a new asset takes 15 to 30 minutes total. The buyer who used to wait two days for a format conversion now gets the file the same day.
The investment is small relative to the time savings across a catalog of dozens or hundreds of assets. The buyers who appreciate fast, complete delivery become repeat buyers. The sellers who do not invest in the pipeline lose those buyers to sellers who did.
Set up the pipeline once. Use it on every asset from then on. The friction of multi-format delivery becomes a non-issue.
Your character model is finished. You sold it to a buyer who wants FBX for Unity. Easy. The next buyer wants OBJ for a print pipeline. Easy. The third buyer wants glTF for a WebGL project. You realize your FBX export does not convert cleanly. The fourth wants USD for a multi-app pipeline. You spend a half day fighting conversion bugs and finally lose the sale because the file does not work in their engine.
This is the format-pipeline problem that hits most indie 3D sellers in their first year of selling. The art is finished. The conversion work is endless and chronic. The fix is a one-time pipeline setup that ships every format from a single source, with the right material handling and the right pre-flight checks.
This guide expands on the pipeline approach from the Digital Asset Seller's Playbook. The pillar names the problem. This one walks through the format-by-format pipeline that solves it.
The Right Mental Model: Export For the Destination
The core principle for asset format work is straightforward: keep your source file in your DCC's native format, and export to each delivery format directly from that source. Do not convert FBX to glTF to OBJ in a chain; each step loses data.
Sellers who get this right keep one source file (Maya .ma, Blender .blend, Houdini .hip, etc.) as the authoritative master, then maintain an export script or manual export checklist that produces the standard delivery formats from that source.
Industry guidance is consistent on this point: each format conversion is a chance for data loss, especially around materials, rigging, and animation. Native exports preserve the maximum quality. Chained conversions degrade it (3D format export strategy).
The Five Formats Most Asset Listings Need
For 3D asset sales in 2026, five formats cover the overwhelming majority of buyer requirements. Cover all five from your source file and most buyer requests need no follow-up.
FBX
The workhorse for game engines (Unity, Unreal) and motion graphics applications. Supports geometry, materials, UVs, rigging, animation, and lights in a single file. Most buyers expect FBX as the primary delivery format for game-ready assets.
Export settings that matter:
•Scale: 1 unit = 1 meter or 1 unit = 1 centimeter depending on the engine convention.
•Smoothing groups: explicit, not implicit.
•Materials: embedded textures or referenced (with textures included as a separate folder).
•Animation: baked to the rig, single take per file or all takes in a single file (note the choice in the description).
•Forward and Up axis: Y-up by default, Z-up for some engines (Unreal).
Common buyer complaints when FBX export is wrong: incorrect scale (the model is the size of a building or the size of a fingernail), broken smoothing (faceted shading on smooth surfaces), missing textures (referenced but the buyer received only the FBX).
OBJ
The universal format for static geometry. No animation, no rigging, no embedded materials. Supports UVs and a separate MTL material file. Used by 3D printing pipelines, simple renderers, and engines that prefer minimal-feature input.
Export settings that matter:
•Triangulated or quad-preserved, depending on the buyer's need.
•Material file (.mtl) accompanies the OBJ for texture references.
•Smoothing groups exported as vertex normals.
OBJ is the easiest format to get right but the most limited in feature support. Treat it as the simplest fallback delivery format.
glTF / GLB
The format for web, mobile AR, and real-time WebGL applications. glTF (.gltf) is the text-based version with separate texture files; GLB (.glb) is the binary version that bundles textures inside the file.
For buyer delivery, GLB is usually the better choice because it ships as a single file with no missing-texture issues.
Export settings that matter:
•PBR materials map to glTF's metallic-roughness workflow. Other shaders (subsurface scattering, advanced reflection) may not translate.
•Animation is supported (skeletal animations work; morph targets sometimes need adjustment).
•Compression: Draco or Meshopt compression reduces file size significantly for web delivery; offer both compressed and uncompressed versions if the buyer's pipeline matters.
glTF is the format with the most rapid evolution in 2025-2026 because of WebGL and AR demand. Stay current on the export tool's capability for the format.
USD / USDZ
The format gaining adoption for large-scale VFX, animation, multi-app pipelines, and Apple's AR ecosystem (USDZ is the iOS AR variant). Used by Pixar, major animation studios, and Apple Vision Pro content.
Export settings that matter:
•Material conversion: PBR materials translate to UsdPreviewSurface, but custom shaders may need manual setup.
•Geometry: supports complex hierarchical scenes natively, which is one of USD's main strengths.
•References: USD supports referenced layers; for asset delivery, flatten into a single file unless the buyer specifically needs layered USD.
USD's material conversion is the most common conversion friction point. Dedicated converter tools handle most cases; manual cleanup is sometimes needed for custom materials.
Source File (.blend, .ma, .max, .c4d)
Include the native source file when the buyer's license permits. Many buyers want the source so they can modify the asset for their specific use.
If you do not want to share the source (proprietary techniques, licensing concerns), state this clearly in the listing. Buyers who need a source-modifiable asset will move on to a listing that includes it.
The Texture and Material Pipeline
The format that handles materials best is FBX or glTF. The format that handles them worst is OBJ (which uses a separate MTL file that is often dropped during transfer).
Best practices:
•Bake all procedural materials to texture maps before export. Procedural shaders do not survive format conversion reliably.
•Pack channels (ARM for Ambient Occlusion / Roughness / Metallic) where the target format supports it (glTF specifically benefits from packed channels for file size).
•Export textures in PNG for transparency support and TGA for game-engine workflows. JPG is acceptable for diffuse-only maps but loses precision on normal maps.
•Use consistent naming: AssetName_Diffuse.png, AssetName_Normal.png, AssetName_ARM.png, AssetName_Emissive.png. The naming convention helps buyers locate the textures even if the material connections break in their engine.
•Provide textures at 2K (2048x2048) as the standard. Offer 4K versions for buyers who request them. Do not ship textures larger than necessary; oversize textures inflate file size and load times.
The Conversion Tools That Work
Format-specific conversion tools that handle the common cases without manual cleanup.
•Blender (free, open source) handles FBX, OBJ, glTF, and USD export from a Blender source. The most accessible all-in-one conversion tool for indie sellers.
•Substance Painter exports texture packs in formats matched to the target engine (Unreal, Unity, glTF). The shader export profiles in Substance handle the texture-side of conversion well.
•Marmoset Toolbag offers texture baking and format conversion suitable for game-asset delivery.
•Reality Composer / Apple's USD tools convert FBX to USDZ for Apple AR delivery.
•Online converters (RapidPipeline, Aspose, etc.) handle bulk conversions but should not replace native exports from your DCC. Use them as a backup or for buyers who need an obscure format.
The Pre-Delivery Checklist
Before any format goes to a buyer, run this checklist.
•Open the exported file in a clean instance of the target software (Unity, Unreal, Blender, etc.) and verify it loads.
•Check the scale matches the documented unit (meters or centimeters).
•Check textures load automatically; if they require manual reassignment, document the reassignment process in a readme.
•Verify any rigging or animation plays correctly in the target engine.
•Check the file size is reasonable; investigate if it is much larger than expected (often a missing compression step).
•Compress the delivery folder (zip) with a clear naming convention: AssetName_Format.zip.
Running this checklist takes 10 to 15 minutes per format. It catches roughly 80 percent of the issues that produce refund requests later.
The One-Time Setup, Forever Payoff
The first time you set up the multi-format pipeline takes a few hours. After that, exporting all five formats from a new asset takes 15 to 30 minutes total. The buyer who used to wait two days for a format conversion now gets the file the same day.
The investment is small relative to the time savings across a catalog of dozens or hundreds of assets. The buyers who appreciate fast, complete delivery become repeat buyers. The sellers who do not invest in the pipeline lose those buyers to sellers who did.
Set up the pipeline once. Use it on every asset from then on. The friction of multi-format delivery becomes a non-issue.