The Best Minecraft Performance Mods

It is reasonable to wonder why a game that looks like this needs help running. The answer is architectural rather than visual.

Minecraft's renderer submits an enormous number of small draw calls rather than batching them, which means the CPU spends most of its time telling the graphics card what to do instead of the card doing it. That is why upgrading a graphics card so often produces disappointingly little improvement, and why the game is limited by single-thread CPU speed on most machines.

The game logic has similar issues. Entity ticking, lighting updates and chunk loading all do more work than they need to, often recalculating things that have not changed.

Performance mods attack both. Rendering rewrites batch the draw calls properly; logic optimisations skip work that has no effect. Neither changes what the game looks like.

Sodium replaces Minecraft's rendering engine outright. It is the single largest improvement available and it is the one to install before considering anything else.

On typical mid-range hardware the frame rate roughly doubles. On older machines the difference can be larger still, because the CPU bottleneck Sodium removes is exactly what limits those systems.

It also fixes a category of visual glitch — flickering blocks, seams between chunks — that most players had assumed was just how Minecraft looks.

It is Fabric-first, with NeoForge support now available. It changes no gameplay, adds no items, and can be removed at any time with no consequences.

Where Sodium fixes rendering, Lithium optimises the game logic — mob AI, chunk ticking, redstone, physics.

It produces no visual change whatsoever, which makes it feel less impressive and means people sometimes skip it. That is a mistake, because it targets exactly the work that causes the stutter and tick lag on busy worlds, especially ones with large farms.

Lithium's design goal is strict behavioural parity: it does not change what the game does, only how efficiently it does it. Redstone contraptions behave identically, mob spawning is unchanged, and farms produce the same rates.

It requires no configuration. Install it and there is nothing to set.

If you want shader packs, Iris is what provides them now. It works alongside Sodium rather than fighting it, which is the crucial difference from the old arrangement.

Historically, wanting shaders meant OptiFine, and OptiFine conflicted with a great deal. Iris supports most popular shader packs — Complementary, BSL, Sildur's — while leaving Sodium's rendering improvements in place.

The practical consequence is that you can run shaders and still have better frame rates than vanilla without them, which was not true before.

Shaders remain expensive. Expect to give up a meaningful share of the gains Sodium provided, and budget an extra gigabyte or two of memory.

Beyond the main three, a handful of smaller mods each remove a specific inefficiency. None is transformative alone; together they are worth a further noticeable improvement.

Entity Culling stops the game rendering mobs and block entities that are hidden behind walls. In a base full of chests and machines this is substantial.

FerriteCore reduces memory usage, often by several hundred megabytes on a large pack, which matters more than it sounds when you are near your allocation ceiling.

ImmediatelyFast optimises the remaining immediate-mode rendering that Sodium does not cover, mostly UI and text.

ModernFix improves startup time and patches a number of memory issues, which on a three-hundred-mod pack can cut minutes from loading.

Figures vary enormously with hardware and settings, so treat these as directional rather than promises.

A machine managing 60 frames per second in vanilla at 12 chunks render distance will typically reach 120 to 150 with Sodium and Lithium. An older laptop struggling at 25 might reach 50 to 60, which is the difference between unplayable and fine.

On a heavy modpack the gains are proportionally larger, because there is more inefficiency to remove. Packs that stutter constantly in vanilla-rendering mode often become smooth.

What performance mods cannot do is overcome insufficient memory. If you are crashing or stuttering because of a low allocation, no rendering mod will fix it — that is a different problem with a different solution.

OptiFine was the answer for a decade and it is no longer the recommendation, which surprises people returning after a break.

Its problem is that it patches the game in ways that conflict with modern mods, it is closed-source, and it updates slowly after new Minecraft releases. It also does not appear on Modrinth at all.

What it still has is convenience: one download provided rendering optimisation, shaders, connected textures, dynamic lighting, zoom and capes. Replacing all of that takes five or six separate mods.

If you use two of those six features, the modern stack is faster and more compatible. If you genuinely use all of them and run few other mods, OptiFine remains defensible — it is simply no longer the default answer.

For anyone migrating, the mapping is straightforward once you know it.

Rendering performance goes to Sodium. Shader support goes to Iris. The zoom key, which is the feature people miss most, comes from Zoomify or Ok Zoomer. Connected textures come from Continuity. Dynamic lighting from held torches comes from LambDynamicLights.

Install Sodium and Iris first and add the rest only if you actually notice something missing. Most people find they used two of the six and never install the others.

Two in-game settings outweigh every mod on this page, and adjusting them is free.

Render distance is the dominant cost and it scales roughly with the square of the value. Going from 16 chunks to 10 is a very large saving and most people stop noticing within minutes of play.

Simulation distance controls how far away entities keep ticking. Lowering it to 6 costs nothing visually and saves considerable CPU on worlds with farms.

Turning down fancy graphics options helps less than expected, because those are mostly GPU costs and the game is usually CPU-bound. Render distance is where the money is.

A common confusion: installing Sodium does nothing for a server, because Sodium is a rendering mod and servers do not render.

If your multiplayer experience is laggy rather than low-framerate, the constraint is the server, and the fixes are different. Lithium has a server build. Starlight rewrites the lighting engine. Reducing view distance and simulation distance in server.properties is free and effective.

Telling the two apart is easy once you know to look. Low frame rate with smooth movement is a client problem. Smooth frame rate with rubber-banding and delayed block breaking is a server problem.

Install Fabric for your Minecraft version. Add Fabric API, Sodium, Lithium and Mod Menu. Launch and check the frame rate on the F3 screen against what you had before. Add Iris if you want shaders, and Entity Culling and FerriteCore if you run a large pack.

Then set render distance to 10 and simulation distance to 6, and see whether you still want more. Most people stop here, because at this point the game runs better than it ever has.