Two sliders sit next to each other in the Minecraft video settings, and they look like they do the same thing. They do not. Render distance and simulation distance control entirely separate systems, and confusing them is one of the most common reasons people tune performance in the wrong direction.

Set render distance too high and your GPU struggles, your FPS drops, and frames stutter. Set simulation distance too high and the server tick falls behind, mobs rubber-band, and your farms run slow even though the picture looks smooth. These are different failures with different fixes.

This guide explains exactly what each slider does, what it costs and on which side of the client-server line, and how to set them for 1.21.4 Java Edition so you stop paying for chunks you do not need.

The short definition

  • Render distance is how far the client draws the world. It is a visual radius, measured in chunks, controlling how many chunk sections your graphics card builds geometry for and renders to the screen.
  • Simulation distance is how far the server ticks the world. It is a logic radius, also in chunks, controlling where mobs spawn and move, crops grow, redstone updates, fluids flow, and block ticks happen.

The key insight: you can render far without simulating far. A huge render distance shows you distant terrain, but if that terrain is outside simulation distance, it is a frozen photograph. Nothing in it is alive.

Even in single-player, "the server" is real. Minecraft runs an internal server thread inside your game. Simulation distance governs that internal server, render distance governs the client that draws what the server reports. This is why the two can be tuned independently even when one machine does both jobs.

What render distance costs, and where

Render distance is paid by your client: CPU for building chunk meshes and GPU for drawing them. The cost scales roughly with the square of the radius, because each step out adds a full ring of chunks around you.

That square scaling is why small changes have large effects. Going from render distance 16 to render distance 12 does not cut the work by a quarter. The number of rendered chunks scales with the area, so dropping from 16 to 12 removes roughly 44 percent of the rendered chunk volume. Going from 32 to 16 is a far bigger cut than the numbers suggest.

Symptoms of render distance set too high:

  • FPS drops, especially when turning the camera quickly
  • A freeze when you cross into a new area and chunks have to be meshed
  • Steady GPU usage near 100 percent with no improvement in feel

The fix when FPS is your problem is to lower render distance first, then raise it back slowly until it stays stable. With performance mods this ceiling rises dramatically: Sodium rebuilds the render pipeline and lets midrange hardware run render distances that vanilla cannot, and it adds fog and culling options that make distant chunks cheaper still.

If your FPS is fine but distant terrain pops in late, that is not a render-distance problem, it is chunk loading speed. Raising render distance will not fix pop-in caused by slow disk or chunk generation. Pre-generated worlds load far chunks much faster, which is a separate topic covered below.

What simulation distance costs, and where

Simulation distance is paid by the server tick, which has a hard budget of 50 milliseconds per tick to hit the target of 20 ticks per second. Every chunk inside simulation distance is a chunk the server must process every tick: entity AI, mob spawning attempts, random block ticks for crops and leaves, redstone, fluid spread, and more.

This cost also scales with area, but the consequence is different. Render distance overload hurts FPS, a client problem you feel as choppiness. Simulation distance overload hurts TPS, a server problem you feel as the world running in slow motion: blocks break a beat late, mobs teleport, farms produce less than they should.

Symptoms of simulation distance set too high:

  • TPS below 20 with smooth FPS (the picture is fine, the world is slow)
  • Mobs stuttering or snapping to new positions
  • Farms underperforming because their processing chunks are competing for tick time

More simulation distance is not more performance and is frequently worse. Every extra ring of simulated chunks is more entities to tick and more spawn attempts to run. On a busy server, a high simulation distance can be the single largest TPS drain. Set it to cover where players actually are, not as a "max everything" reflex.

The mechanic that surprises people: spawning and farms

Mob spawning is tied to simulation distance, not render distance, and this trips up a lot of farm builders.

In 1.21.4, hostile mobs attempt to spawn in chunks that are within simulation distance of a player. If your simulation distance is 8, the spawning sphere extends out to roughly that radius around you. Chunks you can see in the far distance, but that sit outside simulation distance, will never spawn a mob because the server is not ticking them.

This has direct consequences for farm design:

  • A mob farm needs to be inside simulation distance to run while you wait at it. If you stand too far from the spawn platforms relative to your simulation distance, spawns stop.
  • Lowering simulation distance can actually improve a farm's rates in some cases, because it shrinks the spawnable area and concentrates the mob cap closer to your farm instead of spreading spawn attempts across distant caves.
  • The minimum useful simulation distance is effectively driven by what you need ticking. A simulation distance of 4 is enough to keep a compact farm running near you, while saving a large amount of tick budget.

The same logic applies to crop growth, sugar cane, redstone clocks, and anything time-based. If it is outside simulation distance, it is paused. This is why a redstone contraption keeps running when you are near it and stops when you walk far enough away.

How to set both for 1.21.4

The principle is simple once the two are separated in your head: render for the view you want, simulate for the activity you need.

For a single-player client on decent hardware:

Render distance:     12 to 16 chunks
Simulation distance: 6 to 8 chunks

Render high enough that the world looks good, but keep simulation lower because you rarely need distant chunks ticking. This split alone recovers a lot of TPS headroom on a single machine doing both jobs.

For a multiplayer server, the equivalent settings live in server.properties:

view-distance=10
simulation-distance=6

Here view-distance is the server's cap on how far it will send chunk data to clients (the server-side render ceiling), and simulation-distance is the tick radius. On a populated server, keeping simulation distance modest is the highest-leverage TPS setting you have. A server with twenty players at simulation distance 10 is ticking a vast combined area; dropping to 6 can transform TPS without players noticing any loss in how the world looks.

A clean rule of thumb: if FPS is your complaint, touch render distance. If TPS is your complaint, touch simulation distance. They almost never need adjusting in the same direction, and tuning the wrong one is how people end up convinced "lowering settings did nothing."

How they interact with performance mods

On Fabric in 1.21.4, the two sliders interact with different mods:

  • Sodium raises the render-distance ceiling by making rendering cheaper. It is the answer when render distance is your FPS limiter.
  • Lithium optimizes game logic and entity ticking, which is the simulation-distance side. It lets a given simulation distance cost less tick time, so you can keep farms ticking with less TPS penalty.

These attack opposite sides of the line, which is exactly why a strong performance stack usually includes both. Sodium does nothing for TPS, and Lithium does nothing for FPS. Knowing which slider is hurting tells you which mod is doing the work.

There is also a relationship with chunk loading. A high render distance over ungenerated terrain forces world generation, which spikes both client meshing and server tick time as new chunks are created. Pre-generating the world removes that spike, so far render distances stay smooth even while exploring. That is a separate optimization worth doing on any server where players roam.

The takeaway

Render distance and simulation distance are not two strengths of the same setting. One is a GPU bill paid in FPS, the other is a CPU bill paid in TPS. Render distance decides how far you can see; simulation distance decides how far the world is alive, including where mobs spawn and whether your farms run.

Set render distance for the view you want your hardware to hold, set simulation distance only as wide as the activity you need ticking, and you will stop paying twice for chunks that only ever needed one of the two.

Sources & further reading: