FiveM development is full of jargon that nobody explains to beginners. This glossary defines the terms you'll actually encounter, in plain English, so the rest of the ecosystem makes sense. Bookmark it.
Core concepts
Framework — The foundation layer managing core systems (players, money, jobs, inventory). The main ones are QBCore and ESX. Almost every script depends on one.
Resource — A single "module" on your server — a folder with scripts and a manifest. Your framework, each job, each map is a resource. Your server is a collection of them.
fxmanifest.lua — The manifest file inside every resource that tells the server what's in it and how to load it. Errors here are common; see our fxmanifest guide.
server.cfg — Your server's main config file — what resources load, player slots, OneSync, and more. See our server.cfg guide.
Client-side vs server-side — Client = each player's game. Server = the authoritative host. A crucial distinction; explained fully in our client vs server guide.
Technical terms
OneSync — FiveM's system for syncing game state beyond GTA V's 32-player limit, enabling 64/128+ player servers and better server authority.
Artifacts — The FiveM server "build" — the actual server software version you run. Updating artifacts updates your server; it can also break things.
oxmysql — The bridge between your server and its MySQL/MariaDB database. Nearly every data-storing script uses it. See oxmysql issues.
resmon — The built-in resource monitor (resmon 1) showing each script's performance cost. The key performance tool; see our resmon guide.
profiler — A server-side performance tool for catching hotspots resmon doesn't show (like database-heavy scripts).
Native — A built-in game function FiveM exposes to scripts (for spawning, positioning, etc.).
Export — A way for one resource to expose functions to another, so resources can share functionality.
Event — How client and server (and resources) communicate — one triggers an event, another listens. The backbone of FiveM scripting.
The ox ecosystem
ox_lib — A shared library many modern scripts depend on (UI, callbacks, utilities).
ox_inventory — The popular modern inventory system. See ox vs qb inventory.
ox_target — The modern eye/cursor interaction system. See ox vs qb target.
Together these are "the ox stack."
Commerce & legal terms
Escrow — Cfx.re's system for protecting a script's code while still selling it. Core logic is locked; config stays open. See our escrow guide.
Tebex — The Cfx.re-approved payment platform for selling scripts/server perks, acting as Merchant of Record. See Tebex vs alternatives.
Cfx.re — The team and platform behind FiveM. Your Cfx.re account/keymaster provides your server license key.
Cfx Portal / keymaster — Where you manage server keys and where purchased escrow assets are delivered.
MLO — A custom map interior (buildings you can enter). Often paid; license matters.
Nulled / leaked — Stolen paid scripts distributed illegally. Often backdoored. Never use them.
Server roles
txAdmin — The web panel for deploying and managing your server. See our txAdmin guide.
Streaming — Loading custom assets (vehicles, MLOs, textures) into the game. Too much causes texture loss.
Anti-cheat — Systems protecting your server from cheaters. See protecting your server.
Now you speak FiveM
With these terms, the guides, forums, and script docs will make far more sense. FiveM development has a learning curve, but most of it is just vocabulary — once the words click, the concepts follow.
When you're ready for quality resources built by people who know this ecosystem inside out, browse Viper Development's scripts →.