What Is FiveM?
FiveM is a multiplayer modification framework for Grand Theft Auto V. It lets players join community-operated servers with custom game modes, maps, vehicles, interfaces, and scripts. Server owners control the rules and resources, while developers build gameplay using Lua, JavaScript, or C#.
FiveM is part of the Cfx.re platform. It is separate from GTA Online: joining a FiveM server does not place you in Rockstar Games’ official GTA Online service, and each community server manages its own players, permissions, economy, and gameplay.
How a FiveM Server Works
A typical FiveM setup has four layers:
| Layer | Purpose |
|---|---|
| FXServer | Runs the server process and loads configuration |
| Resources | Add scripts, maps, vehicles, interfaces, and other features |
| Clients | Connect players and run client-side game logic |
| Management tools | Configure, monitor, and restart the server, commonly with txAdmin |
The server reads server.cfg, starts the configured resources, and accepts
clients through its network endpoint. Each resource has its own folder and an
fxmanifest.lua manifest that declares scripts, files, dependencies, and
metadata.
FiveM Resources
A resource is a self-contained package of functionality. It can include:
- Lua, JavaScript, or C# scripts
- HTML, CSS, and JavaScript for NUI interfaces
- Maps, models, textures, sounds, and data files
- Configuration shared by client and server scripts
A minimal resource looks like this:
my-resource/
├── fxmanifest.lua
├── client.lua
└── server.luafx_version "cerulean"
game "gta5"
client_script "client.lua"
server_script "server.lua"Place resources inside the server’s resources directory and add
ensure my-resource to server.cfg. Resource names should be unique and avoid
spaces.
Client, Server, and NUI Contexts
FiveM code runs in distinct contexts:
- Server scripts handle authoritative game logic, permissions, persistence, and server-side integrations.
- Client scripts handle player input, local entities, rendering, and native game functions.
- NUI pages run in an embedded browser and provide HTML-based interfaces.
Use FiveM events to communicate between client and server. Treat all client-supplied data as untrusted and validate important actions on the server.
Frameworks vs Standalone Resources
A FiveM framework is a collection of resources and conventions for common roleplay features such as characters, jobs, inventories, money, and database access.
| Option | Best fit |
|---|---|
| Standalone | Custom game modes or small resources without a shared roleplay core |
| QBCore | Roleplay servers using the QBCore ecosystem |
| ESX | Established roleplay servers using ESX resources |
| Qbox | Modern roleplay projects using the Qbox ecosystem |
You do not need a framework to run FiveM. Choose one only when its ecosystem and data model match the server you intend to build.
What You Need
To host a basic server, prepare:
- A supported Windows or Linux system
- Current FXServer artifacts
- A Cfx.re account and FiveM license key
- A server data directory containing
server.cfg - Network access to the configured server endpoint
txAdmin is included with modern FXServer builds and provides a guided setup, recipe deployment, monitoring, and administration interface.
Start Here
- Check the server requirements
- Install a server with txAdmin
- Configure your Cfx.re license key
- Learn the FiveM native API
- Build a FiveM NUI interface
For platform installation and policy details, use the official Cfx.re documentation as the primary source. This site focuses on practical explanations, safe examples, and troubleshooting paths for server owners and developers.