A seed is an instruction, not a saved world
Minecraft uses a seed to initialize its world-generation rules. The game version matters because terrain and structure rules change over time. Biomer asks for both values, then evaluates the corresponding generator before any blocks are placed.
This makes the map useful for planning a new world, verifying a coordinate, or understanding why a familiar seed looks different after a version change.
Generation stays in your browser
The map engine is compiled from Rust and Cubiomes to WebAssembly. Work is distributed across browser workers, keeping the interface responsive while visible map tiles are calculated in parallel.
Your seed is processed on your device. Biomer does not require an account or a server round trip to render the map.
Only the view is calculated first
Instead of generating an enormous square upfront, Biomer prioritizes the tiles closest to the viewport and quietly prefetches the next ring. The result is a fast first render and a natural pan-and-zoom experience.
A bounded in-memory cache retains recently viewed tiles while releasing distant ones. That keeps repeated pans smooth without allowing memory use to grow endlessly.
Use the map to make a practical decision
Start at spawn, identify the biome or landmark that matters most, and then inspect the nearby area at a useful zoom level. This turns an unfamiliar seed into a concrete plan: where to begin a base, which direction to travel, or whether the seed fits the kind of world you want to play.
When you are comparing several seeds, keep the game version constant and save the coordinates that stand out. You can return to a promising area later or send the same map state to a friend, without trying to reproduce the view by hand.