/banlist works on multiplayer servers; a regular singleplayer world does not register it. The list it prints is the live contents of banned-players.json and banned-ips.json in the server folder.
Needs operator permission level 3. From the server console, type it without the leading slash.
Each line follows the same pattern: who was banned, who banned them (or Server for console bans), then the reason. An empty list replies with: There are no bans
/banlist prints the server's ban list in chat. On its own it shows every banned player and every banned IP address together; add players or ips to list just one of the two. It needs operator permission level 3 and only exists on multiplayer servers.
A Minecraft server keeps its bans in two files next to server.properties: banned-players.json for accounts banned with /ban and banned-ips.json for addresses banned with /ban-ip. The banlist command reads those files live, so what it prints is always the current state of the ban list, including entries added by hand or by plugins.
The reply starts with a header in the form There are X ban(s): followed by one line per entry: name was banned by source: reason. The source is the operator who issued the ban, or Server when it came from the console. If no reason was given, the line shows the default text Banned by an operator. A field missing from a hand-edited file shows as (Unknown), and an empty list replies There are no bans.
Permissions are the usual moderation tier: operator level 3, the same level as /ban, /kick and /op itself. Since op-permission-level in server.properties defaults to 4, anyone you promote with /op can run it, and the server console always can. Players without permission do not even see the command in tab completion.
The command has exactly three forms, all of them complete commands with no further arguments:
Example commands you can copy straight into chat or the console:
banlist is the read-only half of the server's moderation toolkit. These are the commands that put entries on the list, take them off again, or handle a problem player without a ban:
If you are here to add an entry rather than read the list, the Ban Command Generator builds the matching /ban command with a target and reason.
Run /banlist in chat as an operator, or type banlist in the server console. The plain command lists every banned player and banned IP address together. Use /banlist players or /banlist ips to show only one of the two lists.
/banlist players shows accounts that were banned with the /ban command, stored in banned-players.json. /banlist ips shows addresses that were banned with /ban-ip, stored in banned-ips.json. Running /banlist with no argument prints both lists combined.
The ban system is a server feature, so /banlist is only registered on multiplayer servers; a regular singleplayer world does not recognize it. On a server you also need operator permission level 3 or higher, and Minecraft reports commands you lack permission for as unknown or incomplete.
Operator permission level 3, the level the game reserves for admin commands. Operators created with /op get the level set by op-permission-level in server.properties, which defaults to 4, so a normal op can always run it. The server console can run it regardless of levels.
In two JSON files next to server.properties: banned-players.json for account bans and banned-ips.json for IP bans. /banlist prints whatever those files currently contain. You can edit them by hand while the server is stopped, but on a running server use the commands so changes apply immediately.
Use /pardon with the exact name shown in the list to remove a player ban, or /pardon-ip with the address to remove an IP ban. The entry disappears from /banlist immediately and the player can join again on their next attempt.
Need to add someone to that list? Or browse more Minecraft tools:
