{"id":22057,"date":"2026-06-11T11:34:24","date_gmt":"2026-06-11T11:34:24","guid":{"rendered":"https:\/\/xgamingserver.com\/blog\/fivem-keymaster-license-key-guide\/"},"modified":"2026-06-11T11:34:24","modified_gmt":"2026-06-11T11:34:24","slug":"fivem-keymaster-license-key-guide","status":"publish","type":"post","link":"https:\/\/xgamingserver.com\/blog\/fivem-keymaster-license-key-guide\/","title":{"rendered":"FiveM Server License Key: Getting a Keymaster Key"},"content":{"rendered":"\n

Every FiveM server needs a free license key before it will start. If you have ever launched the server artifacts and watched the console refuse to boot, you have probably seen the error telling you to set the sv_licenseKey<\/code> console variable. That key comes from Cfx.re’s Keymaster, and getting one takes only a couple of minutes once you know where to look. This guide walks through creating a key on Keymaster, choosing the right binding option, and dropping it into your server.cfg<\/code> so your server actually comes online.<\/p>\n\n\n\n

Why FiveM requires a license key<\/h2>\n\n\n\n

The license key is how Cfx.re ties a running FiveM server back to a registered Cfx.re forum account. It lets the platform list your server in the server browser, enforce platform policies, and associate any premium tier (like FiveM Element Club) you may purchase later. It is completely free for a standard server, and a single forum account can register multiple keys for multiple servers. Without a valid key set, the server process refuses to fully start and you will see a message like this in the console:<\/p>\n\n\n\n

This server does not have a license key specified.\nPlease set the sv_licenseKey console variable to a key\nfrom https:\/\/keymaster.fivem.net\/.<\/code><\/pre>\n\n\n\n
Step 1: Register a key on Keymaster<\/h2>\n\n\n\n
Keymaster is Cfx.re’s official server key management portal. Head to keymaster.fivem.net<\/strong> (you may be routed through the Cfx.re Portal at portal.cfx.re, which is the same login). Sign in with your Cfx.re forum account, then look for the option to register a new server key. You will be asked for a label and an “Initial IP address” or binding preference.<\/p>\n\n\n\n
    \n
  1. Log in to Keymaster with your Cfx.re forum account.<\/li>\n
  2. Click the button to register a new server key.<\/li>\n
  3. Choose a binding option (covered in Step 2).<\/li>\n
  4. Submit the form to generate the key, then copy the long alphanumeric string.<\/li>\n<\/ol>\n\n\n\n
    The generated key is the value you will paste into your config. Treat it like a password \u2014 anyone with your key could impersonate your server, so do not post it publicly or commit it to a public repository.<\/p>\n\n\n\n
    Step 2: IP binding vs none<\/h2>\n\n\n\n
    When you create the key, Keymaster lets you decide how strictly it is tied to a machine. The two practical choices are an IP-based binding or no binding at all. Picking the right one now saves you a migration headache later.<\/p>\n\n\n\n
    Binding option<\/th>How it behaves<\/th>Best for<\/th><\/tr><\/thead>
    IP-based<\/td>Key only validates from the IP address you enter; you must update it in Keymaster if the IP changes<\/td>A server on a fixed, static IP that you do not plan to move<\/td><\/tr>
    None (no binding)<\/td>Key validates from any IP; no manual update needed when you switch hosts<\/td>Frequent host changes, dynamic IPs, or testing on a home PC then moving to a host<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    If you choose IP-based and later move your server to a new host or plan, the key will stop validating until you log back into Keymaster, open that key under your servers list, edit the IP field, and save. The change applies immediately, so you do not need to generate a brand-new key just because your IP changed. For most people renting hosting, “none” is the lower-maintenance choice; pick IP-based only if you want the extra lock-down of a static address.<\/p>\n\n\n\n
    Step 3: Add sv_licenseKey to server.cfg<\/h2>\n\n\n\n
    With the key copied, open your server.cfg<\/code> and add the sv_licenseKey<\/code> line. The official example syntax uses set<\/code> with the key in quotes:<\/p>\n\n\n\n
    # server.cfg\nset sv_licenseKey \"your_key_here\"\n\n# core server settings\nendpoint_add_tcp \"0.0.0.0:30120\"\nendpoint_add_udp \"0.0.0.0:30120\"\nsv_hostname \"My FiveM RP Server\"\nsv_maxclients 48\n\n# start your resources\nensure mapmanager\nensure chat\nensure spawnmanager\nensure sessionmanager<\/code><\/pre>\n\n\n\n
    Alternatively, you can pass the key on the command line when launching the server process with +set sv_licenseKey your_key_here<\/code> instead of putting it in the config. Both methods are documented and equivalent; most hosting panels and txAdmin setups put it in server.cfg<\/code> so it travels with the rest of your configuration. If you run a managed panel, you may have a dedicated field for the key \u2014 check our FiveM hosting documentation<\/a> for where it lives in the control panel.<\/p>\n\n\n\n
    Save the file and restart the server. The startup error should be gone, and the server will register with the Cfx.re backend. If you are still wiring up your framework, our QBCore installation guide<\/a> and the FiveM server artifacts explainer<\/a> cover the next pieces after the key is in place.<\/p>\n\n\n\n
    Common license key problems<\/h2>\n\n\n\n