To fix FPS drops in Minecraft, lower Render Distance and Simulation Distance first, set Max Framerate near your monitor’s refresh rate, make sure the game runs on your dedicated GPU, and on Java Edition install Sodium (the 0.9.x builds support the current 26.x releases) while giving the game enough RAM but not too much. The right order of fixes depends on when the drops happen, so identify the pattern before changing settings at random.
Our Top Picks
ASUS Dual NVIDIA GeForce RTX 5060 8GB GDDR7RTX5060|8GB|OC9 x 4.8 x 2 inches1.4 PoundsCheck on Amazon
Top 3 picks at a glance
Match the symptom to the cause
| When FPS drops | Likely cause | First fix |
|---|---|---|
| Flying or sprinting into new terrain | Chunk generation and loading | Lower Render Distance; pre-generate the world on Java |
| Near large farms or mob grinders | Too many entities and ticking blocks | Lower Simulation Distance and Entity Distance |
| Short freezes every few seconds (Java) | Memory pressure and garbage collection | Adjust allocated RAM to 4–8 GB |
| Locked at 30, 45 or 60 FPS | VSync, integrated GPU or laptop power saving | Check VSync, GPU assignment and power plan |
| Only with shaders or Vibrant Visuals | GPU limit | Lower shadow and reflection quality or resolution scale |
| Blocks snap back, mobs freeze, FPS normal | Server lag, not FPS | Check server TPS; client settings will not help |
The last row matters: rubber-banding and delayed block breaking on a multiplayer server are caused by low server ticks per second, not by your frame rate. Press F3 on Java to see your actual FPS before blaming your PC.
Why render distance is the biggest lever
Render Distance is measured in chunks in each direction, so the area the game has to build and draw grows with the square of the setting, roughly (2 × distance + 1)² chunk columns. Small reductions remove a surprisingly large amount of work.
| Render Distance | Approx. chunk columns | Work vs 16 chunks |
|---|---|---|
| 8 | 289 | About 27% |
| 12 (Java default) | 625 | About 57% |
| 16 | 1,089 | 100% |
| 24 | 2,401 | About 220% |
| 32 (Java maximum) | 4,225 | About 390% |
Dropping from 16 to 12 chunks cuts the loaded area by roughly 43%. Simulation Distance works the same way for ticking: it controls how far mobs move, crops grow and redstone runs, and it costs more per chunk than rendering. Keeping it lower than Render Distance is the usual compromise; you still see far, but the CPU only simulates what is near you.
Java Edition fixes, in order
1. Set the core video options
In Options, then Video Settings, the current layout groups settings into Display, Quality and Performance, and Interface sections.
- Preset: start from Fast, then customize. Any manual change switches it to Custom.
- Render Distance: 8–12 chunks on integrated graphics or older CPUs, 12–16 on mid-range systems.
- Simulation Distance: 5–8 chunks in single-player unless your farms need more. 5 is the minimum.
- Max Framerate: match your refresh rate (for example 144 on a 144 Hz monitor). The default is 120; Unlimited makes the CPU work harder for frames you cannot see.
- VSync: off if you see a hard cap at half your refresh rate, on if tearing bothers you and your FPS stays above the refresh rate.
- Chunk Builder: keep Threaded. Semi Blocking and Fully Blocking stall frames while chunks rebuild.
- Biome Blend: Off or 3×3. Higher values slow chunk building noticeably.
- Clouds Off or Fast, Particles Decreased, Entity Distance around 75%, Entity Shadows off, Improved Transparency off.
2. Try both Graphics API options (26.2 and newer)
Java Edition 26.2 added a Graphics API option in the Display section with Default, Prefer Vulkan (Experimental) and Prefer OpenGL. In 26.3, Default still means OpenGL. Vulkan can help some GPUs and hurt others while it is experimental, so compare both on your system and keep whichever gives steadier frame times. The setting needs a restart and does not affect worlds or servers. Mods that render through OpenGL may not work with Vulkan yet.
3. Install Sodium
Sodium replaces Minecraft’s chunk rendering engine and remains the most widely used performance mod. Current 0.9.x builds cover Minecraft 26.1.2 and 26.3 on both Fabric and NeoForge, and recent versions added asynchronous occlusion culling. Use Iris alongside it if you want shaders, and check that your Iris version supports your Sodium version before updating either. OptiFine is not compatible with Sodium; pick one approach.
4. Fix memory allocation
The official launcher allocates 2 GB by default, which is tight once you add mods or high-resolution resource packs. Regular freezes every few seconds usually mean the Java garbage collector is struggling. Use these ranges as a guide:
- Vanilla or a few performance mods: 4 GB.
- Medium modpacks (around 100 mods): 6 GB.
- Large modpacks: 6–8 GB.
Do not allocate more than about half your system RAM. Over-allocation makes each garbage-collection pause longer, which turns small hitches into big ones. Since 26.1, Java Edition requires Java 25, but the official launcher bundles the correct runtime, so you do not need to install Java yourself.
5. Pre-generate busy worlds
If drops only happen when exploring, the bottleneck is terrain generation. A pre-generation mod such as Chunky can generate a radius around spawn while you are away from the keyboard, so later exploration only loads chunks instead of creating them.
Bedrock Edition fixes
Bedrock runs on a different engine, so mods like Sodium do not apply. Its main performance controls are in Settings, then Video.
- Graphics Mode: Simple gives the highest frame rate, Fancy is the balanced choice, and Vibrant Visuals is by far the most demanding. The mode can only be changed from the main menu, not inside a world.
- If you keep Vibrant Visuals, lower shadow quality, point light shadows, volumetric fog and reflections first, and reduce the resolution scale to about 75%. That noticeably cuts GPU render work with little visible loss at 1080p and 1440p, while 50% is a last resort that looks soft.
- Render Distance: 12–16 chunks is a sensible PC starting point; raise it slowly until drops return, then step back.
- Simulation Distance is a world setting on Bedrock, offering 4 to 12 chunks. Set 4–8 for weaker PCs.
- Turn off VSync if FPS is stuck at a fraction of your refresh rate, such as 45 FPS on a 144 Hz display.
- If FPS collapses after a recent update even on Simple graphics, try disabling Improved Input Response and restarting; some players have linked it to a memory leak.
- Keep the game updated. Bedrock 26.50 fixed stuttering after long play sessions or when the game was left suspended.
PC checks that affect both editions
- Force the dedicated GPU: open Windows Settings, then Display, then Graphics, add javaw.exe or the Minecraft app, and choose High performance. Laptops often default to integrated graphics.
- Plug in laptops and use a balanced or performance power plan; battery mode can halve frame rates.
- Update GPU drivers, especially if you switch to the Vulkan option on Java.
- Close background downloads, browser video and recording software while you diagnose.
- Watch temperatures. If FPS falls after 15–20 minutes regardless of what you do in game, thermal throttling is likely.
Frequently asked questions
Why is my FPS high but the game still stutters?
Average FPS hides frame-time spikes. Chunk loading and garbage collection create short freezes that barely move the average. Lower Render Distance and check your RAM allocation rather than chasing a higher FPS number.
Does more RAM always mean better performance?
No. Minecraft needs enough memory to avoid constant garbage collection, but allocating far beyond what the game uses makes each collection pause longer.
Still Dropping Frames? When an Upgrade Makes Sense
If Minecraft still stutters or falls below your monitor’s refresh rate after every fix above, the limit is usually the graphics card or system memory rather than a setting. These are common upgrade paths for that situation.
As an Amazon Associate we earn from qualifying purchases at no extra cost to you.
