Minecraft 26.4 Makes Vulkan the Default. Here’s What Breaks, and How to Switch Back

Minecraft Java Edition 26.4 renders with Vulkan instead of OpenGL by default, and if that goes wrong the game no longer switches you back on its own. Since 26.4 Snapshot 1, released on September 22, 2026, the "Default" choice in the Graphics API setting means "Prefer Vulkan". And since Snapshot 7, released on November 3, "Default" does something stranger: it picks OpenGL or Vulkan at random every time you start the game. Mojang says that part is temporary.

So if the current snapshot crashes at launch, your shaders have vanished, or the game behaves differently from one launch to the next, the fix is to stop using "Default" and choose the renderer yourself: Options → Video Settings → Graphics API, pick Prefer OpenGL or Prefer Vulkan, then quit and relaunch the game.

Which of the two you should pick comes down to two things: whether you use Iris shaders, and how old your graphics card is. The rest of this page covers that, which GPUs Vulkan leaves behind, the bugs still open in the snapshots, and what to sort out before 26.4 ships.

How to switch Minecraft 26.4 back to OpenGL (or force Vulkan)

1. Open Options → Video Settings.
2. Find Graphics API. It has three values: Default, Prefer OpenGL, and Prefer Vulkan (experimental).
3. Choose Prefer OpenGL for the old renderer, or Prefer Vulkan to lock in the new one.
4. Quit the game and start it again. The renderer is chosen at startup, so the change does nothing until you restart. Leaving and rejoining the world is not enough.

The two "Prefer" options are not mirror images of each other, and the difference matters if your graphics driver is the thing that is unstable. Mojang's description of the setting is that "Prefer Vulkan" tries Vulkan and falls back to OpenGL if it does not work, while with "Prefer OpenGL" set, "no interaction will be made with Vulkan in case that causes crashes." If a Vulkan driver is what crashes your game, Prefer OpenGL is the setting that avoids it entirely.

If the game crashes before you can reach the menu, set the option in the file instead. Open options.txt in your Minecraft folder (%APPDATA%\.minecraft on Windows, ~/Library/Application Support/minecraft on macOS, ~/.minecraft on Linux), find the line that starts with graphicsApiPreference, and make it read:

graphicsApiPreference:prefer_opengl

That is the same line the small PreferOpenGL mod writes on every launch for people whose setup keeps resetting it; its notes add that older versions of the game spelled the key graphicsApi. If the line is missing, add it.

To check which renderer you are actually running, press F3. When Vulkan arrived in the 26.2 snapshots, Mojang's notes said "you can see which backend is being used in your F3 debug overlay (in the system_specs section)." In Snapshot 7 that check matters more than usual, because on "Default" the answer can change every time you launch.

What "Default" does, snapshot by snapshot

The history is on the Minecraft Wiki's Vibrant Visuals page, and the two 26.4 changes are in Mojang's own changelogs for Snapshot 1 and Snapshot 7. The random pick comes with a developer's note that explains the thinking:

As we've been defaulting to Vulkan for this snapshot series, we have had little testing on the OpenGL backend. After some recent big changes to our rendering code, we want to temporarily test both backends. This will be reverted in a future snapshot.

Read that as a warning as much as an explanation. Mojang has rewritten a large part of the renderer during 26.4, and the OpenGL path has had less testing than Vulkan since September. Either backend can have new bugs right now, which is exactly why they are randomising it: to collect crash reports from both. For you it means that, on "Default", a bug that appears on Monday and is gone on Tuesday may not have been fixed. You were simply on the other renderer. Pin the setting and you get consistent behaviour, and a bug report that is actually useful to Mojang.

The change that does not get reverted is the first one. Since Snapshot 1 the game "will no longer change the graphics API setting automatically if a startup crash is detected." In 26.2, a startup crash with Vulkan quietly reset the setting to Default, which from the eighth 26.2 snapshot onward meant OpenGL. Now the game leaves the setting alone and crashes again on the next launch. That is what people are hitting when they say 26.4 "won't open", and the options.txt line above is the way out.

Why Mojang is replacing OpenGL

Minecraft Java has drawn every frame with OpenGL since the first alpha. In February 2026 Mojang announced the switch and gave three reasons.

OpenGL is frozen, and Apple is removing it. In Mojang's words, "9 years ago OpenGL stopped receiving updates and is being deprecated on macOS, and in the future OpenGL will not run at all on macOS devices." Keeping Java Edition on OpenGL meant being limited to the older versions macOS still supported, which made the renderer harder to modernise for everyone.

Vulkan runs everywhere Minecraft does. It is supported natively on Windows and Linux. macOS has no Vulkan of its own, so the game uses MoltenVK, a translation layer that converts Vulkan calls into Apple's Metal, which Mojang says works "without performance penalties."

It is the road to Vibrant Visuals. Mojang called the first Vulkan snapshot "a major step towards bringing Vibrant Visuals to Java Edition." The lighting overhaul that already shipped on Bedrock needs a renderer that can run on its own thread and use a modern API, and that is what 26.2 through 26.4 have been building. To be clear: 26.4 does not bring Vibrant Visuals to Java. It brings the renderer Vibrant Visuals will need.

There is one more line in that announcement worth keeping in mind. "Once we're happy with the performance and stability of Vulkan across devices we will remove the OpenGL implementation. Players will be notified in advance before this happens, and we'll make updates as needed to our 'minimum requirements' specifications." Prefer OpenGL is an escape hatch with an expiry date, not a setting you can live on forever.

Which GPUs can run Vulkan, and which stay on OpenGL

Mojang's stated requirement is "Vulkan 1.2 with dynamic rendering and push descriptors, but this requirement may increase or decrease over time." If your hardware or driver cannot provide that, "OpenGL will be used as a fallback." The rough rule from the February announcement: "For players whose GPUs are 10 years old or more, Vulkan may not be supported."

In practice the cut-off is older on desktop cards than on integrated graphics:

The caveat: a Vulkan driver is necessary but not sufficient. The game also needs two newer extensions, dynamic rendering and push descriptors, and the final drivers written for 2012-era cards may not include them even though "Vulkan" is on the spec sheet. The reliable test is the game itself. Set Prefer Vulkan, launch, press F3 and read which backend it chose.

Two side effects of the switch are worth knowing even on a modern machine:

• Laptops with two GPUs will use the dedicated one. Mojang: "Under Vulkan, we will prefer your dedicated graphics card over any integrated graphics, which is a change from OpenGL." If Minecraft has been quietly running on your laptop's integrated graphics for years, the move to Vulkan can look like a free upgrade. Check which card F3 reports.
• No-Vulkan machines used to get software rendering. Until Snapshot 7, on a GPU without Vulkan the game could pick the llvmpipe software renderer under Vulkan rather than the real GPU under OpenGL, which produced single-digit frame rates on hardware that ran 26.3 fine. That was MC-307991, fixed in Snapshot 7.

Do shaders work with Vulkan? Iris, OptiFine and Sodium

Iris shaders do not run on the Vulkan backend. Iris is an OpenGL mod. Its newest release is 1.11.7 for Minecraft 26.3, on Fabric and NeoForge, and there is no build for the 26.4 snapshots. The description of Vulcade, a mod built for the Vulkan backend, puts it plainly: "Iris is OpenGL-only, so switching Graphics API to Vulkan currently means giving up shaders entirely." Iris's own Modrinth page refers to a port to Vulkan being worked on, but nothing has shipped. So in 26.4, if you want your shader packs, set Prefer OpenGL. The Iris versus OptiFine question does not change; it just gains a third setting to get right.

OptiFine is not a factor. It has no build for any 26.x version, so it cannot run on either backend.

Sodium already runs on both. The June news on Sodium's CurseForge page announced 0.9.x for 26.2 "with early support for Vulkan," adding that "the performance of the Vulkan backend is already in a good place (even faster than before on many devices)." The current release line is 0.9.3 for 26.3. Sodium is a performance mod, not a shader loader, but it means the most-installed mod in the Java ecosystem is not blocking anyone from Vulkan.

Vulcade is the one shader option on Vulkan, and it is limited by design. Vulcade runs shader packs through Minecraft's own post-processing system, so the game compiles them for whichever backend is active. It does colour grading and similar screen-space effects, and its own page says it cannot do shadow maps, water reflections, waves or volumetric clouds, because those need access to world rendering that a post pass never gets. It is a beta for 26.2 with a few thousand downloads. If your shaders are about shadows and water, this is not a replacement.

Mojang warned about this gap in February: moving a rendering mod to Vulkan "will take modders more effort than the updates you undertake for each of our releases," and players should "have patience with authors." Expect a period after 26.4 ships when the choice is shaders on OpenGL, or Vulkan without them.

Known Vulkan bugs in the 26.4 snapshots

Still listed as open in the Snapshot 7 notes on the Minecraft Wiki:

• MC-312444: resizing the window with Vulkan can crash and hard-lock the game on Windows. It has been on the known-issues list since Snapshot 3. Workaround: use fullscreen (F11), and do not drag the window edges while playing.
• MC-312375: windowed mode can render incorrectly under Vulkan, with visual distortion. Same workaround.

Fixed during the snapshot cycle, in case you are on an older snapshot or searching for the symptom:

• MC-307830: frame rate limited to 20 FPS with Vulkan on some systems. Fixed in Snapshot 3.
• MC-312962: the Vulkan backend leaked native memory on every render pass. Fixed in Snapshot 7. If memory use climbed during long sessions on Snapshots 1 to 6, that was it.
• MC-311954: OpenGL could not be used under XWayland on Linux. Fixed in Snapshot 7.

Snapshot 5 also added a Windows-only video setting, Prefer DXGI Present, which asks DirectX to put the finished frame on screen. It is off by default, Mojang calls it experimental and says not all hardware supports it, and the Snapshot 5 notes list what it may improve: variable refresh rate support, faster alt-tabbing in fullscreen, and input method (IME) support. If VRR is not engaging or alt-tab is slow on Vulkan, it is one more toggle to try before giving up on the new backend.

Does any of this affect servers?

No. The renderer is entirely on the client, and server.properties has no graphics settings. The 26.4 server-side changes are about connections, such as the new allowed-connection-ids property. If friends cannot join after you update a server, Vulkan is not the reason; the usual cause since 26.3 is the whitelist.

What to do before 26.4 releases

Decide your setting now. If you use Iris shaders, plan on Prefer OpenGL the day you update, and watch Iris's release page for a Vulkan build. Everyone else should leave Vulkan on and test it, because it is where the fixes and the future features are going.

Test on a snapshot, on a copy of your world. Snapshots can change world generation, and a world opened in a newer version keeps the new chunks. Copy the save first, set Prefer Vulkan, play for an evening, and check F3 to confirm you were really on Vulkan.

Old GPU? Set Prefer OpenGL and note the expiry. OpenGL will be removed once Vulkan is stable, with notice. An Intel Haswell laptop or a GeForce 500-series card will keep running 26.4, but the clock on it has started.

Laptop with two GPUs? Check which one F3 reports. Vulkan prefers the dedicated card. If the game got faster or hotter after updating, that is why.

Update your graphics driver before reporting a bug. Most Vulkan-only failures are driver failures, and Mojang's bug tracker will ask.

On "Default" in Snapshot 7, expect inconsistency. It is a coin flip per launch by design. Pin the setting if you want the same game twice in a row.

The short version

• 26.4 makes Vulkan the default renderer for Minecraft Java, from Snapshot 1 (September 22, 2026). Since Snapshot 7 (November 3), "Default" picks OpenGL or Vulkan at random on each launch, which Mojang says is temporary.
• The game no longer switches itself back after a crash. Set the renderer yourself: Options → Video Settings → Graphics API, then restart. If it crashes before the menu, set graphicsApiPreference:prefer_opengl in options.txt.
• Use Prefer OpenGL if you run Iris shaders (OpenGL-only, newest build is for 26.3) or your GPU is more than about ten years old. Use Vulkan otherwise.
• Vulkan needs version 1.2 plus two extensions. Roughly 2012-era NVIDIA and AMD cards and 2015-era Intel graphics qualify; Macs run it through MoltenVK. F3 shows which backend you got.
• Two Vulkan bugs are still open in the snapshots, both about resizing or windowed mode; fullscreen avoids them. The 20 FPS cap and the memory leak have been fixed.
• Servers are unaffected, and 26.4 is not Vibrant Visuals for Java. It is the renderer that Vibrant Visuals will eventually need, and OpenGL will be removed once Vulkan is stable.