Reviewed September 11, 2026, including that day's platform-specific hotfixes. Backup and group-planning steps are Palpikt's recommendations.
You do not have to delete your old world to play Valheim 1.0. The practical decision is whether to continue a familiar settlement or start a shared progression journey. Preserve the existing save before experimenting, then choose based on the experience you want.
Should you start a new world?
Existing saves continue to work. New biome content generates properly in unexplored areas; Iron Gate nevertheless recommends a fresh playthrough for the fullest experience. Achievement statistics begin with the 1.0 update, so earlier accomplishments may need repeating.
Use these questions to make the decision:
- Do you want discovery or continuity? A fresh world suits a group that wants to learn together. Continuing suits a group attached to its settlement and accumulated work.
- How much of the intended destination was explored before the update? Do not assume a familiar area will rebuild itself with the new biome content.
- Is the group at a similar stage? A veteran's spare equipment can change a newcomer’s progression experience. Agree on whether to share it.
- Does the save depend on mods? Confirm the setup before deciding that a launch problem means the world is lost.
Our recommendation is to preserve a favorite world even if you begin another. Give the new playthrough an unmistakable name and write down its settings. You can make a fresh start without treating the old settlement as disposable.
Make a backup you can identify and restore
A backup is useful only if you can tell which character, world, and game version it belongs to. Before changing the setup, close the game normally and wait for any platform synchronization to finish. For a shared server, have its owner stop it using the supported shutdown process before copying its save data.
Use the game's save-management options and the relevant platform or host instructions. Preserve the complete world data and its associated character data, rather than following an old tutorial that assumes every save is only a pair of files. The 1.0 release uses a chunked world-save system.
For a PC or hosted backup, keep a dated copy outside the active save location. Record the world name, game version, mod profile if any, and the reason for the backup. A short note such as “before first 1.0 session” is much more useful than three folders all called “latest.”
If you test restoration, use a separate location or test setup. Do not overwrite the working save to discover whether your backup is complete. After the test, identify which copy remains the real campaign so that different players do not unknowingly continue different versions.
For a dedicated world, follow the server save and shutdown instructions to locate saves, configure backups, and stop the process with Ctrl+C. Hosts can customize locations, so verify the actual configuration before copying files.
Check mods before opening the important save
Iron Gate does not officially support mods or guarantee compatibility after updates.
Our suggested update sequence is deliberately small:
- Record the mod profile and loader version used by the existing campaign.
- Read each maintainer's compatibility notes for the installed game version.
- Keep a backup of the original save before testing any changed setup.
- Use a disposable test world to check launch, joining, crafting, and the features your group actually uses.
- Return to the campaign only after you understand what the updated profile changes.
Distinguish testing a clean installation from opening a mod-dependent campaign without its mods. The first can help identify a launch problem; the second may alter content you intended to preserve. Do not strip a live world down as a casual troubleshooting step.
If the game fails, capture the version, the action immediately before the failure, and the relevant error message. Change one thing at a time. Repeatedly adding or removing several mods makes it harder to identify what solved the problem.
Achievements: the launch FAQ is not the whole current answer
The launch FAQ describes cheat flags and temporary restrictions, including restrictions associated with spawned items. The September 11 Steam hotfix changes the available options: version 1.0.12 adds an explicit achievement opt-in for previous devcommand or mod use. The announcement says this hotfix's additional changes will reach other platforms later. Check your installed version before assuming the option is present.
For an achievement-focused group, agree on your approach before exchanging items or experimenting with commands. Read the current in-game messages and achievement status. Keep testing worlds distinct from the campaign, and do not use an old guide's blanket “permanently impossible” conclusion without checking whether it predates this hotfix.
Our website checklist is independent of this system. Recording a boss defeat on Palpikt does not unlock a game achievement, and resetting the checklist does not change your save.
Crossplay and shared worlds
Crossplay is supported, but crossplay is not universal save synchronization. The FAQ identifies Xbox and Microsoft Store PC as the supported shared-save pairing; other platforms do not automatically synchronize progress with each other.
Choose who owns the shared world and where backups live. Decide when that person will update it and how the group will know the session is ready. For a small group playing at the same times, simple hosting may suit the schedule; a persistent server adds ongoing administration, so choose it for a concrete need.
If players cannot join after an update, first compare the installed versions and server configuration. Do not diagnose a damaged world from a connection error alone. The September 11 announcement specifically says its platform-specific fixes remain crossplay compatible; delivery timing and the installed build still deserve checking.
Once the setup is settled, use our first-session guide and progress checklist. The Valheim hub also links the progression route and Deep North preparation for returning groups.