Technical docs · Large FiveM clothing packs
Clothing packs & server limits
Technical documentation for installing and running large FiveM clothing packs: YMT budgets, game builds, engine limits, Asset Escrow, and the crashes they cause.
This is not a general FiveM clothing encyclopedia. Every page here answers one question: does this help you avoid a crash, understand a limit, choose a build, optimise a pack, or run several packs at once?
When a clothing pack breaks a server, it is almost always one of these:
YMT collections per gender, capped by your game build.
A shared engine budget already filled by cars and maps (TxdStore).
The game build or platform — Legacy vs Enhanced.
Escrow, entitlement, or a corrupt streamed file.
Who this is for
Installing a pack · Count your YMTs first.
How to read tags
Official Cfx docs, Cfx source, or a merged Cfx pull request.
Specialist clothing docs and reproducible community counts. Cfx publishes no official table.
Changes with game build, FXServer artifact, or client channel.
Do not carry the fix across platforms.
Observed or requested, not verified. Do not build a server around it.
Open Cfx work. Never on a live server.cfg.
Rules
- Gigabytes are not slots. A 200 MB pack can crash a server that runs an 8 GB pack fine.
- Male and female collections are counted separately. Never add them into one number.
- The pack you installed last is often only the one that crossed a budget that was already full.
- A crash hash is a build fingerprint, never a guaranteed single cause.
- There is no
increase_pool_size "YmtLimit". citizenfx/fivem#2938 is still an open request.
Need a ticket? Use the support checklist. Never send license keys or passwords.
