Mojang has replaced Minecraft: Java Edition's underlying windowing and input library, switching from GLFW to SDL3, as detailed in snapshot 26w3a (version 26.3) released on July 16, 2026 (Minecraft.net). The change reworks how the game creates windows, processes input, and communicates with the operating system across all supported platforms.

With the SDL3 migration, keyboard input now uses SDL scancodes — identifiers tied to a key's physical position on the keyboard rather than to the character that layout produces. Key bindings correspondingly reference physical keys. For players who use non-QWERTY layouts, this means the physical position of a bound key stays consistent regardless of which layout is active. The shift from logical to physical key addressing is a meaningful change for international users and for anyone who switches layouts mid-session.

The snapshot sets Borderless Fullscreen as the new default fullscreen mode. Borderless Fullscreen runs the game in a window that fills the screen without taking exclusive control of the display, while Exclusive Fullscreen asks the operating system to hand the display over entirely. Switching between the two no longer requires restarting the game, which removes a long-standing friction point. However, Exclusive Fullscreen support has narrowed: macOS no longer supports it at all in this build.

Linux systems get native Wayland support, which the game will prefer when available. Wayland is the modern display protocol used by most Linux desktop environments, replacing the older X11 system. Minecraft players on Linux have relied on X11 or translation layers to bridge the gap, and SDL3's mature Wayland support brings the game into line with the direction most Linux desktops have taken.

Several known issues accompany the snapshot. Exclusive Fullscreen on Windows may cause the game to crash in certain situations, particularly with multiple monitors. On Wayland, entering Exclusive Fullscreen crashes the game outright. These are flagged as known issues in the snapshot notes, meaning they are acknowledged but not yet resolved. Players who depend on Exclusive Fullscreen — particularly on multi-monitor Windows setups or on Wayland compositors — should treat the current snapshot with caution.

Beyond the platform-layer changes, the snapshot adds new item components for custom furnace fuels and ships technical changes covering signs, world generation, and loot tables. The Data Pack version moves to 111.0 and the Resource Pack version to 92.0. Creators maintaining custom data packs and resource packs will need to account for the version bumps.

The broader context here is that a library migration of this scope touches every layer of the game's interaction with the operating system: window creation, input event routing, display mode negotiation, and monitor enumeration. SDL3, released by the Simple DirectMedia Layer project, consolidates these platform concerns into a single API and has been adopted across a wide range of games and engines. GLFW, by contrast, is narrower in scope, focused on OpenGL/Vulkan context creation and input handling. The move to SDL3 gives Mojang a more comprehensive platform abstraction layer, which is reflected in the Wayland support and the seamless fullscreen-mode switching arriving in the same snapshot.

In this author's view, the known issues around Exclusive Fullscreen on both Windows and Wayland are worth flagging for anyone considering this snapshot for daily play. The crashes are acknowledged, and snapshot builds are inherently experimental, but the fact that Exclusive Fullscreen is unstable on two of the three platforms where it remains available suggests the migration is still settling. Borderless Fullscreen as the default is a sensible hedge, since borderless mode avoids the display-mode negotiation that makes Exclusive Fullscreen fragile on multi-monitor and Wayland setups.

The combination of physical-key input, native Wayland, and borderless-default fullscreen addresses several long-running pain points for Java Edition players on non-Windows platforms. The migration cost, measured in current known issues and pack version bumps, is real but contained. For a snapshot, that is a reasonable trade.