Java vs Bedrock Seeds — What Changes Between Editions
By the ChunkScan Team · Updated June 2026
Java and Bedrock use the same seed number system for terrain generation, but structures land in different places. A seed that gives you a village at spawn in Java might put that village 300 blocks away in Bedrock — or not generate it at all. We scan both editions separately: over a million Java seeds and over 500,000 Bedrock seeds for Minecraft 26.3, 26.2, 26.1 and 1.21.
What actually matches between editions?
Since Minecraft 1.18, Java and Bedrock share the same terrain and biome generation algorithm. If you enter the same seed in both editions on the same version, the mountains, rivers, oceans, and biome boundaries will be nearly identical. The big landscape is the same. What differs is everything built on top of that landscape — villages, temples, portals, strongholds, and other structures use edition-specific placement code, so they end up in different locations or may not generate at all.
Why do structures differ between Java and Bedrock?
Structures in Minecraft are placed using a separate system from terrain generation. Each edition has its own structure spacing, salt values, and placement rules. A village in Java uses different chunk-level calculations than a village in Bedrock, even on the same seed. This means a seed with a perfect village-and-portal start in Java could have neither structure nearby in Bedrock. This is not a bug — it is how the two codebases have always worked.
Seed number format: 64-bit in both editions
Both editions use 64-bit seed numbers, which means seeds can be extremely large positive or negative numbers, and Bedrock keeps all 64 bits. Terrain and biomes follow the whole number in both editions, so even a long Java seed gives the same landscape on Bedrock. Bedrock places villages and most other structures from the last 32 bits of the seed, which is one more reason they land somewhere else. A text seed becomes the same 32-bit number in both editions. ChunkScan handles each edition with its own database. When you search Java seeds, you only see Java results, and vice versa.
How to use ChunkScan for cross-edition checking
If you find a great seed in one edition, it is worth checking the other. Type it into the box at the top of this page and open it on each edition — or open it in the Seed map, pick the other edition and press Explore. The terrain and biomes will look similar, but pay attention to structure distances — they will almost certainly be different. Some players check both editions and pick whichever places the structures more conveniently for their plans.
Version differences within the same edition
Even within Java or Bedrock, seeds can change between Minecraft versions. A village that exists in 1.20 might not generate in 1.21 if the structure placement rules were adjusted. Stronghold positions can shift, new structure types like trial chambers only exist in newer versions, and biome boundaries can move slightly. Always match the version selector to the version you will actually play. Our database covers Minecraft 26.3, 26.2, 26.1 and 1.21 for both editions.
Which structures are most affected?
Villages and ruined portals tend to be the most noticeably different between editions because players check them first. Strongholds also shift significantly — the average stronghold distance in our Java scans is about 1,686 blocks, but this varies by edition and version. Ocean monuments and mansions are affected too, though their rarity (mansions appear in only 4.8% of seeds) means most players encounter the edition difference less often. The safest assumption is to treat every structure position as edition-specific.
Our recommendation
Pick your edition first, then search. Do not copy a seed from a Java list and assume it works in Bedrock. The terrain will look right, which makes the missing village or moved portal even more frustrating. ChunkScan scans each edition independently using the correct generation libraries, so every result you see has been verified for the platform you selected.