Iron Gate has dated Valheim 1.0 for September 9, 2026. It ships the Deep North, the final biome of the original roadmap, alongside PS5 and Switch 2 releases with crossplay. For anyone running a dedicated server, that combination means two separate things to prepare for: a world-content update that touches generation, and a player-base change as console players arrive.
What 1.0 Changes for Servers
- Deep North biome: the last unfinished region of the map gets its real content. Like Mistlands and Ashlands before it, expect the biome to populate in unexplored parts of existing worlds, while already-explored terrain keeps its old generation.
- Console crossplay expands: PS5 and Switch 2 players join the pool. Crossplay runs through the PlayFab relay, which has known throughput limits compared to direct connections.
- Mods will break: every major Valheim content patch has broken BepInEx and most mods for days to weeks until maintainers catch up. 1.0 will be no different, and possibly worse given the size.
The Prep Checklist
1. Back up your world now, and again on September 8. Your world files live in the server's worlds_local folder (.db and .fwl files). Copy both. A pre-1.0 backup is your only path back if the update interacts badly with your world.
2. Decide your update posture before launch day. Two honest options:
- Update day one, vanilla: if your server runs few or no mods, updating immediately is fine and your players get Deep North on launch night.
- Pin and wait, modded: if your server depends on BepInEx mods, do not update on day one. Hold the server on the current version until your critical mods publish 1.0-compatible releases. A modded server that updates before its mods is just a server nobody can join.
3. Stage a test world. Spin up a second Valheim instance (or a temporary small plan), copy your world onto it, and run the 1.0 update there first. You will see immediately whether your world loads, whether generation behaves, and what breaks, without risking the community's main world.
4. Check your RAM headroom. Each new biome has historically pushed memory usage up, and a console-crossplay influx means more concurrent players than your server may have seen. If you are already near your plan's memory ceiling with your current player count, upgrade before September 9 rather than during the launch-night rush. Our Valheim server requirements guide has the sizing table.
5. Make the crossplay decision explicitly. Crossplay on means console players can join and all traffic runs through the PlayFab relay. Crossplay off means direct connections, better performance for PC players, and BepInEx mods that actually work, but no consoles. Modded servers effectively have this decision made for them: mods require crossplay off. Decide which community you are, and announce it before launch so console players know what to expect.
FAQ
Will my existing world get Deep North content? In previously unexplored parts of the world, yes, following the same pattern as Mistlands and Ashlands. Terrain your players already explored keeps its old generation, so communities wanting the full biome sometimes generate a fresh world or use a world regeneration tool on the far north.
Do I need to wipe for 1.0? No wipe is required. The backup-and-test-first routine above is about safety, not necessity.
When will mods work again after 1.0? Historically, BepInEx itself updates within days and popular mods follow over one to three weeks. Track your critical mods' Thunderstore pages, and see our mod sync guide for keeping players' mod lists matched to the server.
Can Switch 2 and PS5 players join my existing server? With crossplay enabled and the server visible in the in-game browser, yes. IP-direct joining is a PC behavior; console players rely on the server browser.
Ready Before the Rush
A Valheim server that is backed up, staged, and sized before September 9 turns launch day into a non-event. Valheim server hosting plans run on NVMe SSD with DDoS protection included, and you can add a temporary second instance for staging.