Best Performance Mods for Minecraft
The best performance mods for Minecraft are Sodium, Lithium, FerriteCore, ImmediatelyFast, and Entity Culling. Together they raise frame rates, cut stutter, and lower memory use without changing how the game plays. This guide explains what each mod does, which loader it needs, and how to install them safely.
Minecraft Java Edition is a heavy game for what it looks like. A world made of simple blocks still asks a lot of your computer. It draws thousands of blocks every frame, runs the logic of every mob and farm, and holds a huge world in memory. When any one of those jobs gets slow, you feel it as low frame rates, freezing, or long loading screens. Performance mods split that work into separate jobs and fix each one on its own. That is why a small set of mods, each doing one thing well, beats one giant mod that tries to do everything.
What performance mods actually change
A performance mod does not change the game itself. Your recipes, mobs, blocks, and combat stay exactly the same. What changes is how hard your computer works to run them. There are four places where the game usually struggles.
First is rendering, which means drawing the world on your screen. Every frame, the game turns blocks, entities, and particles into a picture. A slow renderer means low frame rates. Second is game logic, which means everything the game thinks about: mobs moving, crops growing, redstone ticking. Slow logic means the world stutters even when the picture looks fine. Third is memory, which is how much RAM the game holds. Too much memory use means long pauses while the game cleans up. Fourth is entity drawing, which covers mobs, chests, item frames, and text on signs. The game often draws things you cannot even see, which wastes effort.
The five mods in this guide each fix one of these places. Used together, they cover all four.
Sodium: the frame rate mod
Sodium is the first mod most players should install. It replaces the way Minecraft draws the world with a faster, modern renderer. Chunks load faster, the frame rate goes up, and stutter while exploring drops sharply. It is also the mod behind most of the big frame rate gains people report, because rendering is usually the largest bottleneck.
Sodium works on Fabric and on NeoForge, so it fits both of the popular modern loaders. On Fabric, it also needs Fabric API, which is a small library mod that many Fabric mods share. One important detail: Sodium changes the renderer, so it does not work with OptiFine shaders on its own. If you want shaders with Sodium, you pair it with Iris, a separate shader mod built to work with it.
When you pick a Sodium file, match it to your exact Minecraft version and loader. A file built for one game version can crash on another, even when the names look close. Check the file page for your version before you download anything.
Lithium: the game logic mod
Lithium fixes the second bottleneck: game logic. It makes the game’s thinking faster without changing what the game does. Mobs still behave the same way, farms still work the same way, and redstone still follows the same rules. The difference is that the game spends less time on each tick, which is the small step the game repeats twenty times per second. That shows up as a smoother world, especially on servers and in busy bases with many mobs and machines.
Lithium works on Fabric and NeoForge. It is safe to use on servers too, because it does not change vanilla behavior, only how fast that behavior is calculated. Like Sodium, you must pick the file that matches your Minecraft version and loader. If you run a server, Lithium is one of the easiest wins available, since slow ticks hurt every player at once.
FerriteCore: the memory mod
FerriteCore fixes the third bottleneck: memory. Minecraft holds a lot of data in RAM, and some of that data is stored in wasteful ways. FerriteCore packs it tighter, so the game uses less memory for the same world. Less memory pressure means fewer long pauses and a game that stays smooth for longer sessions.
FerriteCore works on NeoForge and on Fabric through its ports, so check the file page for the loader you use. It pairs naturally with Sodium and Lithium: Sodium speeds up drawing, Lithium speeds up thinking, and FerriteCore keeps memory use under control. If your game starts fine but gets choppy after an hour of play, memory is often the cause, and FerriteCore is the mod that helps most.
ImmediatelyFast: the interface and entity drawing mod
ImmediatelyFast targets a smaller but real slice of rendering: immediate-mode drawing. That covers entities, block entities like chests, particles, maps, and text on screen. These are the things the game draws one by one, and the vanilla way of doing it is slow. ImmediatelyFast speeds that path up, which helps most in busy scenes: a village full of villagers, a storage room full of chests, or a fight with many particles in the air.
ImmediatelyFast works on Fabric, Quilt, and NeoForge, and it is built to stack with Sodium rather than replace it. It is small and client-side, which means it only affects your own game, not a server. If your frame rate drops mainly around mobs and chests rather than open terrain, ImmediatelyFast is the mod that addresses that exact problem.
Entity Culling: the mod that skips what you cannot see
Entity Culling fixes a simple waste. Vanilla Minecraft draws every entity and block entity inside your view, even when a wall stands between you and that chest or cow. You cannot see it, but your computer still draws it. Entity Culling runs a cheap visibility check on spare CPU threads and skips the draw calls for things that are hidden. The result is higher frame rates in bases, villages, and caves, where many hidden entities sit behind walls.
Entity Culling is client-only. The server keeps simulating those mobs exactly as before, so nothing about gameplay changes. It only stops your computer from drawing what is out of sight. If you play with large builds or busy farms, this mod often gives a bigger gain than people expect, because hidden entities are everywhere in a developed world.
How to choose by loader and version
The single most important rule is to match every file to your exact setup. Pick one loader, either Fabric or NeoForge, and never mix the two in one mods folder. Then, for each mod, pick the file that lists your exact Minecraft version. A file for a nearby version is not close enough and can crash the game on launch.
A safe starter set is Sodium first, then Lithium, then FerriteCore, then ImmediatelyFast, then Entity Culling. Add them one at a time and launch the game after each one. That way, if the game crashes, you know exactly which file caused it. If you use Fabric, remember Fabric API, since several of these mods need it. Give the game enough RAM too, but more RAM is not always better. Four to eight gigabytes is plenty for this set, and giving it far more can actually make pauses worse.
If you are unsure which loader to use, Fabric is the simpler choice for a small performance set, while NeoForge is the better choice if you already run NeoForge mods. Our Java Edition guide covers loaders in more detail, and our NeoForge crash page covers what to do when a NeoForge setup fails to start.
How to install them safely
Installing performance mods is simple, and the safe way takes only a few extra minutes. First, install your chosen loader for your Minecraft version using a launcher that handles loaders cleanly, such as Prism, the Modrinth App, or the official launcher with a custom installation. Second, add Fabric API if you chose Fabric. Third, drop the mod files into the mods folder, one at a time, launching after each one.
Get every file from the official CurseForge project page for that mod, found by searching the mod name on CurseForge. Never download mod files from random reupload sites, since those copies can hide malware. This site does not host mod files, and you should be careful of any site that offers them outside the official pages. If the game crashes after adding a mod, remove the last file you added and check that its version matches your game and loader. Most crashes come from a version mismatch, not from a broken mod.
Conclusion
The best performance mods for Minecraft are a small team, not a single fix. Sodium speeds up rendering, Lithium speeds up game logic, FerriteCore cuts memory use, ImmediatelyFast speeds up entity drawing, and Entity Culling skips what you cannot see. Installed one at a time, matched to your exact version and loader, and downloaded from the official CurseForge pages, they give most players a clearly smoother game without changing how Minecraft plays.
FAQs
Do performance mods work on servers?
Yes, for the most part. Lithium helps servers directly, since it speeds up game logic for everyone. Sodium, ImmediatelyFast, and Entity Culling are client-side, so they help your own game no matter which server you join. FerriteCore helps wherever it is installed. A server owner does not need to install your client mods, and you do not need the server to install anything for your client mods to work.
Do performance mods work with shaders?
Sodium does not work with OptiFine shaders on its own, because it replaces the renderer that OptiFine expects. If you want shaders with Sodium, use Iris, which is built to pair with it. The other mods in this guide do not affect shaders directly, so they work fine alongside a shader setup.
Should I use Fabric or NeoForge for performance mods?
Both work. Fabric is simpler for a small performance-only set, and most of these mods publish Fabric files first. NeoForge is the better pick if you already play with NeoForge mods or want to stay on that loader. What matters most is that every file matches the loader you chose. Never mix Fabric and NeoForge files in one folder.
Can performance mods get me banned?
No, not on normal servers. These mods do not change gameplay, give unfair advantages, or touch the game’s rules. They only make the game run faster. Some competitive servers have their own allowed-mod lists, so check the rules of a server you play on, but performance mods are allowed nearly everywhere.
Why did my game crash after adding a mod?
Almost always, the file does not match your Minecraft version or your loader. Remove the last mod you added, then check its file page for the exact version and loader it supports. Also check that Fabric API is installed if you use Fabric. If the game still crashes, our troubleshooting guide covers the common causes step by step.
