A client-side mod by RaphiMC for the rendering work Sodium leaves alone: entities, block entities, particles, text, maps and the HUD, which Minecraft rebuilds every frame. It batches that drawing into fewer GPU calls, adds targeted fixes, and needs no other mods.
ImmediatelyFast, a performance mod by RaphiMC, goes after one specific part of Minecraft's renderer: everything drawn fresh each frame rather than built once and reused. Mobs, chests and signs, particles, text, maps and the HUD all go through that path, and it is the path Sodium largely leaves alone. It is most useful to people who play on busy servers, build map walls or run a crowded HUD, and it drops into almost any Fabric, Quilt or NeoForge setup without a single extra library.
Terrain is built into large meshes when a chunk loads or changes, then reused frame after frame. That is where Sodium does most of its work.
Almost everything else is drawn in what graphics programmers call immediate mode: assembled on the spot, every frame, and handed to the graphics card in many small pieces. One entity, one line of chat or one map in an item frame costs very little. Hundreds of them mean hundreds of small submissions per frame, and in a busy scene the processor spends its time preparing those rather than the graphics card spending its time drawing.
ImmediatelyFast swaps the buffers that work passes through for its own implementation, which gathers compatible pieces into fewer, larger batches and uploads them to the GPU more efficiently. The project applies this to entities, block entities, particles, text, the GUI and HUD, and the immediate-mode drawing of other mods, which is why modded overlays can benefit too.
On top of the general batching, the mod rewrites a handful of specific routines. In current versions each has its own key in the config file, and all of these are on by default (older version lines use a somewhat different set of keys):
One further change, sign text buffering, keeps sign text instead of redrawing it every frame. It sits in the experimental section, is off by default, and the project warns it may cause issues with high-resolution or custom fonts.
The developer is unusually direct about this: ImmediatelyFast can only raise frame rates when the CPU is the bottleneck, and slower CPUs gain more than fast ones. If your graphics card is the limit, reorganising CPU work changes little.
The scenes that benefit are the ones full of immediate-mode drawing: a server hub packed with players, holograms and signs; a wall of map art; a mob farm in view; a HUD stacked with a scoreboard, boss bars and status effects. It is not a chunk-loading, world-generation, server tick or memory optimisation, and it will not make a lagging server answer any faster.
The project page does publish benchmark tables with large multipliers, and they are the figures most other sites repeat. Read the small print first: they were measured with an early release of the mod on a Minecraft version several years old, on one test PC, in scenes built to stress a single system, such as a pen of a thousand cows or hundreds of maps on screen. They show where the mod concentrates its effort. They are not a forecast for a current version on your hardware, and the entity test itself shows the gain shrinking sharply once Iris shaders were added.
Much of ImmediatelyFast's compatibility comes from knowing when to step aside, and current versions do so without being asked:
The Iris and Intel decisions are written to the game log as warnings, which is worth reading before you start changing options by hand.
There is no settings screen. Options live in config/immediatelyfast.json, created on first launch, and the project's advice is to leave most of them at their defaults. The file is split into regular, experimental and debug sections. The debug keys switch off the mod and hardware conflict handling described above and are labelled "do not touch", which is good advice.
When another mod looks wrong with ImmediatelyFast present, the useful move is to disable one optimisation at a time, starting with the one nearest the symptom: garbled text points to text lookup or the font atlas, broken maps to the map atlas, and anything else to the general enhanced_batching key (on older version lines the nearest equivalent for HUD problems is hud_batching). Knowing which key fixed it makes a bug report to the developer far more useful than "it breaks".
The project lists two known incompatibilities: OptiFine, including OptiFabric, and most closed-source clients, naming Lunar Client and LabyMod. Iris and Sodium are its usual companions, and recent releases include fixes aimed at Iris specifically.
Unlike most Fabric mods, ImmediatelyFast declares no dependencies: no Fabric API, no config library, nothing but its own file.
Open the ImmediatelyFast Downloads section on this page and filter it by your Minecraft version and loader. Fabric files are also tagged for Quilt, NeoForge has files of its own, and Forge files exist for older Minecraft releases only. Click Download on the matching row and Bravith sends you on to that exact file on Modrinth, where the download itself happens.
Version names spell out both numbers: 1.17.1+26.3-fabric is mod version 1.17.1 for Minecraft 26.3 on Fabric. Different Minecraft versions sit on different mod version lines, so the highest mod number is not automatically the one for you.
mods folder.ImmediatelyFast is listed as incompatible with OptiFine and OptiFabric. If either is in the same instance, take it out before judging whether the mod works.
There is no menu entry to look for. Open logs/latest.log and search for Initializing ImmediatelyFast: that line names the mod version, your GPU and the rendering backend. Warnings just after it list any optimisation switched off for your hardware or mods. A config/immediatelyfast.json file also appears after the first launch.
Modrinth lists ImmediatelyFast as client-only. It changes how your own game draws, and a dedicated server draws nothing, so leave it out of server mod folders. It does not need to match anything the server runs.
config/immediatelyfast.json to false, restart and test. Repeat until the problem goes, and leave the debug keys alone.New to loaders? The mod installation guide starts from zero. A crash on launch rather than a rendering glitch is a different problem, and fixing mods that are not working walks through reading it.
No builds match these filters.
It speeds up Minecraft's immediate mode rendering, the drawing done fresh every frame for entities, block entities, particles, text, maps and the HUD. It batches that work into fewer, larger submissions to the GPU and adds targeted changes for maps, fonts and text.
Yes, and the two complement each other. Sodium mainly changes how terrain is rendered, while ImmediatelyFast targets the immediate-mode drawing Sodium largely leaves alone. Both are common on Fabric and NeoForge performance setups.
No. The project README lists OptiFine and OptiFabric as known incompatibilities, so the two should not be installed in the same game.
Yes. When Iris is present the mod forces its experimental sign text buffering off, and recent releases include fixes for Iris specifically. Expect a smaller gain with shaders on: the developer's own entity benchmark improved far less once Iris was added.
There is no reliable single number. It only helps when the CPU is the bottleneck, slower CPUs benefit more, and the gain concentrates in scenes full of entities, text, maps or HUD elements. The multipliers quoted online come from the developer's own benchmark tables, measured with ImmediatelyFast 1.1.x on Minecraft 1.19.3 in stress-test scenes, so they do not describe current versions.
No. Current files declare no dependencies on any loader, so the single JAR is all you install.
No. It is a client-side mod marked unsupported on servers. It changes how your own game draws and does nothing for a dedicated server.
Edit config/immediatelyfast.json, which is created on first launch, set the relevant key to false and restart. There is no in-game settings screen. Leave the debug-only keys alone, since they disable the mod's own conflict handling.
No. The project lists most closed-source clients, naming Lunar Client and LabyMod, as known incompatibilities. It is meant for standard Fabric, Quilt, NeoForge or Forge installs.
For older Minecraft releases, yes. The newest Forge file is for Minecraft 1.21.4. Current releases are Fabric, Quilt and NeoForge, and the download table shows which loaders each Minecraft version has.
Sodium is a client-side optimization mod for Minecraft that replaces the game's rendering engine with a faster, modern one. It significantly improves frame rates and reduces micro-stutter without changing how the game looks or plays, and it stays compatible with a wide range of other mods.
A client-side performance mod by tr7zw that skips drawing mobs and block entities such as chests and signs when a wall or floor hides them, using visibility tests on a separate thread. It changes only what your own game draws, not how entities behave on the server.
More Culling is a client-side rendering mod for Minecraft: Java Edition that changes how the game decides which block faces, leaves, framed items and paintings are worth drawing. The build you need depends on the exact Minecraft release you play rather than on one universal latest version.