How to host a FiveM server: RAM, txAdmin, frameworks and setup

FiveM turns Grand Theft Auto V into a platform for custom multiplayer servers, and it is where most GTA roleplay communities live. A FiveM server is not a single game you switch on: it is a server runtime, a stack of resources, a framework that ties them together and, for almost every roleplay server, a database. Getting it right comes down to how much memory the stack needs, which framework you build on, and how carefully you add resources. This guide covers all three, then explains how we set a server up for you on GGHOST Cloud.

How a FiveM server works

The server software is called FXServer, and it is maintained by Cfx.re. You download it as an “artifact” build, and it runs everything players do not run on their own machines: synchronising players and vehicles, running server-side scripts and talking to the database.

Everything else is a resource: a folder with a manifest (fxmanifest.lua) and scripts in Lua, JavaScript or C#. Maps, cars, jobs, inventories, phones and the framework itself are all resources. The server reads server.cfg at start-up, top to bottom, and starts each resource you list with an ensure line. Because the file runs in order, load order matters: the database connector and framework core need to start before the scripts that depend on them.

Two more pieces are worth knowing:

• The licence key. Every server needs a free key from the Cfx.re Portal, set as sv_licenseKey in server.cfg (or entered in txAdmin). Without it the server will not start.
• txAdmin. A web-based management panel that ships with FXServer. It deploys servers from “recipes”, schedules restarts, shows a live console and handles player actions such as kicks, warnings and bans.

How much RAM does a FiveM server need?

On FiveM, memory is driven mostly by the resource stack and the streamed assets (custom cars, clothing and maps), not by the player count alone. These are the figures we size real servers at:

• Up to 32 players: 8 GB. A light resource stack.
• 32 to 64 players: 16 GB. A full framework and database.
• 64+ players: 24 GB or more. Heavy roleplay stacks.

A server with a hundred custom vehicles and a large mapping pack can need more than a lightly scripted server with twice the players. Watch the memory graph at your busiest hour: if it sits above roughly 80%, size up before it becomes a problem.

You pay for memory on GGHOST Cloud, not player slots. sv_maxclients is a setting you choose in server.cfg, not a line on your invoice.

Larger servers also need OneSync, FiveM’s server-side state system, which you enable with set onesync on in server.cfg or from txAdmin’s settings. Most modern frameworks expect it to be on.

Frameworks and the database

A framework provides the shared building blocks that roleplay scripts rely on: characters, jobs, money, inventories and permissions. The choice matters because most resources are written for one framework and will not work on another without changes.

ESX

One of the oldest and most widely used frameworks, now maintained as ESX Legacy. A huge number of scripts target it, which makes it a safe choice if you plan to buy or download a lot of ready-made resources.

QBCore

A popular framework with its own large script ecosystem, and the base many newer servers start from.

Qbox

A newer fork of QBCore that aims to remain compatible with QBCore resources while modernising the core. Worth a look if you like QBCore’s approach but want a more actively reworked base.

Standalone

You can also run FiveM without a framework, for a racing, drifting or freeroam server where nobody needs a job or a bank account.

ESX, QBCore and Qbox all store their data in MySQL or MariaDB, usually through the oxmysql resource, which reads its connection details from a mysql_connection_string setting in server.cfg. On our Pterodactyl panel you have database access alongside the server, so the framework and its data sit together.

Performance tips that actually help

• Measure before you guess. Type resmon 1 in the client console (F8) to see which resources are using the most CPU time, and use the built-in profiler command for a deeper look. One badly written script often accounts for most of the hitching.
• Watch for tight loops. Scripts that run every frame without a wait, or query the database on every tick, are the most common cause of a slow server.
• Keep streamed assets in check. Every custom car, clothing pack and map adds to what players download and what the server holds. Remove what nobody uses.
• Index your database. Large roleplay servers build up big tables; slow queries show up as delays when players load in, buy items or open inventories.
• Restart on a schedule. A daily restart clears out leaks from long-running scripts. Schedule it in txAdmin or as a scheduled task in our panel, with an in-game warning beforehand.

Adding resources safely

Upload resources into the resources folder through the panel’s file manager or over SFTP, add an ensure line for each one in server.cfg, and restart. Watch the console for errors on start-up. A few habits avoid most problems:

• Check the framework and version. A QBCore script will not run on ESX, and a script written for an old framework version can break on a newer one.
• Mind the order. Dependencies (oxmysql, the framework core, libraries such as ox_lib) must be ensured before the scripts that use them.
• Run the SQL. Many resources ship with an .sql file that creates their tables. Import it into the database before starting the resource.
• Only use trusted sources. Leaked or “free” copies of paid scripts are a common route for backdoors that hand control of your server to someone else.

Backups: the server and the database

A FiveM server has two halves that both need backing up: the files (resources, server.cfg, txAdmin data) and the database that holds every character, vehicle and bank balance. Losing either one hurts.

On GGHOST Cloud, backups run on a schedule you set and restore from the panel without a ticket. Take a manual backup and a database export before any framework update, large resource change or artifact upgrade. If you are moving from another host, bring your resources, server.cfg and a database dump, and we can get you running on the same data.

Getting your FiveM server on GGHOST Cloud

FiveM is set up on request at the moment, rather than ordered through checkout.

1. Ask us on Discord (or open a ticket) with the framework, resources and player count you need. If you are migrating, tell us what you are bringing.
2. We size it and quote a monthly price. We use the sizing above as a starting point and adjust it for your resource stack.
3. We set it up on our Pterodactyl panel, usually within a few days, in the region closest to your players. Singapore and Europe (France–Germany border) are live today; the United States (East, Central and West), the United Kingdom, India, Japan and Australia are available on demand.
4. Add your licence key and connect. Your server address and port are shown in the panel; players join through FiveM’s direct connect or the server list.

From there you have the full panel: live console, file manager, SFTP, scheduled tasks for restarts and announcements, sub-users for your staff, and database access. Every node is behind DDoS protection from our network providers, on every plan, and you can change the server build, artifact version or startup flags from the panel and restart. There is no setup fee and no contract; billing runs through app.gghost.cloud, and support comes from the people who run the servers, on Discord and at hello@gghost.cloud.

The short version

Get a free licence key from the Cfx.re Portal, manage the server through txAdmin, pick a framework based on the scripts you want, and treat the database as part of the server. Start at 8 GB for a light stack and 16 GB for a full roleplay framework, profile with resmon before buying more memory, and back up files and database before every big change.