How to Install Scripts on a FiveM Server

What You'll Need

Before you start, make sure you have:

• Access to your FiveM server files — either via SFTP, a web-based file manager (most managed hosting providers include one), or direct disk access if you're self-hosting.
• A database client — HeidiSQL, DBeaver, phpMyAdmin, or the CLI. Only needed if the script ships with a .sql migration.
• A text editor — VS Code, Sublime, Notepad++. You'll edit server.cfg and likely config.lua.
• The script you want to install — grab one from the Scripts marketplace or a custom commission. The rest of this guide assumes you already have the ZIP in hand.

Quick Reference

If you've installed scripts before and just want the happy path:

1. Extract the script into server-data/resources/[script-name]/
2. Import [script-name].sql into your database (if included)
3. Add ensure [script-name] to server.cfg
4. Restart the server and watch the console for errors

If any of those steps aren't familiar, the full walkthrough below explains each one.

2Upload the Script to resources/

Every script you buy from the marketplace ships as a ZIP archive. Extract it locally first — you should see a folder with the script's name containing files like fxmanifest.lua, client.lua, server.lua, a config.lua, and maybe a sql/ or ui/ subfolder.

Upload the entire script folder (not the ZIP, not the files inside it individually) into your server's resources/ directory. For organization, many server owners group scripts by framework:

server-data/
└── resources/
    ├── [qb]/
    │   ├── qb-core/
    │   ├── qb-inventory/
    │   └── qb-policejob/
    ├── [esx]/
    │   ├── es_extended/
    │   └── esx_policejob/
    ├── [standalone]/
    │   └── ox_lib/
    └── advanced-housing-script/    ← your new script goes here

The square-bracket folders (like [qb]) are just visual groupings — FiveM scans subfolders automatically, so nesting works either way. Pick whatever matches your existing layout.

4Configure the Script

Open the script's config.lua (or config.js, or shared/config.lua — location varies) in your text editor. Every well-built marketplace script exposes its behavior through a config file so you don't have to edit the actual logic.

What you'll typically configure:

• Framework toggle — Config.Framework = 'qb' or 'esx'. Pick the one your server runs.
• Locations / coordinates — if the script places NPCs, blips, or interaction points, they're configured as vector3(x, y, z) coordinates.
• Prices, rewards, cooldowns — numeric values tuned to your server's economy.
• Job restrictions — which jobs can use which features (e.g., only police can access the police garage).
• Integrations — dependency toggles for things like ox_inventory, ox_target, or qb-phone.

-- Example: advanced-housing-script/config.lua
Config = {}

Config.Framework = 'qb'         -- 'qb' or 'esx'
Config.UseOxInventory = true    -- set to false if you use qb-inventory
Config.StartingPrice = 50000    -- base house price
Config.KeysPerHouse = 3         -- how many keys each owner gets
Config.AllowShells = true       -- interior shell system

Read the script's README before launching — it usually calls out which config keys matter most and which integrations need extra setup.

6Restart the Server & Test

Restart the server. How you do that depends on your setup:

• Managed hosting — click "Restart" in the dashboard.
• txAdmin — "Restart Server" button in the web panel.
• Self-hosted / VPS — stop the server process and relaunch it with your usual startup command.
• In-game — if you're admin and have live resource reloads enabled, restart advanced-housing-script in the server console works too, provided the script was already loaded once (first install still needs a full server restart to pick up the server.cfg change).

Watch the console output as it boots. You're looking for the script's "started" line — something like Started resource advanced-housing-script — with no red error lines below it. If it errors, jump to the troubleshooting section.

Once the server's up, join it in-game and try the script's main feature — buy a house, start a job, open the menu, whatever the script does. That's your real smoke test.

Next Steps

Once you've got the installation workflow down, a few directions to take your server from here:

• Browse more scripts — the Scripts marketplace has 1,200+ pre-made gigs across jobs, crime, economy, vehicles, housing, and activities.
• Level up the hosting — if you're getting lag under load, check out managed Cloud Hosting, VPS, or dedicated servers built for FiveM.
• Add weapons, vehicles and MLOs — every weapon pack, vehicle, and MLO installs the same way as a script. The folder goes in resources/, the line goes in server.cfg.
• Commission custom work — need something that doesn't exist yet? Hire a developer to build it on spec.
• Stuck on install? Every gig has direct seller chat on its page, and the support center covers the common ones with working fixes.

FAQ