Why Is Minecraft So Laggy? Fix Lag on Java & Bedrock
By Tier1Settings Updated Published
On this page
Minecraft is laggy mostly because of render distance and chunk loading, not a weak GPU: drop render distance to 12 chunks, then on Java allocate about 4 GB of RAM and install Sodium, and on Bedrock switch off Vibrant Visuals or ray tracing and lower simulation distance. That is why Minecraft can show hundreds of FPS and still feel choppy. This guide fixes Minecraft lag, stuttering and lag spikes on PC for both Java and Bedrock editions.
| Your symptom | Most likely cause | First fix |
|---|---|---|
| Freezes every few seconds (Java) | Garbage-collection pauses, too much or too little RAM | Set RAM to 4–8 GB, install Sodium |
| Hitches when moving or flying | Chunk loading from high render distance | Render distance 12 chunks, game on an SSD |
| Bedrock low FPS on a decent PC | Vibrant Visuals / ray tracing, high render distance | Graphics mode → Fancy, render distance down |
| Bedrock lag around farms and redstone | Simulation distance too high | World settings → Simulation Distance 4–6 |
| Smooth in singleplayer, laggy on servers | Network or server lag | Not a settings problem: check ping, try another server |

Work top to bottom — the RAM and render-distance fixes solve most cases before you touch anything else.
Java vs Bedrock: different causes
- Java Edition stutter is mostly JVM garbage-collection pauses, wrong RAM allocation, high render distance, and the default renderer. Mods fix most of it.
- Bedrock Edition stutter is usually render distance, drivers, and background apps — there’s no RAM slider to tune, so the fixes are simpler.
Java players: work through the RAM and Sodium sections. Bedrock players: jump to Bedrock: fix lag on Windows, then the render-distance, driver and Windows sections.
Java: allocate the right amount of RAM
More RAM is not better. Over-allocating makes the garbage collector pause longer when it runs, which shows up as a periodic freeze.
- In the launcher, open Installations → your profile → More Options.
- Set
-Xmxto a sensible amount:- Vanilla / light packs:
4G - Medium modpacks:
6G–8G - Only go higher if you get out-of-memory crashes.
- Vanilla / light packs:
- Leave several GB free for Windows and other apps.
If you’re on a big modpack and still see periodic freezes, the JVM’s garbage collector is the cause — the mods below help more than raw RAM.
Java: install Sodium (the biggest single fix)
For Java Edition, Sodium rewrites the rendering engine and cuts frame-time spikes more than any setting.
- Install Fabric (mod loader).
- Add Sodium (rendering), Lithium (game logic / tick performance), and FerriteCore (memory use).
- Launch and test — 1% lows usually improve immediately.
If you want shaders, use Iris alongside Sodium. Prefer OptiFine? It also helps and adds shader support, but Sodium generally gives steadier frame pacing.
Bedrock: fix lag on Windows
Minecraft Bedrock (the Microsoft Store / Xbox app version on Windows) can’t use Java mods or a RAM slider, so the fixes are all in settings. Work through these in order:
- Graphics mode. In Settings → Video, check the graphics mode. Vibrant Visuals and ray tracing are far heavier than Fancy, and Simple is lighter still. If Bedrock is laggy on a mid-range PC, switch to Fancy first. Graphics options have been known to change after game updates, so re-check this after every update.
- Render distance. Lower it in Settings → Video until frame rate holds steady. Bedrock lets you push render distance far past what most PCs can stream smoothly, so start around 12–16 chunks and raise it only while movement stays smooth.
- Simulation distance. This lives in the world’s settings, not the video menu (edit the world, or set it when creating one). It controls how far mobs, crops, redstone and other block updates keep running. Big farms and redstone builds lag at high values, so try 4–6 chunks. Lowering it reduces CPU load without changing how far you can see.
- Lighter visual extras. Turn off Beautiful Skies, and turn off Smooth Lighting if it still hitches.
- Reinstall if you’re on an old build. Since version 1.21.120, Bedrock on Windows ships as a GDK app instead of the old UWP app, and newer versions need a fresh install from the Microsoft Store. If your game stopped updating, back up your worlds (the
com.mojangfolder) first, then reinstall. - Laptops: make sure Minecraft runs on the discrete GPU (see the driver section below). Integrated-GPU fallback is the most common reason a laptop runs Bedrock badly.
If Bedrock only lags on a server or Realm, while singleplayer is smooth, it’s connection or server lag. Lower settings won’t help: check your ping, use a wired connection, or try another server.
Lower render distance and cap FPS
High render distance forces constant chunk generation, the number-one source of movement stutter on both editions.
| Setting | Recommended value |
|---|---|
| Render Distance | 12–16 chunks |
| Simulation Distance | 8–10 chunks |
| Max Framerate | Cap just below refresh |
| VSync | Off |
| Graphics | Fast |
| Smooth Lighting | Off if still hitching |
Uncapped FPS lets the engine render ahead and spike between chunk loads. Cap it: 141 for 144 Hz, 237 for 240 Hz, 117 for 120 Hz.
Update your GPU driver and force the right GPU
- Install the latest stable GPU driver.
- If stutter started after a driver update, roll back to the previous version, or clean-install with DDU.
- On laptops, force Minecraft (Bedrock) or
javaw.exe(Java) onto the discrete GPU in Windows Graphics settings — integrated-GPU fallback is a common cause of Minecraft stutter on laptops.
Install Minecraft on an SSD
Chunk data streams from disk as you move. On a hard drive, that turns into traversal hitching. Move the game (and its world saves) to an NVMe or SATA SSD and keep 15–20% free space.
Windows fixes worth trying
- Enable Game Mode (Settings → Gaming → Game Mode → On).
- Disable unnecessary startup apps and overlays — see Disable Xbox Game Bar and Game DVR.
- Set the Windows power plan to High Performance — see Best Windows Power Plan for Gaming.
- Close browsers and capture tools while playing.
For smoother movement and steadier frame delivery, also read The Ultimate Guide to Timer Resolution for Gaming — lowering the Windows timer from 15.6ms to 0.5ms tightens the scheduler that paces your frames, which helps the micro-stutter that lingers after garbage-collection and chunk spikes are handled.
If shaders are causing the stutter
Shaders are VRAM- and GPU-heavy, so hitching with shaders on is usually a load problem:
- Lower the shader preset.
- Drop render distance to 12 chunks.
- Make sure your GPU has VRAM headroom (watch it with an FPS/VRAM overlay).
- If it only stutters with shaders, that’s expected load — not a general optimization bug.
Related guides
- Minecraft Lowest Input Lag Settings
- Minecraft Stretched Resolution Guide
- How to Fix Lag Spikes in Games
- The Ultimate Guide to Timer Resolution for Gaming
Most Minecraft stutter comes down to three things: right-sized RAM allocation, a performance mod like Sodium on Java, and a sensible render distance on an SSD. Fix those before blaming your hardware.
Frequently asked questions
Why does Minecraft stutter and lag spike on a good PC?
Minecraft stutter is rarely about raw GPU power. Java Edition runs on the JVM, so most lag spikes come from garbage collection, wrong RAM allocation, or high render distance forcing constant chunk loading. On a strong PC the fix is usually allocating a sensible amount of RAM (not too much), lowering render distance a step, and installing a performance mod like Sodium rather than upgrading hardware.
How much RAM should I allocate to Minecraft?
For vanilla or light modpacks, 4 GB is plenty; 6-8 GB covers most medium modpacks. Allocating too much RAM actually makes stutter worse because the Java garbage collector pauses longer when it finally runs. Leave enough for Windows and other apps, and only raise allocation if you see out-of-memory errors, not to chase smoother frames.
Does Sodium or OptiFine fix Minecraft stutter?
For Java Edition, Sodium is the single biggest smoothness upgrade — it rewrites the rendering engine and dramatically cuts frame-time spikes, especially with the Lithium and FerriteCore mods alongside it. OptiFine also helps and adds shader support, but Sodium generally produces steadier 1% lows. On Bedrock Edition you don't need either; focus on render distance and driver updates instead.
How do I stop Minecraft lag spikes when loading new chunks?
Chunk-loading hitches come from generating and streaming terrain as you move. Lower render distance to 12-16 chunks, install the game on an SSD, and cap your frame rate just below your refresh rate so the engine isn't rendering ahead. On Java, Sodium plus the Lithium mod smooths the chunk-generation spikes the most.
Why does Minecraft stutter with shaders installed?
Shaders are extremely GPU-heavy and often push VRAM to its limit, which turns into hitching rather than a clean FPS drop. Lower the shader preset, reduce render distance, and make sure your GPU has VRAM headroom. If stutter only appears with shaders, that's a GPU/VRAM load problem, not a general Minecraft optimization issue.
Why is Minecraft Bedrock so laggy on PC?
Minecraft Bedrock lag on Windows usually comes from render distance set too high, a heavy graphics mode such as Vibrant Visuals or ray tracing, a high simulation distance in the world settings, or an outdated GPU driver. Bedrock has no RAM slider and doesn't use Java mods, so lower render distance, switch to Fancy or Simple graphics, drop simulation distance to 4–6 chunks and update the driver. If the lag only happens on servers or Realms, it is connection latency, not FPS.
Is Minecraft lag caused by FPS or by my internet?
Check whether it happens in singleplayer. If singleplayer is smooth but a server or Realm rubber-bands, blocks reappear after you break them or mobs teleport, that is network or server lag, and graphics settings won't fix it. If singleplayer also stutters or the FPS counter drops, it is performance lag, which render distance, RAM allocation and drivers do fix.