Sodium 0.6 vs Embeddium on Minecraft 1.21.4: which renderer to choose

The honest answer to "Sodium or Embeddium" in mid-2026 is: whichever one matches your mod loader. They are no longer interchangeable choices the way they were in 1.20. Two years of upstream divergence, one licensing fight, and a slow Forge port have created a real performance and feature gap, and most players never get to make this decision, because their modpack already picked.

This is the long version of that answer, version-pinned to Minecraft 1.21.4.

TL;DR

The fork tree

The lineage matters because it explains the feature gap.

Sodium (CaffeineMC, Fabric)
  └─ Rubidium (Asek3, Forge port) [abandoned 2023]
        └─ Embeddium (FiniteReality, NeoForge) ← based on Sodium 0.5.8

Embeddium picked up the torch when Rubidium stalled, but it forked off the 0.5.x branch, the last release under LGPL-3 before CaffeineMC started tightening control. That choice is why we're here.

The license fight

In November 2024, CaffeineMC opened issue #2400 on the Sodium repository proposing a license change from LGPL-3.0 to Polyform Shield. The stated rationale was direct: prevent third-party forks from "continuing to cut us out of our own project." In practice, that means stopping unauthorized Forge ports, with Embeddium being the most prominent target.

The proposal is still under discussion at time of writing, and Embeddium maintains its position as the last LGPL inheritor of the Sodium rendering pipeline. CaffeineMC has been explicit that Embeddium is unsupported and that users should not file Sodium-tracker issues for it.

This drama matters to readers for two reasons:

1. Sodium 0.6+ improvements are not flowing into Embeddium at the same pace they used to. The contract between projects is broken.
2. If your modpack ships Embeddium today, you're locked into a slower release cadence than Sodium proper.

Architecture differences in 2026

Both mods replace Minecraft's chunk meshing pipeline with modern OpenGL multi-draw rendering, which cuts the per-frame CPU cost of drawing chunks and shrinks the vertex data pushed to the GPU through compressed formats. CaffeineMC does not publish figures for either, and the numbers circulating for them online do not trace back to the team, so treat the mechanism as the claim here, not a percentage.

The relevant divergence on 1.21.4 specifically:

• Sodium 0.6.x rewrote vertex formats, integrated the Fabric Rendering API (FRAPI) directly, and retired the need for Indium as a compatibility shim.
• Embeddium 1.0.12-beta.1 is built on Sodium 0.5.8's pipeline. It includes FRAPI as well, but it does not have 0.6's vertex format work yet.

In practice, that's the difference between "current generation" and "one generation behind." Embeddium maintainers themselves acknowledge that it "may not perform quite as well as the native Fabric version of Sodium."

Performance numbers

A caveat first: CaffeineMC has not published head-to-head benchmarks, and Embeddium 1.0.12 on 1.21.4 is still flagged beta. So this section describes the shape of the difference, not a number.

We are not going to print a table of FPS numbers per graphics card. The figures circulating for this comparison come from content aggregators rather than a controlled test, and a frame rate measured on somebody else's machine in somebody else's world does not predict yours. Sodium's own page says the same thing: performance "will vary depending on exact hardware and software configuration."

What holds across reports is the shape of the result:

• Sodium's gain over vanilla is large rather than marginal, and it grows with render distance.
• The gain is biggest on CPU-bound and low-end machines, because the chunk renderer is the bottleneck it removes.
• Embeddium tracks Sodium 0.5.x, so on the same hardware it lands close to it, and somewhat behind Sodium 0.6.x in chunk-heavy and FRAPI-heavy scenes.

If you need first-party numbers for a specific decision, you'll have to bench your own pack on your own hardware. There is no substitute.

Compatibility matrix

The most common mistake we see in support threads: installing Indium with Sodium 0.6+. Don't. It's no longer needed and will cause a crash.

Modpack reality check

For most players this decision was already made for them by the modpack author.

• All The Mods 10 (NeoForge, ~400-500 mods) ships Embeddium + Oculus. Source: official ATM shader guide.
• Prominence II RPG (NeoForge, quest-driven) ships the same Embeddium + Oculus stack.
• Fabulously Optimized, Simply Optimized, Sodium Plus (Fabric, performance-focused) all ship Sodium.

If you're playing one of these, your renderer is fixed. If you're building a pack from scratch, your loader choice (Fabric vs NeoForge) is what really determines this, not your renderer preference. Our 2026 modpack roundup notes which renderer each major pack ships.

What about the server?

This part trips people up constantly: neither Sodium nor Embeddium helps a dedicated server's TPS. Both are client-only render-pipeline replacements. They don't run on the server JVM at all.

If you're optimizing a server, you want:

• Lithium (Fabric): game logic optimizations
• Krypton (Fabric): network stack improvements
• Their NeoForge equivalents where available

The full server-side stack is covered in the Fabric performance mods guide, and if your server problem is memory rather than rendering, start with how much RAM a server actually needs.

A renderer mod will help every player's FPS at the same time, which is real value, but it won't keep your TPS from collapsing under 80 players. Different problem.

When to choose which

A flowchart, since the decision tree is short:

What's next

A wildcard has entered the picture: Minecraft 26.2 ships an experimental first-party Vulkan renderer. Sodium and its forks were built against OpenGL internals, so how that ecosystem adapts to a second vanilla backend is an open question; for now the OpenGL path (and everything below) remains the performance-modding reality.

Sodium has since moved well past this comparison: 0.9.2 ships for 26.2 and 26.3, and NeoForge builds come straight from CaffeineMC rather than a fork. Embeddium never absorbed 0.6's vertex format work, and its last release of any kind was January 2025. The political situation around issue #2400 will likely determine whether Embeddium continues at all in the medium term. If Sodium relicenses to Polyform Shield, future merges become a legal question, not a technical one.

For 1.21.4 specifically, the picture is stable: Sodium 0.6.7 is the high-water mark on Fabric, Embeddium 1.0.12-beta.1 is the only serious option on NeoForge, and the gap between them is real but not catastrophic.

Most users won't notice the gap. The ones who will are running 200-mod packs at 1440p with shaders, and they're stuck with whatever their loader allows. That's the actual answer.

If shaders are why you're here, the low-end shader roundup covers what runs well on top of Sodium, and if you have landed on Complementary, the Reimagined vs Unbound comparison helps you pick the right variant. The full catalog of renderers, shaders, and performance mods lives in the mods directory.

Frequently asked questions

Which is faster, Sodium or Embeddium?

Sodium, on current hardware. Embeddium is forked from Sodium 0.5.8 and hasn't absorbed the 0.6.x vertex format rewrite, so it lands close to where Sodium 0.5.x was and somewhat behind Sodium 0.6.x in chunk-heavy and FRAPI-heavy scenes. Neither team publishes head-to-head benchmarks, so treat any specific percentage you see elsewhere as directional, not exact.

Can Sodium and Embeddium run together?

No, and you wouldn't want to. They're loader-specific rewrites of the same rendering pipeline: Sodium targets Fabric/Quilt, Embeddium targets NeoForge/Forge. Your mod loader decides which one you're even able to install; they're not a choice you make independently of it.

Is Embeddium a fork of Sodium?

Yes. Embeddium descends from Rubidium, an abandoned Forge port of Sodium, and was forked off Sodium's 0.5.8 branch, the last release under the LGPL-3 license before CaffeineMC proposed a stricter license for Sodium itself. That license split is why Embeddium's improvements no longer track Sodium's at the same pace.

Which one do I use on Forge or NeoForge?

Embeddium 1.0.12-beta.1, paired with Oculus (an Iris fork) if you want shaders. Vanilla Iris also works through the separate Monocle compatibility layer. There's no realistic alternative to Embeddium on NeoForge or Forge modpacks right now.

Does either of these help my server's TPS?

No. Both Sodium and Embeddium are client-only rendering replacements; they never run on the server JVM at all, so they do nothing for TPS. For server-side performance, you want logic mods like Lithium and network mods like Krypton instead, covered in the Fabric performance mods guide.

---

Sources & further reading:

• Sodium 0.6.7 release notes: https://modrinth.com/mod/sodium/version/mc1.21.4-0.6.7-fabric
• Embeddium 1.0.12-beta.1 release notes: https://modrinth.com/mod/embeddium/version/1.0.12-beta.1+mc1.21.4
• Sodium licensing discussion (issue #2400): https://github.com/CaffeineMC/sodium/issues/2400
• Iris and Oculus shader compatibility FAQ: https://blog.curseforge.com/iris-shaders-frequently-asked-questions/
• Current state of shaders in 1.21: https://jangro.com/2024/08/24/the-current-state-of-shaders-in-minecraft-1-21