Render distance sets how many chunks you can see. Simulation distance sets how many chunks around you actually run: mobs move, crops grow, fluids flow. Lower render distance if drawing the world costs you frame rate. Lower simulation distance if a busy world of mobs, farms and machines is the load. The Minecraft Wiki says simulation distance is the more taxing of the two at the same number, so it is the stronger lever per step, and the one that changes gameplay.
This page rests on four Minecraft Wiki pages read on 10 October 2026 (linked at the end). We did not play, benchmark or profile anything, so there are no frame-rate figures here. Where the wiki gives a direction, we give the direction and attribute it.
The two settings side by side
| Fact | Render distance | Simulation distance |
|---|---|---|
| What it controls | How many chunks are visible at once (Java Options page) | The area where entities are updated and blocks and fluids are ticked |
| Java singleplayer range | 2 to 32 chunks, or 16 if under 1 GB of memory is allocated to the game | 5 to 32 chunks on high device performance, 5 to 16 on low |
| Java singleplayer defaults | 16 on Fancy graphics, 8 on Fast, 32 on Fabulous! | 12 on high device performance, 8 on low |
| Java server.properties key | view-distance, 10 by default as of 26.3 | simulation-distance, 10 by default as of 26.3 |
| Bedrock | Range not covered by the sources we read | World option, even numbers 4 to 12 on high device performance with a default of 4, 4 to 8 on low |
| Where Java keeps it | Video Settings, Quality & Performance | Video Settings, Quality & Performance, shared by all worlds |
| Beyond the edge | Terrain fades into the sky colour | Nothing moves or changes |
What render distance controls
On Java Edition, the wiki describes render distance as how many chunks of the world are visible at once. Fewer chunks means each frame can be drawn faster, which raises frame rate. The farthest terrain fades into the sky colour like fog, which is why some players call the option fog.
The number is a radius. A distance of 8 chunks is 128 blocks each way and 289 chunks in total, while 16 chunks is 1,089 and 32 chunks is 4,225 (wiki figures). Doubling the setting roughly quadruples the chunks drawn. Entities are hidden at the render edge too: at 100% entity distance they are visible up to 160 blocks away unless render distance is lower.
What simulation distance controls
On Java, simulation distance defines a square of chunks around you where entities are ticked. The wiki's example is a distance of 6, which gives a 13×13 chunk square where entities move normally. One chunk further out, redstone may run, fluid may flow and crops may grow. Past that, nothing changes. Its Chunk page gives the square side as the smaller of 2s + 1 and 63 chunks, where s is your setting.
On Bedrock, the same option is a per-world setting that also limits mob spawning and despawning. The wiki says pure redstone circuits keep working at any distance, but break where they touch hoppers, pistons, observers or anything else that needs ticks.
How each setting affects lag
The wiki's Options page says simulation distance is more taxing on performance than the equivalent level of render distance. Its simulation page adds that the setting is ideally lower than render distance, because updating every entity in range costs more than drawing the same chunks. We have no number for how much more, and none is sourced.
The two costs show up differently. Render distance mostly decides how much the screen has to draw, so it is tied to frame rate. Simulation distance decides how much the world has to process, which grows with the mobs, farms and machines inside the square. The wiki does not split the two into frame rate versus tick lag, so treat that reading as our summary of its descriptions, not a measured result.
What you see when you lower each one
- Lower render distance, and the horizon moves in. Distant hills and structures fade out sooner. Nothing about how the world behaves changes.
- Lower simulation distance, and the world looks the same but stops acting at range. On Java, mobs and crops past the square freeze. On Bedrock, mobs also spawn and despawn within a smaller shell around you.
- Set simulation above render distance and you can have chunks that tick but are not drawn. The Chunk page's examples show this: with simulation 5 and render 2, entities move within a 5×5 chunk column, but crops stop growing just outside it.
Which to lower first on a weak device
Start with the symptom. If the frame rate is low while you explore or fly, lower render distance first, since the wiki ties fewer visible chunks to faster frames. If the game stutters near big farms, redstone or crowded pens, lower simulation distance, since that setting decides how much of that is running. Our general lag and FPS guide covers the other settings to try.
If you want both, the wiki's point that simulation costs more per chunk suggests trimming simulation distance toward the low end of its range before cutting render distance hard. The trade-off is plain: a lower simulation distance stops crops and mobs near the edge of your area, which a lower render distance never does. A farm you rely on needs to stay inside the simulation square, so stand near it.
Hardware sets some limits for you. The wiki notes Bedrock caps simulation distance at 10 chunks on Xbox and PlayStation and at 6 on devices with under 2 GB of RAM. On Java, the low-performance range tops out at 16 and the render maximum drops to 16 if the game has less than 1 GB allocated. Our RAM allocation guide covers that last case.
Where the settings live on Java, Bedrock and servers
On Java, both sliders are under Video Settings, Quality & Performance. The simulation distance setting is shared by all worlds on the client and can be changed at any time. On Bedrock, simulation distance sits in the Advanced tab of the create-world or edit-world screen, belongs to that one world, and cannot be changed while the world is loading. Our Java vs Bedrock comparison covers other differences between the two.
On a Java server, view-distance and simulation-distance are keys in server.properties, both 10 by default as of 26.3, and the server must be restarted after a change. The wiki lists entity-broadcast-range-percentage as another lever: higher values send entities from farther away and can cause more lag. Hosting is covered in our modded server guide.
What this means if you use mods
If you play with mods, the two settings above still apply as the wiki describes them. Distant Horizons has its own page, How to use Distant Horizons. Performance mods are listed under Minecraft performance mods. None of the wiki pages we read say how any mod changes these two settings, so we make no claim on that.
