7,445
pages
Reason: Organize this page more like Java Edition distance effects - should allow a lot more in-depth analysis of each effect
This feature is exclusive to Bedrock Edition.

As the player travels far from the world origin in Bedrock Edition, the world starts to behave abnormally. This is mostly caused by precision loss of the 32-bit floating point numbers used for location.

Note: Effects marked with an asterisk (*) are well-known effects. Effects shaded in blue are effects affected at the coordinates other than powers of two. Effects shaded in gray are effects affected beyond the 32-bit integer limit.

## General effects

Some effects can occur at any distance but gradually worsen as coordinates increase. Bedrock Edition uses 32-bit floating points for many of its calculations, such as the player's position, as opposed to Java Edition, which uses 64-bit floating points. A 32-bit floating point uses 23 of these bits for precision (the other 9 are used for the sign and the order of magnitude). Thus, there are 223 (8,388,608) possible positions for any given order of magnitude. For example, there are 8,388,608 possible positions between 1 and 2, each 18,388,608 apart, but there are also 8,388,608 possible positions between 8,388,608 and 16,777,216, each a full block apart. In general, between 2n and 2n+1, the valid positions are 2n-23 apart. At higher coordinates, the valid positions are farther apart, so position is less precise. This principle has several implications.

### Block rendering errors

Various blocks are rendered as partial blocks, and the game uses 32-bit floating points to calculate the corners. At high coordinates, these coordinates become offset, causing the block to render incorrectly. Blocks with more detailed models usually become glitched at lower coordinates (a few blocks start to render incorrectly at a relatively low 131,072 blocks), while full blocks continue to render correctly past 8,388,608 blocks, farther out than most partial blocks.

### Slow movement becomes impossible

For an entity to move, it advances a certain distance each tick. At slow speeds or high coordinates, the increase in distance per tick is so little that when rounding to the nearest valid position, the entity is placed at its original position, so it essentially does not move at all. More specificially, between 2n and 2n+1, an entity's speed is rounded to the nearest multiple of 20*2n-23, so it must move at least 10*2n-23 to actually be considered moving.

There are several ways to slow the player’s movement, such as sneaking, status effects, using an item (e.g. drawing back a bow), or certain blocks (such as cobwebs). In addition, moving diagonally decreases the player’s speed on any given axis. This effect can be amplified by moving almost (but not exactly) along an axis, and by walking into an object, one can do this without changing their coordinate on the other axis. Note that due to trigonometric rounding errors,[verify] extremely small angles do not cause the player to move as slowly as expected. The slowest form of movement without walking into objects (sneaking through cobweb over blue ice with Slowness VI while touching powder snow and drawing back a bow) becomes impossible at 256 blocks, and coincidentally, the slowest form of movement achievable by walking into an object at a slight angle also becomes impossible at 256 blocks; as a result, both methods must be used to slow the player down if one wishes to observe this effect at lower coordinates.

### Jitter

The game normally runs at 60 frames per second, so when the player moves, the game must calculate the camera position on the intermediate frames between ticks. This is normally not an issue, but if the player is moving close to the slowest possible speed, the camera position on intermediate frames becomes distorted, and the game starts to jitter.

Eventually, the slow speed and precision errors reach a point where the player only advances by 1 valid position per tick, forcing that the game to render the intermediate frames at exactly the starting or ending position. As a result, the camera moves as though the game ran at 20 frames per second instead of 60.

Since slower speeds become jittery at lower coordinates, it is impossible to say exactly where jitter "starts."

### Falling through the world

At extreme coordinates, small entity hitboxes shrink to width 0, and such entities can fall through the edges of solid blocks. For example, if an entity smaller than 14 blocks exceeds coordinate 2,097,152, its position is rounded to the nearest quarter. Since its hitbox extends less than 18 from a valid position in each direction, both sides of the hitbox are rounded to the same position, so the apparent hitbox size is 0.

In addition, it is possible to manipulate hitboxes and fall through the world at much lower coordinates. While the positions of the centers of entities are stored in NBT, the positions of the individual hitbox corners are stored in memory. If the player is crossing a power of 2, these corners may move at different speeds, if they are affected differently by floating point precision errors, thus changing the hitbox size. The hitbox size resets to 0.6 in certain situations, including:[more information needed]

Again, if the player's hitbox size shrinks to 0, it becomes possible to fall through the edges of blocks and into the void (MCPE-39299). Conversely, it is possible to stretch one's hitbox to several blocks wide.

## Minor effects (X/Z ±1–131,071)

Coordinates Effects
X/Z ±1 (20)
• Coordinates of all entities are slices of 8,388,608 (18,388,608 blocks).
• It is impossible to walk into an object at a 0.02-degree angle through cobweb over blue ice with Slowness VI while touching powder snow.
• Using the above method of movement at (0,0), it is theoretically possible to fall through the world by crossing the X/Z ±1 limit. However, it is almost impossible to do at these coordinates, as it takes nearly 6 real-life days of nonstop gameplay (where one must start over if they exit the game).
X/Z ±2 (21)
• Coordinates of all entities are slices of 4,194,304 (14,194,304 blocks).
X/Z ±4 (22)
• Coordinates of all entities are slices of 2,097,152 (12,097,152 blocks).
X/Z ±8 (23)
• Coordinates of all entities are slices of 1,048,576 (11,048,576 blocks).
X/Z ±16 (24)
• Coordinates of all entities are slices of 524,288 (1524,288 blocks).
X/Z ±32 (25)
• Coordinates of all entities are slices of 262,144 (1262,144 blocks).
X/Z ±64 (26)
• Coordinates of all entities are slices of 131,072 (1131,072 blocks).
X/Z ±128 (27)
• Coordinates of all entities are slices of 65,536 (165,536 blocks).
X/Z ±256 (28)
• Coordinates of all entities are slices of 32,768 (132,768 blocks).
• The slowest method of travel becomes impossible, sneaking on blue ice with cobwebs while touching powder snow and under the effect of slowness VI while using an item.
• It is impossible to walk into an object at a 0.0025-degree angle. As discussed before, lower angles do not yield similar results at lower coordinates.
X/Z ±512 (29)
• Coordinates of all entities are slices of 16,384 (116,384 blocks).
• Sneaking on blue ice with cobwebs and under the effect of slowness VI while using an item becomes impossible.
X/Z ±1,024 (210)
• Coordinates of all entities are slices of 8,192 (18,192 blocks).
• Sneaking on blue ice with cobwebs and under the effect of slowness V while using an item becomes impossible.
X/Z ±2,048 (211)
• Coordinates of all entities are slices of 4,096 (14096 blocks).
X/Z ±4,096 (212)
• Coordinates of all entities are slices of 2,048 (12048 blocks).
• Sneaking on blue ice with cobwebs while using an item becomes impossible.
X/Z ±8,192 (213)
• Coordinates of all entities are slices of 1,024 (11024 blocks).
X/Z ±16,384 (214)
• Coordinates of all entities are slices of 512 (1512 blocks).
• It becomes impossible to move in cobwebs on blue ice while using an item.
X/Z ±32,768 (215)
• Coordinates of all entities are slices of 256 (1256 blocks).
• It becomes impossible to sneak diagonally on top of soul sand with cobwebs while drawing back a bow.[1]
X/Z ±65,536 (216)
• Coordinates of all entities are slices of 128 (1128 blocks).
• It becomes impossible to sneak diagonally on top of soul sand with cobwebs.
• Sneaking vertically and out starts to become jittery.

## Medium effects (X/Z ±131,072–1,048,575)

Eventually, some common forms of movement begin to glitch. In addition, blocks with detailed models begin to render incorrectly.

Coordinates Effects
X/Z ±131,072 (217)*
• Coordinates of all entities are slices of 64 (164 blocks).
• Climbing up ladders, vines, twisting vines, and weeping vines while sneaking is slightly slower than normal if climbing by walking against a block.[2]
• Sneaking diagonally starts to become jittery.
• Lecterns and tripwire hooks start to become distorted, lecterns don't always become noticeably distorted at this point.
• When the player stops walking, they are bumped.
• Fire on top of a block melts surrounding ice.
X/Z ±262,144 (218)*
• Coordinates of all entities are slices of 32 (132 blocks).
• Climbing up ladders and vines while sneaking is even slower and less smooth.[2]
• Moving in powder snow while sneaking becomes impossible if the player waits for too long.
• Sea pickles render with slightly thinner stems than normal.
• Tripwire string becomes invisible.
• Sweet berry bushes and cobwebs appear slightly larger.
• Sunflowers become glitched and are Z-fighting on the X-axis. They aren't glitched on the Z-axis.[3]
• Sneaking in soul sand with a spyglass stops movement.
• Sneaking in all directions is more bumpy.
X/Z ±524,288 (219)*
• Coordinates of all entities are slices of 16 (116 blocks).
• All entities are on the edges of block pixels.
• Paintings are pushed half a pixel into the block causing the painting to turn black.
• The inner part of item frames render flush along the block' which means that the inner part of item frames become 2D.
• Moving horizontally while on cobwebs becomes impossible.
• Moving in powder snow becomes entirely impossible while sneaking.
• Jitter is noticeable beyond this point.
• Most mobs are unable to jump on blocks correctly.
• Sea turtles and axolotls can no longer move on land.
• The top part of candles renders incorrectly.
• It becomes impossible to sneak outside the X/Z axis on soul sand.
• The stem of mangrove propagules render incorrectly.
• Leads start to become easily noticeably distorted.

## Major effects (X/Z ±1,048,576–16,777,215)

This section is missing information about the following features and effects:
• Cave generation
• Raycasting, which seems to result in incorrect blocks being targeted.
Please expand the section to include this information. Further details may exist on the talk page.

Blocks are rendered based on their corners, whose coordinates are 32-bit floating point numbers. Generally, these are multiples of 116. Thus, most blocks render normally as long the floating points are precise to the nearest sixteenth. This breaks at X/Z ±1,048,576 (220), and blocks continue to render incorrectly as the coordinates go even farther out. However, there is never any vertical distortion.[4]

In the RTX betas, the lighting is unaffected by floating-point precision errors, although block shapes themselves are incorrect.[5]

Besides, many "normal" forms of movement become impossible.

The different types of block model deformation have changed a lot over the years, although the update specifics and hardware requirements are unknown. Previously, blocks such as flowers and grass would appear completely 2D beyond 8,388,608 blocks, whereas they appeared as almost normal X shapes in more recent versions, but appearing as 2D again as of 1.16.220. Also, sunflower heads could previously distort to become square, which also no longer happens; the flower appears detached from the plant instead.

In addition here, the terrain starts to break down following the table.

Coordinates Effects
X/Z ±1,048,576 (220)*
• Coordinates of all entities are slices of 8 (18 blocks).
• Walls render wider than normal.
• Fences (excluding the posts) and closed fence gates render completely flat.
• Doors and open trapdoors render thinner than normal.
• Iron bars and glass panes render twice as wide than normal.
• Climbing up ladders and vines is impossible without holding the jump button, and climbing up them while sneaking is extremely slow.
• It becomes impossible to sneak outside the X/Z axis.
• Moving in powder snow becomes impossible if you wait too long, though rapidly inputting sprint allows you to escape.
• The cube inside slime blocks is slightly wider.
• The cube inside honey blocks is stretched to a full block, which results in a flickering effect.
• Cakes appear stretched to full block.
• Fire renders a bit differently.
• Sea pickles render in slightly different places without stems.
• Lanterns render wider than usual and without the top part.
• The logs in campfires render farther apart, overlapping with each other.
• In brewing stands, the base renders incorrectly and the central pole is invisible.
• The bases of anvils render incorrectly.
• The supports of grindstones render incorrectly.
• The sides of item frames render wider than the top and bottom.
• Flower pots appear slightly wider.
• The inside of beacons render incorrectly.
• The supports of bells render incorrectly.
• Horizontal end rods render flat, while vertical end rods render only with their bases.
• The shafts of lightning rods render as flat.
• Redstone renders slightly differently.
• Torches become invisible.
• Buttons placed anywhere other than the sides of blocks are distorted and pushed buttons are pushed all the way into the block.
• Pressure plates cover an entire block.
• Redstone repeaters and Redstone comparators render without torches.
• Cocoa beans in the second stage render as wide as mature cocoa beans.
• Cacti render as full blocks, with gaps at the edges.
• Bamboo renders wider than normal, flat, or invisible.
• The dragon egg appears to be blockier.
• Turtle eggs are distorted.
• The small bumps on chorus plant stems disappear.
• Medium amethyst buds are slightly smaller than normal.
• Walking is as fast as running speed.
• The stem of mangrove propagules render twice as wide as normal.
• Sniffer Eggs become stretched to full block.
• The first stage of Pitcher Pods render wider than normal.
• The second, third, and fourth stages of Pitcher Pods are smaller than normal.
X/Z ±2,097,152 (221)*
• Coordinates of all entities are slices of 4 (14 blocks).
• Moving while sneaking becomes nearly impossible.
• Walking feels very bumpy.
• Dropped items fall through the edges of blocks. Dropped items that land on the edges of lava bounce off without burning; this effect continues into the Stripe Lands.
• Fence posts are invisible.
• Open fence gates are completely flat.
• Lightning rods render entirely flat.
• Doors and trapdoors render wider than normal.
• Iron bars and glass panes render completely flat.
• The supports of scaffolding are invisible.
• Cauldrons and composters have completely flat walls and whatever is inside them are stretched to fit the top.
• Flowers begin to distort.
• The bottom part of hoppers are invisible.
• Lecterns are wider more than a block.
• Nether portal blocks are completely flat.
• Flowers, sweet berry bushes, cobwebs, and tall grass are much smaller than normal.
• Hanging roots render thinner than normal.
• All four stages of amethyst buds render thinner than normal.
• The first stage of cocoa beans is flat.
• Chorus flowers render as full blocks.
• The top part of the dragon egg is invisible.
• The big bumps on chorus plant stems are bigger.
• The stem of Mangrove propagules are invisible.
• End rods become invisible.
X/Z ±2,812,333
• Terrain generation partially breaks down at this point. Certain sections of land do not generate any terrain whatsoever, only leaving behind aquifers, generated structures, the lava that replaces all air below Y=-56, and the bedrock layer. Scattered monolith-like strips of land that extend up to approximately Y=250 can also be seen in these areas. These terrain generation breakdowns most often occur in areas that contain mountain biomes.[6]
X/Z ±4,194,304 (222)*
• Coordinates of all entities are slices of 2 (12 blocks).
• It becomes extremely difficult to traverse the world on foot from here. In order to continue navigating around the world, Players need to use ender pearls, chorus fruit, elytra with fireworks or a Riptide trident (if raining or underwater), horseback, boats, or any method that would be at least five blocks per second normally, meaning moving in normal walking speed is impossible.
• One can travel on foot past 4,194,304 by jumping one time and sprinting.
• One cannot jump normally. The Jump Boost effect does not work. Stairs and slabs or blocks less than 0.5 blocks tall are work past this point.
• Entities less than 0.5 blocks wide (such as items and silverfish) fall through the edges of blocks, but can still stand on the centers. This is likely because the hitbox corners on both sides round to the same coordinates, resulting in a "null" hitbox; however, it is not confirmed.[verify]
• Status effect particles snap to the center of the player, causing them to bunch around the center of the screen.
• All stages of amethyst buds are stretched to a full block.
• The stems of both big dripleaves and small dripleaves become two-dimensional.
• Eyes of ender placed inside end portal blocks are stretched to cover the entire block.
• Piston bases are stretched to full block. If retracted, the front "flickers" between the head and base textures.
• Crops, hanging roots, and seagrass render on the edges of blocks.
• The second stage of cocoa beans is flat just like the first stage.
• The third stage of cocoa beans appears stretched as a full block.
• When the player is in powder snow the screen sometimes flickers fighting trying to see if the player is inside or outside of powder snow even with leather armor on.
• The second highest top part of the dragon egg is invisible including the highest part.
X/Z ±8,388,608 (223)*
• Coordinates of all entities are integers (1 block), meaning that all entities are on the edges of blocks. As a result, most entities less than 1 block wide including Players always fall through blocks. The only entities that can stand on blocks from this point onward are boats, minecarts on rails (when placed correctly), spiders, horses, iron golems, polar bears, and ravagers. The player falls through blocks if the player rides an entity other than the ones described above, uses an ender pearl, or teleports beyond this coordinate.
• If only one coordinate exceeds this value, blocks still have collision detection from the side.
• The player can still be considered "under" blocks, meaning that phantoms do not spawn. Thus, it is theoretically possible to travel to and from the Stripe Lands in survival using above-average in speed horses.
• The minimum movement speed is increased to ten blocks per second, meaning that sprinting, boats (except in frozen oceans), horses (except for the faster ones mentioned above), and swimming are no longer usable sources of movement.
• To fly in creative the player must sprint or look directly along an axis, unless the player position is controlled by 64-bit doubles instead of 32-bit floats. The Speed effect does not work, due to MCPE-61425. In addition, flying at this coordinate is bumpy, even when the player is sprinting and looking directly along an axis.
• Most blocks that normally render as partial blocks are either stretched to become full blocks, or squished to become 2-dimensional. The exception is a few blocks that render normally no matter how far out the player travels, such as chests and bells.
• If both coordinates exceed this value, partial blocks that normally render as 2D this far out become 1-dimensional and are therefore completely invisible.
• The terracotta strata in badlands biomes become noticeably distorted at this point.
• The blade of a stonecutter duplicates, with each blade appearing on the edge.
• Spore blossoms are stretched so that the player sees only half of the flower.
• Entering active end portals becomes impossible.
• Previously, cross models would render stretched out (changed from rendering 2D as of an unknown update), however as of 1.16.210 they render flat again.
• The first and second stage of cocoa beans are pushed into the block when placed horizontally and render as full blocks when placed vertically.
• Riding Minecarts on active powered rails becomes impossible.
• Chains are stretched to a full block.
• Caves generate incorrectly.
• Mangrove propagules are stretched to 2 blocks wide.

## Game-breaking effects (X/Z ≥±16,777,216)

This section is missing information about notable effects beyond the 32-bit limit (X/Z ≥2,147,483,648).
Please expand the section to include this information. Further details may exist on the talk page.

Here, the rendering fundamentally breaks down to the point where normal gameplay is completely impossible.

Coordinates Effects
X/Z ±16,777,216 (224)*
• The floating point precision errors cause only blocks with even coordinates not divisible by 4 to render, and are stretched to 2 blocks wide. Blocks at other coordinates are rounded to the nearest multiple of 4 and render 2 dimensional. Blocks render only if they are "exposed" to air or another see-through block. This phenomenon is known as the Stripe Lands. In contrast, the Stripe Lands starts at X/Z ±9,007,199,254,740,992 in Java Edition, as the block rendering coordinates use 64-bit doubles instead. In the Corner Stripe lands, blocks with both coordinates 2 mod 4 render double length and double width, blocks with 1 such coordinate render 2D and double length, and blocks with no such coordinate render 1D (thus, the block is completely invisible unless the player is inside it.
• Coordinates of all entities are multiples of 2.
• This does not impact the way maps are rendered.
• 2D blocks are non-solid, even from the sides. However, ghasts, large slimes, and large magma cubes treat both 2D and 3D blocks as solid as they are more than 2 blocks wide.
• The minimum speed is increased to 20 blocks per second, meaning that slow Creative mode flight and horses are no longer possible to move with, leaving only flight by an elytra (either with firework rockets or a Riptide trident) and teleportation by any means.
• In any biome where multiple blocks can generate as part of the top surface layer, such as windswept hills and old growth taigas, their surfaces become distorted and start to form blocky shapes. The terracotta strata in badlands biomes also become distorted further. Because the majority of blocks do not render in the Stripe Lands, this is noticeable only when viewed on a map.
• Fast Creative mode flight only works if the player looks directly along an axis.
X/Z ±33,554,432 (225)*
• Horizontal block rendering stops completely, leaving only vertical block rendering in its place, marking the start of the Slice Lands.[unofficial name] Blocks whose sides are not "exposed", such as the naturally-generated water, are completely invisible.
• At this point, the slices are 4 blocks apart, but the gap widths double for every power of 2.
• Coordinates of all entities are multiples of 4.
• It is difficult to place blocks from this point onward. The player must look at an existing block and extend it along an axis. The only way to generate blocks (to place on) without external tools is to use structure blocks.
• Past this point, blocks are now completely invisible on a superflat world.
• Block rendering essentially stops completely in the Corner Slice Lands;[7] almost all blocks are rendered as one-dimensional, and are therefore impossible to see. Only certain block entities and any normally visible water side textures render in this area which means that due to the end having no liquids the end is almost completely invisible.
• The minimum movement speed is increased to 40 blocks per second, meaning ender pearls no longer work. Teleportation is now only possible by chorus fruit because teleportation by commands stops at 30 million blocks. Elytras either require a steep angle or a Riptide trident in rain to propel the player. Tridents, arrows shot from bows or crossbows and ender dragons are the only other entities that can move horizontally beyond this point, other than the player.
• Teleporting past X/Z 33,554,432 directly using external tools (like Toolbox), since the game won't let you teleport past X/Z 30,000,000 using commands, chunks will just straight up refuse to load, resulting in the player not seeing any terrain, and not being able to move. This boundary was added back in 2023 in an unknown update. (possibly)
X/Z ±67,108,864 (226)*
• The minimum movement speed is increased to 80 blocks per second, meaning that thrown tridents cannot move horizontally and the use of an elytra requires a Riptide trident.
• It becomes impossible to look horizontal in third person view.
• Coordinates of all entities are multiples of 8.
• The game crashes at this point if the world is playing in any version below 1.18 without the "Caves And Cliffs" experiment feature on, this is only possible using an NBT editor.
• If both coordinates exceed this value, setting the player to third person view causes the game to freeze and crash.
X/Z ±134,217,728 (227)*
• Coordinates of all entities are multiples of 16, equivalent to one chunk section.
• The visual gaps are 16 blocks wide.
• All entities are on the edges of chunks.
• The minimum movement speed is increased to 160 blocks per second, meaning that arrows cannot move horizontally and Riptide starts to become less usable at low levels.
• Maximum coordinates where generated structures can generate on mobile devices. However, on Windows, structures continue to generate all the way to the 32-bit integer limit.
• Teleportation using chorus fruit becomes impossible.
• More specifically, Riptide I works only if the player looks directly along an axis and does it many times.
X/Z ±268,435,456 (228)
• Coordinates of all entities are multiples of 32, equivalent to two chunks section.
• The visual gaps are 32 blocks wide.
• The minimum movement speed is increased to 320 blocks per second, meaning that levels of Riptide below level II no longer work, and Riptide II barely works.
• More specifically, Riptide II works only if the player looks directly along an axis and does it many times.
X/Z ±536,870,912 (229)
• Coordinates of all entities are multiples of 64, equivalent to four chunks section.
• The visual gaps are 64 blocks wide.
• Since beta 1.17.30.24, some devices (low and mid-end classes) can no longer survive in this position and frequently crash at this point. If players can successfully go to this coordinate or over, they can survive for few seconds before the game crashes. Therefore, increasing the render distance can crash the game and only high-end devices can survive at this position.
• The minimum movement speed is increased to 640 blocks per second, meaning that no method of vanilla movement works, even Riptide III.
X/Z ±1,073,741,824 (230)
• Coordinates of all entities are multiples of 128, equivalent to eight chunks section.
• The visual gaps are 128 blocks wide.
• The minimum movement speed is increased to 1,280 blocks per second, meaning that Riptide levels below IX no longer work.
• The world is completely invisible with a render distance of 7 chunks or less.
• The phenomenon is called the Invisible Stripe Lands.
X/Y/Z ±2,147,483,647 (231 − 1)*
• The game crashes near this point, as this is above the maximum value for a signed 32-bit binary integer in C++. Specifically, the game crashes if the player attempts to load a chunk that is within 64 blocks of this limit of 2 frames, so increasing the render distance can make the rendering limit get closer and crash the game.
231 and beyond
X/Z ±2,147,483,648 (231)
• Coordinates of all entities are multiples of 256, equivalent to 16 chunks section.
• The visual gaps are 256 blocks wide.
• The minimum movement speed is increased to 2,560 blocks per second, meaning that Riptide levels below 18 no longer work.
X/Z ±4,294,967,296 (232)
• Coordinates of all entities are multiples of 512, equivalent to 32 chunks section.
• The visual gaps are 512 blocks wide.
• The minimum movement speed is increased to 5,120 blocks per second.
X/Z ±8,589,934,592 (233)
• Coordinates of all entities are multiples of 1,024, equivalent to 64 chunks section.
• The visual gaps are 1,024 blocks wide.
• The minimum movement speed is increased to 10,240 blocks per second.
X/Z ±17,179,869,184 (234)
• Coordinates of all entities are multiples of 2,048, equivalent to 128 chunks section.
• The visual gaps are 2,048 blocks wide.
• The minimum movement speed is increased to 20,480 blocks per second.
X/Z ±34,359,738,368 (235)
• Coordinates of all entities are multiples of 4,096, equivalent to 256 chunks section.
• The visual gaps are 4,096 blocks wide.
• The minimum movement speed is increased to 40,960 blocks per second.
X/Z ±68,719,476,736 (236)
• Coordinates of all entities are multiples of 8,192, equivalent to 512 chunks section.
• The visual gaps are 8,192 blocks wide.
• The minimum movement speed is increased to 81,920 blocks per second.
X/Z ±137,438,953,472 (237)
• Coordinates of all entities are multiples of 16,384, equivalent to 1,024 chunks section.
• The visual gaps are 16,384 blocks wide.
• The minimum movement speed is increased to 163,840 blocks per second.
X/Z ±274,877,906,944 (238)
• Coordinates of all entities are multiples of 32,768 equivalent to 2,048 chunks section.
• The visual gaps are 32,768 blocks wide.
• The minimum movement speed is increased to 327,680 blocks per second.
X/Z ±549,755,813,888 (239)
• Coordinates of all entities are multiples of 65,536, equivalent to 4,096 chunks section.
• The visual gaps are 65,536 blocks wide.
• The minimum movement speed is increased to 655,360 blocks per second.
X/Z ±1,099,511,627,776 (240)
• Coordinates of all entities are multiples of 131,072, equivalent to 8,192 chunks section.
• The visual gaps are 131,072 blocks wide.
• The minimum movement speed is increased to 1,310,720 blocks per second.
X/Z ±2,199,023,255,552 (241)
• Coordinates of all entities are multiples of 262,144, equivalent to 16,384 chunks section.
• The visual gaps are 262,144 blocks wide.
• The minimum movement speed is increased to 2,621,440 blocks per second.
X/Z: ±53,905,378,846,979,747 (2^63 - 1/171.103)
• The Far Lands would generate at this expected distance from the center of the world, however, since the source code is unavailable to the public, it is impossible to modify the game to allow terrain generation past the 32-bit maximum signed integer limit, unlike in Java Edition, making them inaccessible regardless of the means to do so.
X/Y/Z ±9,223,372,036,854,775,807 (263 – 1)
• The game would crash near this point, if it were to be theoretically patched to use 64-bit integers, as this is above the maximum value for a signed 64-bit binary integer in C++. Also, the game would crash if the player attempted to load a chunk beyond this coordinate, so increasing the render distance would make the rendering limit get closer and crash the game.[verify]
X/Z ±9,223,372,036,854,775,808 (263)
• Coordinates of all entities are multiples of 1,099,511,627,776 (240).
• The visual gaps are 1,099,511,627,776 blocks wide.
• The minimum movement speed has reached 10,995,116,277,760 blocks per second by this point.
X/Y/Z ±~3.402824 × 1038 (2128)
• This is the maximum value for a 32-bit floating-point integer in C++. Beyond this point, it is expected that the player's coordinates would roll over to read "infinity," as the 32-bit floating point precision has run out of bits to represent coordinate data. It would be impossible to go past this point, as a value of "infinity" would break rendering code in Bedrock Edition. It would probably also become a NaN (not a number) or a null value, potentially breaking the game, possibly even resulting in a crash.[verify]

### Stripe Lands

The Stripe Lands are an artifact of the game's rendering and block hitbox calculation, rather than a quirk relating directly to terrain generation.[8] The Stripe Lands start at X/Z ±16,777,216. They exist because coordinates are off by up to a full meter, causing the blocks themselves (not just their corners) to appear in the wrong places.

Past X/Z: ±33,554,432 all blocks are rendered as two-dimensional, and the gap between valid blocks doubles to 1 out of four. This gap doubles again at every power of 2 and reaches 128 blocks wide at X/Z: ±1,073,741,824. This is the widest the gaps can be since the game crashes near X/Z: ±2,147,483,647.

## Vertical limits

Like the X and Z axes, the game breaks at excessive Y coordinates. Since blocks cannot be placed above Y=320, block rendering glitches do not occur, but other effects do.

Many of these effects would occur at negative coordinates, but there is a barrier at Y=-104. Beyond this entities can move only vertically using the "fall through the world" glitch, or teleporting below Y=-104. Thus the barrier can be avoided by teleporting past X/Z ±8,388,608. Also, all entities, except players in creative, disappear in the void.

Coordinates Effect
Y ±65,536
• Particles turn black or dull green depending on the time of day within 64 blocks of this limit, this occurs at every power of 2 starting from this point.
Y ±131,072
• Opening the inventory is impossible if the player hits this point between ±131,072 and ±262,144, the inventory will still work if the player teleports beyond ±262,144, but not below that point.
Y 262,144
• Floating with levitation I becomes slightly slower than normal.
Y ±524,288
• Floating with levitation I becomes slightly faster then normal.
• It becomes possible to notice jumping being less smooth.
Y ±1,048,576
• Levitation II floating is slightly faster at this point.
• It becomes impossible to float with levitation I.
Y ±2,097,152
• Floating upward by holding the jump button with elytra and Slow Falling is no longer possible.
• There is a delay between when the player exits flight mode while having slow falling and when the player actually starts falling.
• Floating with Levitation II and lower becomes impossible.
• Slightly looking upward while gliding with elytra could keep your height constant.
Y ±4,194,304
• Flying upward in Creative is faster than normal.
• If the player summons a shulker this high and falls on it, after the player lands on the shulker the players hand moves up and down rapidly (only if view bobbing is on). if the player switches to 3rd person during the small jumps, the player appears as if the player was not jumping.
• Floating with Levitation V and lower becomes impossible.
Y ±8,388,608
• Status effect particles snap to the head, feet, and center of the player, resulting in a glitched animation assuming the player is in first person.
• Slow Falling causes the player to be stuck in mid-air.
• Flying upward in Creative is no longer possible, although the player can still fly downward.
• There is a delay between when the player exits flight mode and when the player actually starts falling.
• Flying downward in Creative is much faster than normal.
• Floating with Levitation 11 and lower becomes impossible.
Y ±16,777,216
• The delay described above is even longer.
• Flying downward in Creative is no longer possible.
• Floating with Levitation 22 and lower becomes impossible.
• It is possible to fly over Border Blocks
Y ±33,554,432
• The delay described above is over twice as long as the previous one.
• Floating with Levitation 44 and lower becomes impossible.
Y ±67,108,864
• It becomes impossible to Fall.
• Floating with Levitation 88 and lower becomes impossible.
Y ±134,217,728
• Floating with Levitation 177 and lower becomes impossible.
• It becomes impossible to look up or down in 3rd person.
Y ±268,435,456
Y ±536,870,912
• Since beta 1.17.30.24, some devices (low and mid-end classes) can no longer survive in this position and frequently crash at this point. If players can successfully go to this coordinate or over, they can survive for few seconds before the game crashes. Therefore, increasing the render distance can crash the game and only high-end devices can survive at this position.
Y ±2,147,483,647
• The game crashes near these coordinates on 32-bit devices (see above), although, a few frames are rendered before it crashes.
• although, the position is 64-bit, there can be a few frames left when you teleport here.
Y ±~3.402824e+38 (2128)
• This is the maximum value for a 32-bit floating-point integer in C++. Beyond this point, it is expected that the player's coordinates would roll over to read "infinity," as the 32-bit floating point precision has run out of bits to represent coordinate data. It would be impossible to go past this point, as a value of "infinity" would break rendering code in Bedrock Edition. It would probably also become a NaN (not a number) or a null value, potentially breaking the game, possibly even resulting in a crash.[verify]

## History

This section needs expansion.
You can help by expanding it.
Pocket Edition Alpha
v0.10.0build 1Chunk jittering at extreme coordinates no longer occurs.
Bedrock Edition
1.17.30beta 1.17.20.20The Far Lands have been pushed past the maximum signed 32-bit integer limit, and terrain beyond X/Z ±12,550,821 for the most part generates normally.
1.18.0beta 1.18.0.22The partial terrain generation breakdown beyond X/Z ±2,812,333 has inadvertently been introduced as a result of the terrain generation rewriting process.[is this the correct version?]
?The large cone beyond X/Z ±536,870,912 no longer appears in front of the player.
1.19.0?Particles beyond Y ±65,536 no longer turn black.
?The player can no longer fall through water beyond X/Z ±8,388,608 and X/Z ±33,554,432.
1.19.10?Particles now turn black again but dull green in certain times of the day beyond Y ±65,536.

## References

1. MCPE-30198 — Cannot move diagonally while sneaking in cobwebs on soul sand while drawing back a bow at excessive coordinates
2. a b MCPE-102410 — Climbing up ladders and vines while sneaking are slower after X/Z ±131,072
3. MCPE-102412 — Sunflower slightly glitches after X/Z ±262,144
4. MCPE-102351 — Rendering error beyond X/Z ±1,048,576
5. MCPE-146021 — "Mountains won't generate higher in high distances, instead it will generate a deep, glitched hole that sometimes generates aquifers" — resolved as "Won't Fix".
6. "So, I've teleported to X=32.000.000... the Stripe Lands?"@_tomcc (Tommaso Checchi) on X, May 5, 2014