Valheim Save Location: Find the World You Actually Use

If you searched for a Valheim save location, first identify the edition and the world that actually opens. A Windows folder can contain a local copy, while Steam Cloud, a Microsoft Store PC install, an Xbox console, and a dedicated server may each use a different place. Check the cloud or local label in the game, then compare the world name and save time with the folder or server configuration. This guide helps you find the candidate before backing it up; a recent timestamp alone does not prove that a save is healthy.

Identify which platform and world you are checking#

Start with the device that last opened the world. A Windows Steam world, Windows Microsoft Store world, Xbox console world, and hosted server are not interchangeable folders. Record the store or console, the world name shown in Valheim, whether the game marks it local or cloud, and the last time someone played it.

Iron Gate’s 1.0 FAQ says an Xbox save can be accessed from a PC if you launch the game from the Microsoft Store. It also says there is no other cross-platform save sync. That is an account and platform route, not an Xbox folder path. If you have only used the console, do not search a Windows directory and assume it contains that world.

For a dedicated server, the effective -world name and -savedir path are stronger clues than the server’s public listing name. Keep those values separate: -name identifies the listing, while -world tells the server which world to load or create. The official dedicated-server manual lists both arguments.

Find the Valheim save location on Windows#

For a standard Windows install, check the local Valheim data under:

%USERPROFILE%\AppData\LocalLow\IronGate\Valheim\worlds_local

Paste the path into File Explorer’s address bar after replacing %USERPROFILE% with your Windows account path, or enter it as written in Run. Iron Gate’s server manual documents AppData/LocalLow/IronGate/Valheim as the Windows dedicated-server default. The game’s Steam notes separately distinguish local worlds_local and characters_local saves from cloud saves. If your install or server uses a custom directory, the default can be the wrong place.

Do not expect every world to appear as a single old-style file pair. Valheim’s 1.0 save-system announcement describes a chunked world-save system, with data stored in folders. For this location guide, the useful check is the named world folder and its newest contents. Keep the whole world folder together when making a separate copy; identify the files in a Valheim 1.0 world folder before transferring it.

Characters are separate from shared worlds. If you are looking for your inventory or character progression, check the character save area and the game’s own save manager; a server’s world directory is not each player’s character folder.

Separate local saves from Steam Cloud#

Steam keeps cloud and local saves in different places. Iron Gate’s Steam save-system notes say local worlds use worlds_local and characters use characters_local under the Valheim data directory; cloud files are stored beneath Steam’s userdata area for the account and Valheim’s app ID, 892970.

On a typical Windows Steam installation, the Steam account data root is:

C:\Program Files (x86)\Steam\userdata\<account-id>\892970\

Your Steam client may be installed elsewhere, and the account folder is a numeric ID, so do not treat the example’s drive as universal. On Linux, Valve documents Steam’s default userdata location under ~/.local/share/Steam/userdata; alternate package formats or custom client locations can differ. Use Valheim’s save manager to see whether the world is labeled cloud or local before copying anything.

If the same named world appears in both places, do not decide by folder name alone. Check which entry Valheim opens, when each copy was last used, and whether the game reports a cloud/local status. A sync conflict needs its own investigation; keep both candidates intact while you identify the copy the game actually uses.

Find the Linux or dedicated-server save root#

Iron Gate’s official dedicated-server manual lists these defaults for the server process:

Windows: ../%USERPROFILE%/AppData/LocalLow/IronGate/Valheim
Linux:   ~/.config/unity3d/IronGate/Valheim

The Linux path is relative to the account running the server. A system service may run as a different user than the one you use in a terminal. The manual’s -savedir argument overrides the default root for worlds and permission files. If it appears in the active launch line, follow that path instead of checking the default.

ps -ef | grep '[v]alheim_server'

Inspect the actual service or container command if process listing hides arguments. Record the -world and -savedir values, then match the expected world folder under that root. For exact flags and their documented limits, see Valheim dedicated-server launch arguments. Changing -savedir points server activity at a different root; it does not move a world that is already stored somewhere else.

Trace a container save back to its host volume#

A container path only tells you where the server sees a save. To find the durable host copy, match the server’s -savedir value to the container mount that covers it. For example, one documented community image mounts a host configuration directory at /config, while the official Docker script uses a configurable data volume. Those are different setups, so /config is not a universal Valheim path.

docker inspect <container-name> --format '{{json .Mounts}}'
docker inspect <container-name> --format '{{range .Config.Env}}{{println .}}{{end}}'

In the output, find the mount whose container destination contains the active save directory. Its Source is the host path for a bind mount; for a named volume, inspect that volume’s mountpoint using Docker. If the server runs with -savedir /custom-saves but the volume is mounted at /data, you have not found the same path yet. Trace the mapping until both sides refer to the same saved world.

For an unfamiliar image, read its documentation and environment settings before copying. A wrapper may map a config folder, game installation, and backup folder separately. Do not back up only the install directory because it contains the server executable.

Handle Xbox and PC Game Pass saves carefully#

An Xbox console save is not a Windows path you can browse from File Explorer. Iron Gate documents one PC access route: launch Valheim from the Microsoft Store on the same account that owns the Xbox save. Its FAQ does not document a console export command or a per-app folder to copy. Do not download a random “Xbox save” directory recipe and treat it as an official path.

If you own the PC Microsoft Store edition, open Valheim there and check its world list and save-management screen. Community guides describe moving a PC Game Pass world to local storage before looking under worlds_local, but that exact menu flow was not tested for this article and can vary by build. Confirm the world appears in the PC game before treating a folder as the active copy. Do not assume a Steam install or Xbox app install will silently expose the same files.

If the Microsoft Store PC game does not show the Xbox world, check the account and edition first. Iron Gate says Xbox saves are accessible on PC through the Microsoft Store version; the FAQ does not promise access from the Steam build or a generic Windows package folder.

Confirm the candidate before backing it up#

A folder timestamp is a clue, not a restore test. A copy may be new because the game wrote metadata, while an older-looking copy may still be the one your crew uses. Confirm the world name in Valheim or the server’s -world setting, compare the last-save time shown by the game or panel with the candidate files, and note whether the entry is local or cloud.

Use a copy for any load check. Stop a dedicated server cleanly before copying its world folder; then preserve the untouched original and place the separate copy in a test location. Have the matching Valheim edition recognize the expected world name before relying on it. Do not point a live server at an unverified copy, overwrite the active save, or delete a duplicate to “clean up” the list. The wrong-world troubleshooting guide covers what to check if the server loads a fresh world instead.

Use a server panel when shell access is the blocker#

If the world belongs to a managed server and you cannot inspect its process or volume, use the provider’s file manager or world controls. For example, Game Hosting’s Valheim service includes a World tab that exposes details such as last save and supports import/export controls; the product documentation says it backs up the current world before a replacement. That is useful for server-side file access, while finding and copying a world on your own PC remains a free task.

The control panel describes the server copy; it does not identify which local Steam or Xbox world your friends played last. Compare its world name and last-save time with the crew’s records before replacing anything. If you are not managing a hosted world, stay with the local or cloud path above and keep your original files unchanged.