What is the serveradmin.xml file in 7 Days to Die?

The serveradmin.xml file is the configuration file that tells a 7 Days to Die server which accounts have admin rights and what permission level they get. It contains an <admins> block with one or more <user ... /> entries, typically using platform="Steam" and a SteamID64 as userid. In 2026, this remains the standard way to enable admin commands on dedicated servers. At MineStrator, we see most “admin not working” cases fixed by correcting this file and restarting cleanly.

How do I find my SteamID64 for a 7 Days to Die server?

A SteamID64 is your 17-digit Steam identifier and is the format 7 Days to Die uses for admin entries. The fastest method is to open your Steam profile in a browser and copy the number after /profiles/ (example: 76561198021925107). If you have a custom Steam URL, paste your profile link into a lookup tool like steamid.io to display the SteamID64. MineStrator recommends saving the SteamID64 because you’ll reuse it for admin files, whitelists, and some server tools.

How do I add a SteamID64 admin in 7 Days to Die in 2026?

To add an admin in 7 Days to Die, you must stop the server, edit serveradmin.xml, add a <user> line inside <admins>, then restart the server. Use this format: <user platform="Steam" userid="YOUR_17_DIGIT_STEAMID64" name="YourName" permission_level="0" />. The file is commonly located at /.local/share/7DaysToDie/Saves/serveradmin.xml on Linux-based installs, and the folders may appear only after the first server start. At MineStrator, we recommend a full stop/start (not just a reload) because serveradmin.xml changes are often ignored if edited while the server is running.

What permission level should I use for 7 Days to Die admins?

The best permission level for a main 7 Days to Die server owner is usually permission_level="0" because it grants full access to all admin commands. Permission levels work as a minimum threshold: an admin can run commands with a required level greater than or equal to their own level, so lower numbers mean more power (0 is the highest privilege). Common setups are level 0 for super admin, 500 for moderators, and 1000 for limited helpers. MineStrator typically suggests starting with 0 to validate the setup, then increasing the number only if you want to restrict staff permissions.

Why is my 7 Days to Die admin not working after editing serveradmin.xml?

7 Days to Die admin access usually fails because the server was not fully stopped, the XML syntax is invalid, the wrong Steam ID format was used, or the permission level is too restrictive. First, ensure you performed a complete stop before editing and a full restart after saving, because live edits are often ignored. Next, verify the <user ... /> line is inside <admins> and that quotes/tags are correct, since one broken tag can prevent parsing. Finally, confirm you used a 17-digit SteamID64 (not SteamID3/SteamID) and test with permission_level="0" to rule out command restrictions—these are the most common fixes we see on MineStrator-hosted servers.

🔧 7DTD Admin Setup 2026: Add SteamID64 Fast

Want to run your 7 Days to Die server like a boss? Before you can use admin commands, the server needs a way to identify you as staff.

In 2026, the most common setup is still based on your SteamID64, added to the server’s admin file. In this guide, you’ll learn how to find your SteamID64, where to edit serveradmin.xml, how permission levels work, and what to check if it doesn’t work.

Get your SteamID64

Your SteamID64 is your unique Steam identifier (usually 17 digits). The server uses it to grant you admin rights, so you can’t skip this step.

Find it from your Steam profile URL

Log in to Steam in your web browser.
Open your Steam profile page.
Copy your profile URL (example: https://steamcommunity.com/profiles/76561198021925107/).
Copy the number after /profiles/: that’s your SteamID64.

Find it with a SteamID tool

If your profile uses a custom URL, a lookup tool is faster.

Open one of the tools above.
Paste your Steam profile URL or type your Steam username.
Copy the SteamID64 shown by the tool.

💡 Tip: Keep your SteamID64 in a note somewhere. You’ll reuse it for whitelists, admin files, and some server tools.

Edit the serveradmin.xml file

This is where you officially tell the server: “Yep, this SteamID is an admin.”

⚠️ Warning: The server must be completely shut down before editing, or your changes may not apply.

Locate serveradmin.xml

The file is named serveradmin.xml and is located here: /.local/share/7DaysToDie/Saves/serveradmin.xml. You can access it from the Files tab in your panel.

📝 Note: If the folder doesn’t exist yet, start the server once, then stop it. The server will generate the required folders automatically.

Add your admin line

Open serveradmin.xml, then find the section. You’ll usually see example lines (sometimes commented out) that show the expected format.

Add your own line inside the block.

Use this template:

Here’s what each parameter means:

platform="Steam": Steam authentication (use EOS for Epic Games).
userid="YOUR_STEAMID64": Your full SteamID64 (17 digits).
name="YourName": A label to recognize the admin.
permission_level="0": Your admin permission level.

Example with two admins:

🚨 Important: Don’t delete or . One missing tag and the file won’t parse correctly.

Understand permission levels

The permission level decides which admin commands you can use. Lower numbers mean more power, because you’re allowed to run commands with a level equal to or higher than your own.

Level 0: Full access (super admin).
Level 500: Access to commands level 500 and above.
Level 1000: Limited access to basic commands.

Rule of thumb: an admin can use commands with a level greater than or equal to their permission level.

💬 Good to know: If your permission level is too high (like 1000), you may “feel” like admin isn’t working because many commands are restricted.

Restart and test your admin access

Once your line is added, you just need to apply it properly. A simple reload usually isn’t enough for this file, so go for a clean restart.

Save serveradmin.xml.
Completely restart the server.
Join the game using the Steam account linked to that SteamID64.
Test an admin command like /help or /admin.

Fix common problems

If it doesn’t work, it’s almost always one of these classic issues. Check them in order before you rage at the zombies.

Changes don’t apply: The server wasn’t fully stopped while editing. Stop it, edit again, then restart.
XML syntax error: A missing quote, a broken tag, or a line outside can break parsing.
Wrong SteamID: Make sure you used the SteamID64 (17 digits), not SteamID3 or SteamID.
No command access: Your permission_level is too restrictive, or the line has a typo.

Questions frequentes

Do I need to restart the server after editing serveradmin.xml?

Yes. To reliably apply changes, stop the server completely, save the file, then restart it. Editing while the server is running often results in ignored changes.

What Steam ID format does 7 Days to Die require?

You need the SteamID64, which is typically a 17-digit number. You can find it in your Steam profile URL under /profiles/ or via a lookup tool.

Why does permission level 0 give more access than 500?

Because permission levels work like a minimum requirement. With level 0, you can run everything. With level 500, you can only run commands that are level 500 or higher.

Conclusion

Once your SteamID64 is added to serveradmin.xml with the right permission level, you’re officially in charge. Save the file, restart the server, and test a command to confirm everything is working.

Need a reliable host for your next apocalypse? You can run a 7 Days to Die server on MineStrator and keep full control from your panel.