How to Boost FPS in Minecraft: Settings, Mods and Fixes That Work

First, confirm it is FPS and not lag

Players use “lag” for two unrelated things. If the whole picture stutters — turning your head is choppy, the frame counter is low — that is FPS, produced by your own device, and this guide fixes it. If the game renders smoothly but blocks reappear after you break them and you get pulled backwards, that is network latency, and you want the ping guide instead. Press F3 on Java to see the FPS counter top-left; on Bedrock, enable the FPS display in video settings or watch for the stutter.

A third possibility on multiplayer is server lag: everything slows for everyone at once, mobs freeze, chat lags. Nothing on your side fixes that.

The in-game settings that matter, in order

Options → Video Settings on Java. These are ranked by how much frame rate they cost relative to how much you notice them.

Render distance alone is often the whole fix. Players set it to 24 because the slider goes there, then wonder why a capable PC drops to 40 FPS in a forest.

Performance mods: Sodium, Lithium, OptiFine

Java Edition’s vanilla renderer is not efficient, and a mod that replaces it is the single largest improvement available — larger than any hardware upgrade short of a new GPU. There are two families:

Sodium (Fabric)

Sodium rewrites the rendering engine and typically doubles or triples frame rates while smoothing out the stutters when chunks load. It needs the Fabric mod loader, which is a two-minute installer from fabricmc.net. Pair it with Lithium (game logic optimisation) and, if you want shaders, Iris. Sodium has no built-in zoom or connected textures; small separate mods add those. This is the recommended setup for anyone on 1.21.

OptiFine

OptiFine is the older all-in-one: performance, zoom, connected textures, dynamic lighting and shader support in a single jar that installs into the vanilla launcher without a mod loader. It still helps, especially on very old versions, but on modern Minecraft it gives smaller gains than Sodium and lags behind on version support. If you already use it and are happy, there is no urgent reason to switch; if you are installing fresh, Sodium wins.

Installing Fabric and Sodium

1. Download the Fabric installer from fabricmc.net, run it, choose your game version, click Install. A “fabric-loader” profile appears in the launcher.
2. Download Sodium (and Lithium) from Modrinth for the same game version. Put the .jar files in your .minecraft/mods folder (open it via the launcher: Installations → the profile → folder icon).
3. Launch the Fabric profile. Check Video Settings — Sodium replaces the screen with its own.

Mods only affect your client; you can join any vanilla server with them. Download only from Modrinth or CurseForge — sites offering “OptiFine download” with an installer .exe are malware.

Allocating RAM properly

The launcher gives Java Edition 2 GB by default, which is enough for vanilla. If you run a modpack or notice frequent stutters with “Allocated memory” near 100% in the F3 screen, raise it: Installations → Edit → More Options → JVM arguments, change -Xmx2G to -Xmx4G. Rules of thumb:

• Vanilla or Sodium: 2–3 GB. Modpacks: 6–8 GB, or whatever the pack recommends.
• Never more than half your physical RAM. The game, the OS and your browser need the rest.
• More is not faster past what the game needs. Very large heaps make garbage collection pauses longer, which appears as periodic stutter.

If you have 8 GB total, 3–4 GB is the ceiling. If you have 4 GB total, Minecraft will struggle regardless, and the PC guide is the honest next read.

Laptop and Windows fixes

Laptops lose frames for reasons that have nothing to do with the game.

• Integrated vs dedicated GPU. Laptops with an NVIDIA or AMD card often run Java on the weak integrated Intel/AMD chip instead. Press F3 and read the GPU line on the right; if it says Intel UHD or AMD Radeon Graphics (no model number) while you own a proper card, fix it in Windows Settings → System → Display → Graphics: add javaw.exe (from the launcher’s runtime folder) and set it to High Performance.
• Power mode. On battery, Windows throttles the CPU and GPU hard. Plug in, and set the power plan to Best Performance while gaming.
• Thermals. A laptop that starts at 120 FPS and drops to 40 after ten minutes is overheating and throttling. Clean the vents, use it on a hard surface, consider a cooling pad. Ten-minute FPS is the number that matters.
• Background apps. Discord’s hardware acceleration, Chrome with forty tabs, and antivirus scans all compete. Close what you can.
• Drivers. Update the graphics driver from NVIDIA, AMD or Intel directly, not Windows Update. Old Intel drivers in particular cause stutter and crashes in Java.
• Windows Game Mode is fine to leave on; “Hardware-accelerated GPU scheduling” is worth trying both ways.

Bedrock: phone, console and Windows

Bedrock is written in C++ and runs far better than Java on the same hardware, but phones and older consoles still hit limits. In Settings → Video:

• Render distance to 8 chunks on phones, 10–12 on consoles and PCs. This is still the dominant setting.
• Fancy graphics, fancy leaves, smooth lighting, beautiful skies off on phones.
• Resolution scale (in Windows Bedrock and on some phones) down to 75% or lower for a large gain on weak GPUs.
• Max framerate capped at 60 (or your screen’s rate). On phones this also cuts heat, which prevents the throttling that causes stutter after a few minutes.
• Ray tracing off on Windows unless you have an RTX-class card and want the look.
• Particle render distance and anti-aliasing down on phones.

Xbox Series and PlayStation 5 run Bedrock at a locked 60 with high settings; if a console stutters, it is almost always a heavily modified world or a marketplace map with too many entities. On Nintendo Switch, render distance to 7 or 8 is the difference between playable and not.

Shaders without killing your FPS

Shader packs (SEUS, BSL, Complementary, and the many lightweight ones) transform how the game looks and cost anywhere from a third to ninety percent of your frame rate. If you want them on a modest PC: use Iris with Sodium rather than OptiFine, choose a pack marked as lightweight (Complementary Unbound at low settings, or one of the “lite” packs), keep render distance at 8, and turn off the pack’s shadows or reduce shadow resolution first — shadows are the most expensive single feature. On Bedrock, deferred/vibrant visuals on Windows and higher-end phones provide a similar look with a built-in performance profile.

Frequently asked questions