Do old Valheim worlds survive 1.0? Server size, cross-save limits, the 1.0.12 banlist fix, the item-stand warning and Iron Gate’s default_old Switch 2 workaround.<\/p>","protected":false},"author":1,"featured_media":5478,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[883],"tags":[],"blog_tag":[],"class_list":["post-5469","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-valheim"],"acf":{"redactor":[{"acf_fc_layout":"text","text":"
Your old Valheim<\/a> worlds and characters survive 1.0: Iron Gate's 1.0 FAQ states that old saves stay where you last left them and remain playable, and that a pre-1.0 world still receives new content<\/a>. The catch is biome generation, which only works properly in areas you have not explored yet, which is why the studio recommends starting over. This guide covers the save rules, the 1 \u2013 10 player server limit, the cross-save scope, the 1.0.12 banlist and item-stand fixes, and the exact TL;DR<\/p> Valheim 1.0 landed on 9 September 2026 across Steam (Windows, Linux, Mac), the Mac App Store, Humble, the Microsoft Store, Xbox One, Xbox Series X|S, PlayStation 5 and Nintendo Switch 2. For anyone running a world with friends, four things matter: the world save, the character save, how many people can be in it, and which platforms can reach each other. Valheim is developed by Iron Gate, with Coffee Stain Publishing as publisher. Crossplay at 1.0 was announced as covering all platforms, which is a different thing from save sync. Our reading of third-party host documentation is that 1.0 also replaced the old Iron Gate's own Iron Gate's save-system FAQ on Steam<\/a> is the document to read here, because it settles the question the 1.0 FAQ does not: a PC save lives in one of two places, and which one decides how you back it up. With Steam Cloud on (the default), worlds and characters are stored under Two consequences follow directly from that FAQ. First, a dedicated server reads local files only<\/strong>: cloud saves are bound to your Steam account, so a world you want to host must be moved to local before you copy it. Second, if the world you are looking for is not in Consoles are the hard wall: the 1.0 FAQ<\/a>'s only cross-platform save statement is the Xbox-to-PC route via the Microsoft Store build, and it says there is no sync beyond that. A PS5 or Switch 2 world cannot be lifted onto a dedicated server; the server is the practical way to keep one shared world for a mixed-platform group.<\/p>"},{"acf_fc_layout":"table","headers":[{"header_text":"Source"},{"header_text":"What you get"},{"header_text":"Requirement"},{"header_text":"Who it suits"}],"rows":[{"cells":[{"cell_text":"Local PC world folder"},{"cell_text":"The full world you can copy, back up and upload "},{"cell_text":"Steam, Humble or a local install on PC or Linux "},{"cell_text":"Anyone hosting their own group"}]},{"cells":[{"cell_text":"Dedicated server save directory"},{"cell_text":"One persistent world every platform joins into "},{"cell_text":"Server stays on the same build as clients "},{"cell_text":"Groups split across PC and console"}]},{"cells":[{"cell_text":"Xbox to PC (Microsoft Store)"},{"cell_text":"Access to your Xbox saves from PC "},{"cell_text":"The PC copy must be launched from the Microsoft Store "},{"cell_text":"Game Pass and Xbox players"}]},{"cells":[{"cell_text":"PS5 or Switch 2 save"},{"cell_text":"No cross-platform sync is offered "},{"cell_text":"Not applicable "},{"cell_text":"Nobody \u2014 plan around it"}]}],"size":"small"},{"acf_fc_layout":"title","heading":"Best Way to Back Up and Move a Valheim 1.0 World","tag":"h2"},{"acf_fc_layout":"image","image":5476,"caption":"Illustration: a 1.0 world moves as one folder \u2014 copy all of it, with the server stopped.","alt":"A Viking carries a heavy chest across snow toward a longhouse \u2014 the whole world folder travels together"},{"acf_fc_layout":"text","text":" The save format itself is documented by Iron Gate, not by hosters: the Patch 0.221.13 announcement<\/a> introduced it \u2014 a world is no longer a Keep, restart, or restart with a new character?<\/strong> Three different decisions, and the 1.0 FAQ<\/a> backs none of them as the \"right\" one. Keep the old world<\/em>: free, and the studio says old saves keep receiving new content \u2014 but Deep North generation only works properly in ground you have not explored, so a heavily charted far north stays as it was. New world, same character<\/em>: you keep skills, gear and inventory, lose nothing but the map, and get clean generation; this is the middle path most groups miss. New world, new character<\/em>: the studio's recommendation for \"the best possible experience\", and the only route where achievements track a full run \u2014 the FAQ says stats count from the moment you install 1.0. How long each costs you is your own play speed; we are not going to invent a number. Our guide to what each Forsaken boss gates<\/a> is the order you would be repeating.<\/p> Warning<\/p> 1.0.12 stops items on armour stands and item stands losing durability and upgrade level \u2014 and the two official write-ups word the condition differently. The Steam post says the fix holds \"IF the world has not yet been loaded in the 1.0 update\"; the same hotfix note on valheim.com<\/a> ties it to whether you have already been near the stands since 1.0. Either way the studio's advice is the same: do not take high-level items \u2014 fish, weapons, armour \u2014 off stands without a backup if you have played on 1.0, until the better fix it is \"looking into\" ships.<\/p><\/div>"},{"acf_fc_layout":"table","headers":[{"header_text":"Method"},{"header_text":"Speed"},{"header_text":"Effort"},{"header_text":"Best for"}],"rows":[{"cells":[{"cell_text":"Copy the whole world folder offline"},{"cell_text":"Minutes"},{"cell_text":"Low, but manual every time "},{"cell_text":"Before any update or branch switch "}]},{"cells":[{"cell_text":"Host panel or scheduled backup"},{"cell_text":"Automatic"},{"cell_text":"Setup once "},{"cell_text":"Groups playing most evenings "}]},{"cells":[{"cell_text":"Upload a local world to a server"},{"cell_text":"One transfer"},{"cell_text":"Medium \u2014 whole folder, correct save path "},{"cell_text":"Moving a solo world into co-op "}]},{"cells":[{"cell_text":"Pre-1.0 world conversion"},{"cell_text":"One load"},{"cell_text":"Low, but one-way in practice "},{"cell_text":"Reviving an Early Access save "}]}],"size":"small"},{"acf_fc_layout":"title","heading":"Switch 2 Crossplay: The default_old Workaround Step by Step","tag":"h2"},{"acf_fc_layout":"text","text":"\n Due to an unforeseen issue the 11 September 2026 hotfix could not be uploaded to Switch 2, so crossplay between Switch 2 and other platforms is not currently supported. The official post gives one workaround, and it only covers Steam and Switch 2, including a dedicated server. There is no workaround for crossplay between PS5 or Xbox and Switch 2 at the moment.<\/p>\n\n\n\n What you lose: on 1.0.12 shipped on Steam on 11 September 2026 alongside 1.0.10 for all platforms, and Iron Gate states the fixes are fully crossplay compatible and will be extended to all platforms in an upcoming hotfix pushed out as soon as possible. No rollout date has been announced for Xbox, PS5 or Switch 2.<\/p>\n\n\n\n On the launch build the lists only accepted the new V_ format; 1.0.12 makes both formats work. Our reading of admin reports and host documentation is that the working ID on 1.0 is the V_ prefix plus the existing SteamID64 as shown in the in-game F2 panel, and that a bare SteamID64 with no prefix is no longer accepted. Treat the permitted list with respect: third-party documentation reports that the moment it contains a single ID it becomes a strict allowlist that refuses everyone else, so a half-finished ID edit can lock out your whole group.<\/p>\n\n Tip<\/p> Copy the ID exactly as the in-game F2 panel prints it rather than converting between formats yourself, and on a pre-1.0.12 build expect Steam_ entries to be ignored entirely.<\/p><\/div>\n\n 1.0.12 added a devcommand that opts a character back into achievements even after devcommands or mods were used: Iron Gate has not said whether the item-stand bug affects console players who already loaded a world in 1.0, nor scoped or dated the better fix it is looking into. The opt-in devcommand is Steam-only as of 11 September 2026, and the notes do not say the underlying cheat mark is deleted.<\/p>\n\n"},{"acf_fc_layout":"table","headers":[{"header_text":"Fix"},{"header_text":"Where it applies"},{"header_text":"Why it matters"}],"rows":[{"cells":[{"cell_text":"Banlist and whitelist accept old IDs"},{"cell_text":"1.0.12, Steam "},{"cell_text":"Steam_123456789 entries work again alongside V_123456789 "}]},{"cells":[{"cell_text":"Item stands keep durability and upgrade level"},{"cell_text":"1.0.12, only if the world has not been loaded in 1.0 "},{"cell_text":"Protects stored endgame gear on untouched worlds "}]},{"cells":[{"cell_text":"Forge of Potential recipe unlocks"},{"cell_text":"1.0.12, Steam "},{"cell_text":"Stops recipes unlocking that should not "}]},{"cells":[{"cell_text":"Unloaded-zone crash"},{"cell_text":"1.0.12, Steam "},{"cell_text":"Fewer drops on a busy server "}]},{"cells":[{"cell_text":"Deep North heavy armour repair"},{"cell_text":"1.0.10, all platforms except Switch 2 (hotfix not yet uploaded there)"},{"cell_text":"Endgame armour is maintainable again "}]}],"size":"small"},{"acf_fc_layout":"title","heading":"Common Misconceptions About Valheim 1.0 Saves and Crossplay","tag":"h2"},{"acf_fc_layout":"image","image":5477,"caption":"Illustration: Familiar ground borders land nothing has touched yet","alt":"Explored Valheim coastline beside untouched northern land \u2014 new biome generation only appears in ground you have not visited"},{"acf_fc_layout":"text","text":"\n\n It does not \u2014 the FAQ's answer to what happens to your saves is \"Nothing\", and old worlds keep receiving new content. The real limit is generation: new biome content only appears properly in ground you have not explored, which is why the studio still recommends a fresh start. Decide that before you sail north, not after. If you are keeping the old world, our Deep North materials checklist<\/a> is the shopping list for what is up there.<\/p>\n\n Crossplay was announced as supported between all platforms, but save access is far narrower: Xbox saves can be reached from a PC only when the game is launched from the Microsoft Store, and the FAQ states there is no cross-platform sync beyond that. And right now crossplay itself has an exception \u2014 Switch 2 is cut off after the hotfix, with a Steam-side workaround only.<\/p>\n\n There is no official mod support, no console mods and no Steam Workshop for 1.0, and Iron Gate cannot guarantee any mod works at release. Community loaders did rebuild for 1.0 \u2014 third-party data lists BepInExPack_Valheim 5.4.2350 and Jotunn 2.30.0 published on 9 September 2026 \u2014 but that is unofficial infrastructure, not support. Console clients cannot install mods, but that does not make every modded server PC-only: the community Valheim Modding wiki<\/a> separates server-side mods, which vanilla clients (including Xbox) can join, from mods every player must install. Check each mod's page for that, for its 1.0 version, and for crossplay support before you decide. Sources conflict on whether enabling crossplay stops BepInEx loading: one host's documentation says mods will not run with crossplay on, another says the flag only changes the matchmaking backend and the breakage is mods assuming SteamID64 identities. No Iron Gate statement settles it, because mods are unsupported.<\/p>\n\n"},{"acf_fc_layout":"title","heading":"Our Take: Keep the Old World or Start Over?","tag":"h2"},{"acf_fc_layout":"text","text":" Our Take<\/p> Back up the folder, then choose one of three paths on purpose.<\/strong><\/p> Keep the old world if your group's far north is largely uncharted \u2014 old saves keep receiving content and nothing forces a restart. Start a new world on your existing characters if you want clean Deep North generation without regrinding skills and gear; that is the option Iron Gate's FAQ neither pushes nor forbids, and it suits most groups. Start completely fresh only if you want the full achievement run. The server side is in decent shape: 1\u201310 players as before, crossplay on every platform but Switch 2 for now, and 1.0.12 fixing the ID formats that broke whitelists. The two things that should slow you down are the item-stand warning and the Switch 2 gap, and both are handled the same way \u2014 an offline copy of the whole world folder before you touch anything, and a version check before you blame the server. If you do level a character again, our Valheim skills and death penalty guide<\/a> explains what each death costs on the way.<\/p><\/div>"},{"acf_fc_layout":"text","text":" This table separates what the studio has published from secondary restatements and our own reading. Every link was fetched before publishing.<\/p>default_old<\/code> workaround for Switch 2 crossplay.<\/p>"},{"acf_fc_layout":"text","text":"default_old<\/code> is the only workaround.<\/li>.db<\/code> plus .fwl<\/code> file pair with a folder per world holding chunked data, which changes how you back things up. If you want the wider picture of what shipped, our Valheim 1.0 Deep North update breakdown<\/a> covers the content side.<\/p>\n\n\n\nSteam\\userdata\\<numeric Steam ID>\\892970\\remote<\/code> \u2014 a folder the FAQ says is \"not meant to be manipulated manually\". With Steam Cloud off, they sit locally in C:\\Users\\<you>\\AppData\\LocalLow\\IronGate\\Valheim\\worlds_local<\/code> (Linux: ~\/.config\/unity3d\/IronGate\/Valheim\/worlds_local<\/code>), with characters in characters_local<\/code> next to them. The game shows an icon under each character and next to each world telling you whether that save is cloud or local, and the world menu has Move to Local<\/strong> \/ Move to Cloud<\/strong> buttons \u2014 every move writes a backup, which the FAQ notes are never deleted automatically.<\/p>worlds_local<\/code>, it is almost certainly on the cloud \u2014 press Move to Local in the world list rather than hunting through userdata<\/code>. On a dedicated server the folder is whatever -savedir<\/code> points at; without that flag it is the same LocalLow \/ .config path, per the official dedicated-server guide<\/a>.<\/p>.db<\/code> + .fwl<\/code> pair but a folder in which the world is split into chunks, only changed chunks are written on each save, backups get their own folders, and \"when loading a world that is not chunked, a backup is made first\". That is why a 1.0 world must be moved as the whole folder<\/em>: copy half of it and the server quietly generates a fresh map under the same name.<\/p>Moving a world onto a dedicated server, in order<\/h3>
-backups 4<\/code>, -backupshort 7200<\/code> and -backuplong 43200<\/code> are the automatic defaults per the official dedicated-server guide<\/a> (one 2-hour backup and three 12-hour ones) \u2014 keep your own copy anyway.<\/li>-savedir<\/code>, or the default LocalLow \/ .config path if you did not set one.<\/li>-world \"<exact world name>\"<\/code> \u2014 the guide says an existing world of that name is loaded, and a new one is created if the name does not match. A typo here is the other way people end up on a fresh map.<\/li>default_old<\/code> you are playing without the 1.0.10 and 1.0.12 fixes, so the bugs those patches addressed may still be present \u2014 including the item-stand and Forge of Potential fixes and the unloaded-zone crash fix. Note also that the Xbox build of the all-platform hotfix is listed as 1.0.11 but is identical to 1.0.10, which is worth knowing if you are comparing version numbers across a mixed group.<\/p>\n\n"},{"acf_fc_layout":"steps","intro":"The four steps below are Iron Gate's own, from the 11 September Steam post; the first and last lines are ours.","steps":[{"title":"Back up the world folder first","description":"Take an offline copy of the whole world folder before switching branches \u2014 a world already opened on 1.0 is in the new folder format and cannot be read by an older build.","image":null},{"title":"Open Properties in Steam","description":"Right-click Valheim (or Valheim Dedicated Server) in your Steam library and select \"Properties\u2026\".","image":null},{"title":"Open the Game Versions & Betas tab","description":"Go to \"Game Versions & Betas\" in the side tabs.","image":null},{"title":"Pick default_old","description":"Choose \"default_old\" from the list on the right and close the window.","image":null},{"title":"Wait for the game to update, then check the branch","description":"Let Steam finish downloading the branch, then confirm every machine in the group is on the same branch \u2014 default or default_old \u2014 because a default_old client cannot read a world already saved in the 1.0 folder format and will not see a default server. Within a branch, Iron Gate states 1.0.12 stays crossplay compatible with the 1.0.10\/1.0.11 builds on other platforms, so a build-number difference alone does not block a join. Do the same branch check for the Dedicated Server app if you host one.","image":null}]},{"acf_fc_layout":"title","heading":"Banlist, Whitelist and Achievement Fixes in 1.0.12","tag":"h2"},{"acf_fc_layout":"text","text":"\nAdmin check: which player ID format your lists use<\/h3>\n
Getting achievements back after devcommands<\/h3>\n
yesiuseddevcommandsbutiwantmyachievementsanyway<\/code>. Iron Gate leaves it to your own judgement whether to activate it. The patch also added a popup that makes it clearer when achievements can be received again after being temporarily disabled. Our reading of admin documentation is that this is a client-side console command each affected player runs on their own machine, with nothing to set on the server. The FAQ's underlying cheat-flag rules \u2014 spawn flagging character and world, freefly as an exception, spawned items causing a temporary cheat state \u2014 are covered in our breakdown of how devcommands lock achievements<\/a> rather than repeated here.<\/p>\n\nWhat is still unanswered<\/h3>\n
Myth: 1.0 wipes or breaks your old world<\/h3>\n
Myth: crossplay means cross-save<\/h3>\n
Myth: 1.0 added mod support or Steam Workshop<\/h3>\n
Sources and Confidence<\/h2>
Claim<\/th> Where it comes from<\/th> Status<\/th><\/tr><\/thead> Old saves survive 1.0; biome generation only works in unexplored areas; 1\u201310 players; cross-save only Xbox\u2194PC via Microsoft Store; no mod support or Workshop<\/td> 1.0 FAQ<\/a> (valheim.com)<\/td> Official<\/td><\/tr> Cloud vs local save locations, Move to Local\/Cloud, backups on every move, dedicated servers read local files only<\/td> Iron Gate's save-system FAQ on Steam<\/a><\/td> Official<\/td><\/tr> 1.0 world format: folder of chunks, only changed chunks saved, backup before converting an old world<\/td> Patch 0.221.13 announcement<\/a> (Steam, 6 May 2026)<\/td> Official<\/td><\/tr> -world<\/code>, -savedir<\/code>, -backups<\/code> \/ -backupshort<\/code> \/ -backuplong<\/code> defaults<\/td>official dedicated-server guide<\/a> (valheimgame.com)<\/td> Official<\/td><\/tr> default_old workaround for Steam\u2194Switch 2 crossplay, incl. dedicated server; no workaround for PS5\/Xbox\u2194Switch 2<\/td> hotfix 1.0.10 & 1.0.12 post<\/a> (Steam, 11 September 2026)<\/td> Official<\/td><\/tr> 1.0.12 banlist\/whitelist accept Steam_ and V_ IDs; achievements opt-in command; Steam-only for now, consoles \"as soon as possible\", no date<\/td> hotfix 1.0.10 & 1.0.12 post<\/a><\/td> Official<\/td><\/tr> Item-stand fix condition worded differently in the two official write-ups<\/td> hotfix 1.0.10 & 1.0.12 post<\/a> vs the same hotfix note on valheim.com<\/a><\/td> Official \u2014 sources differ<\/td><\/tr> Server-side mods can be joined by vanilla clients; client mods cannot<\/td> Valheim Modding wiki (community)<\/a><\/td> Community<\/td><\/tr><\/tbody><\/table>"},{"acf_fc_layout":"faq","items":[{"question":"Do I need a new world to see the Deep North in 1.0?","answer":"No \u2014 old worlds receive new content, but biome generation only works properly in areas not yet explored, and Iron Gate recommends starting over for the best experience. You can head straight for the Deep North on an old save; the studio's answer is still that it recommends starting over. "},{"question":"How many players can join a Valheim 1.0 server?","answer":"The FAQ states 1.0 is a game for 1 \u2013 10 players, the same as before. "},{"question":"Can Switch 2 players join my server right now?","answer":"Not on the patched build \u2014 the hotfix could not be uploaded to Switch 2, so crossplay with Switch 2 is not currently supported; Steam players and a Steam dedicated server can roll back to default_old to play with them, losing the 1.0.10 and 1.0.12 fixes. There is no workaround for PS5 or Xbox with Switch 2. "},{"question":"When do the 1.0.12 fixes reach consoles?","answer":"Not stated \u2014 Iron Gate says the fixes are crossplay compatible and will be extended to all platforms in an upcoming hotfix pushed out as soon as possible, and secondary coverage flags that no rollout date has been announced. "},{"question":"My whitelisted player cannot connect after 1.0 \u2014 what do I check?","answer":"Check the ID format first: the launch build only accepted new V_ IDs and 1.0.12 made old Steam_ IDs work again, so update the server before editing anything. Our reading of admin documentation is to paste the ID exactly as the in-game F2 panel shows it, and to remember that a permitted list containing even one entry becomes a strict allowlist that refuses everyone else. "}]}],"bottom":[{"acf_fc_layout":"more_articles","heading":"","posts":[],"count":10},{"acf_fc_layout":"chat","heading":""}],"meta_description":""},"_links":{"self":[{"href":"https:\/\/neonsect.com\/es\/wp-json\/wp\/v2\/posts\/5469","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/neonsect.com\/es\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/neonsect.com\/es\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/neonsect.com\/es\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/neonsect.com\/es\/wp-json\/wp\/v2\/comments?post=5469"}],"version-history":[{"count":2,"href":"https:\/\/neonsect.com\/es\/wp-json\/wp\/v2\/posts\/5469\/revisions"}],"predecessor-version":[{"id":5473,"href":"https:\/\/neonsect.com\/es\/wp-json\/wp\/v2\/posts\/5469\/revisions\/5473"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/neonsect.com\/es\/wp-json\/wp\/v2\/media\/5478"}],"wp:attachment":[{"href":"https:\/\/neonsect.com\/es\/wp-json\/wp\/v2\/media?parent=5469"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/neonsect.com\/es\/wp-json\/wp\/v2\/categories?post=5469"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/neonsect.com\/es\/wp-json\/wp\/v2\/tags?post=5469"},{"taxonomy":"blog_tag","embeddable":true,"href":"https:\/\/neonsect.com\/es\/wp-json\/wp\/v2\/blog_tag?post=5469"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}