Overworld scale 1×
/execute in minecraft:overworld run tp @s 344 64 -1290
The Nether scale 8×
/execute in minecraft:the_nether run tp @s 43 64 -162
Portal Search Range Map
Click inside either pane to drop a second marker (an existing portal) and check whether it falls inside the search circle.
Java vs. Bedrock
| Mechanic | Java Edition | Bedrock Edition |
|---|---|---|
| Search range (Overworld side) | 128 blocks | 128 blocks |
| Search range (Nether side) | 16 blocks | 128 blocks (1,024 Overworld-equivalent) |
| Nether build height | Up to Y=255 (roof at Y=127 is still walkable) | Hard-capped at Y=127 |
| Portals above the roof | Yes, if placed manually | Not possible |
| Coordinate conversion | ÷8 or ×8, Y unchanged | ÷8 or ×8, Y unchanged |
Quick Reference
| Nether distance | Overworld distance | Notes |
|---|---|---|
| 1 | 8 | The base ratio |
| 16 | 128 | Java Nether search range (Overworld-equivalent) |
| 128 | 1,024 | Bedrock Nether search range (Overworld-equivalent) |
| 1,000 | 8,000 | One ice highway segment example |
How portal linking actually works
A Nether portal does not remember which portal it is "paired" with. Every time an entity steps through, the game runs a fresh search centered on the converted coordinates, looking for the closest existing portal within the search radius for that side. If it finds one, it links to that one; if not, it generates a brand-new portal frame nearby and links to that instead. This means the same portal can, in theory, connect to a different destination later if the nearer one gets removed or a closer one gets built.
Why mislinks happen
A mislink happens when some other portal — often one you built ages ago and forgot about, or one generated automatically during an earlier trip — sits inside the converted search radius around your expected destination. The game always prefers the closest candidate it finds in that radius, not necessarily the one you intended, so a stray frame a few dozen blocks away in Nether-space (a handful of blocks after the 8:1 conversion) is enough to hijack the link.
How to fix a mislinked portal
- Stand where you want the new portal to land and read your exact coordinates (F3 on Java, the coordinate display on Bedrock).
- Run those coordinates through the conversion above (÷8 for Overworld→Nether, ×8 for Nether→Overworld, Y unchanged) to find the matching spot on the other side.
- Manually build a portal frame at that exact converted position rather than letting the game auto-generate one.
- Track down whichever stray portal was stealing the link and remove it, or simply ignore it if removing it is not practical.
- Step through in both directions to confirm the link now goes where you expect.
FAQ
How is the destination actually calculated? The game takes your current coordinates, converts them by the 8:1 ratio for the dimension being entered, and searches a fixed radius around that converted point for the nearest valid portal.
Why did a brand new portal appear instead of linking to mine? Your built portal was outside the search radius for that trip, so the game generated a fresh one at the nearest valid location instead of finding yours.
Do the Y coordinates matter for linking? Not for the conversion math — Y carries straight across unchanged — but the receiving portal still needs a legal, unobstructed spot to generate or connect at that height, and on Bedrock nothing can exist above Y=127 in the Nether.
How far apart should two portals be to guarantee they never cross-link? Keep unrelated portals farther apart than the search radius for that dimension — more than 128 blocks apart in the Overworld on either edition, and more than 16 blocks apart in the Nether on Java (128 blocks on Bedrock) — and each pair will only ever find itself.
Uses the game’s exact coordinate math (floor division for Overworld→Nether). Search-range numbers are the standard Java/Bedrock values as of recent versions — double check against your specific server/version if you rely on the exact figures.
Nether portal in Minecraft?
Nether portals in Minecraft?
