Business
Selling your FiveM scripts through Tebex
How FiveM developers sell scripts: why Tebex is the delivery route for escrowed FiveM Assets, creating a store and verifying identity, uploading assets to the Cfx.re Portal, packages that deliver a FiveM Asset, open-source vs escrowed releases, previews, support and updates.
Overview
Plenty of good scripts never earn anything because the developer does not know how delivery, protection and payment fit together on FiveM. The route most paid resources take is simple once laid out: encrypt the resource on the Cfx.re Portal, sell it as a Tebex package, and support buyers well enough that they come back.
01The steps
- Register on Tebex, verify your email and complete identity verification.
- Create a project, choose your currency, and associate your Cfx.re account.
- Complete the go-live requirements: store description, support contact, wallet, ID verification, at least one package.
- Submit the store for Tebex’s review.
- On portal.cfx.re, create an asset and upload your zipped resource (max 1 GB) — see asset escrow.
- In Tebex, create a package that delivers a “FiveM Asset” and select your uploaded asset.
Escrowed or open source?
| Escrowed | Open source | |
|---|---|---|
| Copy protection | Runs only for entitled accounts | None |
| Buyer can edit | Only escrow_ignore files | Everything |
| Typical buyers | Server owners who want it to just work | Developers who customise |
| Common pricing | Lower price, larger audience | Higher price (“source access”) |
Many sellers offer both: an escrowed version and a pricier open-source licence. Always leave config, locales and bridge files editable.
A listing that sells
- A 30–90 second video showing the script in game — more convincing than any text.
- A features list, the frameworks supported and the dependencies (ox_lib, oxmysql…).
- Performance numbers: resmon idle and active — see resmon.
- A link to documentation — see script documentation.
- How to get support and how updates are delivered.
After launch
- Re-upload on the Portal to ship updates; announce them with a changelog.
- A Discord with a verified-buyer role for support.
- Track the questions you answer repeatedly and turn them into docs.
- Price changes and bundles: script pricing.
Frequently asked questions
How do I sell FiveM scripts?
Escrow the resource on the Cfx.re Portal and sell it as a Tebex package that delivers the FiveM Asset.
Can I sell escrowed scripts outside Tebex?
No. Escrowed assets can only be distributed through a Tebex package.
Does Tebex review my store?
Yes. After identity verification and the go-live steps, you submit the store for review.
How do buyers receive the script?
Tebex emails a download link and the asset appears in their Cfx.re Portal account.
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
- BusinessAsset escrow: protecting and buying FiveM resourcesAsset escrow encrypts Lua, YFT, YDD and YDR files uploaded to the Cfx.re Portal and delivers them through Tebex. An escrowed resource only starts on servers whose owner holds the entitlement; otherwise the console shows “You lack the required entitlement”. Sellers leave config files editable with escrow_ignore. NUI files are not encrypted. Re-uploading replaces the version on the seller’s account, and subscription assets stop working when the subscription ends.
- 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.
- 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.
- BusinessA portfolio that wins FiveM workShow five or six of your best finished pieces with short in-game videos, link clean open-source samples on GitHub, and write brief case studies (problem, solution, result, resmon numbers). State your stack (Lua, ox_lib, frameworks, NUI), services and availability clearly, add testimonials from real clients, and keep contact one click away.