Coordinate Calculator

Convert between Overworld and Nether coordinates. Calculate distances and find midpoints between locations.

Dimension Converter

Nether Equivalent:

X
0
Y
64
Z
0

Distance Calculator

Point A

Point B

3D Distance
141.4
2D Distance (X/Z)
141.4
Midpoint
50, 64, 50

Nether coordinates, and why portals link where they do

The Nether is compressed horizontally by a factor of eight. One block walked in the Nether covers eight blocks of Overworld ground, which is the whole reason Nether highways are worth building. The compression applies to X and Z only — Y is never scaled. An Overworld portal at Y 64 links to a Nether portal at Y 64, not Y 8.

Converting in both directions

Overworld to Nether is a division by eight, floored. Nether to Overworld is a multiplication by eight. The asymmetry is real and worth understanding: division loses information, so the round trip does not always return you to where you started.

OverworldNetherNote
1000, 64, 500125, 64, 62500 ÷ 8 is 62.5, floored to 62
−100, 64, −100−13, 64, −13−12.5 floors to −13, not −12
−1, 64, −1−1, 64, −1Everything from −8 to −1 maps to −1
7, 64, 70, 64, 0Everything from 0 to 7 maps to 0
−104 to −97−13One Nether block covers eight Overworld blocks per axis

Negative coordinates are where most conversions go wrong. Dividing −100 by 8 gives −12.5, and the block containing that position is −13. Calculators that truncate toward zero return −12 instead, putting the portal one block east or south of where it should be. It is a small error that only shows up on one side of the world, which is exactly why it survives so long unnoticed.

The Y axis is the part people forget

Because Y is not scaled, a high Overworld build can be impossible to mirror. The Nether is only 128 blocks tall: five rough layers of bedrock form a ceiling from Y 123 to Y 127, and five more form the floor from Y 0 to Y 4. That leaves roughly Y 5 to Y 122 of usable space.

The Overworld in current versions runs from Y −64 to Y 319. A base at Y 200 converts to a Nether coordinate of Y 200 — which is above the Nether's ceiling. In Java Edition you can build there, because the Nether build limit is 256 and the roof is reachable. In Bedrock Edition you cannot: the Nether build limit is 128, even though the End's is 256 and the Overworld's is 320. A Nether hub design that works on Java can be flatly impossible on Bedrock.

Why two Overworld portals sometimes share one Nether portal

Portals do not store a link. Each time you step through one, the game converts your position, then searches the destination for an existing portal near those coordinates. Arriving in the Nether it searches a 32×32 block square — a 16-block radius — across the full map height. Arriving in the Overworld it searches a 256×256 block square, a 128-block radius. If it finds nothing, it builds a portal, looking for somewhere suitable within 16 blocks horizontally and any distance vertically.

The two radii cover the same real distance, because 16 Nether blocks correspond to 128 Overworld blocks. Before Java Edition 1.16.2 both searches used 128 blocks, so the Nether search reached the equivalent of 1,024 Overworld blocks and routinely captured portals meant for somewhere else. Guides that still quote 128 blocks in both dimensions predate that fix.

The practical consequence: two Overworld portals less than about 128 blocks apart convert to Nether coordinates less than 16 blocks apart, so both will find the same Nether portal and both will link to it. If you want separate destinations, either space the Overworld portals more than 128 blocks apart, or build the Nether portals yourself at the exact converted coordinates so each search finds its own.

Building a link that stays put

  1. Stand in the Overworld portal and note the coordinates.
  2. Convert: divide X and Z by 8 and floor, keep Y as it is.
  3. Go to the Nether and build a portal at exactly those coordinates.
  4. Light both, and step through each once to confirm they find each other.

Building the destination portal yourself is what makes a link reliable. Letting the game generate one puts it wherever the terrain allowed, and if that spot is later blocked or destroyed the next trip generates another one somewhere else.

Distances

The distance figures here are straight Euclidean measurements. The 3D figure includes the height difference; the 2D figure ignores Y, which is the more useful number for surface travel and for working out how far a Nether highway needs to run. The midpoint is simply the average of each axis, rounded to a block.

Sources

Overworld-Nether Coordinate Relationship

In Minecraft, the Nether dimension is spatially compressed relative to the Overworld by a factor of 8. This means that traveling 1 block in the Nether is equivalent to traveling 8 blocks in the Overworld.

Conversion Formulas

To convert Overworld coordinates to Nether coordinates:

Nether X = floor(Overworld X ÷ 8)
Nether Z = floor(Overworld Z ÷ 8)
Y coordinate remains unchanged

To convert Nether coordinates to Overworld coordinates:

Overworld X = Nether X × 8
Overworld Z = Nether Z × 8
Y coordinate remains unchanged

Why 8:1 Ratio?

This ratio was chosen by Mojang to make Nether travel a viable fast-travel option. Building a Nether highway allows players to traverse large Overworld distances quickly. For example, traveling 1000 blocks in the Nether moves you 8000 blocks in the Overworld.

Portal Linking Mechanics

When you enter a portal, the game converts your position to the destination dimension and looks for an existing portal near the converted coordinates. In current Java Edition the search area is a 32×32 block square — a 16-block radius — when arriving in the Nether, and a 256×256 block square, a 128-block radius, when arriving in the Overworld. It searches the full map height in both cases.

The two radii are not a mistake: 16 Nether blocks correspond to 128 Overworld blocks, so the two searches cover the same real distance. Before Java Edition 1.16.2 the radius was 128 blocks in both dimensions, which meant a Nether search swept the equivalent of 1,024 Overworld blocks and grabbed portals that belonged to somewhere else entirely.

If no portal is found, the game builds one, looking for a suitable spot within 16 blocks horizontally of the destination coordinates but any distance vertically.

To link portals precisely:

  • Build your Overworld portal at coordinates (X, Y, Z)
  • Convert to Nether coordinates: (floor(X÷8), Y, floor(Z÷8))
  • Build your Nether portal at those exact coordinates
  • Both portals will now link to each other reliably

Distance Calculations

3D Euclidean distance between two points is calculated using:

d = √[(x₂-x₁)² + (y₂-y₁)² + (z₂-z₁)²]

2D distance (ignoring Y/height) is useful for surface travel:

d = √[(x₂-x₁)² + (z₂-z₁)²]

Midpoint Formula

The midpoint between two coordinates is the average of each axis:

Midpoint = ((x₁+x₂)÷2, (y₁+y₂)÷2, (z₁+z₂)÷2)

Rounding

Coordinates entered here are floored to a block before conversion, because the coordinate readout in game shows a position rather than a block. Division is floored too, which matters only for negative coordinates: −100 ÷ 8 is −12.5, and the block containing that position is −13. Rounding to nearest, or truncating toward zero, puts every portal west or north of the origin one block out of place.

References