seedlookout
English
All articles

Why we started SeedLookout

A woodland mansion on a tall stone base above a river, in dark forest with red mushrooms and snowy mountain peaks behind. In-game screenshot, Java 1.20.1.

SeedLookout is a catalogue of Minecraft seeds that we have loaded in their listed game version. Each listed location has a check in that version, within the horizontal and vertical limits explained below, and every screenshot on the page comes from the game itself. We started building it at the end of September 2026. When we published this post on 30 September 2026, it had 116 seeds checked in game: 106 for Java 26.3 and 10 for Java 1.20.1.

SeedLookout also has a seed map, a seed finder and a set of world tools. They run in your browser.

Why we started

We wanted a seed list with coordinates that hold up when you load the world, and tools that explain how far you can trust their output. Before building anything, we collected 674 public seed listings from 181 pages: two seed sites, three publisher roundups, a creator’s village guide and the seed list from one video. Together they cover 634 different seed numbers. We then checked each listing for the details a player needs to reproduce the world.

Bar charts. Panel a: share of 674 public seed listings missing each detail. World type not stated 542, some feature heights missing 488, no exact release 412, creator not credited 87, version not stated 81, no coordinates 62, Java or Bedrock not stated 28. Panel b: listings by the release family they name. 26.x 329, 1.21 23, 1.20 57, 1.19 11, 1.18 9, 1.0–1.17 148, Alpha and Beta 15, not stated 81, other 1.

Figure 1. What 674 public seed listings left out (a) and which releases they named (b). A listing can have several gaps. Collected from 181 public pages up to 30 September 2026; these are the sources’ own claims, which we had not checked.

The version and edition matter most for reproducing a world. Of the listings, 412 (61%) gave no exact release: 331 named only a release family such as “1.20” rather than an exact release such as “1.20.1”, and 81 (12%) gave no version at all. Another 28 did not say whether the seed was for Java or Bedrock. Coordinates were missing for every feature in 62 listings, and 488 (72%) left out the height of at least one. Four listings contained details that contradicted each other or an earlier source: a seed number with its minus sign dropped, a different seed number for the same coordinates, and two coordinates given two different ways.

The listings also span the game’s whole history: 329 named a 26.x release, 148 named a release from 1.17 or earlier, and 15 named the Alpha or Beta era.

Those gaps matter because a seed does not always give the same world. When an update changes world generation, the same seed can produce different terrain. Java and Bedrock can share a seed’s terrain and biomes and still place structures differently. The About page explains how to match a seed to your game. We treat every listing we collect as unverified, and it stays in our research files, off the site, until we have checked it ourselves.

How a seed gets checked

A Java structure claim with a supplied Y passes when a generated structure piece is within 16 blocks horizontally and 32 blocks vertically of that coordinate. Original candidates with only X and Z were checked horizontally; a surface Y shown for those claims does not establish the structure at that height. Buried portal rows now give a depth from the saved structure bounds and label the old surface point separately. Underground teleports may enter solid terrain, so inspect them in Spectator mode. Cave-biome checks cover a vertical column rather than an exact biome height. Bedrock locate checks establish X and Z, not Y.

The screenshots on a seed page come from the listed release with vanilla textures, and each one carries a caption with the version and coordinates.

A person reviews every check: we confirm each verdict and make sure each screenshot shows the feature it is supposed to show. A seed is published only after that review, and never if a listed location failed.

Two charts. Panel a: outcome of 141 seeds checked in game. Published 116, held for review 11, rejected 14. Panel b: for the 16 listed structures that were not at their listed position, the horizontal distance to the structure the game generated. Desert pyramids, 6, at 536–1,270 blocks. Trail ruins, 4, at 372–908 blocks. Jungle pyramids, 2, at 1,314 and 1,444 blocks. Ancient city 458 blocks, trial chambers 256 blocks, abandoned camp 900 blocks. One mineshaft was at the listed X and Z but 49 blocks deeper than listed. The passing band is 16 blocks.

Figure 2. What the in-game checks found. (a) The latest check of each of the 141 seeds we have checked in game. (b) The 16 listed structures, in the 14 rejected seeds, that the game did not generate where the listing put them, by distance from the listed X, Z to the nearest generated one. The green band shows the 16-block horizontal tolerance. Claims with a supplied Y also needed a generated piece within 32 blocks vertically; original candidates without Y were checked horizontally, so their surface points do not establish structure height. 547 structure claims, up to 30 September 2026.

Of the 547 structures listed for those seeds, 531 passed the check. The other 16 were far from their listed positions: 15 were 256–1,444 blocks from where the game put the nearest one (a median of 900 blocks), and one mineshaft was in the right place on the map but 49 blocks deeper than listed. Desert pyramids and trail ruins account for 10 of the 16. None of the 14 seeds with a misplaced structure is on the site, and the 11 held seeds are waiting for review.

Seed 17108149081942125 in Java 26.3 lists an abandoned camp in dappled forest at X, Y, Z: -176, 73, -256. The listed X and Z fall inside the camp the game generated. This screenshot shows it from the west:

Small tent on a ledge at a lake’s edge, red and orange trees behind and a field of blue ice spikes beyond. In-game screenshot, Java 26.3.

What “checked in game” covers

A check covers the structures and biomes listed on the seed’s page, at their coordinates, in that one version. It does not cover loot, the spawn point or any other version. If you play a seed in a different release, test the locations yourself before you rely on them.

The tools

The seed map shows biomes and predicted structures for Java and Bedrock in the Overworld, Nether and End. The seed finder tests a range of seeds for the biomes and structures you choose for an exact version, and opens each match on the seed map. The world tools read the seed and spawn point from a world file, find slime chunks, build Java superflat presets and estimate a stronghold’s position from two Eye of Ender throws.

The map, the finder, the slime chunks and the stronghold estimate are model predictions, and the pages say so. The finder cannot search every seed and can miss small biome patches. The map is built on open-source Cubiomes forks, with separate Java and Bedrock builds so a Java prediction is never shown as a Bedrock one. Some features are still missing: the map does not predict Java dungeons, for example. The About page lists the gaps we know about.

Update, 15 October 2026: selected Bedrock structure predictions have since been compared with the game. The Bedrock structure study compares the Bedrock 26.50 model with Minecraft Bedrock 1.26.52 on nine seeds across 17 structure types. SeedCard Finder 1.0.2 lists 35 structures the game does not generate there and misses 4. Those comparisons cover the selected seeds and areas; other outputs remain model predictions.

A faster seed finder

The next step for the tools is speed. We are optimizing the publicly available Cubiomes engines that power the map and finder so the same computer can test far more seeds in the same time. That matters most for rare seeds: a search for four witch huts close together, for example, has to rule out about 15 million seeds for every one that matches. A faster engine makes searches like that more practical. The seeds it finds are still model predictions.

We call the faster engine v0.1. It runs only on our own computers; the seed finder on the site uses the current engine. In our first benchmark runs, v0.1 found exactly the same seeds as the site’s own evaluator on every test range, and it was faster in most of the searches we tested:

Bar chart on a logarithmic scale of seeds searched per second for four searches. Village within 256 blocks of spawn on one thread: current site engine 155–242, Cubiomes-style search 465–490, SeedLookout finder v0.1 4,390–4,860. Mushroom fields, stronghold and village near spawn on 16 threads: Cubiomes-style 2,800, SeedLookout finder v0.1 31,000. Village within 256 blocks of 0, 0 on one thread: current site engine 353–611, Cubiomes-style 32,600–34,100, SeedLookout finder v0.1 33,600. Nether fortress and village on one thread: current site engine 2,665–5,440, Cubiomes-style 326,000, SeedLookout finder v0.1 323,000.

Figure 3. Seeds searched per second on four Java 26.3 searches (log scale). “Current site engine” is the evaluator behind today’s seed finder; “Cubiomes-style” is a native search written the usual way with Cubiomes; whiskers span the recorded runs. Preliminary: one short run per setting on one shared workstation (Ryzen 7 7840H) with 30–60% background load, so treat the ratios as indicative.

On a single thread, the search for a village near spawn ran at 155–242 seeds per second with the site’s current engine and about 4,400–4,900 with v0.1, nine to ten times the speed of the Cubiomes-style search. On 16 threads, a rare search for mushroom fields, a stronghold and a village near spawn ran at about 31,000 seeds per second, compared with about 2,800 for the Cubiomes-style search. In the other two searches, v0.1 and the Cubiomes-style search ran at about the same speed. We are continuing to optimize the engine beyond v0.1. We will record a full baseline on an idle machine before quoting firmer numbers.

What comes next

We will keep checking listed seeds and publish only the ones where every listed location is confirmed. We will add more Java releases one version at a time.

The catalogue now also includes a Bedrock plains village, meadow mountain and dappled forest camp, seed 812572768. Its page uses the Bedrock 26.50 generation scope and records checks in Minecraft Bedrock 1.26.52. Those checks cover the locations listed on that page.

You can browse the catalogue and filter it by version. The About page has the full definition of what we check.

SHAREReddit

Seeds in this post

Sources

  1. SeedLookout coordinate and verification scope
  2. SeedCard Finder 1.0.2 Bedrock structure comparison
  3. Seed (level generation), Minecraft Wiki
  4. Java Cubiomes fork used by the seed map (xpple/cubiomes)
  5. Bedrock Cubiomes fork used by the seed map (FragrantResult186/cubiomes-bedrock)