ABOUT SEEDLOOKOUT

Sources, versions and accuracy

Page updated October 23, 2026

SeedLookout is a catalogue of Minecraft seeds with a seed map and a seed finder. The map and finder run a generation model for each game version in your browser.

Who runs SeedLookout

SeedLookout is an independent website. Its pages and articles are published under the SeedLookout name. It is not an official Minecraft service and is not approved by or associated with Mojang or Microsoft.

How SeedLookout is made

We use our own software and AI agents for much of the work. That lets us check far more seeds and game versions than we could by hand, and publish the site in several languages. This is how each part is made.

Seed pages

1. Our seed finder and seed map find candidate seeds and predict where each structure and biome is.
2. Our verifier runs the exact game release in a fresh world: for Java, the official server in Docker and the game client for screenshots; for Bedrock, Bedrock Dedicated Server and the Bedrock game. It records what the game generated at each listed coordinate and keeps the logs, the hash of the server build and a hash of every original screenshot.
3. A person then visits each listed location in the game, guided by those coordinates, and reviews it. Only then is the seed published.
4. Page copy is drafted with AI assistance from that evidence and then edited. It describes only what the checks and screenshots show.

Maps, finders and studies

The seed map and finders run independent generation models: separate builds of open-source Cubiomes libraries for Java and Bedrock, pinned to recorded commits, with a model for each supported game version. We compare their predictions with the game and publish each study, failures included, with its method, sample, date and limits on our research page.

Guides and finder pages

AI research agents gather the facts for structure guides and finder pages. Each brief is researched twice, independently, or checked by a separate reviewing agent; every claim needs a source, and claims the passes disagree on stay out until they are checked. Source research is not a game check, and the pages say which is which.

Translations

Translations are made by an AI translator and checked by a separate AI reviewer, with a terminology dictionary for each language so that game names stay consistent. A translated passage appears only after it passes review; until then the page shows the English text and says so. Native speakers have also reviewed each published language.

Verified in game

Every catalogue seed is verified in game. We check the listed locations and review the in-game screenshots before publication. Seeds that sources report but we have not verified in game stay off the site.

A seed verified in game has each listed structure or biome found at its coordinates in the edition and version on its page, and its screenshots come from that game. Verification covers those locations in that version only, not loot, the spawn point or other versions. 187 seeds are verified in game: Java 26.3 (167), Java 1.20.1 (19), Bedrock 26.50 (1).

A Bedrock seed page names two versions: the seed map model we predicted it with (Bedrock 26.50) and the exact game build we checked it in (Bedrock 1.26.52.3). The map models selected releases, so the two numbers can differ; the game check applies to the build shown.

Java structure coordinates are within 16 blocks horizontally and 32 blocks vertically of a generated structure piece. When a candidate has no height, the verifier initially checks X and Z using the generated surface height; this does not verify the structure at that Y. Buried portal rows use a depth from the saved structure bounds and label the old surface point separately. Underground teleports may enter solid terrain: use Spectator mode to inspect them.

Cave-biome checks cover a vertical column, rather than an exact biome height. Bedrock structure checks use the game's locate result for X and Z; the locate command does not verify Y.

Everything the seed map and seed finder show is a prediction from a generation model. Selected Java 26.3 outputs, and Bedrock structure locations on nine seeds, have been compared with actual game generation; those checks cover the selected cases only. Read the latest Java 26.3 finder review.

Match the generation version

Pick the edition and version that generated the chunks you are looking at. A world upgraded from an older version can mix terrain from several versions. Data packs, experimental features, custom world settings and mods can all change what generates.

The map covers the Overworld, Nether and End in the versions below. Unlisted patches and preview builds may generate differently, and the map does not substitute another version for them.

Java Overworld maps support Large Biomes. Java accepts numeric and text seeds; Bedrock needs the numeric seed. The block property pages label their own data versions.

Biome previews on Java 1.20.1 seed pages are drawn with the 1.20.6 model and labelled with that version. Java 26.3 seed pages link to the seed map's 26.3 model instead.

What the map can tell you

Biome colors show the height slice you selected. Structure markers come from the engine's placement rules and the biome checks it has, so terrain or a later generation step can still stop a predicted structure from generating. Spawn positions are estimates. A structure marker does not promise particular rooms, loot or a safe place to stand.

Terrain shading uses approximate heights. Cave slices sample a density model; they can show open sky and leave out some carvers, aquifers and later features. Ore points sample large ore-vein noise at the selected Y and do not map every ore block that generates. Zoomed-out views and searches sample more coarsely, and dense layers tell you when they reach a computation limit.

Finder distances measure the straight-line separation between X and Z coordinates. Overworld searches start at estimated spawn, which can differ from your actual spawn. Enter your own coordinates to search from somewhere else.

A copied /tp command needs cheats or permission. Its ~ Y value keeps your current height. Check for a safe entrance when a structure is underground or underwater; the predicted X and Z give its horizontal location.

Bedrock results use a separate model. We compared its structure locations with Minecraft Bedrock 1.26.52 at every possible structure location in large areas of nine seeds and corrected it to match. For most structure types it now matches the game there exactly; for the others it lists a few places where the game builds nothing. Terrain, loot, abandoned camps, Nether fossils and dried ghasts were not compared, and other seeds remain predictions. We checked catalogue examples at the listed locations, in the edition and version shown. Other finder results are predictions.

Each distance sample uses 14,000 seeds in Java 26.3 or Bedrock 26.50, with default generation settings and Large biomes off. We asked the finder for ten results per seed. The median is the halfway distance among seeds where it returned a result. Percentages within a distance count all sampled seeds, including those with no result. These percentages describe our sample; the share across all Minecraft seeds may differ.

The Nether samples start at estimated Overworld spawn X and Z divided by 8, with each coordinate rounded down. Distances are in Nether blocks; multiply by 8 for the Overworld equivalent. The figures measure horizontal separation, without estimating your walking route or portal journey.

The End samples start at X 0, Z 0 on the main island. Both sampled models exclude End city starting points less than 1,008 blocks from there, so the 1,000-block distance band falls inside that empty central area. This Bedrock model rule has not been independently checked in game. Searching from an End gateway exit or your own coordinates measures from that point instead.

The Java 26.3 desert temple searches returned a location for 12,328 of the 14,000 seeds. In total, 12,427 searches hit the work limit, including 1,672 with no result. For 1,384 seeds, the first result lay beyond the area fully searched, so a closer temple may have been missed. Fully searched radii ranged from 1,008 to 5,104 blocks. An empty search here does not show that there is no temple within the nominal 50,000-block radius.

Which features the map covers

The layers you can turn on depend on the edition and version. They include major structures, slime chunks, strongholds, mineshafts, biome highlighting, End gateways, geode candidates and some smaller features. Details such as a bastion's type or a predicted End ship appear only when the model provides them.

• Java cave and ravine markers show the chunk where a cave or ravine starts, not its entrance or full path.
• Bedrock dungeon predictions use a partial terrain model. The map does not predict Java dungeons or Java surface lava lakes.
• It also does not predict Overworld fossils, Bedrock Nether fossils, Bedrock dried ghasts, or Bedrock ores and loot.
• The enchanted apple layer checks Java desert temple chests only, not other structures whose chests can hold one.
• The seed finder tests a limited range of seeds against sampled conditions. It cannot search every Minecraft seed, and it can miss small biome patches.

Open generation models

The map uses separate builds of the Java Cubiomes fork and the Bedrock Cubiomes fork. Bedrock has its own random-number and placement rules, so the map never reuses Java predictions as Bedrock results. Build identifiers and licenses are listed in the engine manifest and the open-source credits.

Contact

Questions about the site or corrections to a seed page: contact@seedlookout.com.