
You have a NeoForge modpack, maybe a 1.21.1 pack from CurseForge or a fresh 26.3 instance, and you want shaders. The old habit is to drop OptiFine into the mods folder. So does OptiFine work with NeoForge? Below is the answer for each Minecraft version, read from OptiFine's own download page and changelogs on 4 November 2026, followed by the shader files that do run on NeoForge today and what to take out of an older pack.
Quick answer: No, not on any NeoForge version after 1.20.1. OptiFine's changelog names NeoForge exactly once, in the 1.20.1 HD U I6 entry ("compatible with NeoForge 47.1.56"), and OptiFine's install docs say: "OptiFine is not yet available for NeoForge." For shaders on NeoForge 1.21.1 through 26.3, install Iris together with Sodium (on CurseForge they are called Iris Shaders and Sodium). On 26.3, pair Iris 1.11.7 with Sodium 0.9.3-beta.1, because Sodium 0.9.2 crashes on NeoForge 26.3.0.65-beta and newer.
Does OptiFine Work With NeoForge? Version by Version
OptiFine's changelog repeats every earlier release under the newest one, so a single search of the 26.2 preview changelog covers all of them, including 1.20.2, 1.21, 1.21.3, 1.21.4 and 1.21.6 to 1.21.9, which are not in the table. The word NeoForge appears once. The table lists the newest build for each version below on optifine.net/downloads, with the date and the Forge column shown there:
| Minecraft | Newest OptiFine build (date) | Forge column on optifine.net | NeoForge named? |
|---|---|---|---|
| 26.3 | None yet | No | |
| 26.2 | HD U K2 pre5, preview (20 Oct 2026) | N/A | No |
| 26.1.2 | HD U K1 pre2, preview (22 Jun 2026) | N/A | No |
| 1.21.11 | HD U J9 (5 Feb 2026) | Forge 61.0.8 | No |
| 1.21.10 | HD U J7 pre11, preview (3 Dec 2025) | Forge 60.1.0 | No |
| 1.21.1 | HD U J1 (24 Sep 2024) | Forge 52.0.16 | No |
| 1.20.6 | HD U J1 pre18, preview (27 Sep 2024) | Forge 50.1.19 | No |
| 1.20.4 | HD U I8 pre4, preview (23 Mar 2024); last full release HD U I7 (17 Mar 2024) | Forge 49.0.31 | No |
| 1.20.1 | HD U I6 (21 Dec 2023) | Forge 47.2.18 | Yes: NeoForge 47.1.56 |
How to read the table:
- 26.1.2 and 26.2 do not even run on Forge. Both preview changelogs end with "not compatible with Forge", and the download page shows N/A in the Forge column.
- 1.20.1 is the one exception, and it is a narrow one. NeoForge 47.1.56 is a NeoForge build for 1.20.1 that still used Forge's numbering (NeoForge's Maven publishes it as
net.neoforged:forge1.20.1-47.1.56). That line goes up to 1.20.1-47.1.106, and OptiFine does not say whether the later builds work. The developer did work on NeoForge back then: a NeoForge crash with I6 pre5 (issue #7505, July 2023) was answered with "Fixed in pre6." - NeoForge's own numbering starts at 20.2 (the first
net.neoforged:neoforgebuild is 20.2.3-beta, for Minecraft 1.20.2). No OptiFine build names any version from that series.
On Forge itself OptiFine still works as a mod: its Forge install guide only asks that the OptiFine build be compatible with your Forge version, which is what the Forge column above shows.
What the OptiFine Developer Has Said
The NeoForge page of the OptiFine docs has two lines: "OptiFine is not yet available for NeoForge." and "See issue GH-7626." The docs were last updated on 9 February 2026.
That issue, "[1.20.4+] Support for NeoForge", has been open since 9 March 2024. On 13 March 2024 the developer, sp614x, replied: "There will be support for NeoForge at some point. Probably for the next major MC release (1.21)." OptiFine has since shipped builds for ten 1.21.x versions, from 1.21 to 1.21.11, plus previews for 26.1.2 and 26.2, and none of their changelogs mention NeoForge. A newer request for NeoForge support on 1.21 and up (issue #8093, opened 13 January 2026) is still open with no reply.
So there is no date. Plan your pack around what exists today.
What Happens If You Put OptiFine in a NeoForge Mods Folder
A player tried it with OptiFine 1.20.4 HD U I7 on NeoForge 20.4.237 and reported it as issue #7925. The OptiFine installer's Install button created no file in the mods folder, so they used its Extract button and put the extracted jar into .minecraft/mods. The game crashed straight away, even with no other mods. No crash report was written: the errors only appeared in the launcher's log, launcher_log.txt. These are the lines from that log:
| Line in the log | What it tells you |
|---|---|
Error Service failed to load OptiFine | NeoForge's mod launcher tried to start OptiFine's loading service, and it failed |
cpw.mods.modlauncher.api.IncompatibleEnvironmentException: Error loading OptiFine ZIP file: union:/.../mods/OptiFine_1.20.4_HD_U_I7_MOD.jar%23216!/ | OptiFine tried to open its own jar through the path NeoForge handed it |
java.nio.file.NoSuchFileException: <WORKDIR>\.minecraft\mods\OptiFine_1.20.4_HD_U_I7_MOD.jar#216 | That path, with #216 glued to the file name, does not exist on disk |
Exception in thread "main" cpw.mods.modlauncher.InvalidLauncherSetupException: Invalid Services found OptiFine | The launch stops here, before the game window loads |
What to do if you see this:
- Open
launcher_log.txtin the launcher folder, which on Windows is%APPDATA%\.minecraftby default. Look there, not incrash-reports, which stays empty for this crash. If you start the game from another launcher, search its log output for the same lines. - Delete the OptiFine jar (
OptiFine_..._MOD.jarorOptiFine_....jar) from the instance's mods folder. - Install Iris and Sodium for your Minecraft version from the table below. Your shader packs can stay where they are.
Which Shader Loader to Use on NeoForge (and on CurseForge)
These are the newest NeoForge builds on Modrinth on 4 November 2026. The "Pair with" column is the Sodium file each Iris build names as its dependency, except on 26.3, where the dependency it names crashes on current NeoForge:
| Minecraft | Shader mod for NeoForge (date) | Pair with (date) |
|---|---|---|
| 26.3 | Iris 1.11.7 (30 Sep 2026) | Sodium 0.9.3-beta.1 (15 Oct 2026) |
| 26.2 | Iris 1.11.4 (13 Sep 2026) | Sodium 0.9.2 (11 Sep 2026) |
| 26.1.2 | Iris 1.11.4 (13 Sep 2026) | Sodium 0.9.2 (11 Sep 2026) |
| 1.21.11 | Iris 1.10.8 (29 Sep 2026) | Sodium 0.8.14 (28 Aug 2026) |
| 1.21.10 | Iris 1.9.7 (18 Dec 2025) | Sodium 0.7.3 (10 Nov 2025) |
| 1.21.1 | Iris 1.8.14-beta.1 (13 Jun 2026) | Sodium 0.8.13 (28 Aug 2026) |
| 1.20.2 to 1.20.6 | None from Iris, Oculus or OptiFine | |
| 1.20.1 | Oculus 1.20.1-1.8.0 (24 Dec 2024) | Embeddium 0.3.31 (31 Aug 2024) |
Notes per version:
- 26.3: use Sodium 0.9.3-beta.1, not 0.9.2. Sodium issue #3949, "Incompatibility with Neoforge >=26.3.0.65-beta", reports that the game crashes at launch with Sodium 0.9.2 or 0.9.3-alpha.1 on NeoForge 26.3.0.70-beta, even with Sodium as the only mod. The fix (pull request #3948, merged 12 October 2026) shipped in Sodium 0.9.3-beta.1, whose changelog says "Fix compatibility with Neoforge 26.3.0.65-beta". The newest NeoForge 26.3 build on NeoForge's Maven is 26.3.0.101 (1 November 2026), so unless your pack pins NeoForge 26.3.0.64-beta or older, you need the beta. Iris 1.11.7 still names Sodium 0.9.2 as its dependency on Modrinth, but the Iris jar itself accepts any Sodium from 0.6 up (
versionRange = "[0.6,)"), so it loads with 0.9.3-beta.1. - 1.21.11: update Iris and Sodium together. Sodium 0.8.14 for Fabric refuses Iris 1.10.7 and older (
"iris": "<=1.10.7"underbreaks). The NeoForge jar of Sodium 0.8.14 declares no such check, so NeoForge will load an old Iris next to the new Sodium without a warning. Use Iris 1.10.8 with Sodium 0.8.14. Sodium 0.8.15-beta.1 (20 Sep 2026) also exists for 1.21.11 if you want to test it. - 1.21.1: the newest Iris is a beta. Modrinth files Iris 1.8.14-beta.1 under releases, but its name is "Iris 1.8.14 Beta 1" and it needs Sodium 0.8.13. If you prefer the last full release, use Iris 1.8.12 (17 Jun 2025) with Sodium 0.6.13 (4 Apr 2025), the pair that Iris file names.
- 1.20.2 to 1.20.6 have no shader option on NeoForge. Iris's first NeoForge builds are for 1.21, Oculus stops at 1.20.1, and OptiFine names no NeoForge build for these versions. Embeddium does have NeoForge builds here, but it is a performance mod, not a shader loader.
- 1.20.1 uses Oculus, described on its Modrinth page as an "Unofficial Fork of 'Iris', made to work with FML", on top of Embeddium, which is "based on the last FOSS-licensed version of the Sodium codebase". Modrinth tags both files for Forge and NeoForge. Oculus has had no new build since 24 December 2024.
On CurseForge the projects are called Iris Shaders and Sodium, and both list NeoForge files there (for example "Iris 1.11.7 for NeoForge 26.3" and "Sodium 0.9.3-beta.1 for NeoForge 26.3"). Add both to your NeoForge profile and pick the file that matches your Minecraft version. On 4 November 2026 the Sodium page still shows Sodium 0.9.2 for NeoForge 26.3 as its main file, so on 26.3 pick 0.9.3-beta.1 from the file list yourself. On Modrinth, the NeoForge file lists are at modrinth.com/mod/iris/versions?l=neoforge and modrinth.com/mod/sodium/versions?l=neoforge. For the full install steps and where shader packs go, see our Iris and Sodium setup guide. If you are still deciding between the two shader mods on a loader where both run, read Iris vs OptiFine; for replacements for OptiFine's other features, see OptiFine alternatives.
Remove These From an Old Pack
When you move a pack to NeoForge 1.21.1 or newer with Iris and Sodium, take these out of the mods folder first:
- OptiFine. No build after 1.20.1 names NeoForge, and on 1.20.4 it stops the launch with the errors above.
- Embeddium. Iris's NeoForge metadata marks it as incompatible with the reason "Iris and Embeddium cannot be used together." Sodium 0.8.13 for NeoForge 1.21.1 does the same: "Sodium and Embeddium cannot be used together. Please remove Embeddium." Embeddium has a NeoForge 1.21.1 build (1.0.15, January 2025), so an older 1.21.1 pack may still carry it.
- Oculus. It requires Embeddium and has no build newer than 1.20.1.
If your pack is a 1.20.1 NeoForge pack, keep Oculus and Embeddium and leave Iris and Sodium out, since neither has a NeoForge build for 1.20.1.
Do Shaders Go on the Server?
No. Modrinth lists Iris, Sodium, Oculus and Embeddium as client mods that are unsupported on servers. Each player installs them in their own game, and the server only needs the modpack's server files, so leave them out of the server's mods folder.
If you run the pack on a server with us, our Minecraft modpack hosting has NeoForge, Forge and Fabric as server types: install a listed CurseForge or Modrinth pack with the panel's modpack installer, or upload the pack's server files over SFTP. Shaders stay on each player's computer either way. New to the loader itself? Our NeoForge install guide covers it.
FAQ
Does OptiFine work with NeoForge?
Only on Minecraft 1.20.1: OptiFine 1.20.1 HD U I6 lists "compatible with NeoForge 47.1.56". No later OptiFine build names NeoForge, and OptiFine's docs say "OptiFine is not yet available for NeoForge." Use Iris with Sodium instead.
Does OptiFine work with NeoForge 1.21.1?
No. OptiFine 1.21.1 HD U J1 (24 September 2024) is listed for Forge 52.0.16 and its changelog does not mention NeoForge. On NeoForge 1.21.1, install Iris 1.8.14-beta.1 with Sodium 0.8.13, or Iris 1.8.12 with Sodium 0.6.13 if you want the last full release.
Is there OptiFine for NeoForge 26.3?
No. On 4 November 2026 optifine.net has no build for Minecraft 26.3 at all; the newest is a 26.2 preview that is "not compatible with Forge". For 26.3 on NeoForge, use Iris 1.11.7 with Sodium 0.9.3-beta.1.
Which shader loader should I use on CurseForge with NeoForge?
Iris Shaders, together with Sodium, both from their CurseForge pages, choosing the NeoForge file for your Minecraft version. Do not add Embeddium or Oculus to the same profile, and on 26.3 take Sodium 0.9.3-beta.1 rather than 0.9.2.
Do OptiFine shader packs work with Iris on NeoForge?
Mostly, yes. Iris describes itself as "intended to be compatible with existing OptiFine shader packs", and its README says it "supports almost all shader packs". The Iris team keeps a short list of packs that do not work, such as Continuum 2.1, RT and other Focal Engine shaders, and Chronos 4.x. For packs to try, see the best shader packs for Sodium and Iris.
Will OptiFine ever support NeoForge?
The developer said in March 2024 that support would come "at some point", probably with 1.21. It has not arrived on any 1.21 or 26.x build, the NeoForge issue is still open, and there is no announced date.
Sources
All opened on 4 November 2026:
- OptiFine downloads (newest build, date and Forge column per Minecraft version)
- OptiFine changelogs: 1.20.1 HD U I6, 1.20.4 HD U I7, 1.21.1 HD U J1, 1.21.11 HD U J9, 26.1.2 HD U K1 pre2, 26.2 HD U K2 pre5
- OptiFine docs: Install With NeoForge and Install With Forge
- OptiFine issues: #7626 Support for NeoForge, #7925 NoSuchFileException and IncompatibleEnvironmentException with NeoForge and its attached launcher_log.txt, #7505 NeoForge crash fixed in pre6, #8093 NeoForge 1.21+ request
- NeoForge Maven: neoforge versions and 1.20.1 forge versions
- Modrinth API, NeoForge files: Iris, Sodium, Oculus, Embeddium
- Modrinth project pages: Iris, Sodium, Oculus, Embeddium
- Metadata inside the jars: Iris 1.11.7 for NeoForge 26.3 (
neoforge.mods.toml), Sodium 0.8.13 for NeoForge 1.21.1, Sodium 0.8.14 for NeoForge and Fabric 1.21.11, Sodium 0.9.3-beta.1 for NeoForge 26.3, and the Iris NeoForge mods.toml on GitHub - Sodium: issue #3949, pull request #3948, 0.9.3-beta.1 changelog on Modrinth
- Iris: README and unsupported shader packs
- CurseForge: Iris Shaders and Sodium
- Minecraft Wiki: .minecraft (launcher folder and launcher_log.txt)