Skip to main content
server.cfg is the file FiveM reads on boot. It sets your server name, player slots, what shows in the server browser, which resources start, and your license keys. On Lumix Solutions you edit it from the Files tab (it lives in your server root) or through txAdmin’s built-in cfg editor. Every line is either a command (sv_hostname), a convar (set, sets, setr), or a resource directive (ensure, start). Lines starting with # are comments and are ignored.

​
Server name (sv_hostname)

This is the name that shows in the FiveM server browser. It supports color codes (^ followed by a digit) and emojis.
A color code applies to every character after it until the next code. The full set: sv_projectName and sv_projectDesc are separate - they’re what txAdmin shows on its dashboard, not the public list:
The icon is the small image shown next to your server in the FiveM browser. Drop the file in your server root and load it with load_server_icon:
The icon must be a 96x96 pixel PNG. Any other size or format is silently ignored and FiveM falls back to the default Cfx icon. Resize it before uploading - the game does not scale it for you.
Upload the PNG to your server root through the Files tab (same folder as server.cfg), then reference it by filename. If it’s in a subfolder, include the path: load_server_icon images/myLogo.png. Restart for the change to take effect.

​
Connection banners

Banners are the larger images players see while connecting and on your server’s info card. Unlike the icon, these are loaded from a URL, not a local file:
Host the images somewhere public (a CDN, imgur direct link, or your website). banner_connecting shows on the loading screen; banner_detail shows on the server’s detail panel in the browser.

​
Tags, locale, and discovery

sets tags controls the searchable tags in the browser. sets locale sets your server’s region/language flag:

​
Player slots and OneSync

sv_maxClients caps concurrent players (max 2048 with OneSync). OneSync is required for anything above 32 slots and for most modern frameworks:
Slot count is also bound to your plan’s resources. Setting sv_maxClients 128 won’t help if your CPU/RAM can’t carry the load - check your plan or open a ticket before raising it.

​
License keys and endpoints

Your server needs a Cfx license key to boot. Generate one at keymaster.fivem.net and paste it in:
The endpoint lines tell FiveM which port to listen on. On Lumix Solutions these are pre-filled to match your allocation from the Network tab - don’t change them unless support tells you to:
Never share or commit your sv_licenseKey or steam_webApiKey. If a key leaks, revoke it in keymaster and generate a new one. See Database Setup → Best practices for keeping secrets out of public repos.

​
Starting resources

ensure starts a resource and is the modern default (it also handles restarts cleanly). Order matters - frameworks and dependencies must start before the scripts that rely on them:

​
A minimal working example

​
Applying changes

server.cfg is only read on boot. After any edit, restart from the Console for it to take effect. If the server won’t come back up, walk through Startup Issues - a malformed cfg line is the most common cause.