Escrow Limits for Large Packs
Quick answer
An escrowed asset cannot exceed 1 GB. For a clothing pack that is a design constraint, not paperwork: it caps how many models one purchasable resource can contain, regardless of how many YMT slots you have left.
Difficulty: Intermediate · Affects: LEGACY · Cap CONFIRMED
INFO
Search: 1gb, upload limit, too large, split pack, portal upload, escrow size limit.
Last verified 31 August 2026 · Cfx Asset Escrow.
The constraint in practice
A creator on the Cfx forum, arguing for higher YMT limits, described fitting roughly 91 YDD models under the 1 GB ceiling with everything already stripped down as far as it realistically could be. Treat that as one reported data point rather than a formula — the real number depends entirely on mesh complexity and texture budget — but it illustrates the scale. A large pack runs into 1 GB long before it runs into anything else about delivery.
Two ceilings that fight each other
| Ceiling | Pushes you toward |
|---|---|
| 1 GB per escrowed asset | More resources, each smaller |
| YMT slots per gender | Fewer resources, each larger |
This is the central tension in large pack design. Splitting a pack to fit under 1 GB creates additional collections, and additional collections cost slots the customer may not have.
There is no clean resolution. The practical compromises:
- Keep each shipped resource under 1 GB, and design collections so a customer can repack them into fewer if they need to.
- Publish the exact YMT cost of each part — male, female, and whether creature metadata is included — so buyers can budget before purchase.
- Split along lines a customer might legitimately not install, rather than arbitrarily.
What consumes the gigabyte
| Contributor | Notes |
|---|---|
| YDD meshes | Usually the bulk in a model-heavy pack |
| YTD textures | Resolution-driven; 4K normals are expensive |
| Duplicate variations | Near-identical recolours that could share a texture |
| Unused source files | Anything in the resource that is not streamed |
Texture resolution is the fastest lever here, and unlike most optimisation advice, in this specific case it works — the 1 GB cap is a genuine size limit, not a count limit.
Delivery
If a pack must be split, each part is a separate Portal asset and a separate entitlement. Document clearly which parts are required together, because a customer who installs part 2 without part 1 will see missing items rather than an error.