A Practical Guide to Delivering 3D Assets
Packaging 3D work for clients, including formats, textures, documentation and licensing.
Imogen Clarke
The key figures
- Formats
- clients may need native and interchange formats
- Textures
- must be included with correct paths
- Scale and orientation
- should match the client's convention
- Rights
- ownership and reuse terms should be written down
Why this is worth getting right
Clients often need assets in formats their own tools can open, and missing textures make deliveries useless.
Do this, not that
Do
- Deliver native and interchange formats
- Package textures with relative paths
- Confirm scale and axis conventions
- Include a short documentation file
- State ownership and reuse terms
Don’t
- Deliveries with missing textures
- Single proprietary formats
- Undocumented scale conventions
- Rights left unstated
When to bring in help
Our advice Bring in help when assets move between studios.
Where this comes from
- Khronos Group — glTF 2.0 Specification
- U.S. Copyright Office — Circular 30 Works Made for Hire
The figures and practices above come from the sources listed.
Working on something like this?
We take on 3D Design & Development work for teams who want it done once, properly. Tell us what you are building and we will tell you honestly whether we are the right studio for it. Start a project.
Where to go next
Spotted something wrong? Report an error on this page. We correct on the page and say what changed.
