Last verified July 17, 2026. Skyrim's PC console is one of the most useful cheat tools in any long-running RPG, but it is also one of the easiest ways to make a save messy. The console can give gold, toggle god mode, move you through walls, revive NPCs, unlock doors, advance quests, spawn items, or teleport you across the map. It can also skip a trigger the game needed, duplicate an NPC in the wrong place, or leave a quest in a state that looks fine until ten hours later.
This guide keeps the focus on essential player-facing commands, not every debug option in the engine. If you are on PlayStation, Xbox, or Switch, this is not your cheat system. Skyrim console commands are a PC feature, and they are best treated like a repair kit and sandbox tool rather than a normal progression path.
Pixel Twelve's Skyrim game page is the broader hub. This page is the practical reference for the PC commands players look up when a lock is annoying, a quest marker is wrong, or they just want to fly over a mountain without pretending it was honorable.
Before You Type Anything
Make a manual save before using the console. Not a quicksave, not an autosave you hope is recent enough, but a clean manual save you can recognize later. Console commands can be temporary, but some effects write themselves into the save. Gold, items, completed quest stages, dead or resurrected NPCs, changed relationships, altered stats, and skipped triggers may not cleanly undo themselves.
Open the console with the tilde or grave key, usually the key below Escape on an English keyboard. Keyboard layout can change that, so if the console does not open, check your input layout before assuming Skyrim is broken. Type the command, press Enter, and close the console with the same key.
Commands that target something usually require clicking an object, NPC, door, container, or enemy while the console is open. Skyrim shows a reference ID at the top of the console when something is selected. If the wrong thing is selected, the command hits the wrong thing. That is funny once and painful when you accidentally disable an important NPC.
The Commands Most Players Use First
`tgm` toggles god mode. It makes the Dragonborn extremely hard to kill and is the classic testing command, but it also removes the pressure that makes combat meaningful. Use it for unsticking a situation, checking a build idea, or surviving a bug, then turn it off when you want the game back.
`tcl` toggles collision. This is the no-clip command players use when they are trapped in geometry, blocked by a broken doorway, or need to move through a wall. It is useful, but it can also drop you into spaces the game never meant you to visit. Turn it off as soon as you are free.
`coc` teleports you to a named cell. It is powerful, but not beginner-friendly unless you know the exact location ID. Use it carefully and save first. Teleporting into a cell is not the same thing as progressing through the quest path that normally leads there.
`unlock` opens a selected door or container. Click the locked object with the console open, confirm the reference ID, then enter the command. It is cleaner than giving yourself 200 lockpicks, but it can bypass quest locks that were there for a reason.
`kill` and `resurrect` are tempting, especially when a fight gets ugly or an NPC dies badly. Use them with caution. Killing a protected quest NPC, resurrecting someone who died as part of a scripted event, or reviving the wrong reference can create problems that are not obvious right away.
Gold, Items, and Carry Weight
The workhorse item command is `player.additem`. The structure is simple: command, item ID, amount. For gold, the common command is `player.additem f 1000`, which adds 1,000 gold because gold's item code is often shortened to `f`. For lockpicks, players often use `player.additem a 50` to add 50 lockpicks.
The same structure works for weapons, armor, ingredients, soul gems, potions, and crafting materials, but you need the correct item ID. This is where a specialist Elder Scrolls reference becomes useful. Do not guess IDs from memory unless you are willing to reload. A wrong item code may simply fail, but it can also add something you did not intend.
`player.setav carryweight 500` changes your carry weight value. It is cleaner than constantly adding stamina if your only goal is to haul loot, but it still changes balance. A softer option is to use it temporarily, move items to a safe home, then return the value closer to normal.
Avoid using item commands to skip every crafting step on a first playthrough. Skyrim becomes flatter when the economy stops mattering entirely. The console is best when it removes friction you no longer enjoy or repairs a broken moment, not when it erases the whole survival texture of the world.
Skills, Perks, and Leveling Commands
`player.advskill` advances a skill as if you had gained experience in it. `player.setav` sets an actor value directly. Those two commands can look similar to new players, but they feel different in practice. Advancing a skill is closer to pushing progression forward. Setting a value is more like editing a number on the character sheet.
For perks, the common command is `player.addperk` followed by a perk ID. This is more fragile than adding gold because perk trees have dependencies. If you add a high-level perk without the expected path underneath it, the build may not behave the way you imagine. It is usually smarter to use perk commands for repair or late-game testing, not for building a first character from scratch.
`player.modav` adjusts a value up or down instead of replacing it outright. That can be useful for stamina, health, magicka, or carry weight when you want a controlled tweak. Still, permanent stat changes should be treated as save edits. Write down what you changed if you care about undoing it.
Quest Commands Are for Repairs, Not Shortcuts
Skyrim's quest commands are powerful and risky. `showquesttargets` can help identify active quest targets. `getstage` can show a quest stage. `setstage` can move a quest to a specific stage. That last command is the one players reach for when a quest is stuck, and it is also the one most likely to skip hidden triggers.
Before using `setstage`, check the quest ID and stage from a reliable reference, save manually, and try the smallest fix that solves the problem. Do not jump to the end of a quest because one marker is annoying. Skyrim quests often move NPCs, unlock dialogue, place items, and trigger scenes behind the curtain.
If the bug is mild, try normal fixes first: leave the cell, wait, fast travel, reload, talk to the NPC again, or complete nearby objectives. Use the console when the game has genuinely stopped responding to normal play.
Follower, NPC, and World Commands
`moveto player` can bring a selected NPC to you if you know the correct reference. `player.moveto` can send you to a selected NPC or reference. These are useful for missing followers, but they can also drag someone away from a scene they were supposed to finish.
`disable` hides the selected object or actor. `enable` brings it back if the same reference is still selected or remembered. This is useful for stuck clutter or bugged objects, but dangerous around NPCs and quest items. If you disable something important and close the console without knowing its reference, recovery gets much harder.
`resetai` can snap a selected NPC's behavior back into a cleaner state. It can help if someone is frozen, hostile for strange reasons, or refusing to resume normal routines. It is not a magic cure for every quest bug, but it is less destructive than killing and resurrecting characters.
A Safer Essential Command List
`tgm` toggles god mode. `tcl` toggles collision. `unlock` opens a selected lock. `player.additem f 1000` adds gold. `player.additem a 50` adds lockpicks. `player.setav carryweight 500` changes carry weight. `showquesttargets` lists active quest target information. `getstage` checks quest stage. `setstage` moves a quest stage when you know exactly what you are doing. `resetai` can refresh selected NPC behavior.
That list covers most real player needs without pretending the console is harmless. Skyrim has hundreds of commands and thousands of IDs, but the essential approach stays the same: identify the problem, save first, make the smallest change, and keep playing only after you know the fix worked.
When Not to Use the Console
Do not use the console during a first encounter with a major quest unless the game is genuinely broken. Do not use it to skip a lock tied to a story sequence. Do not resurrect a dead character if the death was clearly part of a quest. Do not stack commands when you are frustrated and then save over your only file.
The console is a brilliant PC feature because it lets players rescue themselves from old open-world weirdness. It is also a reminder that Skyrim is held together by triggers, references, scripts, and character states that are not always visible. Respect that machinery and the console becomes a useful tool instead of a save-file gamble.
Item IDs and Why They Matter
Skyrim item commands are only as good as the ID behind them. Some common shorthand IDs are easy to remember, such as gold and lockpicks, but unique weapons, quest objects, spells, ingredients, and Creation Club items need more care. If you are using Anniversary Edition content or modded content, IDs can be even easier to confuse because load order can affect the first digits of some forms.
Use item commands for practical fixes before using them for everything. Replacing a quest reward lost to a bug is different from adding every rare ingredient in the game. The first keeps a save moving. The second can make crafting, looting, and dungeon rewards feel empty. Skyrim is more fun when the console supports the adventure instead of replacing the reason to explore.
A Good Console Workflow
A clean workflow keeps the console from becoming a problem. Save manually, enter one command, close the console, check the result, and only then continue. If the command did the wrong thing, reload immediately. Do not stack five changes and then try to work backward from memory.
For quest repairs, write down the quest ID and stage before changing anything. For NPC commands, make sure the selected reference is the actual character you intend to affect. For teleporting, avoid saving in strange interior cells or test spaces. Those habits sound cautious, but they let you enjoy the power of the console without turning every fix into a new mystery.
One final safety habit: if a command solves a bug, play for a few minutes before saving again. Make sure the NPC talks, the quest advances, the door opens, or the item behaves normally. A fix is only useful if the game keeps behaving after the console closes.
