Your server.cfg Explained: Every Line That Matters

Almost every "why won't my server work" question traces back to server.cfg. It's the file that tells FiveM what to load and how to behave. Understanding it turns guesswork into control.

The essentials

• endpoint_add_tcp / endpoint_add_udp — the port players connect on (default 30120).
• sv_licenseKey — your Cfx.re key; the server won't start without it.
• sv_hostname — the name shown in the server browser.
• sv_maxclients — your player slot count.

Loading resources

ensure resourcename starts a resource. Order matters — frameworks and dependencies must load before the resources that rely on them. A wrong order is a top cause of scripts and vehicles silently failing.

Permissions (ACEs)

ACE permissions control who can run admin commands. Granting yourself the right principal here is how you safely give admins power without opening the door to everyone.

Convars and tuning

Many scripts read settings (convars) from server.cfg — database connection strings, framework options, feature toggles. Keep these organized and commented so future-you isn't lost.

Keep it clean

• Edit with a plain text editor — smart quotes break the file.
• Comment sections so you can find things fast.
• Back it up before big changes, especially before an artifact update.

Master server.cfg and most of FiveM stops feeling like a black box. New to all this? Start from our full server setup guide.