Ancient-debris finder
Enter a Java 26.3 seed and your Nether coordinates to find predicted places to search for ancient debris.
Page updated
Placement predictions · Java 26.3 only · Reviewed ore measurements and limits
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, 38/38 displayed origins matched the game, while only 22/38 nearby windows contained debris. 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.
Debris is harder to confirm than diamonds: 16 of the 38 checked windows were empty even though their origins matched. In the seed 0 fixture, both origins matched and both windows held no debris. The counts describe those fixtures, not a success rate for every seed.
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 origins of the two ancient-debris placement features in each chunk. One feature places its origin between Y 8 and 24; the other uses Y 8 through 119.
A target is a placement origin. Ancient debris can scatter nearby, and the origin itself can contain no debris. Terrain, replacement blocks, air exposure and later features have not been reconciled.
| Feature | Height range | Blocks per attempt | Farthest block from the origin, per axis |
|---|---|---|---|
| Large ancient debris | Y 8 to 24, most often near Y 16 | 0–3 | 2 blocks |
| Small ancient debris | Y 8 to 119, any height equally | 0–2 | 1 block |
The block counts and distances come from the scatter rule in the finder’s engine, which follows Java’s ore code; no game check measured them directly. By that rule, a large attempt places nothing one time in four and a small attempt one time in three.
The engine’s settings for both features also discard every block that would touch air, and let debris replace only netherrack, basalt and blackstone. The finder does not look at the blocks around an origin, so it cannot say how many of an attempt’s blocks exist. Together these rules can empty a window around a correct origin.
Use Nether coordinates
Enter X and Z from the Nether. The finder does not convert Overworld coordinates. Choose the version that generated those chunks: upgrading an older world to 26.3 does not regenerate existing chunks. This model covers standard Java 26.3 generation; custom data packs and Bedrock are unsupported.
- Enter your seed and Nether X and Z coordinates.
- Choose a chunk radius and run the prediction.
- Copy a target’s X, Y and Z, then inspect the surrounding area in game.
If you only know an Overworld position, divide its X and Z by 8, or convert it with the Nether portal calculator.
Mining around a target
Use a target’s X, Y and Z as a placement origin to inspect. Our comparison counted debris within four blocks along each axis; it did not measure how much terrain a bed or TNT blast clears, whether a blast exposes every block, or which mining method gives the best yield.
An empty area around a target can mean the attempt placed no debris. Check your seed and generation version before inspecting another origin. The finder does not predict a guaranteed debris block.
Ancient-debris finder FAQ
What Y level is best for ancient debris?
In the engine’s height rules, the large feature’s origins stay between Y 8 and 24 and are most likely near Y 16, while the small feature spreads one attempt across Y 8 to 119. That makes Y 8 to 24 the densest band, in line with the Minecraft Wiki’s figure of Y 16. Each target lists its own Y.
Can I use Overworld coordinates?
No. Ancient debris generates only in the Nether, and the finder reads X and Z as Nether coordinates. Convert an Overworld position first.
Does it work for Bedrock?
No. This finder models standard Java 26.3 generation only. Bedrock Edition has its own debris settings, with five attempts per chunk instead of two according to the Minecraft Wiki.
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: Ancient Debris, Bed and Tutorial: Mining/Ancient debris. 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 Overworld mining, open the diamond finder.