COMPATIBILITY & REQUIREMENTS

Which Minecraft Versions Support Complementary Shaders?

Illustration for: Which Minecraft Versions Support Complementary Shaders?

Complementary Shaders is unusually generous with Minecraft versions: the current release supports more than a decade of the game. But "supported" has fine print, the loader pairing is strict, and older game versions pair with older loaders. This guide sets out exactly which Minecraft versions the current Complementary Shaders release supports, how the three version numbers (game, loader, shader) fit together, and what to do when your combination is not on the list.

Supported versions for the current release

The current release, r5.9.3, lists support for Minecraft Java Edition:

RangeVersions
Classic line1.7.10 through 1.21.11, including 1.8.x, 1.12.x, 1.16.x, 1.18.x, 1.20.x and the 1.21 series
New line26.1, 26.1.1, 26.1.2, 26.2 and 26.3

That breadth is deliberate design: one shader release serves many game versions, so players on long-running worlds and modpacks are rarely forced to choose between their world and current shaders. Version history context: latest version and release history.

The three version numbers

Every working setup has three versions that must agree:

  1. Minecraft version, yours to choose; everything else follows it.
  2. Loader version, Iris or OptiFine builds are made for specific Minecraft versions. This pairing is strict: a loader for 1.21.1 does not run on 1.21.4.
  3. Shader version, the pack release, whose supported range (above) is broad. Any release whose range covers your game version is a candidate.

Nearly every "shaders don't work after I changed versions" story is a loader mismatch wearing a shader costume. When something breaks, interrogate the loader first, the checklist is in fixing shaders after a Minecraft update.

Playing on an old Minecraft version

For legacy versions (a 1.12.2 modpack, a 1.16.5 server), the recipe is: the current or a period shader release whose range covers your version, plus the loader build made for that version. Iris's history covers more recent versions; OptiFine's archive reaches further back, which is one reason long-tail setups often run OptiFine. If you deliberately choose an older shader release, downloading older versions covers the archives and the matching logic.

Playing on the newest Minecraft version

On day one of a new Minecraft release, the shader is rarely the problem, the current pack's range usually extends quickly, but the loader may not exist yet for the new version. The honest options are patience (loaders update fast, Iris especially) or staying on the previous game version until the stack is complete. Forcing a mismatched loader is how saves get corrupted and evenings get wasted; do not.

Snapshots and pre-releases

Minecraft snapshots are moving targets, and loader support for them is inconsistent by nature. Treat snapshot play as experimental: back up your worlds, expect shader quirks, and do not troubleshoot a snapshot setup as if it were a release setup, the ground itself is unfinished.

Reading the supported range correctly

The range in the table, 1.7.10 through 1.21.11 and 26.1 through 26.3, is the pack's statement about its own code, taken from the current release's listing metadata. It means the shader code in r5.9.3 is written to work across that span of game versions. It does not mean every other part of your setup spans the same distance. In particular:

  • The range belongs to this release. An older Complementary release has its own, usually narrower, range. When you deliberately run an old game version with an old pack release, check that release's listing rather than assuming today's range applies backwards.
  • The endpoints are inclusive, the middle is continuous. Point releases inside the span, the many 1.20.x and 1.21.x updates, for example, are covered as part of the line, which is why the FAQ below can answer a specific version like 1.21.5 without a separate table row for it.
  • A covered game version still needs its own loader build. Coverage answers "can the shader run here?", not "does everything in my folder already fit?" The loader question is separate and strict, as the three-numbers section explains.

Keeping those three ideas separate prevents the most common misreading: downloading the current pack, seeing your version inside the range, and concluding that an old loader from a previous setup should work too. The pack is the forgiving component; the loader is not.

Checking your own combination before you troubleshoot

Before changing settings or reinstalling anything, write down your three numbers and verify them in order. It takes two minutes and resolves most version confusion without touching a file:

  1. Game version: read it from the launcher profile or the bottom corner of the title screen, not from memory, because many players run several profiles.
  2. Loader version: confirm the Iris or OptiFine build you installed was made for that exact game version. The build's filename or listing line states its target; "close" versions do not count.
  3. Shader version: confirm the pack release in your shaderpacks folder, and that your game version falls inside that release's supported range. The current release is r5.9.3; its range is the table at the top of this page.
  4. Selection: in Video Settings, confirm the pack is actually selected and not merely present in the folder, a present-but-unselected pack explains a surprising number of "nothing changed" reports.

If all four check out and the pack still misbehaves, the problem is almost certainly not version support at all. Move on to symptom-based help, Complementary Shaders not working for general triage, or the specific fix for a black screen or a pack missing from the list, rather than reinstalling versions at random.

Modpacks, servers and version lock-in

For many players the game version is not a free choice, and that is fine, the breadth of the pack's range exists precisely for locked-in setups. A long-running modpack pins the game version, which pins the loader build, and the shader simply has to fit inside that frame. Because r5.9.3 reaches back to 1.7.10, even quite old packs usually have a compatible Complementary release available, either the current one or a period release from the archives.

Servers do not change the equation. The pack is client-side: it is required on your machine and unsupported, and unnecessary, on the server. You can join a server running one game version from a matching client and see shaders locally, while the server neither knows nor cares which pack you selected. What the server does dictate is the client game version you must run to join it, and that in turn dictates your loader build. So the practical workflow for server players is: note the server's version, build your loader for exactly that version, then pick any pack release whose range covers it.

Finally, expect version choices to be sticky. Worlds, modpacks and server communities all resist casual version changes, so choose the game version for the world and community first, and fit loaders and shaders around it, never the other way round. The update path, when you do choose to move, is covered step by step in updating without losing your settings.

Frequently asked questions

Does the shader version need to match my Minecraft version exactly?

No, it needs to fall within the release's supported range. The loader is the component that must match exactly.

My version is 1.21.5. Am I covered?

Yes, the current release's range includes the full 1.21 series up to 1.21.11. Pair it with the Iris or OptiFine build made for 1.21.5.

What about Bedrock versions?

None. Complementary Shaders is Java Edition only, on every version, see the Bedrock guide.