Type “best minecraft performance mods” into any search bar and you’ll get the same four names on repeat: Sodium, Lithium, FerriteCore, Iris. Install them on Fabric and you’ll see the FPS jump the articles promise. Try to install Sodium on a Forge modpack and the game won’t even launch — Sodium was never built for Forge, and no amount of re-downloading fixes that.
The actual performance stack isn’t one list of mod names. It’s four jobs — rendering, game logic, memory, and load time — filled by a different mod depending on whether you’re running Fabric, NeoForge, Forge, or Quilt. Get the wrong mod for your loader and you either crash on launch or leave real FPS on the table. Here’s the correct stack for each, checked directly against every mod’s own current listing for Minecraft 26.2 (“Chaos Cubed”) rather than an older roundup.
Quick Start: The Four Jobs Your Stack Needs to Cover
Every Minecraft performance mod handles one of four jobs: rendering (what your GPU draws each frame), game logic (what the CPU recalculates every tick — mob AI, physics, block updates), memory (how much RAM the game hoards while running), or load time (how long you stare at the loading screen). A complete stack covers all four. Most “best mods” roundups just list seven names and call it done, without saying which loader each one actually runs on — which is exactly how players end up dragging a Fabric-only file into a Forge instance and wondering why the game won’t start.
Here’s the one-line version for every loader. The reasoning behind each pick follows below.
| Job | Fabric / Quilt | NeoForge | Forge |
|---|---|---|---|
| Rendering | Sodium | Sodium (native) or Embeddium | Embeddium |
| Game logic | Lithium | Lithium | Canary (unofficial, stale — see below) |
| Memory | FerriteCore | FerriteCore | FerriteCore |
| Load time | ModernFix | ModernFix | ModernFix |
Why “Just Install Sodium” Breaks on Half These Loaders
Sodium does not run on Forge, and it never will. We checked this directly on Sodium’s own versions page rather than trusting older roundups that still call it Fabric/Quilt-only — as of 26.2 the supported-loader list reads Fabric, Quilt, and native NeoForge builds [1]. Forge isn’t on it. Sodium replaces Minecraft’s chunk renderer at a level that plugs into Fabric’s rendering hooks; Forge’s older mixin and rendering architecture doesn’t expose the same entry points, so there’s no version of Sodium to install even if you wanted one.
That gap is exactly why Embeddium exists. When Sodium’s developers switched the project to the Polyform Shield license — a source-available license with a noncompete clause that isn’t recognized as free and open source — a separate team forked the last fully open-source build of the Sodium codebase and kept building it for the loaders Sodium’s own team didn’t prioritize [4][13]. Embeddium isn’t a Sodium reskin; it’s a parallel lineage, explicitly “not supported by CaffeineMC” (Sodium’s developers) [4], covering Forge 1.20.1 and older plus NeoForge 1.20.1 and newer.
Here’s the full cheat sheet: every rendering, logic, memory, and load-time pick across all four loaders, in one place.
The Fabric Stack: Sodium, Lithium, FerriteCore — and Now Vulkan
Fabric gets the reference build of every mod in this guide, which is why the developers themselves recommend it as “the most simple and lightweight experience” [1] for running Sodium. Sodium rewrites the chunk renderer with modern GPU buffer management and aggressive face culling — it “only optimizes the rendering code of Minecraft” [1], nothing else, which is why it needs Lithium alongside it. Lithium reworks the systems that run every tick regardless of what’s on screen: mob AI, physics, block ticking [2]. Add FerriteCore for memory — CaffeineMC’s own documented example showed a heavily modded 1.16.4 pack drop from roughly 3.1GB to 1.1-1.2GB of heap after garbage collection on the title screen alone, though actual savings depend entirely on the pack [3].
The freshest reason to run Fabric in 2026: Sodium 0.9.x shipped experimental Vulkan support alongside 26.2’s new “Prefer Vulkan (Experimental)” graphics-API toggle [1][9]. It’s early — OpenGL is still the safer default for most setups — but Fabric is where that backend lands first. Pair this stack with our Java Edition FPS settings guide, and if you’re deciding between Fabric and NeoForge for a fresh instance, our head-to-head performance test found Fabric ahead by 20-30% FPS even with equivalent mods on both.
The NeoForge Stack: Native Sodium or Embeddium — the Real 2026 Choice
Most “best mods” guides still treat NeoForge like Forge’s twin and route you straight to Embeddium. That’s outdated. Sodium now ships native NeoForge builds directly alongside its Fabric and Quilt versions [1] — on a current 26.2 instance, Sodium and Embeddium are both live options on the same loader, not a Fabric-mod-versus-Forge-mod split.
The actual decision comes down to what else is in your modpack. Pick native Sodium if you want the newest features first — the Vulkan backend and active CaffeineMC development, plus Iris shader support (Iris requires Sodium and only supports Fabric and NeoForge 1.21.1+, never Forge) [6]. Pick Embeddium if you’re running a heavier, older-leaning pack where broad mod compatibility matters more than being first in line for updates — it’s built from a stable, previous-generation Sodium codebase specifically to prioritize compatibility [4]. Either way, layer Lithium [2], FerriteCore [3], and ModernFix [5] on top — all three list NeoForge as a first-class supported platform, which makes NeoForge the only loader in this guide that gets full four-job coverage no matter which rendering mod you pick. Grab any of these from Modrinth or CurseForge — see our CurseForge vs Modrinth comparison if you’re unsure which source to use.
The Forge Stack: Embeddium and ModernFix Carry the Load — With One Honest Gap
Forge users get real rendering and memory gains: Embeddium for the chunk renderer [4] and FerriteCore for heap usage [3], plus ModernFix to cut launch time — packs can start “roughly twice as fast,” and heavy packs can run on 3GB of allocated memory or less [5]. That covers three of the four jobs solidly.
The honest gap is game logic. Lithium has no official Forge build — its own platform list names only Fabric, NeoForge, and Quilt [2]. The closest substitute, Canary, is an unofficial fork that ports Lithium’s mob-AI and tick optimizations to Forge, but it hasn’t been updated in roughly three years [12] — running it means putting unmaintained code against a current 26.2 build, a real stability risk rather than a free win. This is one concrete reason the modded community keeps pushing toward NeoForge as the default for new packs: it’s the loader where the full four-mod stack still gets active support. If you’re on Forge for compatibility reasons, our guide to making Forge load faster covers launch-time fixes beyond ModernFix alone, and our best Minecraft mods for 2026 roundup covers picks beyond pure performance.
The Quilt Stack: Just Run the Fabric Builds
Quilt doesn’t need its own version of anything in this guide. Quilt Loader runs the large majority of Fabric mods directly, and QuiltMC maintains a short published list of the rare exceptions that don’t work [7]. Sodium, Lithium, and FerriteCore all publish Quilt-tagged builds anyway [1][2], so install the Fabric picks above and they load normally.
We also checked whether Quilt’s December 2025 shutdown of Quilt Standard Libraries broke anything for players — it didn’t. That change retired a developer API for building cross-platform Fabric/Quilt mods; it doesn’t touch your ability to run existing Fabric-loader mods on Quilt today [7]. See our Quilt vs Fabric compatibility guide for what little else actually changes when you switch.
Worth Adding, Worth Skipping
Three more mods show up on almost every performance list. Only one of them earns a place in most 2026 stacks without a caveat attached.
| Mod | What it does | Loaders | Add it if | Skip it if |
|---|---|---|---|---|
| Entity Culling | Stops rendering mobs and block entities hidden behind walls, using async path-tracing on spare CPU threads [8] | Fabric, Forge, NeoForge, Quilt | You build large bases with lots of entities — farms, villages, storage rooms | You mostly play in open terrain with few entities on screen |
| Krypton | Optimizes the networking stack — Netty handlers, flush consolidation, packet serialization [11] | Fabric only | You run or connect to a busy multiplayer server | You play singleplayer exclusively |
| Starlight | Rewrites the lighting engine for faster chunk lighting [10] | Fabric only | You’re still on 1.19 or earlier | You’re on 26.x — Starlight’s own benchmarks call the 1.20+ gap against vanilla “close enough that this test is also useless” [10] |
Which Stack Fits How You Play
| Player type | Priority |
|---|---|
| New player | Install just Sodium (or Embeddium/native Sodium on NeoForge) first. One mod, the biggest visible FPS jump, nothing to configure. |
| Casual player | Add Lithium and FerriteCore once Sodium’s running — both work silently in the background with zero settings to touch. |
| Hardcore / optimiser | Full four-job stack plus Entity Culling and Krypton on Fabric; try Sodium’s Vulkan backend once the rest of your mods confirm 26.2 support. |
| Completionist / heavy modpack player | ModernFix is non-negotiable — it’s the difference between a fast launch and a multi-minute wait on packs with 200+ mods, and it’s what lets low-memory instances run at all. |
FAQ
Can I run Sodium and Embeddium at the same time?
No, and you shouldn’t try. Both mods replace the same chunk renderer, so loading both crashes on startup instead of stacking benefits. On NeoForge, where both are valid options, pick one based on the trade-off above — Sodium for cutting-edge features, Embeddium for compatibility — not both.
Is Embeddium actually as fast as Sodium?
For the rendering gains that matter day to day — chunk culling, buffer management — yes, since Embeddium is built from Sodium’s own codebase [4]. Where it lags is features added to Sodium after the fork, like the 26.2 Vulkan backend [1][9], which Embeddium doesn’t carry because it’s a separate, independently maintained project now.
Do I need OptiFine with any of this?
No, and installing it alongside Sodium or Embeddium will crash your game. OptiFine and Sodium both replace the same rendering pipeline, so they conflict at the code level instead of stacking. Want shaders instead? Use Iris (Fabric/NeoForge, requires Sodium) or Oculus (the Forge-side shader loader built for the Embeddium lineage) [6].
Why does my Forge pack still feel slower than a Fabric friend’s, even with Embeddium and ModernFix installed?
Because you’re missing the fourth job. Embeddium fixes rendering and ModernFix fixes load time and memory, but neither touches the mob-AI and tick logic that Lithium handles on every other loader — and Forge has no actively maintained equivalent [2][12]. That gap alone accounts for a meaningful share of the difference; it isn’t something a settings tweak closes.
Key Takeaway
Pick your loader first, then fill all four jobs — don’t copy a Fabric mod list onto a NeoForge or Forge instance and hope it launches. Fabric and NeoForge both get the complete stack with zero compromises, and NeoForge additionally gives you the choice between cutting-edge Sodium and compatibility-first Embeddium. Forge gets real rendering, memory, and load-time gains from Embeddium and ModernFix, but its game-logic gap is real — and worth factoring into whether a new modpack belongs on Forge at all in 2026.
Sources
- CaffeineMC. “Sodium.” modrinth.com/mod/sodium
- CaffeineMC. “Lithium.” modrinth.com/mod/lithium
- “FerriteCore.” curseforge.com/minecraft/mc-mods/ferritecore
- “Embeddium.” curseforge.com/minecraft/mc-mods/embeddium
- “ModernFix.” curseforge.com/minecraft/mc-mods/modernfix
- Iris Shaders. modrinth.com/mod/iris
- QuiltMC. “FAQ.” quiltmc.org/en/about/faq
- “Entity Culling.” modrinth.com/mod/entityculling
- Minecraft Wiki. “Java Edition 26.2.” minecraft.wiki/w/Java_Edition_26.2
- “Starlight.” modrinth.com/mod/starlight
- “Krypton.” modrinth.com/mod/krypton
- “Canary.” modrinth.com/mod/canary
- CaffeineMC. “sodium” (GitHub, license file). github.com/CaffeineMC/sodium
Verified against each mod’s own current listing for Minecraft 26.2 (“Chaos Cubed”) as of August 2026. Loader support and version compatibility change with new Minecraft drops — check each mod’s page before installing.
I've been playing video games for over 20 years, spanning everything from early PC titles to modern open-world games. I started Switchblade Gaming to publish the kind of accurate, well-researched guides I always wanted to find — built on primary sources, tested in-game, and kept up to date after patches. I currently focus on Minecraft and Pokémon GO.