FiveM Server Config Generator

Build a complete server.cfg for your FiveM server. Configure resources, permissions, network settings and download the ready-to-use config file.

General Settings
1 128
Network Settings
Resources

Select the resources to include in your server.cfg. They will be added as ensure lines.

Framework
Core / Dependencies
UI / HUD
Gameplay
Voice / Chat
Admin / Anticheat
Permissions / ACE
Generated server.cfg

What this tool is for

A server.cfg contains network settings, resource start order, permissions and licence keys in one file, and the order of the lines matters. This generator produces a complete, working config from your inputs, with the parts in the right sequence and the settings that are easy to get wrong already correct.

How to use it

  1. Step 1:

    Fill in the basics: server name, player count, locale and game type.

  2. Step 2:

    Add your resources. Order matters, frameworks and database wrappers have to start before anything that uses them.

  3. Step 3:

    Set the network options, endpoints and OneSync, and add your licence key from the Cfx portal.

  4. Step 4:

    Download the file, put it next to your server data and start with the FXServer executable.

Frequently asked questions

Where do I get the licence key?

From keymaster.fivem.net with your Cfx account. It is tied to the IP address you register it for. Without a valid key the server starts but stays invisible in the server list.

Why do my resources not start?

Almost always the order or the path. A resource that needs the framework must be listed after it, and ensure only works for folders that actually sit under the resources directory. A missing fxmanifest.lua produces the same silent failure.

What is the difference between start and ensure?

ensure starts the resource and restarts it if it is already running, start does not. In a config ensure is the safer form, because a manual restart during development does not leave you with a stale resource.

How do I protect my config?

Keep the licence key and the database password out of the file you share, put them in a separate config that is not in version control, and pull it in with exec. A leaked key can get your server delisted.