Best Minecraft Settings for FPS (Java and Bedrock)
Published
On this page
The fastest way to boost FPS in Minecraft is to lower render distance to 8–12 chunks, set Graphics to Fast, and allocate a sensible 4–6 GB of RAM — Minecraft is limited by your CPU and chunk loading, not your GPU, so these three changes matter more than any graphics card. This guide gives you the best video settings for both Java and Bedrock Edition plus the Windows tweaks that keep frame times smooth.
Minecraft looks simple but hammers your CPU — the wins come from render distance and clean frame times, not raw graphics power.
Best Minecraft video settings
Set these in Options → Video Settings. Values apply to Java Edition; Bedrock equivalents are noted below the table.
| Setting | Recommended value |
|---|---|
| Graphics | Fast |
| Render Distance | 8–12 chunks |
| Simulation Distance | 6–8 chunks |
| Smooth Lighting | Off (or Minimum) |
| Max Framerate | Cap slightly below refresh (e.g. 141 for 144 Hz) |
| VSync | Off |
| Particles | Minimal |
| Clouds | Off |
| Entity Shadows | Off |
| Biome Blend | Off (or 3x3) |
| Mipmap Levels | 1–2 |
| GUI Scale | Personal preference (no FPS cost) |
The single biggest FPS setting is Render Distance. Every extra chunk multiplies the world your CPU has to load and light, so going from 32 to 12 chunks often doubles frame rate on a mid-range PC while still leaving plenty of view distance for survival or PvP.
Why Minecraft runs badly on strong PCs
Minecraft is CPU- and single-thread bound, not GPU-bound. When you see low FPS with a powerful graphics card, the GPU is sitting idle while the CPU struggles to generate and mesh chunks. That is why lowering render distance, simulation distance, and particle counts — all CPU work — does far more than dropping texture quality.
This is also why Minecraft benefits so much from Windows-side latency and scheduling tuning. The same tools that help competitive shooters help here.
Render distance and simulation distance
These two settings decide almost everything:
- Render Distance controls how far chunks are drawn. Lower it first. 8–12 chunks is the sweet spot; drop to 6 on a weak laptop.
- Simulation Distance controls how far entities, redstone, and mobs tick. Set it to 6–8 — it barely affects visuals but eases a heavy CPU load.
Keep them a few chunks apart (render slightly higher than simulation) so the world still looks full without the CPU ticking everything you can see.
Best FPS cap for smooth frame times
An uncapped frame rate makes frame times uneven and wastes power. Cap Max Framerate just below your monitor’s refresh rate:
141 FPSfor 144 Hz237 FPSfor 240 Hz117 FPSfor 120 Hz
A stable cap under your refresh rate keeps mouse feel consistent. For the full explanation of why a cap lowers input lag, see How to Cap Your FPS Correctly and Best FPS Cap for Low Latency.
Java Edition: Sodium beats OptiFine for raw FPS
If you play Java Edition, the biggest single upgrade is a performance mod:
- Sodium (with Lithium and Starlight) rewrites the rendering and lighting engine and typically delivers 2–4x the FPS of vanilla with much smoother frame times.
- OptiFine is simpler and adds shader support and extra toggles, but its raw FPS gains are smaller than Sodium’s.
Both are free. For pure competitive FPS, choose Sodium; for shaders and convenience, OptiFine. Neither is a cheat — they are client-side rendering optimizations.
How much RAM to allocate
More RAM is not better. Allocate:
- 4–6 GB for vanilla or light modpacks
- 8 GB+ only for heavy modpacks with hundreds of mods
Over-allocating makes the Java garbage collector run longer, less frequent pauses that show up as periodic stutter. Set it in your launcher’s JVM arguments with -Xmx6G -Xms6G.
Bedrock Edition notes
Bedrock is written in C++ and already runs faster than vanilla Java, so the same principles apply with fewer knobs:
- Lower Render Distance first.
- Turn VSync off and enable a high frame rate cap in options.
- Disable Fancy Graphics, Fancy Leaves, and beautiful skies for extra frames on weak hardware.
Windows-side checks worth doing
These help every game but matter more in Minecraft because it is so CPU-sensitive:
- Set Windows to a high-performance power mode (or Ultimate Performance on desktops).
- Close browsers, overlays, and capture tools — Java shares CPU with everything.
- Update Java to a current build and make sure the launcher uses your discrete GPU on laptops.
- Consider disabling VBS for extra CPU headroom.
- Install Minecraft and its worlds on an SSD to cut chunk-load hitching.
For deeper system tuning, use How to Minimize Input Delay for Competitive Gaming and The Ultimate Guide to Timer Resolution for Gaming + Tier1Suite.
Build your Minecraft cluster
Related guides
- How to Cap Your FPS Correctly
- How to Minimize Input Delay for Competitive Gaming
- How to Optimize Your Monitor for Gaming
The best Minecraft settings come down to a short render distance, Fast graphics, a sensible FPS cap, and 4–6 GB of RAM. On Java, add Sodium for the biggest jump. None of it needs a new GPU — Minecraft rewards CPU headroom and clean frame times over raw graphics power.
Frequently asked questions
What is the best render distance for FPS in Minecraft?
Set render distance to 8–12 chunks for the best balance of FPS and visibility. Render distance is the single most expensive setting in Minecraft because it controls how much of the world is loaded and lit each frame; dropping from 32 to 12 chunks can double your frame rate on a mid-range PC.
Does Minecraft need a good PC to run well?
No. Minecraft is CPU- and RAM-bound rather than GPU-heavy, so most stutter and low FPS come from render distance, background apps, and too little (or too much) allocated RAM — not a weak graphics card. Vanilla Minecraft runs at high FPS on modest hardware once render distance and graphics are tuned.
Should I use OptiFine or Sodium for more FPS?
On Java Edition, Sodium (with Lithium) gives the largest FPS gains and the smoothest frame times, often 2–4x vanilla. OptiFine is easier and adds shaders and dynamic options but has smaller raw FPS gains. Bedrock Edition has no equivalent mod but already runs faster than vanilla Java.
How much RAM should I allocate to Minecraft?
Allocate 4–6 GB for vanilla or light modpacks. More is not better — over-allocating RAM makes the Java garbage collector pause longer, which causes periodic stutter. Only heavy modpacks with hundreds of mods need 8 GB or more.
Why is my FPS low in Minecraft with a good GPU?
Minecraft leans on the CPU and single-thread performance, so a strong GPU sits idle while the CPU builds chunks. Lower render and simulation distance, cap background apps, allocate a sensible 4–6 GB of RAM, and on Java switch to Sodium — that removes the CPU bottleneck a faster GPU alone cannot.