seedlookout
English

Diamond finder

Enter a Java 26.3 seed and your Overworld coordinates to find predicted places to search for diamonds.

Page updated

Placement predictions · Java 26.3 only · Reviewed ore measurements and limits

Find predicted targets (diamond)

Dimension Overworld

Scans a square of chunks around the center chunk. Coordinates and distances use this dimension; enter Nether coordinates for ancient debris.

Inspect surrounding biomes and predicted structures on the Minecraft seed map.

How the targets compared with the game

In the reviewed Java 26.3 fixtures, 42/42 displayed first origins matched the game, while only 38/42 nearby windows contained diamond ore. We reviewed these comparisons on October 2, 2026 in fresh official Java 26.3 worlds, using three fixed seeds chosen as baseline, control and boundary cases. Each window reaches four blocks from its origin along X, Y and Z.

A target is therefore a dependable place for a placement attempt to start, but 4 of the 42 checked windows held no diamond ore at all. The counts describe those fixtures, not a success rate for every seed.

Diamond targets compared with the gamePlacement origin matched the game: 42 of 42 (100%). Window held diamond ore: 38 of 42 (90%).
Diamond targets compared with the game. Each bar shows how many of the 42 checked targets passed a test, as a share of all checked targets (the outline). We made these comparisons on October 2, 2026 in fresh official Java 26.3 worlds for 3 fixed seeds; each window reaches 4 blocks from its origin along X, Y and Z. The counts describe those fixtures, not a success rate for every seed. Chart by SeedLookout. Data: Reviewed ore measurements. © 2026 SeedLookout.

Our October 12 review of the Java 26.3 finders rechecked the current implementation in 135 comparisons, including selected ore targets. Its two partial results were a terrain-flatness check and an island check, not ore.

Read the ore measurements for the fixtures and replay links, our ore finder accuracy article for how to use a target in your world, and the latest Java 26.3 finder review.

What the targets mean

The finder follows the seeded placement rules for the first attempt from each of the four diamond features in each chunk. Further attempts are omitted because earlier terrain checks can affect their random sequence.

A target is an ore feature’s placement origin. The vein can form nearby, and the origin itself can contain no diamond ore. Terrain, air exposure, caves, replacement blocks and later features have not been reconciled.

Each target’s label names its feature. The table shows what each label means in Java 26.3 and how many attempts the game makes per chunk. The finder lists only the first attempt of each feature: at most four of a chunk’s 13 attempts, or 14 when the large feature passes its 1-in-9 check.

Diamond ore features in Java 26.3 generation, from the finder’s engine
FeatureAttempts per chunkHeight rangeChance a block next to air is skipped
Small diamond7Y −144 to 16, peaking at −6450%
Medium diamond2Y −64 to −4, any height equally50%
Large diamond1 in 9 chunksY −144 to 16, peaking at −6470%
Buried diamond4Y −144 to 16, peaking at −64Always

These are the Java 26.3 ore settings in the finder’s engine. The game comparison checked target origins and nearby ore, not each setting separately.

By the engine’s height rule, the small, large and buried features peak at Y −64, so roughly half of their attempts start below the world. The finder leaves those out, which is why most chunks show fewer than four targets.

Start heights of Java 26.3 diamond placement attemptsSmall, large and buried diamond: from Y −144 to 16, most likely at Y −64 (1.2% per level). Medium diamond: any height from Y −64 to −4, 1.6% per level. 49.4% of triangular attempts start below Y −64 and are left out.
Start heights of Java 26.3 diamond placement attempts. Chance that one placement attempt starts at each height, per one-block Y level, for the four diamond features as set in the finder’s engine. The small, large and buried features (solid line) use a triangular rule from Y −144 to 16 that peaks at Y −64; the medium feature (dashed line) picks any height from Y −64 to −4 equally. Attempts that would start below the world bottom at Y −64 (hatched) are left out by the finder: 49.4% of each triangular feature’s attempts. These are model settings for Java 26.3; the game comparison checked target origins, not each setting. Chart by SeedLookout. Data: Version-pinned generation models. © 2026 SeedLookout.

The last column explains many empty windows: a diamond block that would touch air can be skipped, and buried veins never touch air. The finder does not model air, caves or aquifers, so it cannot tell how much of a vein survived.

Use the generation version

Choose the version that generated the chunks you plan to mine. Upgrading an older world to 26.3 does not regenerate its existing chunks. This model covers standard Java 26.3 generation; custom data packs, superflat worlds and Bedrock are unsupported.

  1. Enter your seed and Overworld X and Z coordinates.
  2. Choose a chunk radius and run the prediction.
  3. Copy a target’s X, Y and Z, then inspect the surrounding area in game.

Mining around a target

  1. Run the finder from your current position. Results are sorted by horizontal distance from the center X and Z, so the first rows are the closest targets.
  2. Go to the target’s X and Z, then dig down to its Y. In Java Edition, press F3 to see your coordinates.
  3. Open up the blocks around it. Our comparison looked four blocks out along each axis, and that range held diamond ore for 38 of 42 checked targets.
  4. If the area is empty, confirm the seed and generation version, then move on to the next target.

Most of a chunk’s attempts are not listed, so the rock between targets can still hold diamonds.

Diamond finder FAQ

What is the best Y level for diamonds?

In the engine’s height rules, three of the four features favour the lowest layers and the medium feature spreads evenly from Y −64 to −4, so attempts are densest just above the bedrock floor. The Minecraft Wiki puts the peak for placed ore at Y −58 and −59. A target’s own Y gives you a placement origin to inspect; our comparisons did not measure mining yield against a fixed-level strategy.

Does the finder show every diamond in a chunk?

No. It shows the first attempt of each of the four features, at most four of the chunk’s 13 or 14 attempts. Later attempts depend on terrain checks the finder does not run, and it does not predict which blocks become ore.

Does it work for Bedrock or older Java worlds?

No. It models standard Java 26.3 generation only. Chunks generated by an older version keep their old ore after an upgrade, and Bedrock Edition, custom data packs and superflat worlds are not supported.

Sources

Our evidence is the reviewed finder measurements and the Java 26.3 ore settings in the finder’s engine. Facts checked against these Minecraft Wiki revisions: Diamond Ore and Bedrock. We have not checked those facts separately in game.

SeedLookout drafted this page with AI assistance, working from our own code and data and the facts cited here. See How SeedLookout is made for our methods and who runs the site.

For Nether mining, open the ancient-debris finder.

← All world tools