Valheim console commands: a complete practical guide

Valheim console commands

Valheim ships without a traditional cheat menu, but the developers left a developer console that exposes spawning, traversal, and quality-of-life toggles. When you launch Valheim with a specific Steam launch option, the game accepts a command line that lets you call up that console at runtime, enable cheats, and start running console commands. Once unlocked, the console becomes a useful production-style tool: it lets a solo builder recover lost gear, a tester reset a stress scenario, and a creator capture clean screenshots without the in-game HUD getting in the way.

This guide focuses on the practical questions that come up when players first try to use Valheim console commands. It explains how to enable the console on Steam and on Xbox, how to turn cheats on and off, how to spawn items and creatures, how to enter the closest thing the game has to creative mode, and how to hide the HUD for screenshots. Each section treats the console as a tool that has a defined scope, some real limitations, and a few common pitfalls you should know about before relying on it in a long-running world.

How to enable the developer console in Valheim

The console is not exposed by default. You have to opt in through the launcher before the game starts, and then authenticate inside the session.

On Steam, the verified path is to add a launch option that requests the console, then press a key in-game to open it:

• Open your Steam library and right-click on Valheim.
• Choose Properties, then go to the General tab.
• In the Launch Options field, type -console without the quotes.
• Close the Properties window and launch the game as usual.
• In-game, press F5 to bring up the console command box.

Once the console is open, you still need to authenticate before the cheat commands are accepted. Type devcommands and press Enter. Until you do this, most spawning and traversal commands will either error out or do nothing. Re-entering devcommands later toggles cheats off again, which is useful if you want a single console session where you can switch between vanilla and modified play.

A useful habit is to verify that the console round-trips correctly. Type help and confirm that the game lists several pages of commands, because the build’s full command set is paginated. If help returns nothing, the console is not actually attached to the session and the rest of this guide will not work for you.

Using console commands on Xbox

Valheim on Xbox does not have a keyboard bound to the system, but the developers still expose a way to open the console. The verified sequence is unusual and easy to get wrong on a controller.

1. While in a Valheim session on Xbox, hold RB + LB + RT + LT at the same time.
2. While those four triggers and bumpers are still held, press the Xbox Menu button (the icon with three horizontal lines).
3. Release everything. The console command box should appear.
4. Press A to bring up the on-screen Xbox keyboard.
5. Type devcommands and press Enter to enable cheats.

To close the console on Xbox, repeat the same RB + LB + RT + LT + Menu combo. The toggle is symmetric: re-entering devcommands later turns the cheats off again, just as it does on PC. Players who only own a controller should expect typing long spawn identifiers to be slow, so plan your inputs ahead of time rather than searching for the right name at the keyboard.

Scope and limits: singleplayer, multiplayer, and dedicated servers

Valheim console commands are not a universal admin tool. The verified scope is narrow, and understanding it prevents wasted effort.

The cleanest mental model is that the developer console is a singleplayer development aid. If you want persistent, server-wide control over spawning, time of day, or player inventories, the supported path is to run a dedicated server and use the server-side configuration rather than the F5 console.

Spawning items, creatures, and objects

Spawning is the most common reason players open the console in the first place. The verified pattern is consistent: enable cheats, type a spawn command, and add suffixes to control how many and how the item is created.

The base command is spawn <item> <amount>, where <item> is the in-game identifier of the object and <amount> is the quantity. Two modifiers are worth memorizing:

• Add an asterisk * after the item name to spawn every object whose identifier contains that word. This includes furniture and non-equippable objects, so it is a useful “give me everything that looks like a chair” search.
• Append p, e, or i to the end of the command to control how the item is generated. p refers to player-suitable state, e refers to enemy-suitable state, and i refers to an item form. The exact behavior depends on the target, so test in a safe area before committing to a full stack.

There are hundreds of spawnable items, and the in-game console does not provide an autocomplete. Two community-maintained references are widely used: a Valheim cheats and codes list for the command set itself, and a third-party tool called Valheim.tools for browsing item identifiers. The IGN page is the better reference if you want to stay close to the verified command names, and the third-party tool is faster when you are trying to find the exact internal name of a specific object.

For a clean test cycle, follow this sequence in singleplayer:

1. Open the console with F5.
2. Type devcommands and press Enter.
3. Type spawn Wood 50 and press Enter to confirm a familiar object works.
4. Type help 1 through help 5 to page through the available commands.
5. Close the console with F5 when you want to play normally.

For additional context, If a spawn command fails silently, the most common causes are a missing or mistyped identifier, or a suffix that is not valid for that object. The console will sometimes echo an error, but in other builds it will simply do nothing, so the safest diagnostic is to retry with a known-good item like Wood or Stone.

Debug mode: Valheim’s closest analog to creative mode

Valheim does not have a built-in creative mode toggle, but it does have a debugmode command that unlocks a creative-style sandbox while it is active. The verified behavior is that the game exposes several binding-driven powers once the flag is set, which makes the mode useful for builders, screenshot artists, and developers who want to inspect the world without survival pressure.

Key bindings inside debug mode are not always consistent across Valheim patches, so the safer habit is to look at the on-screen prompt after enabling debugmode rather than memorizing a key from an older guide. If a binding is no longer present, the underlying flag is still set, which means the rest of the cheats remain available.

Debug mode is also a useful QA tool. It is a quick way to inspect a base, validate pathing, or confirm whether a build placement is blocked by terrain. For a serious playthrough, however, treat it as a separate save. World state in debug mode can desynchronize from what you would experience in normal survival, and items created with the spawn command are still subject to the regular placement rules of the world.

Useful everyday console commands

Beyond spawning and debug mode, a smaller set of commands gets used most often. The list below groups them by intent, with the practical decision each one supports.

• help and help 1 through help 5: list the paginated command set, useful as a first check that the console is wired up.
• devcommands: toggle cheats on and off, and confirm that the current session accepts spawn commands.
• debugmode: enter the closest thing the game has to creative mode, with the binding-driven powers described in the table above.
• spawn <item> <amount>: create items, creatures, or objects; modifiers *, p, e, and i adjust the result.
• HUD hide/show for screenshots: Ctrl + F3 in the verified keybinding hides the in-game interface. This works without enabling cheats, which makes it safe to use in normal play if you just want clean screenshots.

These are the commands that come up in most practical situations. If you only memorize five, make it help, devcommands, debugmode, spawn, and the Ctrl + F3 HUD toggle.

Hiding the HUD for clean screenshots

Valheim’s interface is dense. Health, stamina, food timers, the equipped hotbar, the minimap, and the build-hammer overlay all compete for attention, and any of them can ruin a screenshot. The console pipeline for clean shots is short:

1. Position the camera where you want it. Move slowly so the scene settles.
2. Press Ctrl + F3 to hide the UI.
3. Take the screenshot using your platform’s normal capture method (Steam overlay, Xbox capture, or the operating system).
4. Press Ctrl + F3 again to bring the UI back so you can keep playing.

Because the HUD toggle does not require devcommands, it is one of the few console-style actions that is safe to bind into a normal survival session. Combined with debug mode’s free-fly camera, it is the standard toolkit for builders, lore photographers, and anyone capturing reference for a community post.

Common failure modes and how to debug them

When console commands misbehave, the symptoms usually fall into a small set of buckets. The table below maps each common symptom to its likely cause and a reasonable first check.

Most console headaches come from one of those five causes. A quick check of launch options and devcommands state resolves the majority of them.

When to use the console, and when not to

The console is a good fit for a defined set of workflows. It is a poor fit for several others, and using it for the wrong job tends to make a session feel hollow.

Use the console when you want to recover lost gear in a singleplayer world, prototype a base layout, capture clean screenshots, or inspect a build for QA purposes. The spawn command is the right tool for replacing a stack of iron you dropped into the ocean, and debug mode is the right tool for testing a defended perimeter.

Avoid leaning on the console when the goal is long-term progression in a survival world. Spawned items do not bypass the regular rules of placement, hunger, or boss unlocks, and the more you spawn, the more the world drifts away from the game the developers actually shipped. A useful rule of thumb is to keep one or two separate save files: a survival world for the long playthrough, and a creative-style sandbox for testing and screenshots. Switching between them keeps each one feeling intentional.

Verifying your setup before a long session

Before relying on the console in a long singleplayer world, run a short verification pass. It takes only a few minutes and prevents most mid-session surprises.

• Confirm the launch option: -console in Steam, no launch option needed on Xbox.
• Confirm the binding: F5 on PC, RB + LB + RT + LT + Menu on Xbox.
• Confirm cheats: type devcommands, run spawn Wood 10, then run devcommands again to verify the toggle off.
• Confirm commands: type help and page through with help 1 through help 5.
• Confirm the HUD toggle: Ctrl + F3 should hide and restore the UI without enabling cheats.

If every step passes, the console is wired up correctly and the rest of the guide applies as written. If a step fails, the earlier troubleshooting table gives the most common cause and the cheapest fix.

Frequently asked questions

Do Valheim console commands work in multiplayer?

No. The verified behavior is that cheats only work in singleplayer. If you join another player’s hosted world, the F5 console is not the path for admin actions, and you should not expect spawn or debugmode to function. Co-op and dedicated servers use server-side configuration instead.

Will using console commands disable achievements on my save?

Valheim tracks progression state, and using the developer console changes the conditions under which you earn it. Treat any world where you have run devcommands or debugmode as a separate creative-style save, and keep at least one clean survival save for the progression you want to be measured against.

Can I open the console on a Steam Deck?

Yes. The Steam launch option path is the same, and F5 is bindable through Steam Input, so on a Deck you add -console to the launch options and map F5 to a button you actually press. The behavior of the console once it is open is identical to a desktop session.

How do I turn cheats off again?

Open the console and type devcommands a second time. The flag is a toggle, and the same command that enables cheats also disables them. This is the right move if you want a single session where you occasionally need a spawned item but want to return to normal play afterward.

What is the difference between debug mode and creative mode?

Valheim does not ship with a creative mode toggle. Debug mode is the closest analog: it unlocks free-fly traversal, unlimited item handling, and several other binding-driven powers, but it is still a development aid rather than a polished creative sandbox. For a true creative workflow, expect to combine debug mode with spawn calls and the HUD hide toggle.

Why does my spawn command silently do nothing?

The most common cause is a wrong identifier or an invalid suffix. Confirm the console is open and that devcommands is on, then try a known-good item like Wood or Stone. If those work, refine the identifier using a reference list such as the Valheim cheats and codes list rather than guessing internal names.

Is there a way to hide the HUD without enabling cheats?

Yes. Ctrl + F3 is bound to the UI hide toggle in the verified keymap, and it works without running devcommands. This makes it safe to use in normal survival sessions whenever you want a clean screenshot, and it is the only console-adjacent toggle that is worth committing to muscle memory on its own.

Where can I find a complete list of item identifiers?

The in-game console lists commands when you type help, but it does not list every spawnable item. For specific item identifiers, the IGN cheats and codes reference and the third-party Valheim.tools index are the two widely used starting points. Use the IGN page when you want to stay close to the verified command names, and the third-party tool when you are searching by visual reference.