Bedrock Edition distance effects

• There is absolutely no jitter at this point.
• Coordinates of all entities are slices of Infinity ( ¹⁄_Infinity blocks) or multiples of 0 (0 blocks).

• Coordinates of all entities are slices of 8,388,608 (¹⁄_8,388,608 blocks).
• It becomes impossible to walk into an object at a 0.02-degree angle through cobweb over blue ice with Slowness VI (achievable in Survival mode by using the potion of the Turtle Master II) 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 non-stop gameplay (where one must start over if they exit the game).

• Coordinates of all entities are slices of 4,194,304 (¹⁄_4,194,304 blocks).

• Coordinates of all entities are slices of 2,097,152 (¹⁄_2,097,152 blocks).

• Coordinates of all entities are slices of 1,048,576 (¹⁄_1,048,576 blocks).

• Coordinates of all entities are slices of 524,288 (¹⁄_524,288 blocks).

• Coordinates of all entities are slices of 262,144 (¹⁄_262,144 blocks).

• Coordinates of all entities are slices of 131,072 (¹⁄_131,072 blocks).

• Coordinates of all entities are slices of 65,536 (¹⁄_65,536 blocks).
• An (extremely) (small) amount of jitter appears at this point, noticeable only if the player has slowness VI and uses spyglass and does the method listed below outside the X/Z axis.
• The slowest method of travel becomes impossible within commands.​^{[more information needed]}

• Coordinates of all entities are slices of 32,768 (¹⁄_32,768 blocks).
• Lowest coordinates at which anyone has fallen through the world, although unlikely at this distance. Since the glitch is caused by hitbox corners affected by different levels of floating point precision errors, it could theoretically happen at X/Z ±1. However, this would require nearly 6 real-life days of nonstop gameplay (where one must start over if they exit the game). (see above)
• It becomes 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.

• Coordinates of all entities are slices of 16,384 (¹⁄_16,384 blocks).
• The player has a rare chance of falling through the world when colliding with a block.

• Coordinates of all entities are slices of 8,192 (¹⁄_8,192 blocks).
• Sneaking diagonally on blue ice with cobwebs and under the effect of slowness VI while using an item becomes impossible.
• Sneaking diagonally on blue ice with cobwebs while touching powder snow and under the effect of slowness VI while using an item become impossible
• The slowest method of movement in Survival without standing against a solid block (Sneaking while under the effect of Slowness VI and using an item while in a sweet berry bush that is diagonally over ice with cobwebs) becomes impossible.
• Spontaneously falling through the world is now possible from this point on, although unlikely at this distance. This is caused by floating point precision errors causing hitboxes of blocks to have small gaps. If any entity's coordinate falls close to an edge of a block, then it falls through the world and into the void. The precision loss also affects the player's movement speed slightly, although only at extremely low speeds at this distance.

• Coordinates of all entities are slices of 4,096 (¹⁄₄₀₉₆ blocks).
• This is the smallest observed distance of the player falling through the world; however, the player must move extremely slow, enough to allow this to happen. Because of this, it is hypothetically possible to fall through the world at X/Z: 0.
• In Pocket Edition v0.9.0 alpha, chunk borders start to become visible (although it's hard to notice at this point), with the block selection highlight appearing to flicker when the camera is moved.
• Sneaking on blue ice with cobwebs and under the effect of slowness VI while using an item becomes impossible.
• Sneaking on blue ice with cobwebs and under the effect of slowness V while using an item becomes impossible.
• The third 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.

• Coordinates of all entities are slices of 2,048 (¹⁄₂₀₄₈ blocks).
• Sneaking on blue ice with cobwebs while using an item becomes impossible.

• Coordinates of all entities are slices of 1,024 (¹⁄₁₀₂₄ blocks).
• Cobwebs become 1 block wide^[verify] (They are 0.998 blocks wide at lower coordinates.)

• Coordinates of all entities are slices of 512 (¹⁄₅₁₂ blocks).
• It becomes impossible to move in cobwebs on blue ice while using an item.
• (Very) minor jittering during movement can be experienced beyond this point; it is noticeable if the player moves slowly.
• As of Pocket Edition v0.9.0 alpha, borders of chunks begin to become clearly visible depending of the camera angle.
• It becomes impossible to sneak diagonally in blue ice with cobwebs while touching powder snow.

• The Walking Sound of the player becomes layered and plays fast when walking.
• The player must rejoin the world for the glitch to have an effect. This also applies with the ≈40,960 and ≈44,036 block limitation on the walking sound effect. The coordinates of this glitch depends on which direction player travel in. The flat world preset also has the effect further away. Beyond this point, Speed IV is required to hear the sound again.
• Other mobs are unaffected by this bug.

• Coordinates of all entities are slices of 256 (¹⁄₂₅₆ blocks).
• It becomes impossible to sneak diagonally on top of soul sand with cobwebs while drawing back a bow^[3]; this effect eventually evolves into being unable to move diagonally at all at far more extreme coordinates.
• The screen starts to flicker when the player is at the edge of the powder snow when the player rotates the camera, even with leather armor on.
• It becomes impossible to sneak on blue ice with cobwebs while touching powder snow.

• The walking sound of the player stops being played when walking. The coordinates also depend on which direction the player travels in. The flat world preset also has the effect further away. Beyond this point, Speed IV is required to hear the sound again.

• Coordinates of all entities are slices of 128 (¹⁄₁₂₈ blocks).
• It becomes impossible to sneak diagonally on top of soul sand with cobwebs.
• Sneaking vertically and out starts to become jittery, although one needs keen (sensitive) eyes to notice this.
• Falling through the world is now possible when colliding with a block in the corners.^[4]
• The clouds start to become jittery, although one needs keen (sensitive) eyes to notice this.
• In Vibrant Visuals, the outline box begins to distort.

• Coordinates of all entities are slices of 64 (¹⁄₆₄ blocks).
• Climbing up ladders, vines, twisting vines, and weeping vines while sneaking is slightly slower than normal if climbing by walking against a block.^[5]
• Sneaking diagonally starts to become jittery or bumpy; However if the player is going full sneaking speed even without speed effect and the player is going diagonally and does not have the slowness effect it's hard to notice the bumps or jitter of it.
• Lecterns and tripwire hooks start to become distorted, getting worse at higher coordinates.
• Sneaking diagonally through cobwebs becomes impossible.
• When the player stops walking, they are bumped.
• The handle part of the Levers appear a bit distorted if the player is viewed in full.
• Fire on top of a block melts surrounding ice.
• In Pocket Edition v0.9.0 alpha, chunk rendering issues become really noticeable beyond this point, with the chunks "shaking" in response to camera movement.
• It becomes impossible to sneak horizontally on top of soul sand with cobwebs.
• Flying in normal speed start to become jittery.
• However, lecterns, tripwire hooks and handle of lever has different distortion type:
  • Handle of lever has (very) slight curvy lines.
  • Lectern are slightly stretched to a full block with one need keen eye to see it.
  • Tripwire hooks start to have curvy lines.

• Coordinates of all entities are slices of 32 (¹⁄₃₂ blocks).
• All entities are on the half of a block pixel.
• Climbing up ladders and vines while sneaking is even slower and less smooth.^[5]
• 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 appear slightly larger.
• Sunflowers become glitched and are Z-fighting on the X-axis before 1.21.60. They don't become glitched on the Z-axis prior to 1.21.60.^[6][7]
• Sneaking in soul sand with a spyglass stops movement.
• Sneaking in all directions is bumpier.
• Fireflies can no longer move horizontally.
• The top part of the tripwire hook metal hook is thin and further distorted.

• Coordinates of all entities are slices of 16 (¹⁄₁₆ 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 and Z-fighting along the block, which means that the inner part of item frames becomes 2D.^[7]
• Walking horizontally while on cobwebs becomes impossible without the Weaving effect.
• Moving in powder snow becomes entirely impossible while sneaking.
• Jitter is easily noticeable beyond this point.
• Most mobs are unable to jump on blocks correctly; This is probably due to entities being on the edge of block pixels. and the mobs are not fast enough to get through the block.
• Sea turtles and axolotls can no longer move on land.
• The top part of candles renders incorrectly and a single candle become flat, 2D or invisible.
• It becomes impossible to sneak outside the X/Z axis on soul sand without using soul speed boots.
• Running on soul sand becomes noticeably bumpy.
• The stem of mangrove propagules render incorrectly.
• Leads starts to become easily noticeable and distorted.
• Walking is slightly slower than normal.
• It starts to become harder to go from walking to sprinting on an axis.
• In Pocket Edition v0.9.0 alpha, player movement starts to become jittery, but it is hard to notice due to chunk rendering problems.
• The player can no longer move with slowness VI (6).
• The Tripwire metal hook becomes flat.

• Coordinates of all entities are slices of 8 (¹⁄₈ 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 while sneaking is extremely slow.
• It becomes impossible to sneak diagonally (i.e. outside the X/Z axis).
• Moving in powder snow becomes impossible if the player waits too long, though it is possible to escape by engaging the sprint function rapidly.
• The cube inside slime blocks is slightly wider than normal.
• The cube inside honey blocks is stretched to a full block, which results in Z-fighting.
• Cakes appear stretched to a 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 2D or 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.
• The cacti renders as a full block, 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.
• The barrier at Y=-105 is effectively disabled in 1.18 and up.
• The barrier at Y=-41 is effectively disabled in older versions than 1.18.
• Walking is faster than normal.
• Leads start appearing as a zigzag.
• Item frames render Two-Dimensional (2D) or become flat.
• 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.
• Ladders and vines become pushed into the block it is connected to.
  • In 0.12.1 builds, Ladders and vines start to experience Z-fighting.
• The screen starts to flicker when the player is near powder snow, getting worse at higher coordinates, even with leather armor on. (X/Z Unlike beyond 32,768, as it getting farther when player go near it)
• Running through cobwebs becomes impossible.
• Firefly bushes are slightly wider.
• Dried ghasts render incorrectly. (Tentacles are filled in the middle and are squished)
• The lower part of candles become 2D.
• Chain becomes flat.
• Tripwire metal hook become thick.
• In Vibrant Visuals, shadows start to distort.

• Coordinates of all entities are slices of 4 (¹⁄₄ blocks).
  • Entities less than 0.25 blocks wide (such as baby turtles) fall through the edges of the blocks, but can stand on the centers.
• Moving while sneaking becomes nearly impossible without Swift Sneak II.
• 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 become more than a block wide.
• 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 flat, 2D or invisible, and are even more blocky.
• The big bumps on chorus plant stems are bigger.
• The stem of mangrove propagules are invisible.
• End rods become invisible.
• Climbing up ladders and vines becomes impossible without holding the jump button.
• Standing still continuously triggers sculk sensors.
• The stems of pink petals, leaf litter, and wildflowers start to become distorted.
• Tripwire hook now thin again similar to X/Z 524,288, but tripwire hook base become flat and undiggable.

• Terrain generation partially breaks down at this point. Certain sections of land do not generate any terrain whatsoever, 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, monoliths occur only at negative/positive X or negative/positive Z coordinates. These terrain generation breakdowns most often occur in areas that contain mountain biomes.^[10]
• Depending on what platform/console that player are on (whether that be Xbox, PlayStation, etc.), these terrain breakdowns differ between terrain-less areas and monolith-like strips.^{(It depends on the platform that the game is being played on)} For example, on PlayStation, these breakdowns result in monolith-like strips of land, while on Xbox, they do not generate any terrain at all. On Nintendo Switch, the breakdown does not happen at all and on PC and Mobile it could be both, but the terrain never generates normally past this limit on PC and Mobile.​^{[more information needed]}
• On Xbox, when loading up some worlds made in previous versions, there is a chance of seeing chunks entirely filled with water in these terrain-less areas, replacing any chunk that had no terrain generated within it. These "water chunks" do not affect what was previously generated there, and simply fill the chunk with water up to approximately Y=64. These chunks can also be either partially frozen or completely frozen into chunks full of ice depending on their location. They do not generate outside of the terrain-less areas. On some occasions, these chunks can have small parts of land inside of them.
• The cause for these water chunks is unknown, and only one player so far is known to have witnessed this.

• Coordinates of all entities are slices of 2 (¹⁄₂ 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 (the minimum speed possible from here is 10 blocks per second), meaning moving in normal walking speed is impossible.
• One can travel on foot past 4,194,304 by jumping one time and sprinting. If it was walking, then it moves 1 block.
• One cannot jump normally. The Jump Boost effect does not work. Stairs and slabs or blocks less than 0.5 blocks tall still work past this point.
• Moving while sprinting works only if the player looks directly into an axis and is faster than normal.
• 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.
• 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.
• Doors and open trapdoors render completely flat.
• The floating point precision loss causes at least half of the valid coordinates to be considered "invalid", making it easy to fall through the world beyond this point.^[12]
• The stems of both big dripleaves and small dripleaves become two-dimensional.
• Stairs still render correctly until X/Z 8,388,608.
• Eyes of ender placed inside End portal frames 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.
• Certain Non-full blocks like fences, torches, bamboo, and lanterns become flat and other blocks like lecterns become completely distorted.
• 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.
• Swimming works only if the player is near a dolphin, or with the Speed effect^[verify].
• The second highest top part of the dragon egg is invisible including the highest part.
• Chains are 2 blocks wide. (No, they are flat)
• Heavy cores and Dried ghasts become stretched to a full block.
• Lanterns render two-dimensional (invisible if both coordinates exceed this value).
• Heads and conduits stretch to a full block. (with hitbox stretched)
• Flower pots becoming 2D and flat.
• Tripwire hook become 2D or flat.
• Block become non-solid.
• In Pocket Edition v0.9.0 alpha, the player falls through blocks, if teleported a few blocks before this position. If teleported past this position the player can still stand on the blocks but cannot move along this axis.

• 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, except when using speed 8. 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, gets in water or lava 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 (10) 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 as a method of movement. Speed 8 allows players to walk past 8,388,608 without falling.
• To fly in Creative mode, 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, bells, copper golem statue, cobweb and beds.
  • If both coordinates exceed this value, partial blocks that normally render as 2D this far out become 1-dimensional and are therefore completely invisible.
  • Stairs render like full blocks or slabs, with stretched textures.
  • Anvil bases are stretched to full block.
  • The inside part of beacons is stretched to full block.
  • Buttons of any kind placed on top or bottom of blocks appear as fat as a pressure plate
  • Pumpkin and melon stems attached to their respective blocks render on the edge of the farmland that has an even coordinate.
  • Flowers, tall grass, sweet berry bushes, dead bushes and doors appear two-dimensional.
• The terracotta strata in badlands biomes start to become distorted at this point.
• The world starts to generate incorrectly.
• The blade of a stonecutter duplicates, with each blade appearing on the edge.
  • Stonecutters render with two blades, one on each side of the block parallel to the slot.
• Spore blossoms are stretched so that the player sees only half of the flower.
• The End portal block becomes unable to teleport entities.
• Ender dragons start to flap their wings faster, getting worse the higher coordinates they are at.
• 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 either pushed into the block when placed horizontally and render as full blocks when placed vertically.
• The shadow of signs are at the edge of the block the sign is on.
• The notes that come from jukeboxes and noteblocks are on the edges of the block.
• Caves in the Caves and Cliffs update sometimes generate with perfect curves or horizontal halls.
• Riding a minecart or more minecarts on active powered rails becomes impossible.
• Chains are stretched to a full block.
• The world generation starts to generate incorrectly.
• Caves generate slightly differently or incorrectly.
• Mangrove propagules are stretched to 2 blocks wide.
• Leaf litter, pink petals, and wildflowers are stretched.
• In older versions (before 1.18 or the Caves and Cliffs terrain redesign), beyond this point, cave generation starts to become distorted, with only every second block being hollowed.
• Tripwire string is now visible again but stretched to a full block.
• Redstone dust, glass panes, iron bars, fences, tripwire hook and closed fence gates are stretched to a full block.
• Torches render flat at the edges of the block.
• In Pocket Edition v0.9.0 alpha, the player can no longer stand on the blocks and falls through the void.
• The void floor at Y=-105 (in the Overworld) or Y=-41 (in the Nether and the End) can no longer support entities, therefore the player can fall infinitely in the void.
• The player can no longer stand on shulker.
• Shelves become 2D in one axis and 3D in one axis, if both axis exceed the value, both axis rendered 2D instead of 1D.
• Canyons generate slightly different.

• The Far Lands starts to generate and begin on these coordinates or more specifically, "The Loop" or the Tunnel Lands prior to Bedrock Edition 1.17.30 (Bedrock Edition beta 1.17.20.20).^[13]
  • Caves generated close to the Far Lands sometimes have an edgy "zipper" consistency, with sometimes only every second block being hollowed out.
  • In Windows 10 Edition (Prior to Better Together Update) and Bedrock Edition for Windows (for PC) in the current versions), the Far Lands cannot generate and turn into nothingness.
  • On negative X coordinates, the terrain generation stops entirely, except for bedrock, badlands biomes, generated structures, and ocean features.
  • On negative Z coordinates, the terrain becomes a skygrid prior to Bedrock Edition 1.16.30

• Terrain becomes a Skygrid prior to Bedrock Edition 1.16.30
  • As of Bedrock Edition beta 1.16.20.50 The Skygrid no longer generates and turn into Nothingness.
  • As of Windows 10 Edition (Prior to Better Together Update) and Bedrock Edition for Windows (for PC) in the current versions), the skygrid cannot generate and turn into nothingness.
  • At negative Z with positive X coordinates, the terrain become skygrid.
    • At negative X with positive Z coordinates, the terrain generation stops entirely, except for bedrock, badlands biomes, generated structures, and ocean features.
  • If both negative coordinates exceed this value, the terrain generation stops entirely, except for bedrock, badlands biomes, generated structures, and ocean features.

• The Far Lands begin to take on a thinner “shredded” appearance, before fading out into either a Nothingness or Skygrid state.

• 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.
  • If the player manages to set their coordinate to an odd number or move into any area not rendered, they get stuck in a glitched position, unable to move the camera view properly, or move in any direction.
• 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 because they are more than 2 blocks wide.
• The game doesn't recognize that the player is in water if the player's coordinates are a multiple of 4, causing the player to fall through water and into the void, it is unable to enter swimming, and the fog is black or dark blue. However, water still causes the player to exit gliding, and boats still float.
  • In the Corner Stripe Lands, water is recognized only if both X and Z coordinates are not a multiple of 4.
• The minimum speed is increased to 20 blocks per second, meaning that it is no longer possible to move using regular Creative mode flight or with horses without using speed effect, leaving only flight by an elytra (either with firework rockets or a Riptide trident or horse with speed effect) and teleportation by any means.
  • Moving using fast Creative mode flight is still possible, but only if the player looks directly into an axis.
    • In older versions before 1.2.0, the player can still use fast Creative mode flight without looking directly into an axis.
• 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 have also become further distorted. Because the majority of blocks do not render in the Stripe Lands, this is noticeable only when viewed on a map.
• In Bedrock Editor, when placing object beyond this point, it place as a stripes.
• If the map turn on in Bedrock Editor beyond that point, it matching with stripes.

• This is the maximum teleportation distance for /tp command and it is impossible to teleport beyond this distance in the vanilla game. Any attempts to teleport farther puts the player back at this coordinate, and using commands at this point causes an "Unable to fill, summon, more object" error message, because it is an Illegal position in the command. Players who write certain command on this coordinates with chat or command block get an error message. Attempting to use any block placement command results in an error message. Despite this, it is still possible to use structure blocks and the /locate command. The only way to teleport is use Bedrock Edition 1.2.0.

• This maximum reachable coordinate can be reached in the Overworld with the Nether dimension by entering a Nether portal past X/Z ±3,999,984 in the Nether.

• Horizontal block rendering stops completely, leaving only vertical block rendering in its place, marking the start of the Slice Lands.^{[unofficial name]} The floating point precision errors cause only blocks with even coordinates not divisible by 8 to render, and are stretched to 4 blocks wide, making start of Stripe Gap Lands. Blocks whose sides are "concealed", such as 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.
  • The phenomenon is also known as the Stripe Gap Lands.
  • Coordinates of all entities are multiples of 4.
  • It has become 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 the structure block.
  • Past this point, blocks are now completely invisible on a superflat world in some low-end and mid-end devices.
• Block rendering essentially stops completely, causing the map to be blank from their outward in the Corner Slice Lands;^[15] almost all blocks are rendered as one-dimensional, and are therefore impossible to see, although some particles emitted from specific blocks, like torches, could still indicate their presence. Only certain block entities and any normally visible water side textures render in this area, which means that, due to the End having no water nor lava, it is almost completely invisible.
• Water can be viewed only from the side, and becomes completely non-solid.
• The minimum movement speed is increased to 40 blocks per second, meaning that thrown ender pearls no longer work. Teleportation is now possible only by chorus fruit because teleportation by commands stops at 30,000,000 blocks. Elytra either require a steep angle or a Riptide trident in rain to propel the player. (Note that since the player is not considered to be "in water", Riptide can be triggered only from rain.) Thrown 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. Ghasts can no longer move horizontally either, but they do remain airborne without ever falling into the void, while moving vertically.
• Teleporting past X/Z 33,554,432 directly using external tools (like Toolbox), since the game won't let the player teleport past X/Z 30,000,000 using commands, chunks 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)
• On some low-end and mid-end devices, the world does not render anymore, and if the player teleports back to X/Z 0, the player can't interact with the world anymore and has to relog. This can be fixed by reloading the world and teleport back to near X/Z 30,000,000 and teleport back to X/Z 0.
• If the player tries to load into the world on some low-end and mid-end devices, beyond this point, it crashes, which prevents the world from being played on without editing the coordinates of the player or the spawn point with an NBT editor.
• It becomes impossible to shoot any mob.
• Phantoms can no longer move horizontally.
• In modern versions, if a riptide trident is used beyond that point, it becomes easy for the player to get stuck, and if the player move back, they automatically get teleported to this coordinate without using the teleport command.
• The map becomes invisible when the map turns on in the Bedrock Editor beyond that point.

• The floating point precision errors cause only blocks with even coordinates not divisible by 16 to render, and are stretched to 8 blocks wide. Blocks whose sides are "concealed", such as naturally generated water, are completely invisible.
• 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 is possible to move only when raining.
• It becomes impossible to look horizontally in third person view.
• Coordinates of all entities are multiples of 8.
• The visual gaps are 8 blocks wide, thus marking the beginning of the Slice Gap Lands.
• The game crashes at this point if the world is in any version below 1.18 without the "Caves And Cliffs" experiment feature on, this is possible only by using an NBT editor.
• If both X and Z exceed this value, setting the player to third person view causes the game to crash.

• The floating point precision errors cause only blocks with even coordinates not divisible by 32 to render, and are stretched to 16 blocks wide.
• 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 shot from bows or crossbows cannot move horizontally and Riptide starts to become less usable at low levels. More specifically, Riptide I (1) works only if the player looks directly along an axis and does it many times; with Riptide II (2) The player don't have to use it as much to propel. Even ender dragons can no longer move horizontally either, but they do remain airborne, similarly to ghasts.
• In older versions, this is the farthest point where generated structures can generate on mobile devices. However, on Windows and non-mobile gaming consoles, structures continue to generate all the way to the 32-bit integer limit.
• Some chunks start to render incorrectly despite make terrain messed up via map.
• Teleportation using chorus fruit becomes impossible, marking the absolute edge of the world reachable without external tools.

• The floating point precision errors cause only blocks with even coordinates not divisible by 64 to render, and are stretched to 32 blocks wide.
• 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 (2) no longer work, and Riptide II (2) barely works. More specifically, Riptide II (2) works only if the player looks directly along an axis and does it many times.
• It is impossible for any entity to move horizontally, without modifying the player's flying speed, or the player position is controlled by 64-bit doubles.

• The floating point precision errors cause only blocks with even coordinates not divisible by 128 to render, and are stretched to 64 blocks wide.
• Coordinates of all entities are multiples of 64, equivalent to four chunks section.
• The visual gaps are 64 blocks wide.
• Until 1.18, a large "cone shape" in front of the player appears. This cone is oriented along the X or Z axis, rather than the direction the player is facing. It is always composed of 16×16×16 cubes (essentially sections of chunks). This presumably occurrs due to fructum culling losing precision.
• 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 vanilla method of movement works anymore, even Riptide III (3).
• In versions older than 1.18, frustum culling lost its precision, which made areas directly in front of the player not render.

• The floating point precision errors cause only blocks with even coordinates not divisible by 256 to render, and are stretched to 128 blocks wide.
• 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 (4) no longer work.
• The world is completely invisible with a render distance of 7 chunks or less.
• Due to the immense distance of the gaps, these Stripe Lands essentially become the Invisible Stripe Lands.
• Until 1.18, the "cone" in front of the player widens. The world is completely invisible with a render distance of 15 chunks or less (unless the player position is controlled by 64-bit doubles), despite the fact that the gaps are only 8 chunks wide.
• Due to the immense distance of the gaps, these Stripe Lands essentially become the Invisible Stripe Lands.
• The camera starts to render parts of the world invisible.
• Parts of the world go invisible depending where the players camera is at.
• It becomes impossible to render fancy leaves with a render distance of 16 chunks or less.
• Could crash beyond this point on some lower end devices.

• 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.
• In older versions, teleporting a few blocks just before this limit causes the player to get stuck in a glitched position after a few seconds, being unable to move in any direction (althrough moving the camera is still possible). This happens especially with a high render distance.

• Coordinates of all entities are multiples of 256, equivalent to sixteen (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 trident levels below XVIII (18) no longer work.

• 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, meaning that Riptide trident levels below 36 no longer work.

• 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, meaning that Riptide trident levels below 72 no longer work.

• 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, meaning that Riptide trident levels below 144 no longer work.

• 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, meaning that Riptide trident levels below 255 no longer work since 255 is the maximum vanilla level possible.
• This would be the point where chunks begin to be overwritten, so the game would presumably crash as a result, much like how it occurs on Java Edition, since chunk coordinates are also 32-bit integers.

• Coordinates of all entities are multiples of 33,554,432, equivalent to 2,097,152 chunks section.
• The visual gaps are 33,554,432 blocks wide.
• The minimum movement speed is increased to 335,544,320 blocks per second.
  • At this point, it would require achieving speeds greater than the speed of light to move, which is approximately 299,792,458 blocks per second, and impossible to achieve in real life based on all currently accepted physics.
  • The game may crash on 64-bit low-end devices at this point.

• Coordinates of all entities are multiples of 1,073,741,824, equivalent to 67,108,864 chunks section.
• The visual gaps are 1,073,741,824 blocks wide.
• The minimum movement speed is increased to 10,737,418,240 blocks per second.
• The player hand start to jitter at every power of two (2). (2540*1080 screen required to notice the hand jitter)

• 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.
• The Far Lands would presumably start at this distance, give or take billions of blocks of offset, since the terrain's generation algorithms, involving high, low and selector noise generators, use 64-bit floats.
• The Corner Far Lands would presumably look like the stack from Java Edition.
• It's unclear if the Far Lands would still break down, or if the Depth Noise Far Lands, Farther Lands, Fartherer Lands and Farthest Lands would exist.
• It's also unclear if the precision loss that caused the Repetitive Edge Far Lands would or directly still occur at its old coordinate, which could mean that or before the Edge or the Corner Far Lands could or would presumably look like the Java Edition Corner Far Lands.

• The game, assuming it were patched to use 64-bit floats, would crash near this point while using 64-bit systems, as this is above the maximum value for a signed 64-bit binary integer in C++. Also, the game would also crash if the player attempts to load a chunk beyond this coordinate, so increasing the render distance can make the rendering limit get closer, resulting again in a crash.^[verify]​^{[more information needed]}

• Coordinates of all entities are multiples of 1,099,511,627,776 (2⁴⁰).
• 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.

• This is the maximum value for a 32-bit floating-point number 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's impossible to go further than this point, as a value of "Infinity" would break rendering code in Bedrock Edition. This could also overflow to read "NaN" (not a number) or a null value, which, again, would break rendering code and result in unpredictable behavior, such as visual glitches, invalid positioning and even the game crashing as a result.^[verify]

• Caves at this point would generate only as single hollowed-out blocks, every 2, 4 and so on.^[verify]

• The game crashes on some certain 64-bit mid-high-end devices.

• Sounds start to play twice at this point^[verify]
  • After 500 quindecillion (5*10⁵⁰), sounds start to play incorrectly.​^{[more information needed]}
    • After 2 sexdecillion (2*10⁵¹), sounds start to mute.

• The cone shape appears on this coordinate after 1.18.0.^[verify]

• Beyond this point, the player sometimes gets stuck at these coordinates.​^{[more information needed][verify]}

• Beyond this point, setting the player to third person view causes the game to crash.^[verify]

• At this point, eating causes the game to freeze and has a 70% of chance that causes the game to crash.^[verify]

• This is the maximum value for a patched 64-bit floating-point number in C++. Beyond this point, just like with the limit of the 32-bit float at around 3.4028237e+38, it is expected that the player's coordinates would also roll over to read "Infinity", assuming it were patched to use 64-bit floats, as the 64-bit double precision has run out of bits to represent coordinate data. It's impossible to go further than this point, as a value of "Infinity" would break rendering code in Bedrock Edition. This could overflow to read "NaN" (not a number) or a null value, which, again, would break rendering code and result in unpredictable behavior, such as visual glitches, invalid positioning and even the game crashing as a result.​^{[more information needed]}

• Altitude of the void floor in the Overworld.^{[after BE 1.18.0]}

• Depth limit of the buildable area of the Overworld.^{[after BE 1.18.0]}

• Altitude of the void floor in the Nether and the End.‌^{[until BE 1.18.0]}

• Depth limit of the buildable area of the Overworld.‌^{[until BE 1.18.0]}, in the Nether and the End.

• Height limit of the buildable area in the Overworld.‌^{[until PE 1.0.0]} and the Nether.

• Height limit of the buildable area in the Overworld.‌^{[until BE 1.18.0]} and the End.

• Height limit of the buildable area in the Overworld.^{[after BE 1.18 0]}

• Particles turn black or dull green (or just dark) depending on the time of day within 64 blocks of this limit, this occurs at every power of 2 starting from this point.^[verify]
• Particles appear to be jittering only if the player has Levitation I or II and floats with them or looks at them closely.
• When the player looks up and down with sensitivity on a low number like 0, the player in 3rd person appears bumpy.
• Snow starts to have a jittery movement beyond this point, getting worse the higher height are.

• Most effect particles cannot rise into the air.
• Opening the inventory is impossible if the player hits this point between ±131,072 and ±262,144, the inventory still works if reloaded the world or the player teleports beyond ±262,144, but not below that point.
• Particle jitter is noticeable beyond this point and appear to be jittering even if the player is standing still.

• Floating with levitation I (1) becomes slightly slower than normal.
• It becomes impossible for Chickens to fall with Slow Falling.
• All effect particles cannot rise into the air.

• Floating with levitation I becomes slightly faster then normal.
• It becomes possible to notice jumping being less smooth if the player summons a shulker this high and jumps on the shulker.

• Levitation II (2) floating is slightly faster at this point.
• It becomes impossible to float with levitation I (1).

• 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. However, noticing the Slow Falling delay is kind of hard.
• Floating with Levitation II (2) and lower becomes impossible.
• Slightly looking upward while gliding with elytra could keep the player height constant.
• It becomes impossible for Chickens to fall.

• 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.
• It is impossible to jump without Jump Boost effect.
• If the player spawns and gets on a shulker, the player appears floating slightly above the shulker even in Survival mode.
• Floating with Levitation V (5) and lower becomes impossible.

• 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, however, particles turn black within 8,192 blocks of this limit.
• 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 significantly faster than normal.
• Floating with Levitation XI (11) and lower becomes impossible.

• The delay described above is even longer.
• Flying downward in Creative is no longer possible.
• Floating with Levitation XXII (22) and lower becomes impossible.
• It is possible to fly over Border Blocks
• The sky Stripe Lands start at this point.

• The player moves slightly in X and Z coordinates. (Negative only)
• It is impossible to teleport beyond these coordinates with /tp command without external tools.

• The delay described above is over twice as long as the previous one.
• Floating with Levitation XLIV (44) and lower becomes impossible.
• Phantoms can no longer swoop up or down at the player.
• Flying upward with elytra and firework rockets becomes impossible.
• Snow particles become suspended in the air.
• The sky Slice Lands start at this point.

• Falling becomes impossible.
• in 3rd person the player can look only horizontal or vertical.
• Floating with Levitation LXXXVIII (88) and lower becomes impossible.
• Flying upward with elytra and jump button in Creative becomes impossible.
• The game crashes at this point if the world is played in any version below 1.18 without the "Caves And Cliffs" experiment feature on this is possible only by using an NBT editor.

• Floating with Levitation CLXXVII (177) and lower becomes impossible.
• It becomes impossible to look up or down in 3rd person.

• Floating with any Levitation level like CCLV (255) becomes impossible since 255 is the maximum vanilla level possible.

• 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.
• In older versions (before 1.2), rain particles become suspended in the air beyond this point.

• Could crash beyond this point on some lower end devices.

• The game crashes near these coordinates on 32-bit devices (see above), although, since the position is 64-bit, there can be a few frames left are rendered before it crashes.
• Although, since the position is 64-bit, there can be a few frames left when the player teleport here.

• The maximum 32-bit floating-point integer in Bedrock Edition. 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's impossible to go further than this point, as a value of "Infinity" would break rendering code in Bedrock Edition. This could overflow to read "NaN" (not a number) or a null value, which, again, would break rendering code and result in unpredictable behavior, such as visual glitches, invalid positioning and even the game crashing as a result.^[verify]

• The maximum 64-bit floating-point integer in Bedrock Edition, comparable to Java Edition. Beyond this point, just like with the limit of the 32-bit float at around 3.4028237e+38, it is expected that the player's coordinates would also roll over to read it is expected that the player's coordinates would roll over to read "Infinity," as the 64-bit double precision has run out of bits to represent coordinate data. It's impossible to go further than this point, as a value of "Infinity" would break rendering code in Bedrock Edition. This could overflow to read "NaN" (not a number) or a null value, which, again, would break rendering code and result in unpredictable behavior, such as visual glitches, invalid positioning and even the game crashing as a result.

​^{[more information needed]}