There's a moment every Valheim group hits eventually. Somebody has to be online for anyone else to play. That somebody has a job, or a bad connection, or an early start, and the world you've all sunk two hundred hours into is now hostage to one person's evening plans. Then they log off mid-raid and the whole thing goes dark.
Moving that world onto a dedicated Valheim server fixes it. Properly, and in one step. The world stays up, everyone keeps their own progress, and nobody has to be the designated host. It's the single most common upgrade path in Valheim and it's genuinely straightforward.
But there are a few things people get wrong about it, and one of them causes real panic on the night. So before you touch a single file, here's what actually moves, what doesn't, and what to decide first. The file-by-file mechanics are already written up in our world upload guide, so I'm not going to repeat those here. This is the decision layer that sits above them.
What actually moves, and what doesn't
This is the bit worth getting straight before anything else, because it surprises people every time.
The world moves. Characters do not. And that's not a limitation you need to work around. It's how Valheim is built.
A Valheim world is a single self-contained thing. The terrain, the buildings, the chests and their contents, the boss altars, every zone anyone has generated. That's what lives on the server. That's what you upload.
Your character is separate, and it lives on your own machine. Skills, inventory, the gear you're wearing, your recorded map markers, all of it is yours and travels with you. When you join a server you bring your character to it. This is why you can take the same Viking to three different worlds and keep your levels.
So when you move a world to a server, this is what happens for each player:
- The world arrives with everything in it, exactly as it was.
- Every player joins with the character they already had, keeping their skills and inventory.
- Nobody loses progress, and nobody needs to re-level.
The panic scenario is a player who assumes their character is stored in the world file, sees the server come up, and concludes their Viking has been deleted. It hasn't. It's on their own computer, where it always was. Nothing was deleted. Have them pick the same character from their character list and join.
One real caveat here. Because characters are local, each player keeps their own copy, and a player who reinstalls the game or moves to a new PC without copying their character folder across genuinely will lose that character. The world on the server is safe. Their Viking is their own responsibility, and it's worth telling them that once, early.
Will your world still work in 1.0?
This is the live question right now, three weeks out from September 9, and it's the reason a lot of people are asking about moving worlds at all. Nobody wants to migrate a world in August and find it's landfill in September.
The short answer is that your world carries over. There's no wipe announced, and Valheim has carried worlds across every major update through early access, Mistlands and Ashlands included. 1.0 will load a world you're playing today. That much is safe.
The longer answer is about the Deep North, and it's the thing most likely to disappoint someone. Valheim generates the world lazily, zone by zone, the first time anyone loads each zone, and once a zone exists it's fixed. The game never goes back and re-rolls it. So the new 1.0 generation only reaches ground nobody has visited yet.
Practically, that means your existing world will get Deep North in the unexplored north, and not in the stretch you've already sailed. If you want the finished game everywhere, that's an argument for a fresh world rather than a migration. If you're attached to your base, migrate and sail north. We've written that decision up properly in Deep North on an existing Valheim world.
There's one more thing worth watching. A public test build back in May introduced a reworked save system, where a world is stored as a folder of smaller chunks rather than the single pair of files everyone is used to, with backups getting their own folders. Iron Gate haven't confirmed whether that ships with 1.0, and the live build hasn't changed yet. If it does land, the mechanics of copying a world by hand change on the same day. It shouldn't cost you anything, because the game converts an old world when it first loads it and takes a backup before it does. But if you're planning a migration for the week of launch, do it before the ninth rather than during, and you sidestep the question entirely.
Self-host or rent
Worth being honest about, because for some groups self-hosting genuinely is the right answer.
Valheim's dedicated server is free. Genuinely free, not trial free. It's a separate download in the Steam library tools list, it's not a big install, and if you have a spare machine that's already on all the time, running it yourself costs nothing but attention. For a technically confident person with a static IP and a router they're happy to forward ports on, that's a perfectly good setup.
What it actually asks of you is the part people underestimate. You're forwarding ports and exposing a machine on your home connection to the internet. You're the one restarting it after a Windows update reboots the box at 3am. You're the one who notices when an update ships and the server silently stops accepting connections because the clients moved first. And your friends' ping is bounded by your home upload speed, which on most domestic connections is the bottleneck, not the CPU.
The honest split I'd give anyone asking:
- Self-host if you enjoy the sysadmin side, have hardware sitting idle, and your group is small and forgiving about the odd outage.
- Rent if you want it to be somebody else's problem at 3am, you want players in more than one country to get a decent ping, and you'd rather spend your Valheim time playing Valheim.
There's a third factor that's become more important with 1.0. If you're mixing console players into the world, an always-on server that nobody has to boot is worth a lot more than it used to be, because your PS5 and Switch 2 friends can't host for you and can't be the fallback when you're out. The host has to be something that's always there. If you're mixing platforms, the join-code half of that is covered in Valheim Crossplay and Join Codes on Dedicated Servers. Our plans and regions are on the Valheim hosting page if you want to compare.
If your world is on Game Pass or Xbox
This one comes up a lot and the answer is less clean, so I'd rather set expectations properly than pretend.
If you've been playing the PC version through Game Pass rather than Steam, there's a proper answer here, and it's better than most people expect. Your world lives in cloud storage rather than sitting in a folder you can browse to, but the game will hand it over if you ask.
From the Valheim main menu, open Manage Saves and choose Move to Local on the world you want. It then drops into the ordinary worlds_local folder as the usual .db and .fwl pair, and from that moment it's a normal world file that moves like any other.
That's the whole trick. Worth knowing, because the common assumption is that a Game Pass world is stuck where it is, and it isn't.
If your world only exists on an Xbox console, that's a different story and the answer is no. Console saves sit in Microsoft's cloud storage with no export path out, and Valheim gives you no way to pull them into files. I know that's not what anyone wants to read, but it's better than sending you looking for a tool that doesn't exist.
And for PS5 and Switch 2, which arrive with 1.0 on September 9: there is no known export path, and I'm not going to speculate about one before the platforms are even live. Anyone publishing a confident method for this today is guessing. If a route appears after launch we'll write it up properly, and if it doesn't, plan on the basis that a console-created world stays on the console.
The workable answer in all three cases is the same, and it's not a bad one: start the server world from a PC copy if anyone in the group has one, or start fresh on the server and treat launch as the clean slate. Everyone keeps their characters either way, which takes most of the sting out of it.
A pre-move checklist
Ten minutes here saves the evening. Run through these before you upload anything.
Back up the original. Copy the world files somewhere that isn't the folder you're about to work in. Not because the process is risky, but because a copy costs nothing and it's the only thing that makes a mistake recoverable.
Have the host stop playing. Take the copy when the world isn't loaded. Copying a world that's mid-session can catch it between saves, and the version you upload might be missing whatever happened in the last few minutes.
Check the world name matches. The server has to be pointed at the world you uploaded, by name. This is the single most common reason a migration appears to fail: the files are there, they're fine, and the server has quietly generated a brand new empty world next to them because it was still looking for the default name. If you log in to an untouched shoreline, this is almost always why. Check the name first.
Tell your players what to expect. Specifically, that they'll join with their existing character and it will look exactly as it did. Saying this once in advance prevents the "my character is gone" message you'd otherwise get three times on the first night.
Decide the mods question before you migrate, not after. If the world has been running with mods, the server needs a compatible setup or things will behave strangely in ways that are hard to diagnose after the fact.
Do it before September 9, not during launch week. Migrating and updating to a major release on the same evening means that if something misbehaves you have two candidate causes and no way to separate them.
When you're ready for the actual file work, the world upload guide has the paths and the steps. And if you'd rather not do it yourself at all, open a ticket with your world files and we'll move it across for you. It's a quick job at our end, and a much better use of your evening than reading folder paths off a screenshot.