Business
Asset escrow: protecting and buying FiveM resources
How Cfx.re asset escrow works: what file types are protected (Lua, YFT, YDD, YDR), uploading and updating assets on the Portal, escrow_ignore for config files, the 'You lack the required entitlement' error, NUI not being encrypted, Tebex delivery, subscriptions, and what buyers can and cannot edit.
Overview
Most paid FiveM resources are escrowed: encrypted by Cfx.re and tied to the buyer’s account, so they only run on servers owned by someone who bought them. For sellers that is copy protection; for buyers it explains why some files cannot be opened and what “lack the required entitlement” means.
What escrow protects
| File type | Escrowed? |
|---|---|
| Lua scripts | Yes |
| YFT, YDD, YDR models | Yes |
| NUI (HTML/JS/CSS) | No |
Files listed in escrow_ignore | No — left readable |
01For sellers: publishing
- On portal.cfx.re, choose Create an asset and upload your zipped resource (max 1 GB).
- Wait for processing; the encrypted version appears under Created Assets.
- In Tebex, create a package that delivers a “FiveM Asset” and pick your asset.
- To update, Re-Upload on the Portal — buyers who downloaded older versions keep them.
escrow_ignore {
'config.lua',
'locales/*.lua',
'stream/*.ytd',
}Selling setup and pricing: selling scripts on Tebex and script pricing.
For buyers: installing and errors
| Message / situation | Meaning |
|---|---|
| You lack the required entitlement | The server’s licence key belongs to an account that does not own the asset |
| Resource runs locally but not on the host | The host server uses a different account’s licence key |
| Cannot open a .lua file | It is escrowed; only escrow_ignore files are editable |
| Stopped working after a subscription ended | Subscription assets are removed when it expires |
The key point: the entitlement follows the Cfx.re account that owns the server’s licence key. Keys are explained in the licence key guide.
What escrow means for customisation
- Anything not in
escrow_ignorecannot be edited — ask the seller for config options or open bridge files. - Escrowed models cannot be optimised or retextured by the buyer.
- Obfuscation on top of escrow is unnecessary.
- Escrowed assets cannot be transferred between accounts.
Frequently asked questions
What is FiveM asset escrow?
Cfx.re’s system that encrypts Lua and model files so a resource only runs on servers owned by accounts that bought it.
What does “You lack the required entitlement” mean?
The account that owns the server’s licence key has not purchased that escrowed asset.
Can I edit an escrowed script?
Only files the seller excluded with escrow_ignore, usually configs.
Is NUI protected by escrow?
No. NUI files are not encrypted.
Can I transfer an escrowed resource to another account?
No. Transfers are not supported.
Need this built, not just explained?
Ten years of FiveM work, from Lua to NUI
Custom resources, React NUI, ESX / QBCore / Qbox integration, OneSync performance audits and security reviews — plus the websites and SEO around your server brand.
Related guides
- BusinessSelling your FiveM scripts through TebexCreate a Tebex account, complete identity verification, make a project and link your Cfx.re account. Upload your zipped resource to the Cfx.re Portal to escrow it, then create a Tebex package that delivers that “FiveM Asset”. Buyers get it in their Portal account and it runs on servers they own. Escrowed assets can only be distributed through Tebex. Add a clear description, a video preview, documentation and a support channel before launch.
- BusinessPricing FiveM scripts without guessingStart from the alternatives buyers see (similar scripts, free options), adjust for what makes yours better (performance, frameworks supported, UI quality, docs), and make sure the price covers the support each sale brings. Offer a cheaper escrowed tier and a pricier open-source tier, use bundles for related scripts, run launch discounts with an end date, and revisit prices after real sales data.
- EngineeringUsing Git to manage FiveM resourcesInitialise a repository in your server-data folder (or per script), commit resources and configs, and ignore caches, logs, txData and anything secret. Move the licence key, database password and tokens into a separate secrets.cfg that is exec’d but never committed. Use Git LFS or keep huge streamed assets out of the repo, work on branches, push to a private remote, and deploy with git pull on the server.
- BusinessWriting documentation for FiveM resourcesStructure docs as: what it does, requirements (dependencies with versions), installation (exact steps, SQL, ensure order), configuration (every option with default and example), usage (commands, keybinds, items), developer API (exports and events with parameters), troubleshooting (common errors and fixes), FAQ and a changelog. Keep it in the resource as a README and publish a searchable docs site for bigger products.