How to Link Nether Portals

Learning how to link nether portals means building (or adjusting) both frames so Minecraft’s linking rules send you where you intended—not into a random ruined portal three biomes away. This guide covers the Survival workflow: read Overworld XYZ, convert with the 1:8 scale, place the matching Nether exit, understand Java vs Bedrock search radii, and repair a portal that goes to the wrong place. Pair it with the Nether portal calculator for the math; this page owns the how-to of connecting portals and keeping both ends pinned in GameCoords.

3D シーンを読み込み中…

Try the map above, then save both portal ends on a map to keep your own pins.

How to link nether portals (the Survival build loop)

Start on the Overworld side you actually care about—home, village railhead, or shopping district. Stand in the finished frame (or on the obsidian sill), read feet XYZ, and name the place before you light anything: “Home OW portal −800, 68, 400.” That pin is the source of truth for every later conversion. How to link nether portals fails most often when the Overworld number lives only in someone’s memory while the Nether side gets rebuilt three times.

Convert horizontal coordinates with the familiar 1:8 rule: Nether X ≈ Overworld X ÷ 8, Nether Z ≈ Overworld Z ÷ 8. Y does not scale 1:8—pick a safe Nether build height for your roof highway, corridor, or hub floor. For −800, 400 Overworld, the target is near Nether −100, 50. Walk or dig to that Nether column, clear a safe chamber, build a full frame, light it, and step through once while watching where you exit. If you land beside the Overworld frame you named, the link succeeded.

After a clean test, save the Nether exit as a second pin—“Home Nether exit −100, 120, 50”—on the same GameCoords map. The calculator page turns numbers; this how-to turns numbers into built frames and recorded pairs. Never mix unlabeled Nether X=−100 with Overworld X=−100 in one chat line—the scale makes that mix-up expensive.

How to link nether portals on Java (search ~16 Nether / ~128 Overworld)

How to link nether portals Java players care about search radius as much as the 1:8 math. When you enter from the Overworld, Java looks for an existing Nether portal near the converted coordinates within roughly 16 blocks horizontally in the Nether. When you return from the Nether, Java searches a much larger Overworld neighborhood—about 128 blocks—around the converted landing. That asymmetry explains “I built close enough in the Nether but still linked weird going home.”

Practical Java habit: place the Nether portal inside that ~16-block budget of the exact ÷8 target whenever possible. If an older portal already sits inside the search volume, Minecraft may prefer it over your new frame—even if your new frame is “more correct” by spreadsheet. Linking is preference among candidates, not a guarantee that your freshly poured obsidian wins. Demolish or move competing frames when a hub must own the exit.

Negative coordinates need floor-aware conversion, not “truncate toward zero.” Overworld X = −1 should not be treated as Nether 0; floor division toward −∞ keeps the intended column. Worked check: Overworld (−800, 400) → Nether (−100, 50); Overworld (−7, 15) → Nether (0 or −1 depending on your rounding policy—prefer consistent floor). After computing, rebuild near the floored target and retest both directions. Save both ends so the next rebuild starts from numbers, not vibes.

How to link nether portals on Bedrock (often ~128 both sides)

How to link nether portals Bedrock follows the same 1:8 intention, but search behavior is often described as a wider ~128-block preference on both sides compared with Java’s tight Nether ~16. Exact internals vary by version; the Survival takeaway stays stable: Bedrock worlds tolerate more “nearby portal hijacking,” so crowded Realms fill with accidental merges unless teams agree on hub coordinates and delete stray frames.

Bedrock workflow: enable Show Coordinates, pin the Overworld frame, convert with 1:8 (still floor negatives carefully), build the Nether exit near the target, then test OW→Nether and Nether→OW separately. If a friend’s abandoned dig portal sits within the generous search volume, your carefully planned exit may dump you into their unfinished basalt hole. Treat “delete unused portals near the hub column” as part of linking, not optional cleanup.

Console and mobile Bedrock players should capture XYZ with screenshots when controllers make typing painful, then enter pins in GameCoords on a phone or PC. The numbers are the same language as Java; the UI path differs. Cross-link save Minecraft Bedrock coordinates and save Minecraft console coordinates for device-specific capture—this page stays on connecting portals.

How to connect nether portals (same job, clearer build checklist)

Searches for how to connect nether portals are the same intent as linking: make two frames talk. Use a checklist so “connect” stops meaning “light something and hope.” (1) Name and save Overworld XYZ. (2) Convert X/Z with ÷8; choose Nether Y on purpose. (3) Clear competing portals inside the relevant search radius. (4) Build, light, and walk through both ways. (5) Update pins if you nudge either frame. (6) Share the map link so teammates stop pasting unlabeled triples in chat.

Connecting multiple destinations means multiple pairs—not one mega-portal that “should somehow know.” A village railhead, a fortress access stub, and a roof-highway tip each deserve their own Overworld frame and matching Nether exit, spaced so search radii do not collide. The demo pins on this page show a home pair plus a highway pair: Home OW −800, 68, 400 with Nether −100, 120, 50; Highway OW 1600, 68, −320 with Nether 200, 128, −40.

When two Overworld portals are close together, their ÷8 images can land inside one Nether search bubble. Space Overworld frames far enough that Nether targets stay distinct, or accept a shared hub design with labeled corridors. The Nether portal calculator helps you pre-check spacing; GameCoords keeps the chosen numbers visible when someone later builds “just one more door” beside the hub.

How to sync / pair nether portals (Java and Bedrock)

How to sync or pair nether portals is linking language with a matching-pair emphasis: one Overworld frame and one Nether frame that own each other. Sync means both directions exit where you intended after a deliberate build—not “I lit two doors somewhere and hoped they married.” Pair means you treat the two XYZ pins as a unit on the same GameCoords map (“Home OW portal” + “Home Nether exit”).

Pairing checklist (edition-shared): save Overworld XYZ → convert X/Z with ÷8 (or ×8 the other way) on the Nether portal calculator or the convert Overworld to Nether coordinates how-to → hand-build the matching exit near that column → break automatic or competing frames inside the search bubble → walk through both ways → update both pins. Java still cares about the tight Nether ~16-block neighborhood; Bedrock’s wider preference makes crowded Realms steal pairs more often—clear strays before you call the pair “synced.”

Product CTA: open the Nether portal calculator, paste both ends into the map above, and create a GameCoords map so the pair stays labeled when someone rebuilds a sill next week. Cross-read how to not get lost in the Nether so the entry pin exists before scenic basalt walks.

How does nether portal linking work? (Java vs Bedrock mechanism)

How does nether portal linking work? Minecraft does not store a permanent “this door married that door” ID for Survival frames. When you step through, the game converts your X/Z with the 1:8 scale, then searches nearby for an existing portal; if it finds one inside the search volume, it prefers that exit, otherwise it may create a new frame. That preference-among-candidates model is why “perfect math” still loses to a leftover dig portal three chunks away.

Edition magnitude (Survival planning numbers, not a promise of every patch’s internals): Java typically searches roughly ~16 blocks horizontally in the Nether when arriving from the Overworld, and about ~128 blocks in the Overworld when returning from the Nether. Bedrock is often described with a wider ~128-block-style preference on both sides. Y still matters for build safety, but horizontal search bubbles are what steal links. Floor negatives carefully when dividing—see the Java and Bedrock H2s above for worked habits.

What linking is not: a seed map, a Chunkbase ruined-portal finder, or a guarantee that the newest obsidian wins. Math lives on /nether-portal-calculator; this section owns the mechanism story so “how it works” searches land next to the build and repair playbooks. Save both XYZ ends so the next rebuild starts from numbers.

Nether portal search radius / how portals choose an exit

Nether portal search radius is the neighborhood Minecraft checks for an existing frame after it converts your coordinates. How portals choose an exit: convert X/Z (÷8 Overworld→Nether, ×8 Nether→Overworld), look for candidates inside that radius, prefer an existing portal when one qualifies, otherwise spawn a new one. Crowded hubs fail when two ÷8 images sit inside one bubble—the game cannot read your Discord intention.

Planning magnitudes again: Java Nether arrival ~16 horizontal; Java Overworld return ~128; Bedrock commonly behaves like a wider ~128-style preference both ways. Exact internals shift by version—the Survival takeaway does not: keep intended exits inside the budget of the converted target, and keep rival frames outside it. The “how far apart” H2 below turns those radii into spacing; this H2 answers the search-radius / choose-exit wording without a second seed essay.

Demo: Home OW −800, 68, 400 wants Nether near −100, 50; the stray −88, 70, 48 sits close enough to hijack a careless hub. Fix by deleting the rival, rebuilding at the computed column, and retesting. CTA: run numbers on the Nether portal calculator, then save both portal XYZ so radius repairs do not restart from memory.

Nether portal goes to the wrong place / wrong location (repair playbook)

When a nether portal goes to the wrong place, resist the urge to pour a second frame three blocks away and relight forever. Wrong location almost always means: (a) an older portal won the search, (b) the Nether exit was built far from the ÷8 target, (c) negative rounding drifted the column, or (d) someone moved one side and never updated the other. Diagnose before you spend another stack of obsidian.

Repair steps: stand in the Overworld frame you want to own and confirm its saved XYZ. Compute the ideal Nether column again. Travel in the Nether by walking or bridging toward that column—do not trust a wrong exit as a landmark. Break or deactivate portals that steal the link inside the search radius (the demo “Stray wrong-link frame −88, 70, 48” is the kind of leftover that hijacks homes). Build the correct exit at the target, light it, and test both directions. Only then update GameCoords pins so the atlas matches the world.

If the portal goes to the wrong location only one way, remember Java’s asymmetric radii: a tight Nether miss can still “work” outbound while the return search grabs a distant Overworld ruin. Fix the side that fails; retest both. Pair this playbook with death-coordinate hygiene if you died mid-repair—save a safe overlook before you punch the wrong frame over a lava lake.

How to fix nether portal linking / portals not linking (Java and Bedrock)

How to fix nether portal linking—or portals not linking—uses one shared triage, not edition folklore. (1) Stand in the Overworld frame you care about and save its XYZ. (2) Convert X/Z with ÷8 (Nether→OW uses ×8) and write the target column. (3) Travel to that column; do not treat a wrong exit as home base. (4) Hand-build the correct frame if missing. (5) Break automatic or competing portals inside the search radius. (6) Relight and walk both directions. (7) Update both GameCoords pins. “Not linking” usually means a rival won the search or the exit was never near the math.

Java vs Bedrock while fixing: expect a tighter Nether neighborhood on Java (~16) and a larger Overworld return search (~128); Bedrock’s wider preference means you may need to clear more strays on busy Realms before the pair sticks. Floor negatives the same way on both editions. If only one direction fails, fix that side’s geometry first—asymmetric radii make one-way “success” common.

Skip seed maps and “just light another door.” Open the Nether portal calculator for the numbers, follow this checklist, then save both ends. Cross-read how to convert Overworld to Nether coordinates for hand math and how to not get lost in the Nether so you do not lose the repair corridor mid-fix.

Nether portal keeps creating / making new portals

When a nether portal keeps creating or making new portals, Minecraft is failing to find an existing frame inside the search radius of the converted target—so it spawns another. Common causes: the “correct” exit sits too far from the ÷8/×8 column, someone tore down the old exit without updating the other side, or you keep lighting fresh Overworld doors whose converted images miss every hub you already built.

Stop the spawn loop: save the Overworld XYZ you want to own, recompute the Nether (or Overworld) target, walk to that column, hand-build one intentional exit, then break the extras the game poured for you—especially the demo-style stray near −88, 70, 48 that sits just close enough to confuse a hub. Retest both ways once only one candidate remains in the bubble. Spacing rivals outside the search radius (see how far apart below) prevents the next “helpful” auto-frame.

Product CTA: use the Nether portal calculator, pin both ends on the map above, and create your GameCoords map before the third accidental door appears. Creating new portals forever is a search-radius problem, not a reason to invent a different 1:8 formula.

How to unlink / disconnect nether portals (Java and Bedrock)

How to unlink or disconnect nether portals is deliberate teardown plus geometry, not a hidden “unlink” button. Break or deactivate the frame you want out of the pair (remove the light / break obsidian), then clear any automatic replacement that respawns inside the search radius when someone still walks through the other side. If both doors must stop talking, deactivate both and rebuild only the pairs you still want—crowded Realms often need a hub redesign more than a single punch.

Edition note: after you remove one side, the next transit from the surviving door may create a brand-new exit near the converted coordinates (same “keeps creating” behavior). That is expected. To finish a disconnect cleanly, either leave that destination dark on purpose, or immediately hand-build the new partner you actually want at the computed column and delete leftovers. Java’s tighter Nether radius and Bedrock’s wider preference change how far you must clear—not the ÷8 math.

Always save XYZ before you disconnect a working pair you might rebuild later. Open the calculator, note both ends, then tear down. Cross-read the fix / not-linking H2 if the remaining door now dumps somewhere worse; cross-read how to not get lost in the Nether before you explore away from a half-demolished hub.

How far apart should nether portals be? (minimum spacing to avoid wrong links)

How far apart should nether portals be depends on search radius more than vibes. In the Nether, Java often prefers existing portals within roughly 16 blocks horizontally of the converted target; Bedrock commonly behaves with a wider ~128-block-style preference. Overworld return searches are large (Java ~128). If two Overworld doors convert to Nether columns inside one search bubble, Minecraft may glue them to the wrong partner—the classic “I built a second base portal and now both go to the hub.”

Practical minimum spacing: keep Nether exits well outside the relevant search radius of each other (comfortably beyond ~16 on careful Java hubs; farther on crowded Bedrock Realms—many teams treat ~128+ Nether separation as a safe planning floor when unsure). Translate that back to Overworld: because X/Z scale 1:8, Overworld portals that must stay distinct often need on the order of hundreds of blocks of horizontal separation so their ÷8 images do not sit in one bubble. Measure the Overworld span with the Minecraft distance calculator, divide by eight, and check whether the Nether tips collide before you pour a third frame.

Demo caution: Home OW −800, 68, 400 → Nether −100, 50 versus a careless neighbor at Overworld −720 could land near the same Nether neighborhood and steal links—exactly what the stray −88, 70, 48 frame illustrates. Prefer one labeled hub with corridors over a spray of close doors. For two-base travel length (not just spacing), see the Minecraft nether travel distance calculator; this H2 only answers “far enough apart to avoid wrong links.”

Negative coordinates, Y choices, and what not to expect

Western and northern bases live in negatives. Always floor when dividing: Overworld X −801 ÷ 8 is not the same mental math as “about −100.” Write the exact triple, convert deliberately, and verify the pin on a map so −100 does not silently become 100 in chat. The Minecraft chunk calculator page explains floor vs truncate if you also think in chunk IDs; portals still care about block XYZ first.

Y is a design choice: roof highways, mid-lava tunnels, and bedrock-busting hubs each pick different Nether heights. Linking still considers height among other factors, but Survival teams succeed when they standardize hub Y and document it on the map (“Nether hub floor Y 120”). Do not divide Overworld Y by 8 and call it science.

This page is not a seed ruined-portal finder, not Chunkbase, and not a second thin calculator clone. Math lives on /nether-portal-calculator; building, connecting, and repairing live here. GameCoords will not scan your world for frames—you save the XYZ you stand on.

Save the pair, share the hub, keep links honest

Durable habit: every linked pair gets two named pins plus optional distance checks between Overworld destinations before you commit to a Nether shortcut. Use the Minecraft distance calculator for Overworld spans, divide by eight for Nether travel expectations, then build. Share the hub map for public exits; keep stash portals on a private map.

Weekly hygiene: after any rebuild, retest OW↔Nether, update pins, and delete abandoned frames near hub columns. Teach newcomers that “connect” means saved coordinates plus search-radius awareness—not lighting the first hole in the wall. Cross-read how to not get lost in the Nether so entry pins exist before scenic basalt walks.

Ready to link tonight’s home door? Compute on the calculator, build with this checklist, paste both ends into the map above, then create your own GameCoords map so the highway tip at 200, 128, −40 still matches Overworld 1600, 68, −320 next month. Linked portals stay linked when numbers outlive memory.

Does Y level matter for Nether portals when linking? (Height vs ÷8)

Does Y level matter for Nether portals when linking? Two layers—do not collapse them into one sentence. Layer 1 (conversion): Y is not divided or multiplied by eight when you convert Overworld↔Nether coordinates; only X and Z use the 1:8 scale. That “Y not scaled” fact lives on how to convert Overworld to Nether coordinates and must stay true. Layer 2 (linking choice): when Minecraft picks the nearest existing portal inside the search neighborhood, Euclidean distance includes ΔY—so a large height gap can make the game prefer a wrong frame or spawn a new one even when X/Z math looked perfect.

Practical height story: you convert Home OW −800, 68, 400 → Nether near −100, 50 on X/Z, then dig a roof exit at Y 128 while an old mid-lava dig portal sits at Y 40 a few blocks sideways. Horizontal search radius still applies, but the 3D distance to the mid-level stray can beat your roof door—especially on crowded Bedrock Realms. Fix by clearing rivals, building the intended exit near the converted column at a documented hub Y, and retesting both directions. Cross-read search-radius / fix-linking H2s above for bubble cleanup; this section owns the Y-matters-for-linking question.

Product CTA: save both portal ends including Y—“Home OW portal −800, 68, 400” and “Home Nether exit −100, 120, 50”—on GameCoords so height is never a shrug. Open the convert how-to for ÷8 literacy and the Nether portal calculator for fields; keep full XYZ pins so linking repairs start from numbers, not “somewhere around the roof.”

Related Minecraft coordinate tools

Frequently Asked Questions