Nether Coordinate Reference: The Floor Rule and Radii

B

By Bikash Roy

B

Bikash Roy

Online Research Specialist · SEO Strategist · Web Developer

Bikash personally verifies every calculator against official standards (WHO, NIH, government data). Online research specialist, SEO strategist, and web developer with 10+ years building accurate digital tools.

Full bio →

· August 16, 2026

The Minecraft nether portal calculator runs on a handful of fixed numbers. This page lists all of them and works the one case that regularly goes wrong by hand.

The ratio

Overworld → Nether:  Nether X = floor(Overworld X ÷ 8)
                     Nether Z = floor(Overworld Z ÷ 8)

Nether → Overworld:  Overworld X = Nether X × 8
                     Overworld Z = Nether Z × 8

Y is never scaled. Height passes through unchanged in both directions. A portal at Y=120 in the Overworld looks for a portal at Y=120 in the Nether, not Y=15.

The floor rule, and why negatives break hand math

floor rounds down, toward negative infinity — not toward zero. For positive coordinates that is the same as dropping the decimal, so nothing looks unusual:

243 ÷ 8 = 30.375   →   floor = 30   ✓ same as truncating

Negative coordinates behave differently:

−243 ÷ 8 = −30.375   →   floor = −31, not −30

Every negative coordinate that is not an exact multiple of 8 lands one block lower than a calculator that simply drops the decimal. Worked cases:

The pattern: Overworld 0 through 7 all map to Nether 0, but −1 through −8 all map to −1. The buckets sit fully below zero on the negative side rather than mirroring the positive side.

Round trips are not always exact

Because the trip in floors and the trip out multiplies, a round trip can land you a few blocks from where you started:

Overworld (803, −1201) → Nether (100, −151) → Overworld (800, −1208)

That is a drift of 3 blocks on X and 7 on Z. The maximum drift is 7 blocks per horizontal axis, and it is normal — not a sign that your portals have unlinked. The linking guide covers how to tell real drift from an actual duplicate.

Search radii

When you step through, the game scales your coordinate and then searches the destination dimension for an existing portal:

If a portal is inside that radius, the game links to it. If not, it builds a new one — no warning, no message. That asymmetry is the source of most duplicate-portal problems, and it is why the tolerance feels tight going into the Nether and generous coming back.

Older Java versions used a Nether-side radius that did not correctly account for the 1:8 scale. That was corrected in Java Edition 1.16.2, and current Bedrock versions use the scale-aware radius too. Only relevant if you are troubleshooting a very old world.

Frame sizes

Any size between the two works. Corner blocks are optional — the game fills them in once the straight edges are complete, so a minimum portal needs 10 obsidian rather than 14.

Quick lookup

The two spacing minimums are derived rather than stated in game — how far apart do nether portals need to be shows where they come from.

What the numbers do not cover

The converted coordinate is the centre of the area the game searches, not a guaranteed arrival point. Terrain matters: a portal cannot generate inside bedrock or in a space with no safe footing, so an auto-generated portal may appear some distance from the exact scaled coordinate. Treat the output as a target to build toward, not a prediction of where the game will place something on its own.