USD / Pipeline
Why Your USD Asset Gets Rejected at Marketplace Ingest (The 6 Reasons)
Key takeaways
- The top reject reason is no metadata, not bad art
- A broken variant silently kills the whole file
- The automated ingest rejects before a human sees it

The six, in order of how often they appear
- No metadata — the pipeline cannot catalog a file it cannot read. A USD prim without the expected schema fields fails ingest at step one. This is the most common reject, and it has nothing to do with the art quality.
- Broken variant — one corrupted variant set can reject the entire file, even if the other variants are fine.
- Poly budget exceeded — the asset is over the category ceiling, and the ingest auto-rejects it.
- No LODs — a single-detail asset fails the "usable at distance" check.
- Wrong hierarchy — orphaned or mis-named prims break the drop-in.
- No thumbnail / preview — the buyer cannot even see the asset, so it never gets the click.
The fix
Before you publish, run the file through the pipeline validator and confirm it passes the automated ingest. The six items above are a checklist: metadata, variant integrity, poly budget, LODs, hierarchy, and thumbnail. Pass all six and the human reviewer is the only gate left.
Affiliate disclosure: Some links on this site may be affiliate links. We may earn a commission at no extra cost to you. See our methodology.