Valheim Deep North: What Happens to Your Existing World

Valheim 1.0 arrives September 9, 2026, and the Deep North biome comes with it. Your existing world might get that new biome and it might not — it comes down to whether you've already sailed up north. The parts of the far north you haven't set foot in yet will generate the real Deep North once you get there. The parts you already explored are locked in as whatever they were when you first loaded them.

That's the short version. The rest of this covers how Valheim decides which zones get the new content, the 500-metre catch that trips up worlds people swear they never touched, what you want to back up before the update reaches your server, who can actually join once PS5 and Switch 2 players show up, and whether any of it means you need more RAM.

Valheim Deep North release date: September 9, 2026

September 9, 2026. Iron Gate and Coffee Stain announced the date at the PC Gaming Show on June 7, ending more than five and a half years of Early Access. It lands simultaneously on PC (Steam, Microsoft Store, Humble), Linux, Mac, Xbox One, Xbox Series X|S, PlayStation 5 and Nintendo Switch 2, with full crossplay across all of them.

Two things to know. There's no public test branch for 1.0 — everyone gets it at once, so there's no beta build to try your world on first. And the price has already moved: Valheim now sells for $29.99, up from the $19.99 it held since 2021, with some regional variation. If you already own it, nothing changes — your copy updates to 1.0 at no extra cost.

Will the Deep North generate in my existing world?

Yes — but only in the parts of the map you haven't explored yet.

How Valheim world generation works

Valheim generates lazily, zone by zone (64m × 64m per zone), the first time a player loads an area. Once generated, a zone is committed to the world database — biome, terrain, locations — and the game never re-evaluates it. That's deliberate: it stops an update dropping new terrain on the base you spent 200 hours on.

So at 1.0 the real Deep North fills the placeholder tiles at the top of your map — but only the ones nobody has been to.

The 500-metre catch

Here's the part most coverage skips, and it comes from Iron Gate rather than from us. It's easy to miss because it isn't in the 1.0 FAQ — it's in the long-standing Valheim FAQ, which has spelled this out since long before Deep North. Their rule: updates that add content fixed in the world — terrain, buildings, dungeons — only apply to previously unexplored areas, and an area stops counting as unexplored once a player has been within roughly 500 metres of it. The studio gave the same number in a fireside chat years back. Mod tooling that regenerates worlds puts the practical figure nearer 350m in normal play. Either way, it reaches well past the fog-of-war you watch clear on the minimap.

So if you sailed along the Deep North's southern border and turned back without landing, some of those zones may already be committed with placeholder generation. Your map won't tell you. It's the most common reason people who think they're fine aren't.

Your situation, in three answers

Never sailed to the far north. You're fine — head up after September 9 and the full biome generates as you go.

Already explored the old placeholder Deep North. Those zones are locked. Either start a fresh world, which is what Iron Gate recommends, or use UpgradeWorld by JereKuusela — its upgrade deepnorth operation regenerates Deep North biomes and nearby water, with terrain handled by the base game. It queues the operation and waits for a start command, and needs installing on both the admin client and the server. Verify it's been updated for 1.0 first; nobody can confirm that until launch.

Somewhere in between. Given the 500m buffer, there's no way to eyeball whether your border is clean — you'd find out on launch day, sailing north into mountain terrain. Start fresh.

Iron Gate creative director Robin Eyre made the same point in PCGamesN's Deep North preview: because 1.0 changes things across the whole world, the studio "can't 100% guarantee" an existing world picks all of them up — but if you've finished Ashlands and just want the Deep North, go ahead.

Will achievements work on my existing world?

1.0 adds achievements, and they only start tracking from the moment you install it. Everything you killed before then doesn't count toward them.

Here's the part that catches server admins out. Valheim has a built-in cheat console you switch on by typing devcommands into the F5 console — it's what people use to spawn items, fly around, or skip a boss they've already beaten twice. The problem is that most of those commands permanently mark the character and the world save as cheated, and that mark locks out achievements for good. Turning the console back off doesn't clear it. Some world modifiers have the same effect.

So if your group cares about the achievement list, decide before launch who's allowed to use the console and what for. And check whether it's already happened — on a world that's been running a while, one afternoon of somebody spawning in iron means that world's achievements are already gone, and a fresh world is the only way to get them back.

Back up your world before you update

This is the one thing to do before September 9, and it takes two minutes.

Why it matters

World database corruption on a major-version update is rare but unrecoverable without a backup, and 1.0 is the biggest version jump in the game's history. With no public test branch, you don't get to find out on a throwaway copy first.

What to back up

Two files, always together: the world's .db and its .fwl. The .db holds world data — terrain, structures, biome assignments; the .fwl holds metadata. A .db without its matching .fwl is not a restorable world. Treat them as a pair and keep the filenames intact.

When to back up

Before the update, not after. Most dedicated servers pull the new build automatically on their next restart, and once your server comes up on 1.0 and a player loads a zone, that zone is committed — you can't un-commit it. Snapshot while the server is still on the current build.

How to do it on EVLBOX

Open your server in the Nitro Panel, stop it, and create a manual backup from the Backups tab — name it something you'll recognise, like Pre-1.00 Backup. Our creating backups guide walks through the exact steps if you haven't done it before.

Plan around your slot count — that's how many snapshots you can hold at once, and it's lower than people expect, so check it in the panel before you start. If a scheduled backup is already occupying a slot, put the manual snapshot in a free one and pull the .db and .fwl down to your own machine as well. For a version jump this size, a copy you control is worth having.

Crossplay, PS5 and Switch 2 — who can join your server?

Valheim 1.0 supports crossplay across every platform it ships on. One world, any mix of platforms, no separate lobbies.

Can PS5 players join a Valheim dedicated server?

Almost certainly yes — here's the exact state of the evidence, since this decides whether a dedicated server is worth it for your group.

Iron Gate has confirmed full crossplay between all platforms at 1.0, and a server launched with the -crossplay flag already routes through PlayFab instead of Steam networking, with console clients joining by numeric join code rather than IP — on EVLBOX that's a toggle in your server settings rather than something you edit by hand.

What is certain: consoles can't host a dedicated server. Without one you're on peer-to-peer from someone's machine, which drops when they log off and pins everyone's performance to their connection.

Crossplay routes through PlayFab, which adds a hop. If your group is spread out, pick the location closest to most of your players — it matters more for parries and boss telegraphs than people expect.

Is Valheim on Nintendo Switch 2?

Yes. Valheim launches on Switch 2 on September 9 as part of the 1.0 release, Deep North included. Iron Gate hasn't published anything about how the Switch 2 build differs technically, if at all — so we're not going to characterise its performance until people are playing it.

Three things to know. It's Switch 2 only: the original Switch hardware isn't supported and hasn't been announced. There's no cross-save — Iron Gate has confirmed save progression works only between Xbox and PC via the Microsoft Store, so Steam, PS5 and Switch 2 saves stay on their own platform, and a Switch 2 player joining your world starts a new Viking. And a Switch 2 can't host a server, so if your group is Switch-and-PC, a dedicated server is what keeps the world up between sessions.

The crossplay/mods tradeoff

Crossplay and BepInEx mods can't run at the same time. With -crossplay set, the game uses PlayFab networking instead of Steam's, BepInEx doesn't load, and no plugins run. This isn't a compatibility bug that gets patched — it's architectural. Iron Gate has also confirmed there's no official mod support at 1.0, none on consoles, and no Steam Workshop. So:

• Console friends in your world? Crossplay on, vanilla or server-side modifiers only.
• A heavily modded world? Crossplay off, everyone on Steam.
• Both? Not available. Decide before you invite people — switching later means rebuilding your setup.

You can still tune a crossplay world hard through world modifiers — combat difficulty, death penalty, resource rates, raids, portal behaviour — with no client mods at all.

One launch-day trap worth warning your group about: everyone needs the same build to connect, and platform updates don't always clear certification together. Expect a window where PC players are on 1.0 and console players are still waiting on a store rollout. Nothing to troubleshoot — just don't let anyone open a ticket over it.

Will the Deep North need a bigger server?

Iron Gate's dedicated-server guidance hasn't changed: quad-core minimum / hexa-core recommended, 2.8GHz minimum / 3.4GHz+ recommended, 2GB RAM minimum / 4GB+ recommended, 2GB storage minimum / 4GB+ recommended. The player cap stays 1–10 at 1.0.

Whether 1.0 raises those numbers hasn't been announced. Iron Gate hasn't published updated hosting guidance, and we'd rather say so than invent a figure. We'll update this section on launch day with numbers from servers running the build.

How much RAM does a Valheim server need?

Two gigabytes will run a server. Four or more is what you actually want once a group is exploring in different directions, and that's before Deep North adds a biome's worth of new zones to hold in memory. Our plans start at 6GB for that reason — headroom is cheaper than diagnosing stutter mid-raid.

What's useful in the meantime:

• Clock speed matters as much as core count. Iron Gate's guidance specifies a minimum GHz alongside a minimum core count, which is a strong hint that per-core speed carries the simulation. A faster core is usually the better upgrade for a busy world.
• Treat the storage minimum as a floor. It predates 1.0, and world files grow as you explore. A Deep North run writes a lot of new zones to disk.
• 1.0 includes server-relevant optimisations. Iron Gate has called out reduced microstutter as zones load in and out of memory, plus faster saving. Large builds aren't this pass's focus, so don't expect a fix there.
• If you're near 2GB, bump it now. A new endgame biome, returning players and two console audiences land the same day. At 4GB+ for a small group you're likely fine.

Our Valheim server hosting starts at 6GB RAM from $16/mo, and you can add RAM or CPU cores from the billing portal at any time without a restart — so if launch week is heavier than you planned for, you're not stuck.

What's actually in the Deep North

The Deep North is Valheim's eighth and final biome — Iron Gate's own store page has described the game as having seven finished biomes out of a planned eight, plus the Ocean. It sits at the far northern edge of every world map.

Per Iron Gate's announcement, arrival is meant to be rough: an impenetrable snowstorm greets you, and once it clears you get snowy mesas and fields frozen in permanent stillness. Explore and you'll find large abandoned villages — evidence you aren't the first Viking to try this.

Two enemies are confirmed. Gammeltrolls are what Valheim's trolls become when they grow too old — they migrate north, become one with the land, and turn into primordial giants that guard the biome. Elakingar live below a surface that only looks empty, tunnelling deep underground, and Iron Gate says they're sometimes accompanied by something considerably worse. That's as close as the studio has come to teasing the final boss.

Beyond that: new weapons, building pieces and dungeons. The boss stays unrevealed, and item details circulating now come from preview builds, so they can still change before September 9. Anything naming Deep North weapons or bosses with confidence is guessing.

One thing explicitly not in 1.0: an Ocean overhaul. Iron Gate has confirmed sea gameplay stays as it is.

Get ready before September 9

The Deep North arrives September 9, 2026. If you run a dedicated server, do one thing first: back up your .db and .fwl together on the current build, labelled something obvious. With no public test branch, that snapshot is your only rollback.

The rest is preference. Start fresh for the full Meadows-to-Deep-North run, or push north on your existing world and take whatever generates. Your base and progress are safe either way — the only thing at stake is how much of the new biome you get.

Setting up a server before launch? Our Valheim plans start at 6GB from $16/mo, and code evlbox25 takes 25% off your first month.