Minecraft Shaders on a Low-End PC: What Survives (2026)

On a weak machine the order is fixed: install Sodium, then Iris, then a pack that has a low-quality profile, then turn the shadows down before you look at anything else. Sodium is the rendering rewrite that buys you the frames; Iris is the loader that spends them. Skipping the first step and installing a shader pack straight onto vanilla is the most common way this ends in 12 FPS.

Two numbers decide whether this is worth trying at all. Sodium's own page requires OpenGL 4.5 and a GPU no older than Intel HD 500 series, GeForce 400 series or Radeon HD 7000 series. And if you are at 30 FPS before shaders, no pack on this page will save you — that is a hardware conversation, and it is covered in the low-end PC FPS guide.

Short answer

Install Sodium first. Iris's own installer ships Sodium with it, so one download covers both.
Requirements from Modrinth: OpenGL 4.5, Intel HD 500 series / GeForce 400 series / Radeon HD 7000 series or newer. No OpenGL translation layers.
Of the packs still shipping for 26.2, Complementary Unbound has an explicit Potato profile and MakeUp Ultra Fast makes every effect optional.
Shadows are the expensive setting. Two independent pack authors say so; turn them down first.
Potato Shaders is genuinely light but its version list stops at 1.20.1 — it is not an answer on a current world.

Iris, Sodium, and what each one actually does

They solve different problems and people constantly conflate them.

Sodium replaces Minecraft's rendering engine. Its description claims greatly improved frame rates and less micro-stutter, plus fixes for a set of graphical faults. It is client-side only, it runs on Fabric, Quilt and NeoForge, and its Modrinth version list runs from 1.16.3 all the way to 26.2. On a weak PC this is the single mod that changes the numbers.

Iris is a shader loader. It is built to be compatible with existing OptiFine shader packs, so the packs you find posted anywhere will load. Its Modrinth listing covers 26.2 and 26.1.x on Fabric, NeoForge and Quilt; the project site adds that Fabric support starts at 1.16.5 and NeoForge support at 1.21.1.

The useful part: the Iris installer ships with Sodium out of the box. You do not have to assemble the pair yourself.

Lithium is the third name you will see. It optimizes game logic rather than rendering, and Sodium's own page recommends running them together. It does nothing for shaders directly, but it takes load off a CPU that is already the limiting factor on most cheap laptops.

Will shaders even start on my GPU?

Check three things in this order.

1. The GPU generation. Sodium officially supports Intel HD Graphics 500 series and newer, NVIDIA GeForce 400 series and newer, AMD Radeon HD 7000 series and newer. Below those lines you are outside what the mod is tested against.

2. The OpenGL version. Sodium asks for OpenGL 4.5 or newer. Potato Shaders asks for 4.0, which is why it runs on some machines Sodium does not — and it also states outright that Intel HD 5000 Graphics and older are not supported on Windows.

3. The translation layer. Android devices and Windows-on-ARM machines that run OpenGL through a translation layer are listed as unsupported. If you are on an ARM laptop, this is where the attempt ends.

Minecraft 26.2 added an experimental Vulkan renderer, which is a different rendering path entirely and not the one these mods use. Nothing on this page depends on it yet.

Four packs, and what each one costs you

Everything below was checked against Modrinth on 6 September 2026. The version column is the part most shader lists omit, and it is the part that decides if the pack is usable at all.

Pack	Versions listed	Low-end profile	Verdict for a weak PC
Complementary Unbound	1.7.x–1.21.x and 26.2	Yes — profiles from Potato to Ultra	The default recommendation. Current, and the only one here with a named Potato tier.
MakeUp Ultra Fast	1.12.2 through 26.2 and 26.1.x	Every effect individually switchable	Best pick if you want to build your own budget: turn off shadows and depth of field and keep the rest.
BSL Shaders	1.7.10–1.21.x and 26.2	A Low profile is tagged, but the pack is built around realtime shadows and volumetric light	Beautiful, and the heaviest of the four. Try it after the other two, not before.
Potato Shaders	Stops at 1.20.1	Ships without dynamic shadows by design	Genuinely the lightest, and unusable on a 26.2 world. Listed here so you stop looking for it.

That table contains the least convenient fact in the whole topic: the packs built specifically for weak hardware are also the packs most likely to fall behind on versions. Potato Shaders excludes dynamic shadows and other expensive effects on purpose, which is exactly what you want — and it has not followed the game into the 26.x releases.

MakeUp's author frames it the way an engineer would: the pack aims for the best quality-to-performance ratio, everything is optional, and you consume only the resources you ask for. They also say plainly which effects are the expensive ones — shadows and depth of field — and that the pack has been tested across Nvidia, Intel and AMD on Windows and Linux, without a guarantee for every model.

Which shader settings actually cost the frames

You do not choose a pack so much as you choose a settings profile inside it. Open the shader options and work down this list.

Shadows. The single most expensive thing a pack does, and the one both MakeUp and Potato Shaders single out. Lower the shadow resolution first, shorten the shadow distance second, and if the frame rate is still not there, switch them off — a pack with no dynamic shadows still looks distinctly better than vanilla.

Volumetric light. BSL lists it as a headline feature, which tells you what it is for. It is a per-pixel effect over the whole screen and it scales badly on integrated graphics.

Depth of field and motion blur. Both are named as resource-intensive by the MakeUp description, and neither helps you see anything in game. Off.

Reflections and refraction on water. Optional in MakeUp, on by default in most pretty packs. Turning water reflections off is usually worth several frames and costs you a screenshot.

Anti-aliasing, especially TAA. The cheapest thing to lose on a small laptop screen where you were not resolving those edges anyway.

Bloom and chromatic aberration. Cheap by comparison. Leave them if you like the look; they are not where your frames went.

Render distance interacts with all of it. A shadow map has to be built for everything the game draws, so cutting render distance cuts shader cost twice over — that mechanic and the numbers behind it are in the low-end PC guide, and the same logic applies almost word for word in Roblox.

Should you install shaders at all at 30 FPS?

No, and this is worth being blunt about because most shader articles will not say it.

A shader pack adds work to a frame you are already failing to finish on time. If vanilla with Sodium gives you 30 FPS, a Potato-profile pack will give you something in the teens, and the game stops being playable long before it stops being pretty. The order that works is: Sodium, render distance, resolution, and only then shaders.

There is one legitimate exception. If you want screenshots of a build rather than a smooth session, load a heavy pack, stand still, take the shot, and unload it. Nothing is stopping you from running two shader profiles for two purposes.

And if you play PvP, treat frames as an input problem rather than a looks problem. A pack that drops you from 90 to 45 changes how the game answers your mouse, and you will feel it in trades long before you notice the shadows are prettier. The Kohi click test and the general CPS test are the cheap way to see how your own clicking holds up once the frame rate moves.

How to test a pack in three runs

Shader benchmarking goes wrong because people change two things at once. Do it like this.

Fix the world and the spot. Same seed, same coordinates, same time of day, looking in the same direction. A world you can recreate on demand is easiest — the seed guide covers reading and saving one properly.
Baseline with Sodium only. No shader loaded. Note the frame rate and, more importantly, the worst dips.
Load the pack at its default profile. Same spot, same direction, note both numbers again.
Change exactly one setting. Shadow resolution, then shadow distance, then volumetric light. One at a time, back to the same spot each time.

Judge on the dips, not the average. An average frame rate rises and falls with where you happen to be standing; the stutters are what make the game feel bad, and they are what a heavy shader pack produces most of.

What usually goes wrong

Shader pack installed without Sodium. Symptom: the pack loads, the game turns into a slideshow, and the pack gets blamed. Cause: vanilla rendering plus shader work, with no engine improvement underneath. Fix: install Iris's own build, which ships Sodium with it, rather than hunting the pack alone.

OptiFine and Iris installed together. Symptom: crashes on launch, or shaders that refuse to appear in the list. Cause: two mods trying to own the same rendering path. Fix: pick one. Iris loads OptiFine-format packs, which is the reason most people no longer need OptiFine at all.

Pack version does not match game version. Symptom: black screen, missing sky, or a shader list that stays empty. Cause: the pack's newest release predates your game — Potato Shaders stopping at 1.20.1 is the clearest example. Fix: check the Compatibility block on the Modrinth page before downloading, not after.

Shaders on an ARM laptop or a phone. Symptom: Sodium refuses to load or renders garbage. Cause: OpenGL through a translation layer is explicitly unsupported. Fix: there is no client-side workaround; this is a hardware limit, not a settings one.

Judged by the average frame counter. Symptom: "the pack costs me only ten frames" and the game still feels worse. Cause: the average hides the stutters, and shader work lands exactly where the stutters are. Fix: watch the worst numbers over a two-minute walk, not the number in the corner while standing still.

Once the game runs the way you want it to, the next question is what to point it at: there is a breakdown of house and base builds by type, a Minecraft name generator for the account that will live in them, and the rest of our Minecraft pages — including the knowledge quiz — on the Minecraft hub.

FAQ

Do I need OptiFine for shaders in 2026?

No. Iris loads OptiFine-format shader packs and is distributed for Fabric, NeoForge and Quilt, with 26.2 and 26.1.x in its Modrinth version list. Its own installer ships Sodium alongside it, so you get the rendering rewrite and the shader loader in one step.

What are the minimum requirements for Sodium?

Modrinth's own page states OpenGL 4.5 or newer, and lists Intel HD Graphics 500 series and up, NVIDIA GeForce 400 series and up, AMD Radeon HD 7000 series and up. Android and Windows-on-ARM devices running OpenGL through a translation layer are explicitly unsupported.

Which shader pack is the lightest?

Of the packs still shipping for 26.2, Complementary Unbound is the one with a documented Potato profile, and MakeUp Ultra Fast makes every effect individually switchable. Potato Shaders is lighter still but its version list stops at 1.20.1, so on a current world it is not an option.

Will shaders work if I get 30 FPS without them?

Not in any way you will enjoy. A shader pack adds work on top of the frame you already cannot finish in time. At 30 FPS the honest move is render distance and resolution first — shaders are for screenshots at that point, not for playing.

Which shader setting costs the most performance?

Shadows. Two pack authors say so independently: the MakeUp description names shadows and depth of field as the resource-intensive effects, and Potato Shaders is built around leaving dynamic shadows out entirely. Turn shadows down or off before you touch anything else.