How to Install FiveM Scripts (Escrow & Source)

Every FiveM script - free or paid, escrow or source - installs the same way: put the resource in your server's resources folder and tell the server to start it. This guide walks through it step by step, then covers the errors people hit most often with escrowed (encrypted) scripts.

What you need

• A FiveM server (FXServer) with access to its files, on recent server artifacts.
• A server licence key from portal.cfx.re, created on the same Cfx.re account that bought the script. Escrowed scripts only run on servers whose key belongs to the account that owns them.
• Your framework (ESX, QBCore, Qbox) already running, unless the script is standalone.

1. Download the script from the Cfx.re Portal

Scripts bought through Tebex are delivered to your Cfx.re account, usually within a few minutes. Log in to the Cfx.re Portal, open Granted Assets and download the script. You get a ZIP file.

2. Add it to your resources folder

Unzip it and move the folder into your server's resources directory. Many servers group resources in bracket folders such as resources/[scripts] - that works too. Keep the folder name as downloaded: it's the resource name you'll use next.

3. Start it from server.cfg

Open server.cfg and add an ensure line with the resource name, after your framework and anything the script depends on:

ensure es_extended   # or qb-core / qbx_core
ensure nobit_map

Order matters: a script that starts before its framework can't find it and fails on boot.

4. Configure it

Most scripts ship a config.lua (escrowed scripts leave config files open). Set it up before the first start - the script's install guide lists every option.

5. Restart and check the console

Restart the server, or run refresh then ensure resource_name in the server console. Watch the console as it starts: a clean start prints no red errors for the resource.

Common errors

“You lack the required entitlement”

The server's licence key belongs to a different Cfx.re account than the one that bought the script. Use a key from the purchasing account, or ask the seller to transfer the asset.

The script works locally but not on the live server

Usually the same cause: your local and live servers use keys from different accounts. Escrowed scripts follow the account, not the machine.

“Couldn't find resource”

The name after ensure doesn't match the folder name, or the folder sits one level too deep (for example resources/nobit_map/nobit_map after unzipping).

Framework errors on start

The script started before its framework. Move its ensure line below the framework's, then restart.

Escrow or source?

Escrow scripts are encrypted by Cfx.re and locked to the buyer's account, with config files open. Source scripts are plain Lua: no key check, and you can edit everything. Both install exactly as above.

Installing a nobit.dev script?

Each of our scripts has its own install guide in the docs, and we reply on Discord in under 24 hours. Browse the FiveM scripts to find yours.