All articles
GuidesJul 26, 2026 7 min read

How to Boost FPS in Minecraft: A Complete Performance Guide

Get more frames in Java Edition — the mods that genuinely help, the video settings worth changing, and how to allocate RAM without making things worse.


Minecraft is unusually demanding for how simple it looks, and the default settings are not tuned for performance. The good news is that a handful of changes reliably transform frame rates — and the biggest one is free.

Start with performance mods

This is the highest-value change by a wide margin. Vanilla's renderer is old, and modern replacements are dramatically faster. All of these are on our Mods page:

  • Sodium — a full rewrite of the rendering engine. On many machines it doubles frame rates on its own, with no visual downgrade. If you install one thing, install this.
  • Lithium — optimises game logic, mob ticking and pathfinding. No visual change at all, but it smooths the stutter you get near farms and villages.
  • FerriteCore — cuts memory usage substantially, which matters most on machines with limited RAM.
  • Iris — adds shader support and is built to run alongside Sodium, so you are not trading frames for visuals.

Our mod installation guide walks through getting these running if you have not modded before. None of them change gameplay, so they are safe on any survival world.

The video settings that matter

Not all settings cost the same. In rough order of impact:

  1. 1.Render distance. By far the most expensive setting. Every extra chunk is more terrain to build, light and draw. Dropping from 16 to 10 chunks is often worth 40% or more.
  2. 2.Simulation distance. Separate from render distance, and frequently overlooked. It controls how far away the game keeps *simulating* mobs, crops and redstone. Lowering it to 6–8 helps a great deal on busy worlds and costs you almost nothing visually.
  3. 3.Graphics: Fancy vs Fast. Fast simplifies leaves, clouds and water. On weak hardware this is a real gain.
  4. 4.Smooth lighting. Set to minimum or off for a noticeable boost on older GPUs.
  5. 5.Particles: Decreased or Minimal. Helps enormously in combat and near farms.
  6. 6.Entity distance and entity shadows. Lower the first, disable the second, especially if you run mob farms.
  7. 7.VSync. Caps frames to your monitor's refresh rate. Turn it off when benchmarking, then decide whether you prefer the smoothness.
TipChange one setting at a time and check the effect with F3. Changing six at once tells you nothing about which actually helped.

Allocating RAM — less is often more

This is where well-meaning advice goes wrong. Minecraft does not run better with as much RAM as you can give it. Java's garbage collector has to work through whatever you allocate, and an oversized heap produces longer pauses — which you feel as periodic stutter rather than low frames.

Sensible allocations:

  • Vanilla or light mods — 2–4 GB is plenty.
  • Medium modpacks — 4–6 GB.
  • Large kitchen-sink packs — 6–8 GB.

Going beyond 8 GB rarely helps and often hurts. To change it, open the Minecraft Launcher, go to Installations, edit your profile, open More Options, and adjust the -Xmx value in the JVM arguments. -Xmx4G means a 4 GB maximum.

Never allocate more than about half your system's physical RAM. Your operating system needs the rest, and swapping to disk is far slower than anything you gained.

Housekeeping that genuinely helps

  • Update your graphics drivers. This fixes more Minecraft performance problems than any in-game setting, and it is the first thing to try if frames suddenly got worse.
  • Close background applications. Browsers with many tabs and chat apps with hardware acceleration compete for the same GPU.
  • Use a lower-resolution resource pack. A 16x pack costs essentially no extra VRAM, while a 256x one uses considerably more. Our resource packs are labelled by resolution.
  • Check you are using the right GPU. Laptops with both integrated and dedicated graphics sometimes run Java on the integrated chip. Force Minecraft's Java executable to the dedicated card in your driver control panel.
  • Turn off fullscreen if it stutters. Borderless windowed is smoother on some setups.

Reading F3 properly

Press F3 and look at the top-left. The first number is your current frame rate. The C: value shows rendered chunk sections — if that number is enormous, your render distance is doing the damage. Watch for the frame time graph (F3 plus 2 on many setups); consistent spikes point at garbage collection or chunk loading rather than raw GPU load, and those are fixed by RAM tuning and Lithium rather than by lowering graphics.

What to expect

On a typical mid-range machine, installing Sodium and Lithium, dropping render distance to 12 and simulation distance to 8, and setting particles to Decreased will usually take a stuttering 45 FPS experience to a comfortable, stable one. Only after that is it worth adding a shader — and if you do, start with a pack rated Potato or Low.

#Performance#Mods#Sodium