Valheim 1.0 is live. After five and a half years of Early Access, the Deep North update went out worldwide on September 9, 2026 — and as with every major patch day in Valheim's history, the biggest obstacle between you and the frozen north is not a boss. It is a version mismatch between your game and your server.
Because 1.0 shipped with no public test branch, every client and every server on the planet updated at the same moment, with no dress rehearsal. That makes today the single most concentrated burst of "Incompatible version" errors, crossplay confusion, and broken mods the game has ever seen. This guide walks through the release schedule and every launch-day failure in the order you should actually troubleshoot them.
PC PS5 Xbox SwitchTL;DR: The fix for almost every launch-day connection problem is the same: make sure your game and your server are on the same build. Update the server first, then have players update and join. Console players: your patch may lag behind Steam by hours — that is expected, not broken.
Release Time: When Valheim 1.0 Unlocked
The scheduled worldwide release was 13:00 UTC on September 9, 2026 — 6:00 AM Pacific / 9:00 AM Eastern / 3:00 PM CEST in Iron Gate's home country of Sweden. Unlike many AAA launches, there is no rolling regional unlock: everyone gets the build at the same time.
| Region | Unlock Time (September 9, 2026) |
|---|---|
| Pacific Time (US West) | 6:00 AM PDT |
| Eastern Time (US East) | 9:00 AM EDT |
| UK (BST) | 2:00 PM |
| Central Europe (CEST) | 3:00 PM |
| Sweden (Iron Gate HQ) | 3:00 PM |
| Japan (JST) | 10:00 PM |
| Australia East (AEST) | 11:00 PM |
Download sizes are roughly 4.3 GiB on most platforms, 3.0 GiB on Xbox One, and 6.5 GiB on the Mac App Store and Microsoft Store versions. There is no preload on PC, so if your group plans an evening raid into the Deep North, have everyone start the download before dinner.
The #1 Launch-Day Error: "Incompatible Version"
The error means exactly one thing: the game you are running and the server you are joining are on different builds. Nothing is broken, nothing is lost — one side is simply behind. Valheim only lets a client connect to a server reporting the same version.
Your version number is printed in the bottom-left corner of the main menu. A dedicated server prints its version in the console window at startup; a hosted server shows it in the control panel. Comparing those two numbers settles most launch-week problems in about fifteen seconds.
One historical trap worth knowing: on builds older than patch 0.220.3, a version mismatch could report itself as "the host does not allow cross-platform play." If you see a crossplay complaint, check the version numbers first before touching any crossplay settings — you may be chasing a setting that was never the problem.
Fix order: follow this sequence
- Update the server first. Players who update before the server does will be refused with "Incompatible version" until it catches up. On a rented server, this is an Update button in the control panel; if the panel still shows the old version afterward, run the update again with file validation — a patch that lands mid-startup can come out half applied.
- Update or verify your game. Restart Steam completely (Steam sometimes will not pull the patch until you do), then right-click Valheim → Properties → Installed Files → Verify integrity of game files. Check the version number in the main menu afterward.
- Match your beta branch. If you opted into the public test branch at any point, switch it back: Steam → right-click Valheim → Properties → Betas → None. A test-branch client cannot join a release-branch server and vice versa. Note that 1.0 itself had no public test branch — this applies to leftovers from previous patches.
- Check for version-changing mods. Server-side mods like Valheim Plus compare their own versions between client and server, and a mismatch produces the same "Incompatible version" message even when the game builds match. More on mods below.
Crossplay Problems: The Console Patch Gap
Crossplay between PC, Xbox, PS5, and Switch 2 is live with 1.0 — but there is a structural catch that hits every patch day: Iron Gate ships each build to Steam first. The Microsoft Store, Game Pass, Xbox, PlayStation 5, and Nintendo Switch 2 builds sometimes follow hours later, occasionally longer.
On a crossplay server, console players will see "Incompatible version" from the moment the server updates until their own platform receives the patch. There is nothing to fix on the server side — the platform update is the only cure. If your Xbox friend cannot join tonight but the PC side works, this is almost certainly why.
How console players connect:
- Join codes, not IP addresses. Crossplay players connect with the server's join code instead of an IP and port. The host can copy it from the pause menu — copy-to-clipboard was fixed in an earlier patch and works on current builds.
- No account needed beyond the platform's own. Iron Gate has not layered a publisher account system on top of console crossplay.
- Password rules are stricter than they look. The game requires at least 5 characters, and on a public server the password cannot appear inside your world name or seed name. A world called "Midgard" with the password "gard" will refuse to start entirely — the server writes an error and shuts down. If your server died within seconds of a password change, this is why.
Mods: Assume Broken Until Proven Otherwise
Iron Gate's official FAQ is blunt: because there is no official mod support, the studio cannot guarantee any mod will be functional when 1.0 releases. The jump from 0.221.x to 1.0 is the largest API change in Valheim's history, there was no test branch for mod authors to prepare against, and everyone is updating blind on the same day.
Two facts to plan around: BepInEx mods break on major version bumps as a matter of routine, and a plugin that throws on load can stop a server from accepting connections at all — the reliable diagnostic is to move the mods out of the way, confirm clean vanilla startup, then re-add them as authors ship 1.0 builds. And enabling crossplay disables BepInEx on PC anyway, because crossplay runs on Microsoft's PlayFab backend instead of Steam networking. A crossplay server is a vanilla server.
If your group cares more about a mod stack than being first into the Deep North, hold the modded server on the old version for a few days and stand up a second vanilla server for 1.0. Running two is cheaper than breaking one.
Launch-Day Checklist
| Symptom | Most Likely Cause | Fix |
|---|---|---|
| "Incompatible version" on join | Client and server on different builds | Update whichever side is behind — server first, then verify game files |
| Console player cannot join, PC players fine | Console patch lags behind Steam by hours | Wait for your platform's storefront to deliver the update; nothing to fix server-side |
| Server vanished from the browser | Version drift, or a "?" icon meaning matchmaking data could not be retrieved | Try joining directly anyway; otherwise update and restart the server |
| Server dies seconds after a password change | Password contained inside world/seed name | Change the password to something not in the world or seed name |
| Modded server will not start | BepInEx plugins broken by 1.0 | Remove mods, confirm clean vanilla startup, re-add as authors update |
| Stuck on "logging in to backend service" | Backend handshake during patch-day surge | Restart the client; try again after patch traffic subsides |
FAQ
What time did Valheim 1.0 unlock?
The scheduled worldwide release was 13:00 UTC on September 9, 2026 — 6:00 AM PDT, 9:00 AM EDT, and 3:00 PM CEST. All platforms received the build on the same schedule, though console storefronts may deliver the patch to individual consoles a few hours behind Steam.
Why does my friend get "Incompatible version" but I can join fine?
Their client is on a different build than the server. Have them fully restart Steam and verify the game files. If they are on Xbox, Game Pass, PS5, or Switch 2, their platform may simply not have received the 1.0 patch yet.
Do console players need the server's IP address?
No. Crossplay players connect using the server's join code, which the host can copy from the pause menu. IP-and-port connections remain the standard route for Steam-to-Steam joins.
Why can't I use mods with crossplay enabled?
Crossplay runs on Microsoft's PlayFab backend, which replaces the Steam networking layer that the BepInEx mod framework depends on. Crossplay servers are effectively vanilla servers on the PC side.
Sources
- Valheim 1.0 Release Time: Global Times, Deep North and Crossplay — Survival Servers, confirmed 13:00 UTC release time and launch details.
- Valheim Incompatible Version Error (and how to fix it) — Survival Servers wiki, version-mismatch causes and the 1.0 launch update order.
- Valheim Version Mismatch and Update Problems — GameServerKings, the 0.220.3 crossplay misreporting trap and client/server update drift.
- Valheim 1.0 (9 September): What Changes for Server Owners — Gamever, download sizes, no-test-branch consequences, and mod guidance.
- Updating your Valheim server to 1.0 — LOW.MS, post-patch connection diagnosis and the password-in-world-name rule.
- Finding & Joining Valheim Servers: What the Server List Rewrite Changed — Gamever, join code fixes and the version-mismatch-as-crossplay-error history.
