7 Days to Die console commands and cheats

On PC, press F1, type a command and press Enter. That is all it takes to use the 7 Days to Die console. What changes between games is your access: a local single-player world gives you control over the session, while a multiplayer server checks your permissions before running restricted commands.

This guide covers useful commands for everyday play, testing and server administration. Commands and arguments can change between builds, and mods can add their own. Run version to identify your installation, then use help to check what it supports. The examples below are a starting point, not a claim that every command works unchanged in every release.

How to open the console in 7 Days to Die

Press F1 while you are in a game on PC. If that does not work, check your keyboard layout. The official command console wiki also lists the double quote key on US keyboards, @ on European layouts, Ö, Ø or F2 on Scandinavian layouts, and Ñ on Spanish keyboards.

Enter help to list the commands available in your build. To check a particular command, add its name:

help giveself

Some commands and item identifiers are case-sensitive. Many commands also have a short alias: cm, for example, stands for creativemenu. On a modded installation, the live help output is more useful than a static commands list.

Console commands vs admin commands

There is no separate console for admins. The difference is permission: on a multiplayer server, your permission number must be equal to or lower than the level required by a command. Level 0 has the highest access; an unassigned player normally has level 1000.

Use lpi to look up player IDs, then grant access with:

admin add Rosa 0

Replace Rosa with the correct name or player ID. Only give level 0 to someone you trust to manage the whole server. You can run this from the server’s web console, through a configured Telnet connection, or manage permissions in serveradmin.xml.

The commandpermission command, also called cp, controls the level required by individual commands. Use cp list to inspect the current settings and help commandpermission before changing them. For example, cp add <command> <level> assigns a required level; replace the angle-bracket placeholders rather than typing them literally.

7 Days to Die commands list

Start with these common commands. Player IDs such as 171 are examples: replace them with IDs from your own session. For version-sensitive commands, the example deliberately opens the built-in help instead of assuming a particular argument order.

Back up your save before changing the time. Moving the clock can interfere with events and timers stored in the world. Be careful with the whitelist too: adding an entry can prevent anyone not on the list from joining. Confirm that the rest of your group is included before enabling restricted access.

Spawn commands and the item list

Items use internal identifiers rather than their translated in-game names. If your build includes listitems, search for part of a name:

listitems rifle
help giveself

Copy the exact identifier from the results and follow the argument order shown by help giveself. For builds using the order itemName quality count, an example is:

giveself gunRifleT3SniperRifle 6 1

Check that the item exists in your build first. Optional arguments may control whether it enters your inventory or drops nearby, and whether it spawns with mods. Do not assume that give uses the same argument order as giveself: consult help give when sending an item to another player.

For zombies and other entities, run se without arguments to inspect the list where supported, then check help spawnentity. The basic pattern uses a player ID and an entity ID:

spawnentity <playerID> <entityID>

Get the player ID from lpi and the entity ID from the current build. Only add a count if your help output supports it, and test with one entity before spawning a crowd. Commands such as spawnairdrop, spawnsupplycrate and spawnscouts provide other spawning options; check their availability and behavior with help before using them in a shared world.

Creative mode and debug mode commands

creativemenu, or cm, toggles access to the creative menu. debugmenu, or dm, enables debug tools, including access to testing features such as god mode. Enabling debug mode is not the same as automatically turning on every debug feature.

cm
dm

On a multiplayer server, these tools require the appropriate permissions. They are useful for testing builds, recovering from a problem or experimenting in a separate world. For a first survival playthrough, consider keeping cheats off: unlimited resources and debug tools change the consequences of exploration and combat.

7 Days to Die admin commands for server owners

Most day-to-day administration uses a small subset of the command list:

• Players and access: lpi, lp, kick, kickall, ban, whitelist and admin.
• World and session: saveworld, settime, weather, say and shutdown.
• Configuration: getgamepref and setgamepref, for preferences that the running build allows you to inspect or change.

Do not assume that a live configuration change survives a restart. Put persistent settings in serverconfig.xml where appropriate and follow your hosting panel’s configuration workflow. If your build lists getsandboxoptions (gso), use its help text to inspect the sandbox settings it exposes.

Treat reset commands as destructive. Commands such as chunkreset, regionreset or worldchunkreset, where available, can reset terrain and remove player constructions or saved chunk data. resetallstats affects statistics rather than repairing a world. Make a separate backup and confirm the exact scope before running any reset command; a manual save is not a substitute for a backup.

With Olimpo Hosting’s 7 Days to Die server hosting, you can run server-side commands from the control panel’s web console. Commands that depend on a local character or camera, such as giveself, teleport, cm and dm, belong in the player’s in-game console instead. Remote access does not create a local player on the server.

7 Days to Die console commands on PS5 and Xbox

Do not confuse a games console with the PC command console. PS5 and Xbox do not provide the same F1 developer console as PC. Creative and cheat options are accessed through the menus available in the console edition, and their availability depends on the release and world settings.

Server administration is a separate matter. A PC dedicated server can expose its admin tools through a web console or configured Telnet connection, regardless of the device an administrator uses to access that interface. Console players can join compatible crossplay servers only when the current game version, server configuration and platform requirements allow it. Check those requirements before choosing a server for a mixed-platform group.

For platform requirements and setup steps, see our guide to 7 Days to Die crossplay between PC, PS5 and Xbox.

Frequently asked questions

How do I use console commands in 7 Days to Die?

On PC, open the console with F1, type a command and press Enter. Use help to see what your build supports. On multiplayer servers, restricted commands also require the appropriate permission level.

How do I enable cheats in 7 Days to Die?

In a local single-player game, use cm for the creative menu or dm for debug tools. In multiplayer, an administrator must grant the required permissions. Do not give full admin access just to enable one tool if a narrower permission will do.

How do I give myself an item with console commands?

Find its internal identifier with listitems if your build supports it, then follow help giveself. On builds accepting item name, quality and count in that order, giveself gunRifleT3SniperRifle 6 1 is an example; confirm the identifier exists before running it.

Do console commands work on a dedicated server?

Yes. Run server-side commands from its web console or configured Telnet connection, or use the in-game console with sufficient permissions. Commands requiring a local character must be run in-game rather than through the headless server console.

Before changing a live world, run help on that server and make a backup. The command registry changes between releases, and mods can introduce commands no general guide includes.