Simulation distance is the range, measured in chunks, around your player where the game actively processes world mechanics. Within this range, mobs spawn and move, crops grow, water flows, and redstone circuits fire. Anything outside it is frozen in place, waiting for you to get closer.
The concept is most commonly associated with Minecraft, where it appears as a dedicated setting in both Bedrock and Java editions, but the underlying idea applies to any game that needs to limit how much of the world it calculates at once.
How Simulation Distance Works
A game world can be enormous, but your hardware can only process so much at a time. Simulation distance solves this by creating a bubble of active gameplay around you. Inside that bubble, the game engine runs every calculation it normally would: animals wander, villagers trade, furnaces smelt, lava spreads, and spawners produce mobs. Outside that bubble, the world exists in a saved but completely inactive state. Nothing happens there until a player moves close enough to bring it within range.
In Minecraft, distance is measured in chunks, which are 16×16 block columns stretching from bedrock to sky. A simulation distance of 4 chunks means the game processes mechanics in a square area extending 4 chunks out from you in every direction. Bedrock Edition measures this using taxicab distance (counting chunk steps horizontally and vertically on a grid) rather than straight-line distance, which means the active area forms a diamond shape rather than a circle.
The simulation area has a thin border with slightly different rules. One chunk beyond the main simulation zone, redstone can still run, fluids can still flow, and crops can still grow under normal random tick rules. But entities like mobs and animals are not updated in that outer ring.
Simulation Distance vs. Render Distance
These two settings control completely different things. Render distance determines how far you can see. It tells the game’s graphics engine how many chunks of terrain, buildings, and entities to draw on screen. Simulation distance determines how far the world is alive. It tells the game’s logic engine which chunks receive active updates.
Simulation distance is always set to a value equal to or lower than render distance. This means everything being simulated is also being rendered and visible to you, but not everything you can see is actually being simulated. You might spot a village on the horizon, but if it’s outside your simulation distance, those villagers are standing perfectly still and no crops in their farms are growing.
The split exists because rendering and simulation tax different parts of your hardware. Drawing distant terrain is mostly a job for your graphics card. Processing mob behavior, block updates, fluid physics, and spawning logic is a job for your processor. By separating the two distances, you can enjoy long sightlines without crushing your CPU under the weight of thousands of simultaneous game calculations.
What Gets Affected
Nearly every active mechanic in the game depends on simulation distance:
- Mob spawning and despawning. Hostile and passive mobs only spawn within the simulation range. If you build a mob farm outside this range, it produces nothing. Mobs that wander outside the range stop being processed entirely.
- Crop and plant growth. Wheat, carrots, trees, and other plants only grow inside the simulated area (or the one-chunk border zone). A farm left behind while you explore stays frozen until you return.
- Redstone and mechanical systems. Pistons, comparators, hoppers, and other redstone components only operate within simulation range. Automated sorting systems or clocks stop working when you walk away.
- Fluid movement. Water and lava only flow and update within the active zone. A lava flow you triggered won’t continue spreading once you leave the area.
- Entity behavior. Animals, villagers, dropped items, minecarts, and any other entities freeze in place outside the simulation bubble.
Impact on Performance
Simulation distance has a direct and significant effect on how hard your processor works. Every additional chunk added to the simulation range means more mobs to path-find, more blocks to tick, and more game logic to resolve each server tick (which runs 20 times per second in Minecraft). Doubling your simulation distance roughly quadruples the number of active chunks because the area is measured in two dimensions.
On a single-player world, a high simulation distance can cause the game to lag, stutter, or fail to keep up with the normal tick rate. On a multiplayer server, the problem compounds because the server has to maintain a simulation bubble around every connected player. If ten players are spread across the map with a high simulation distance, the server processes a massive number of active chunks simultaneously. Lowering the simulation distance is one of the most effective ways to stabilize a struggling server.
Render distance, by comparison, primarily affects your graphics card and the frame rate you see on screen. If you’re experiencing visual lag (low FPS), render distance is the setting to lower. If the world itself feels slow, with mobs teleporting, crops not updating, or redstone behaving erratically, simulation distance is the bottleneck.
Choosing the Right Setting
In Bedrock Edition, you can set simulation distance per world, with options typically ranging from 4 to 12 chunks. Java Edition ties it to a video setting that works alongside render distance. The default values differ by platform: mobile devices and consoles often default to 4 chunks to preserve performance, while desktop versions may default higher.
For most players, 4 chunks is sufficient for general survival gameplay. It keeps farms, mob spawners, and redstone systems working as long as you stay reasonably close to them. A setting of 6 to 8 chunks gives you more breathing room, letting you build larger bases with distant automated systems that stay active while you work on other parts of your build. Going above 8 chunks is generally only practical on powerful hardware or lightly loaded servers.
If you rely on mob farms or automated crop systems, simulation distance is one of the most important settings in the game. A carefully designed mob grinder placed just outside the simulation range will produce exactly zero drops. Plan your builds around the setting, or adjust the setting to cover your builds.
Ticking Areas: Expanding Simulation Beyond the Bubble
Minecraft offers a workaround for the limits of simulation distance: ticking areas. These are specific regions you can designate (through commands in Bedrock Edition) to remain actively simulated regardless of player proximity. A ticking area keeps processing mob spawns, redstone, and crop growth even when every player on the server is far away.
This is useful for builds that need to run continuously, like experience farms near spawn or automated food production systems. But each ticking area adds to the server’s processing load in the same way a nearby player would, so they should be used sparingly. Adding too many ticking areas can degrade server performance just as much as setting an unreasonably high simulation distance.