Valheim 1.0: What Changed for Servers

Valheim 1.0 launches September 9, 2026, and most of the coverage is about the Deep North, the new boss, and the story ending. None of that tells you what actually changes if you’re the one running the server.

We went through Iron Gate’s own 1.0 FAQ and the patch notes specifically looking for what matters to server owners: hardware, save files, startup behavior, and compatibility. Some things genuinely change, the save format most of all. A lot doesn’t. Here’s the honest breakdown of both.

What Actually Changes

No public test branch for 1.0. Iron Gate’s FAQ is direct about this: “No. We want everyone to get to experience 1.0 at the same time!” Every previous major update gave mod authors and hosting providers early access to test against. This one doesn’t. That means mod compatibility and any unusual server behavior get discovered in real time, on launch day, by everyone at once.

Crossplay reaches two new platforms. PlayStation 5 and Nintendo Switch 2 join Xbox, Game Pass, and Steam on the same crossplay backend. If your server already has crossplay enabled, this applies automatically. See our crossplay guide for the full platform breakdown.

The world save format changed. Valheim 1.0 replaced the single .db and .fwl file pair with a folder based format. Each world is now a folder inside worlds_local, named after the world, with the world data split into smaller pieces and backups kept in their own folders. Only the pieces that change get rewritten on each save, which is where the faster saves come from. This changes how you back up and transfer worlds. See the section below.

Saves are faster, and zone loading has fewer microstutters. From Iron Gate’s FAQ: “Some of the optimisations that will make it into 1.0…include decreasing the microstutters that occur when loading new zones in and out of memory, faster saving, and many other minor optimisations here and there.” This is a real, if modest, win for the autosave lag spike that longer-running worlds are known for. Iron Gate is upfront that it’s not a fix-all: “large builds in particular would not be highly impacted by these changes.”

The New Save Format, In Practice

The chunk-based save system Iron Gate tested on the 0.221.13 public test branch shipped with 1.0. Here is what it means day to day:

• A world is a folder now, not a file pair. In worlds_local, each world is a folder named after the world. To back up or move a world, you take the whole folder. On worlds last saved before 1.0 you still have a .db and .fwl pair until the server loads and converts them.
• The first load of an old world is slow. When the server first opens a pre-1.0 world, it converts it to the folder format and writes a backup before it starts. That can take several minutes with nothing visible in the console. It only happens once.
• Automatic backups are folders too. Valheim still keeps 4 rolling backups plus one on update, but each is its own folder in worlds_local rather than a file pair.

Our backup guide and world import guide cover both formats step by step.

What Didn’t Change

It’s worth saying plainly: most of the technical surface of running a server is untouched.

• Player cap stays at 10. Iron Gate’s FAQ: “Just like it is now, Valheim 1.0 will be a game for 1-10 players.”
• No Steam Workshop. Also from the FAQ: “there will be no Steam Workshop featured.” Mods still come from Thunderstore or Nexus and get uploaded manually, same as always.
• The dedicated server app ID and ports are the same. Steam App ID 896660 for the server, 892970 for the game client, UDP ports 2456-2458. Nothing in the 1.0 release changes any of these.
• Startup parameters are unchanged. Server name, password, world name, port, crossplay, and beta branch options all work exactly as before. See our server settings guide for the full list.
• The automatic backup schedule is the same. Valheim’s built-in backups still run roughly every 12 hours, plus one on update, keeping 4 rolling copies. Only the on-disk format changed, from file pairs to folders.
• Mod support policy hasn’t changed, but the practical risk is higher this week. Iron Gate has never officially supported mods, and that hasn’t changed for 1.0. What’s different is the combination of a major version jump with no public test branch, which means more mods than usual will need a few days to catch up.
• No official hardware requirement increase. We looked for an updated RAM or CPU recommendation specific to dedicated servers and didn’t find one. Community estimates about Deep North adding memory overhead are just that, estimates, not something Iron Gate has published.

What This Means If You’re Running a Server

1. Update when you’re ready, not necessarily the second 1.0 goes live, especially if your group runs mods. Set Auto Update to 0 temporarily if you want to control the timing.
2. Back up your world first, regardless of when you update. See our backup guide.
3. Expect the first post-update start to be slow. The server converts your world to the new folder format on that first load and writes a backup before it does. Several minutes of apparent inactivity is normal. Don’t kill the process.
4. Expect mods to lag behind for a few days. Check Thunderstore or Nexus before assuming your plugins are broken for good.
5. Decide on the new-world question separately. Updating your server doesn’t require a new world. Whether you want one is a different question, covered in our Deep North world guide.
6. Turn on crossplay if your group has console players, since PS5 and Switch 2 need it just like Xbox always has.

None of this requires new hardware or a different hosting setup. It’s the same server behind the update, running a game that got bigger.

Get your Valheim server → All plans run at $1.99/GB of RAM with no CPU throttling and 45-day backup retention. Support is available via ticket or Discord, backed by a 48-hour refund policy.