Valheim world rules: old generation vs the 1.0 update

If you've played Valheim since early access, your old seeds don't behave the way they used to. The 1.0 update didn't just add the Ashlands — it reworked how the world itself is built. Here's what changed, and what it means for the worlds you already love.

Same string, different world

A seed string is just an input to the generator. When Iron Gate changes the generation algorithm, the same string produces a different map. After 1.0, old seeds regenerate with the new Deep North, the Ashlands, and adjusted Mistlands and Mountains. So that "perfect" meadow start from two years ago will not look the same if you re-roll it today — the string is identical, the world is not. Treat old seeds as nostalgic, not reliable.

Why old screenshots lie

Every guide screenshot, every "best seed" post, every coordinate you bookmarked from before 1.0 is now a historical artifact, not a map. Boss altars shift, biomes redraw, Haldor moves. Don't trust pre-1.0 coordinates for navigation. If you need a current layout, generate the seed fresh in our free seed viewer — just remember its Preview is an in-house approximation of generation, not the exact in-game coordinates you'd measure with a map table in-game.

World size and edges

Valheim worlds are a roughly 10km circle of land and water wrapped in an impassable ocean border. You can sail to the edge, but past it is endless water with no content and a hard world limit — there's no going around. The 1.0 edge rules are unchanged in shape, but the far north is now real buildable Deep North instead of a frozen void, so the useful part of the map grew considerably.

What the generator actually changed

The headline 1.0 edits are the Deep North rebuild and the new Ashlands continent, but the quieter changes matter more for old players: Mountain and Mistlands terrain was reshaped, and the weighting of biomes around spawn was retuned so early worlds feel less cramped. None of that is visible from the seed string alone — it's baked into the game version. That's why two people sharing the same seed on different versions get maps that diverge the moment you leave the Meadows. If you're comparing notes with a friend, confirm you're both on the same patch first.

Reading your current map

If you're unsure whether a world is old or new gen, sail north. Old worlds hit the frozen void at the top; 1.0 worlds open into buildable Deep North with its own resources. That single trip tells you more than any screenshot, and it's the fastest way to decide whether to migrate or simply start fresh on a new seed.

Migrate or restart?

Old worlds keep their original generation but miss everything 1.0 added — no Ashlands, no new Deep North, no updated peaks. That's fine if you just want to keep building your base and your progress. But if you want the full current game, a fresh world is cleaner than porting an old one into new systems. Our map seed vs world seed explainer shows why a world is more than its seed, and the 1.0 Deep North guide lays out exactly what you'd be missing by staying on the old generation. If you'd rather skip the migration debate entirely, browse the curated seed list for worlds already generated fresh on 1.0, so you start with the full map from day one.

Measured case: how far apart two honest answers can be

The version problem is not just old-versus-new — even tools built for 1.0 can disagree with each other, and it is worth seeing by how much. We measured our curated worlds on Atlas, a community tool that runs the genuine 1.0 generator (engine 1.0.12), and compared those numbers against our own preview engine: boss altar distances came out roughly five times closer in the real bake than in our preview, with trader distances off by about a quarter on average. Neither tool is lying; they are two different bakers reading the same recipe with different hands. This is why our seed pages show Preview facts and measured facts as separate lines, and why cross-version claims deserve the same suspicion as pre-1.0 coordinates. When a number matters — a commute, a base plan, a shopping trip — prefer the measured figure and the version stamp behind it.

Keeping old worlds alive: the archive habit

If you are keeping a beloved pre-1.0 world playable, two habits protect it. First, archive the file pair — the .db and .fwl — somewhere off-machine before every update, because version transitions are exactly when corruption and accidents happen. Second, freeze your expectations: the old world keeps its original generation, its old far-north void, and none of the 1.0 content, and that is precisely what makes it a time capsule worth keeping. Players who maintain one nostalgic world and one fresh 1.0 world get the best of both — a museum they can visit and a living map they can grow. The dedicated server guide covers how the file pair travels if you ever want to host the old world for friends.

What stays true across versions

It is easy to come away from a version change thinking nothing can be trusted, but the deepest rules survived 1.0 untouched. The seed still fully determines the world within a version. The biome ring still hardens with distance from spawn, even where its contents were redrawn. Metals still refuse portals, Haldor still sits in one fixed Black Forest spot per world, and the ocean border still ends every map. When old and new players compare notes, these constants are the shared language — the advice that was true in early access and is true on 1.0. Build your plans on the constants, hold the specifics loosely, and version changes become news instead of disasters.

FAQ

Are 1.0 worlds bigger than old worlds?

No — the total size is unchanged. What grew is the usable portion: the far north went from frozen void to buildable Deep North, and the Ashlands became a real continent. Same map, more of it worth sailing to.

Can I update an old world to 1.0 content?

Largely no. An old world keeps its original generation — the new Deep North and Ashlands do not retro-appear in already-visited regions. Old saves remain playable, but the full 1.0 experience means a fresh seed.

How big is a Valheim world?

Roughly a 10 km circle of playable land and water, ringed by an impassable ocean border. Every seed fills that same footprint — the seed decides the arrangement, not the size.

Do coordinates from pre-1.0 guides still work?

No. The same seed string generates different terrain after the update, so old coordinates point at whatever the new generator built there — which could be open water. Treat pre-1.0 coordinates as historical, not navigational.

Sources & further reading