> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wasabihosting.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Valheim Admin Commands & Access Lists

> Manage admins on your Valheim server hosting instance — adminlist.txt, bans, whitelist, the F5 console, and every useful server command explained.

Valheim keeps server administration deliberately simple: three plain-text lists control who is an admin, who is banned, and (optionally) who may join at all. Admins then run commands through the in-game console. This guide covers all of it.

## The Three Access Lists

These files live in the server's **save directory** — the same location that contains the `worlds_local` folder (or the folder set by `-savedir`; see [server configuration](/games/valheim/server-configuration)). Edit them with the panel **File Manager** or SFTP.

| File                | Purpose                                                                    |
| ------------------- | -------------------------------------------------------------------------- |
| `adminlist.txt`     | Players with admin rights (can use console commands)                       |
| `bannedlist.txt`    | Banned players — cannot join                                               |
| `permittedlist.txt` | Whitelist — **if this file has any entries, only listed players can join** |

Format: **one SteamID64 per line**, nothing else. Lines starting with `//` are comments.

```
// Admins
76561198000000001
76561198000000002
```

<Warning>
  `permittedlist.txt` is all-or-nothing: as soon as it contains a single ID, everyone not on the list is locked out — including you, if you forget to add yourself. Leave it empty for a public (password-protected) server.
</Warning>

<Note>
  You do **not** need to restart the server after editing these lists — they're picked up automatically. However, a newly added admin must **disconnect and rejoin** before their console access works.
</Note>

## Finding a SteamID64

A SteamID64 is a 17-digit number starting with `7656`.

* Paste the player's Steam profile URL into [https://steamid.io](https://steamid.io) and copy the **steamID64** value.
* If the profile URL is the numeric form (`steamcommunity.com/profiles/7656...`), the ID is right in the URL.
* IDs of players currently connecting also appear in the server log in the panel Console.

## Enabling the In-Game Console

The console is disabled by default **on the client** — this is a client launch option, not a server setting.

<Steps>
  <Step title="Add the launch option in Steam">
    In your Steam library, right-click **Valheim → Properties → General**, and add to Launch Options:

    ```
    -console
    ```
  </Step>

  <Step title="Join the server and open the console">
    Connect to your server and press `F5` to open the console.
  </Step>

  <Step title="Verify admin status">
    If your SteamID64 is in `adminlist.txt`, server commands like `kick` and `save` will work. If they're rejected, double-check the list and rejoin.
  </Step>
</Steps>

## Server Commands (F5 Console)

| Command                 | Description                                                       |
| ----------------------- | ----------------------------------------------------------------- |
| `kick [name/ip/userID]` | Kick a player from the server                                     |
| `ban [name/ip/userID]`  | Ban a player (adds them to `bannedlist.txt`)                      |
| `unban [ip/userID]`     | Remove a ban                                                      |
| `banned`                | Show the current ban list                                         |
| `save`                  | Force an immediate world save                                     |
| `lodbias [1-5]`         | Set the server's level-of-detail bias (render distance trade-off) |
| `ping`                  | Show your ping to the server                                      |
| `help`                  | List available commands                                           |

Banning by SteamID64 is the most reliable option — names change, IDs don't.

<Tip>
  No console access at the moment? You can achieve the same result by editing the lists directly: add the offender's SteamID64 to `bannedlist.txt` via the File Manager and they're banned on their next connection attempt — no restart required.
</Tip>

## About devcommands (Cheats)

<Warning>
  Typing `devcommands` in the console unlocks cheat/debug commands (`god`, `fly`, `spawn`, `tod`, and more). These are singleplayer-style developer tools: they only affect the admin who enables them, they're easy to fat-finger, and item spawning can quickly ruin a survival server's economy and trust. Use them sparingly on a live server — if at all — and tell your players when you do.
</Warning>

## Managing the Server Itself

Kicks, bans, and saves run in-game — but starting, stopping, and monitoring the server happens in the [Game Panel](https://panel.wasabihosting.com). If you want co-admins to restart the server or edit the access lists without full account access, give them panel [sub-users](/server/sub-users) permissions. For scheduled restarts and automated saves, use the panel's **Schedules** feature, and keep regular [backups](/server/backups) of your world.

<Card title="Run your own Viking realm" icon="rocket" href="https://wasabihosting.com/game-servers/valheim">
  Valheim server hosting from €7.49/month — full file access, panel console, and 24/7 support included.
</Card>