You updated the server on launch day, everyone piled in, somebody sailed north expecting glaciers and new things to kill, and the map looks exactly like it did last week. Nothing's broken. Your server is fine, the update installed fine, and you haven't lost anything. This is just how Valheim has always handled new biomes, and it catches out a fresh batch of people with every single update.
Here's what's actually going on, and what your options are.
What Iron Gate actually said
Worth quoting directly rather than paraphrasing, because their wording is more precise than most of what's circulating. From the official Valheim 1.0 FAQ:
As usual, your world will receive new content even if it was created before the update, although biome generation will only work properly on areas that have not yet been explored. However, we always recommend that you start the game over from scratch to get the best possible experience.
Two separate things in there. Your old world keeps working and keeps loading: there's no forced wipe, and Iron Gate confirm elsewhere in the same FAQ that your saves stay exactly where you left them. But the new biome generation only lands properly on ground nobody has been to yet.
That second half is the bit that generates tickets.
Note what they didn't say, too. They didn't say the update is optional, and they didn't say old worlds are broken. Both get repeated a lot.
Why explored ground stays as it is
Valheim doesn't build the whole map when you create a world. It builds it zone by zone, the first time somebody loads each one, and then writes that zone into the world save with its terrain and biome settled. It doesn't go back and reconsider afterwards. So a zone generated in 2024 was generated under 2024's rules, and it keeps them, no matter how many updates land on top of it.
When 1.0 shipped the Deep North, the new rules applied to zones that don't exist yet. Everything already written stays written. Which is genuinely good news for the thing you actually care about: your base isn't going anywhere, your longhouse won't have a glacier through the middle of it, and nothing you've built gets re-terraformed under your feet.
The catch is that "explored" is broader than most people assume, and Iron Gate don't define the word anywhere. Going on how zone generation actually behaves, it isn't about what you personally have uncovered on your map. It's ground that got generated for anyone on that world, at any point since it was created, including coastline somebody sailed past at night without really looking at it. If six of you have been playing the same world for two years, you've collectively generated a lot more of it than any one of you remembers.
That's also why the map is a poor way to judge it. Jere Kuusela, who wrote the Upgrade World tool and reads Valheim world saves directly to do it, puts the generated area at several hundred metres out from anywhere a player has been, which is a good deal further than the minimap ever uncovers. So the fog line isn't the generation line. There's a band of already-settled ground past the edge of what you can see, and no in-game way to read where it ends. I wouldn't decide anything purely on how much white is left up there.
Before anything else, take a backup
It takes about a minute, and every option below except sailing north changes your world in a way you can't take back.
- Stop the server from the power controls at the top of its page in the LOW.MS panel.
- Open the Backups tab, press Create backup, and lock it with the toggle on its row so it never rotates away.
- Start the server again.
A scheduled Backup task under Scheduled tasks on the Settings tab will keep taking them, but nothing schedules one for you by default, so don't assume there's a recent one sitting there waiting. Restore on the same tab is the way back if you ever need it, with the server stopped. Backing up and restoring a Valheim server covers both systems.
One thing worth knowing while we're on saves, because it changed with 1.0. The new save system Iron Gate had on the public test branch since May shipped in 1.0, so a world is no longer the familiar .db and .fwl pair. It's a folder named after the world, full of smaller .chunk files, and Valheim's own backups are folders too. Your old world was converted automatically the first time the 1.0 server loaded it, and the game kept the originals as .db.old and .fwl.old plus a dated _backup_ copy. So if the Files tab looks different from last time, that's why, and nothing is missing. If you ever move a world by hand, move the whole folder. Our world upload guide has the detail.
Character saves weren't part of the change at all. And restoring through the Backups tab works the same either way, which is a decent argument for using it rather than shuffling files around yourself.
Your options, and what each one costs
Four realistic routes. None of them is wrong. They just cost different things, and the right one depends far more on how attached your group is to the world you're already in than on anything technical.
Sail north into ground you haven't touched
Cheapest by a mile, and what most groups should do. Head north past the edge of where you've been, and those fresh zones generate with the full 1.0 content in them. Base stays, progression stays, gear stays.
What it costs: travel time, plus the assumption that you've actually got unexplored north left. If your world is old and thoroughly picked over, or your group made a habit of long exploratory voyages, there may not be much virgin territory up there. It also means the rest of your map stays generated under the old rules. And the 1.0 patch notes promise "alternate versions of earlier biomes" out at the outer edges of the map, and those need fresh ground too, so they won't turn up in the parts of the world you already live in.
Start a fresh 1.0 world
This is what Iron Gate recommend, and if you want the finished game as designed, they're right. A new world generates every zone under 1.0's rules, so the whole map reflects the final version rather than just the northern fringe.
What it costs: everything you've built. Bases, farms, portal networks, the lot. Characters are stored separately from worlds in Valheim, so your skills and inventory aren't the sacrifice. It's the world itself, and the sense of place that goes with it. For a group that's been drifting anyway, 1.0 is a good excuse. For a group with a settlement they're proud of, it's a hard sell, and I wouldn't push it on people.
On our panel, pointing the server at a different world is the World Name field on the Manage tab: set a new name there and restart, and the server creates it on first boot. Your old world stays where it is. Two cautions for now: the field's suggestions and the New World tool on the Settings tab were built for the old two-file layout and don't handle 1.0 world folders properly yet, so type the name rather than picking a suggestion, and if you want the old world wiped rather than left alongside, open a ticket. Getting Started with Your Valheim Dedicated Server covers the basics if you want a refresher.
Run both, side by side
Keep the old world going and stand up a second Valheim service for a clean 1.0 map. Nobody has to give anything up, and people drift between the two.
What it costs: a second service to pay for, and, honestly the bigger problem, a group split across two worlds on the evenings when only four people are online. Works well for a large community, badly for a group of five. The Valheim hosting page has the options if you want to price it up.
Force the old zones to regenerate
Possible. It's also the fiddly one, and the one I'd think hardest about before committing to. The community tool is Jere Kuusela's Upgrade World, and it has a dedicated Deep North operation: it clears the already-generated Deep North zones and the water around them so they come back under the new rules. Terrain it leaves to the base game rather than rewriting itself, so this isn't the river-moving operation that some of the tool's other options are. What it does do is empty the zones it touches. Base protection is on by default and deliberately over-cautious, but anything you've built up there that it doesn't recognise as a base goes with the regeneration.
What it costs: it's a BepInEx mod, so there are a few knock-ons. The kinder one first: it doesn't have to live on your server permanently. The tool's own instructions have you install it, run the pass, check your bases survived, then take it off again, so this isn't a commitment to running a modded server from here on. While it is on there, crossplay is worth a thought. Turning crossplay on moves the server off Steam matchmaking and onto PlayFab, and mods that lean on Steam networking or read SteamID64 can misbehave on that backend. It also needs a build that works against 1.0, and Iron Gate said plainly in the FAQ that they couldn't guarantee any mod would be functional at release. Check its Thunderstore page shows a release from after 9 September before you plan around it. It installs from the Mods tab like any other Thunderstore mod, but because the pass rewrites zones in a world you care about, I'd rather you didn't run it alone: take a backup and open a ticket, and we'll either run it for you or talk you through it. Our 1.0 hosting overview covers the wider launch-day picture.
What to tell your players
Most of the ticket volume around this is really a communication problem, so get ahead of it:
- The north will look the same at first. Expected, not a bug.
- New content is out past the edge of where the group has been, so the first session after updating is a sailing trip.
- If you're staying on the old world, say so. If you're starting fresh, say that too, because people will want to know whether tonight's building session is worth doing.
- Mods broke on a version bump this size. Iron Gate said as much themselves. Run vanilla until the mods you rely on have a 1.0 release.
When to open a ticket
Come to us if the server won't start after updating, if a world won't load at all, or if you want the Upgrade World route and need a second pair of hands. Also come to us if something has genuinely gone missing rather than just looking unchanged. That's a different problem with a different fix, and the sooner we look at it the more we can usually get back.
What isn't a fault, and what we'll only tell you the same thing about: an explored northern coastline that looks identical after the update. That one's working as designed, and the fix is a boat.