Sodium Plus

Sodium Plus on Your Minecraft Server

With over 2 million downloads, Sodium Plus has carved out a niche as a leaner alternative to bigger optimization bundles: a client-side modpack built around Sodium with a handful of extra tweaks squeezed in for even better framerates. Like every pure performance pack, Sodium Plus runs entirely on the player's machine and doesn't touch the server itself. Your rented game-serverhosting server needs no special configuration for it — the pack works just as well on Vanilla servers as on Fabric or Quilt servers, as long as the player's client matches.

Tip: Since Sodium Plus is available for both Fabric and Quilt, just pick whichever loader you're already using on the client side — no server-side changes required, whatever Minecraft version up to 26.2 you're playing.

Plan the rollout and operation

Sodium Plus suits players who want a small performance profile rather than a broad modpack. State the tested Minecraft and loader version while leaving graphics settings personal because hardware and preferred view distance vary widely. Check joining from a clean profile and alongside the server resource pack. Do not fill the server with client mods from the pack; keeping them local makes any problem much easier to isolate.

For rollout, publish a tested combination of pack, Minecraft, and loader versions and state clearly that the package is installed locally. A fresh profile should join an unchanged server first; check login, the resource pack, chat, world travel, and typical client features. Players should install the pack in its own instance rather than over an existing profile so stale mods and configuration do not create false conflicts. Keep the previous instance during updates until joining and rendering are confirmed on the new release. Because the server stores no pack content, no world rollback is required. Keep client files out of the server package and treat any additional server-side mods as a separate change with their own test. For support, link the exact profile release and request the client log plus a screenshot of the active instance; this separates loader, pack, and server failures cleanly.