Valheim 1.0 and the Deep North: what it does to your server

Valheim leaves early access on 9 September 2026. What the update does to your world files, your mod folder, your memory use and the way people join.

Valheim leaves early access on 9 September 2026, five and a half years after it sold ten million copies in a matter of months. The Deep North closes the biome roadmap: abandoned villages under the northern lights, Gammeltrolls that fused into the terrain as they aged and throw tree trunks at your base, tunnel networks full of Elakingar. PlayStation 5 and Nintendo Switch 2 get the game the same day, with crossplay across every platform.

None of it wipes your save. Plenty of it changes how the server behaves.

#Your world files change shape

Iron Gate rewrote the save system in May and parked it on the public test branch. A world stops being a world.db and world.fwl pair and becomes a folder with the database split into chunks. It has not reached the live branch. 1.0 is where it goes.

The conversion runs on first load and takes a backup before it starts. What it breaks is anything you have automated that copies *.db off the server. Full detail in Updating your Valheim server to 1.0.

#The Deep North lands where nobody has been

Valheim rolls a zone the first time a player comes within roughly 500 metres, writes it into the world, and never rolls it again. New content appears only in ground that has never been near anyone.

Most groups get away with this. The far north was placeholder snow with nothing to do in it, so few crews sailed up to look. Stop at the Mountain and the real Deep North generates on first approach, base untouched.

Anyone who did map the northern edge keeps flat old snow there permanently. Open your map before the 9th and look at how much of the top is drawn. A thin exploratory line, sail around it. Half the north filled in, and you are choosing between a new seed and a mod that forces regeneration, both covered in The Deep North is not showing up in my world.

#Console players need the other backend

A Valheim server runs one of two networking backends. Steam by default, joined by address and port. Add -crossplay at launch and it registers with PlayFab, which is the only route a PS5, Switch 2 or Xbox player can take. Crossplay servers are joined with a six-character join code, not an address, and the code changes on every restart.

Consoles can join a dedicated server. They cannot run one.

On Hostd the backend is the Crossplay switch under Dashboard → Overview → Plan & schedule. A new Valheim server created without mods starts with it on. The current join code shows on the Connect panel and the invite page after every start, and the dashboard's player list and ban tools understand the Platform IDs that crossplay players carry, so a console player can be whitelisted or banned the same way a Steam player can.

Switching backend switches how everyone joins. Make that call before launch night.

#Mods start from zero

Iron Gate's 1.0 FAQ puts it plainly: "Since we don't have any official mod support, we cannot guarantee that any mods will be functional when 1.0 releases." There is no public test branch carrying the Deep North, so no author has a build to compile against. Updates land after the 9th.

The engine bump already happened, in February's anniversary patch, so what breaks in September is game code. Strip your plugins before you update and add them back as authors catch up. The order to do that in is Valheim mods after 1.0.

#Does it need more RAM?

Not on the 9th. A dedicated server runs with -nographics -batchmode and draws nothing, so the blizzards and northern lights everyone is screenshotting cost it nothing at all. What the server holds is the object records for zones currently loaded, and zones load around players.

The Deep North changes where your crew goes, not what each object costs. For a fortnight everyone sails to a corner of the map nobody has loaded before while somebody else sits at base holding those zones open, and that is where the pressure comes from. It settles once the exploring stops. Chunked saves should take the edge off the periodic save stall, since only modified chunks get written.

Size up if you are starting a fresh world and the group scatters, or if a large base and a northern expedition run at the same time. A world that was comfortable in August does not need double the memory in September.

Iron Gate publish no hardware requirements for the dedicated server, so treat any figure presented as official with suspicion.

#Before the 9th

• Take a manual backup and confirm it is listed. An untested backup is a guess.
• Rewrite anything that copies world.db off the server. It will not find that file afterwards.
• Open the map and settle the new-world question while nobody is waiting on you.
• Note which plugins are server-side and which need matching client files. That list is your rebuild order.

#Where to go next

• Updating your Valheim server to 1.0
• The Deep North is not showing up in my world
• Valheim mods after 1.0: what broke and what to do
• Picking the right Valheim server plan

Written and maintained by the Hostd engineering team. Last updated 2026-09-04. Notice a mistake? Tell us.