Skip to content
Guide

How to Move a Valheim Server to a New Host

Moving a Valheim server to a new host is quick — the world is two small files. This guide covers migrating without losing your progress or characters, matching the version and any BepInEx mods, and cutting over with almost no downtime.

7 min read Beginner Anti-DDoS hosting

A Valheim world is just two files: <world>.db (the world data) and <world>.fwl (the metadata), plus your adminlist.txt / permittedlist.txt and any BepInEx mods. Copy those to a new host, match the version and mods, update the IP, and your world comes with you. It's one of the easiest games to migrate.

Below is the process. Moving to us? Our Valheim hosting is crossplay-ready with a File Manager and DDoS protection — quick to move to.

Before you start

What you'll need

A quick checklist before you begin — have these ready and the rest is easy.

  • Access to the old server's files (File Manager or SFTP).
  • The world's .db and .fwl files (both).
  • adminlist/permittedlist/bannedlist and BepInEx if modded.
  • The same Valheim version (and mods) on the new host.
  • The new IP:port to share with players.
Step by step

Migrate your Valheim server, step by step

1

Back up the world files

Stop the server, then download your world's .db and .fwl files (both, same name), plus adminlist.txt, permittedlist.txt and bannedlist.txt. If you run BepInEx mods, grab the BepInEx/ folder and its configs too.

.db   .fwl
adminlist.txt  permittedlist.txt  bannedlist.txt
BepInEx/  (if modded)
2

Match the version & mods

On the new host, make sure it runs the same Valheim server version, and install the same BepInEx and mods if you use them. A mod/version mismatch is the main thing that stops a world loading, so line this up first.

3

Upload the world files

Stop the new server, then upload the .db and .fwl (keeping the same world name), the admin/permitted/banned lists, and your BepInEx folder, via File Manager or SFTP — overwriting the defaults.

4

Set the world name & flags

Make sure the new server's start config points at the same -world "<name>" as your files, and carry over your -password and -crossplay flags so players connect the same way.

-name "..." -world "" -password "..." -crossplay
5

Update the connect IP

The new server has a new IP:port. Share it, and have players use Join IP with ip:2456. If some are on crossplay, make sure -crossplay is set so they see it.

ip:2456
6

Test, then cancel the old host

Start the server, join, confirm the world and your buildings/characters loaded, and have a friend test. Only cancel the old host once confirmed — keep the .db/.fwl backup a few days.

Migrate safely

World intact, minutes of work

Copy both .db and .fwl

The world needs both files with the same name. Copy them together, and keep the same world name on the new host so they're found.

Match BepInEx exactly if modded

A modded world won't load without the same BepInEx and mods. Install them on the new host before uploading the world.

Grab the .db.old backups too

Valheim keeps .db.old backups. Copy them along as a safety net in case the main .db has an issue.

Keep the crossplay flag

If your players use crossplay, carry the -crossplay flag to the new host or some won't see the server.

Troubleshooting

Common problems & fixes

Hit a snag? These are the issues people run into most — and how to solve them.

The world won't load on the new host

You're missing the .fwl, or the -world name differs. Copy both .db and .fwl and point the start config at the same world name.

A modded world fails to start

BepInEx or a mod version differs. Install the same BepInEx and mods on the new host, then upload the world.

Some players can't see the server

The -crossplay flag didn't carry over. Add it on the new host so crossplay players see the listing.

Players can't connect

They're on the old IP. Share the new one and have them use Join IP with ip:2456.

Skip the setup — host it with ESAGAMES

Moving your Valheim world to us? Our Valheim hosting is crossplay-ready with a File Manager, backups and DDoS protection — a two-file world moves in minutes, and support helps if you need it.

Valheim hosting
FAQ

Frequently asked questions

How do I move a Valheim world to a new host?

Stop the server, copy the world's .db and .fwl files (both, same name) plus your adminlist/permittedlist/bannedlist and any BepInEx folder, then upload them to the new host running the same version. Point the start config at the same -world name and test.

Which files hold my Valheim world?

Two files: .db (the world data) and .fwl (the metadata). You need both, with the same name. Valheim also keeps .db.old backups you can copy as a safety net.

Will I lose my character or buildings when I switch Valheim hosts?

No — buildings live in the world files (.db/.fwl), which you migrate. Character data is client-side (stored with each player), so players keep their characters automatically. Copy the world files and nothing on the server is lost.

Do my Valheim mods carry over to a new host?

Yes — copy the BepInEx folder and its configs, and install the same BepInEx and mods on the new host. A mod/version mismatch is the main reason a modded world won't load, so match them.

How do players connect after I move a Valheim server?

Share the new IP and have them use Join IP with ip:2456. Keep the same -password and -crossplay flags so the connection works exactly as before.

Why won't my Valheim world load after migrating?

Usually a missing .fwl (you need both files), a different world name in the start config, or a mod/version mismatch. Copy both files, match the -world name, and match BepInEx/mods.

More guides

Keep reading

Ready to launch?

Protected, low-latency game hosting in Frankfurt — online in minutes with 24/7 support.

Payments Secure checkout with cards, banking apps and digital wallets.

Choose the payment flow that fits your stack and region without leaving the platform.

Pay by Zen Visa Mastercard Paysafecard PaysafeCash Skrill Trustly Bancontact UnionPay iDeal WebMoney