Iron Gate has given Valheim its first hard release date, and the question flooding r/valheim right now isn't what's in the Deep North — it's a practical one: do I have to throw away my five-year-old world to play it? Short answer up top, then the exact mechanics, a decision table, and how to protect your save before September 9.
Quick answer: do you need a new world for the Deep North?
No — you do not need to start a new world, and you do not need a new character. Valheim 1.0 does not wipe saves. Your existing world file, your base, and your character all carry into 1.0. There is one important catch, and it's the whole reason this question keeps coming up:
Key takeaways
- Your character and world are safe. Updates have never wiped saves, and your character is stored separately from any world, so a maxed Viking can walk into a brand-new 1.0 world with zero progress loss.
- The catch is terrain that's already loaded. Any far-north zones you have already visited keep their old, empty placeholder ground. Only unexplored northern zones will generate the new Deep North after the update.
- The safe play before September 9: stay out of the far north, and back up your world file. That's it.
- If you've already built or explored heavily in the north, a fresh world (bring your same character) is the cleaner way to see the full Deep North.
- Guidance below reflects the live 0.221.12 branch and Iron Gate's official 1.0 announcement — no Deep North content itself is confirmed yet.
When is Valheim 1.0, and is it out yet?
Valheim is still in Early Access today. It has been since February 2, 2021 — more than five years. Version 1.0 launches Wednesday, September 9, 2026, and it is the game's final major content update, built around the eighth and last biome: the Deep North.
Straight from Iron Gate's announcement:
"Valheim 1.0 will arrive on 9 September, with new enemies to kill, bases to build and weapons to craft. The release will hit PC, Linux, Mac, Xbox One and Xbox Series X|S as per usual, and now we're also adding PlayStation 5 and Nintendo Switch 2 to the roster. Of course there will be full crossplay between all the platforms." — The Iron Gate team, valheimgame.com
A few things worth pinning down before you plan around it:
- The official post is deliberately short. It confirms a date, a biome, new platforms and crossplay — it is not a changelog. Anyone showing you a detailed "Deep North feature list" is working from previews and leaks, not a shipped patch. Treat it as such.
- The current live build is patch 0.221.12 (released February 19, 2026). You may see hosting blogs call 0.221.13 "the latest patch" — it isn't. 0.221.13 has only ever been posted to the Public Test branch and has not been promoted to the default branch.
- PS5 and Nintendo Switch 2 are brand-new platforms at 1.0 — there has never been a PlayStation or Nintendo version of Valheim before.
Why does the "new world" question even exist?
Because of how Valheim builds its map. A Valheim world is generated procedurally from a seed, but it isn't all created at once. The terrain and biome for any given zone are baked into your world file the first time a player physically loads that zone — and once baked, the game never re-rolls it, even across a version change.
That single rule is the source of every "do I need a new world" thread:
- Unexplored zones are still just a seed. When a new biome update lands, any zone you've never loaded generates fresh using the new-version rules. So the Deep North will appear correctly in northern zones you haven't touched.
- Explored zones are frozen. Any far-north tiles you already sailed through are baked as the current empty placeholder. The 1.0 update can't retroactively rewrite that ground — those zones stay barren.
Today the Deep North is genuinely empty: a blank snowfield placeholder in the far north of every world, waiting for 1.0 to fill it in. Which means there is almost no reason to have explored up there yet — and if you haven't, you're in the best possible position.
The biggest misconception: seeing the map ≠ generating the terrain
This trips up experienced players constantly, so it's worth stating plainly: revealing an area on your map is not the same as generating its terrain.
- Sharing map data at a Cartography table, or having a friend's exploration show up as fog-cleared on your minimap, only updates what you can see on the map. It does not bake terrain.
- Terrain generation happens when a player's game actually loads that zone — i.e., someone sails or walks close enough for the world to stream it in.
- On a shared or dedicated-server world this is collective: if even one player takes a boat up into the far north, that ground bakes for everyone on that world. So "stay out of the north" is a group agreement, not just a personal one.
The practical takeaway: it's the loading, not the map fog, that locks a zone. Keep everyone's boats south of the far-north snow line until 1.0, and your Deep North will generate clean.
Should you keep your world or start fresh? (decision table)
There's no single right answer — it depends on how far north you've been and what kind of run you want. Here's the honest breakdown:
| Your situation | Recommendation |
|---|---|
| Old world, far north never explored | Keep it. Just don't sail into the far-north snow before Sept 9. Your Deep North will generate correctly. |
| Old world, far north already explored / built in | Roll a fresh world and bring your existing character, so you get the real Deep North instead of frozen placeholder ground. |
| You want the definitive "1.0 launch" playthrough | Fresh world. Keep your character, or restart it too for the full early-game experience with new build pieces. |
| Playing on a shared / dedicated server | Decide as a group, keep everyone out of the north, and back up the server world before launch. |
| You're brand-new or returning after a long break | Start fresh now — a normal run to Ashlands takes long enough that you'll arrive at the north around launch anyway. |
One reassuring note for anyone tempted to restart purely out of FOMO: the update's headline is the Deep North itself, not a rework of the early game. Iron Gate has teased new building pieces — a drawbridge was shown off in an April 2026 dev blog — but there's no confirmed overhaul of the pre-Deep-North weapons, armour or enemies. In other words, continuing your current save doesn't mean "missing" a reworked early game.
How to protect your save before September 9
Whatever you decide, back up your files before launch day. A new biome update is the one time terrain-baking bugs and world-load hiccups are most likely, and older worlds carry more accumulated risk. Two minutes of copying now beats losing a 200-hour world.
Your saves live here on PC:
- Windows: `%USERPROFILE%/AppData/LocalLow/IronGate/Valheim`
- Linux: `~/.config/unity3d/IronGate/Valheim`
Inside that folder:
- World files (`worlds_local`) come in pairs: a `.db` (the actual world) and a `.fwl` (its metadata/seed). Back up both for each world.
- Character files (`characters_local`) are the `.fch` files. Because a character is fully independent of any world, backing these up separately means you can drop the same Viking into a new 1.0 world with no loss of skills, recipes or inventory.
The simplest approach: copy the entire `IronGate/Valheim` folder somewhere safe (a second drive or the cloud) before September 9. For a dedicated server, back up the world files in whatever save path your server uses (the world named with your `-world` flag) — and note that Iron Gate has not published whether Deep North requires any server-side migration, so don't assume a clean auto-upgrade.
What we still don't know about 1.0
Because the announcement was a date and a biome, several launch-day details are genuinely unconfirmed. Don't let a hosting blog tell you otherwise:
- The eighth boss, Deep North gear, materials and enemies — none are officially confirmed. Preview coverage and datamines are not Iron Gate statements.
- Console specifics — PS5 and Switch 2 pricing, preorders, Game Pass status, performance targets, and whether the new platforms can join self-hosted dedicated servers are all unannounced.
- Whether dedicated servers need any special handling for the update.
- Whether the price changes at 1.0 — Valheim has held a single price point with no DLC, season pass or paid battle pass since Early Access, but Iron Gate hasn't said either way.
Expect a pre-launch news cadence from Iron Gate through late August and early September. When the real 1.0 patch notes drop, that's the moment the specifics become fact.
Where to go from here
If you're keeping your world, the best use of the next few weeks is finishing the existing progression ladder so you arrive at the north ready to fight — the Deep North sits past Ashlands, at the end of the current seven-boss run. New to the ladder or fuzzy on the order? See our full Valheim boss order guide for how to beat all seven Forsaken and reach the top tier before launch. For more, browse all our Valheim guides.
FAQ
Do I need to start a new world for the Deep North in Valheim 1.0? No. Your existing world carries over and the Deep North will generate in northern zones you haven't explored yet. You'd only want a fresh world if you've already sailed through or built in the far north, since already-loaded terrain stays as the old empty placeholder.
Will my character carry over to Valheim 1.0? Yes. Characters are stored in separate `.fch` files that are fully independent of any world. Your skills, recipes and inventory travel with the character, so you can even take a maxed Viking into a brand-new 1.0 world with no progress loss.
Will the Deep North appear in a world I've already explored? Only in the parts you haven't loaded. Valheim bakes each zone's terrain into the world file the first time a player loads it, and never re-rolls it — so unexplored northern zones generate the new Deep North, while zones you already visited keep the current placeholder ground.
Do I need to stay out of the far north before September 9? If you want the full Deep North on your current world, yes. Loading those zones now bakes them as empty placeholder terrain. On a shared or dedicated server this is collective — if one player sails north, it generates for everyone, so agree as a group to stay south of the snow line.
Does the 1.0 update wipe my base or my progress? No. Updates have never wiped saves, and your base, world and character all persist. Still, back up your `IronGate/Valheim` folder before launch — new-biome updates are exactly when world-load bugs are most likely, especially on older worlds.
Is 0.221.13 the current version of Valheim? No. The live default-branch build is 0.221.12 (February 19, 2026). Patch 0.221.13 exists only on the opt-in Public Test branch and has not been promoted to the default branch. Valheim also remains in Early Access until the 1.0 launch on September 9, 2026.
Facts in this guide were verified against Iron Gate's official announcement on valheimgame.com and the Steam news feed for app 892970. Guidance reflects the live 0.221.12 branch; nothing about the Deep North's actual content is confirmed until the 1.0 patch notes are published.
