Skyrim Level Up Command: Console Guide & Examples
Introduction
If you play on PC and have ever wanted to skip grind, test builds, or fix a broken progression in Skyrim, the skyrim level up command is a powerful tool. In this guide I explain how console commands like player.advlevel and advskill work, how to add perk points, how to use commands safely, and practical examples you can copy. Whether you want to advance a level, raise a skill, or fully customize your character, these tips will help you use console commands, avoid pitfalls, and keep your save games intact.
Why use the console: when the skyrim level up command helps
Console commands are primarily for PC users and are not available on consoles without mods. They offer a way to:
- Recover from bugs that block leveling or quests
- Test abilities, builds, and perks without grinding
- Create challenge runs or roleplay scenarios quickly
- Fix corrupted skill progress or missing perk points
Common LSI keywords you may encounter in documentation include console commands, advskill, player.setlevel, player.addperk, and perk points. I will use each of these naturally as I walk through examples and best practices.
Getting started: how to open the console and basic safety rules
Open the console on PC by pressing the tilde key (usually `~` or ` key). The console is a simple command line where you type commands. Follow these safety tips:
- Always save: Create a manual save before running any command. Use multiple save slots so you can revert.
- Understand achievements: Using console commands can disable achievements in some versions of Skyrim. If achievements matter, avoid or use separate profiles.
- Test on a copy: If a command manipulates level or skills deeply, try it on a duplicate save to check behavior.
- Note the game edition: Special Edition and Anniversary Edition behave the same for console basics, but mod environments can change interactions.
Core commands related to levelling
Here are the most important console commands for leveling and skill XP:
- player.advlevel – Advances the player by one level and triggers the level-up benefits and menu. This is the most straightforward “level up command” to move up levels step by step.
- player.setlevel <level#> – Sets your character level to the specified number. It may not always grant the same visible level-up flow as player.advlevel, so use it carefully.
- advskill <skillID or name> <points> – Adds skill XP directly, which can cause skill levels to increase naturally and lead to level ups when enough skills increase.
- player.addperk <perkID> – Grants a specific perk. Useful when a player.advlevel or setlevel fails to give the expected perk points.
- player.removeperk <perkID> – Removes a perk if you want to reassign later.
Example: to advance just one level, open the console and type player.advlevel. To add XP to one skill, use advskill destruction 5000 or the numeric skill ID for more precise control.
Detailed examples: practical uses and step-by-step commands
Below are common scenarios with exact commands and tips so you can copy-and-paste into the console. Remember to save first.
1) Simple level up by one
Use this when you just want to gain one level and the level-up menu:
- Open console
- Type: player.advlevel
- Press Enter and close console
This provides the normal level-up flow, adding a perk point and giving you the option to increase Health, Magicka, or Stamina.
2) Set your character to a specific level
If you want to set your level to 50 directly (for testing builds or rebalancing):
- Open console
- Type: player.setlevel 50
Note: this may not trigger the level-up UI or grant perk points for skipped levels. If you need perk points, consider adding them manually with player.additem or player.addperk as needed.
3) Add skill XP to cause natural leveling
To raise a skill so that it levels up and contributes to overall character level:
- Type: advskill smithing 10000 to add 10k experience to Smithing
- Repeat for other skills (e.g., one-handed, archery) to control which skills level first
This method is more natural because it mimics normal gameplay and grants level increases when skill thresholds are reached.
4) Grant a missing perk point
If you gained a level but did not receive a perk point due to bugging, you can manually add a perk:
- Find a perk ID using the help command, or search an online perk list for the ID
- Type: player.addperk <perkID>
Example: player.addperk 000BE12F (use correct perk ID; IDs differ by edition and mods)
5) Bulk level up using scripts or repeated commands
You can run player.advlevel multiple times in a row, but beware of missing perk points or stat allocation concerns. For many levels, consider advancing skills with advskill to allow controlled distribution of Health, Magicka, and Stamina.
Understanding skill IDs and using advskill correctly
LSI terms like skill XP, advskill, and skill leveling are important. advskill accepts either the skill name or the numeric skill ID. If you use names, type them carefully. Common skill names include onehanded, twhanded, archery, block, smithing, etc. You can find skill IDs and exact names in community wikis.
- advskill onehanded 5000 – adds XP to One-Handed
- advskill destruction 2000 – adds XP to Destruction
Tip: If you want to test a perk tree, add skill XP to unlock multiple ranks naturally instead of force-adding perks. This mirrors normal progression and avoids odd stat interactions.
Common pitfalls and troubleshooting
Even simple commands can cause unexpected results. Here are common problems and solutions:
- Missing perk points: Use player.addperk with the perk ID, or use player.additem to add the base item that grants perks isn’t applicable; better to add perk directly.
- Achievements disabled: If achievements are important, avoid running commands in your main save. Use a backup or a separate experimental profile.
- Setlevel oddities: player.setlevel can change your level without giving proper perks or health increases. If that happens, either run player.advlevel enough times or manually add stats/perks.
- Mod conflicts: Mods can change perk IDs and skill behavior. Check mod documentation if something behaves strangely.
Tip: Keep a small log of commands you run on a save. That way if you need to revert, you can reverse the key commands like player.removeperk or player.setlevel to previous values.
Advanced tips: combining commands, automation, and mod considerations
Advanced users often combine commands for precise control over progression. Examples:
- Raise several skills with advskill so the game assigns level increases and stat bonuses organically.
- Use player.addperk after setting level if you want specific perk trees open without relying on random distribution of perk points.
- For repeated testing, use console scripts or batch them in SKSE plugins or mod tools, but be mindful of save compatibility.
Skyrim Special Edition has the same console system but may use different plugin load orders and perk IDs when mods are active. When following community guides, ensure the guide matches your edition (Original, Special, or Anniversary).
Best practices summary
- Always backup your save files before using console commands
- Prefer advskill to mimic natural skill progression; use player.advlevel for one-off level jumps
- Use player.setlevel sparingly and verify perk points afterward
- When adding perks, verify the correct perk ID for your game edition and active mods
- Remember console commands are PC-only and may disable achievements
Frequently Asked Questions
Q1: Is the skyrim level up command only for PC?
A1: Yes. Console commands (including player.advlevel and advskill) are available only on PC versions of Skyrim. Consoles like Xbox and PlayStation do not have a built-in console without mods or save editors.
Q2: Does player.setlevel give me perk points?
A2: Not always. player.setlevel changes your level but may not grant the same perk point allocation or level-up UI that player.advlevel triggers. If you need perk points after using setlevel, add them manually using player.addperk or advance levels with player.advlevel step-by-step.
Q3: How do I find skill or perk IDs for commands like advskill or player.addperk?
A3: Use the help command in the console (help smithing 4) to list related IDs, or consult reliable online wikis and community resources. Be careful: IDs may differ between Original, Special, and modded installations.
Q4: Will using console commands break my game or save?
A4: Console commands are powerful and can cause instability if misused. The best defense is to make a manual backup save before trying anything risky. Avoid complex scripted changes on your main progression save.
Q5: Can I restore achievements after using the console?
A5: In many cases, once certain commands are used achievements may be disabled for that save. The exact behavior depends on your platform and game version. If achievements are important, avoid using commands on a trophy-worthy playthrough or use a separate save slot dedicated to experimentation.
Conclusion
The skyrim level up command and related console tools offer flexible ways to control progress, debug issues, and experiment with builds. Use player.advlevel for simple levelups, advskill to raise skills naturally, and player.addperk to fix missing perks. Always save first, test on a copy, and be mindful of edition differences and mods. With these steps and examples you can safely leverage console commands to improve your Skyrim experience without unnecessary risk.
Happy adventuring in Tamriel — and remember that powerful commands are most valuable when used responsibly.

