Sway 1.12 Adds HDR10 on Vulkan, Expands Wayland Protocols and Improves GPU Compatibility

Announcement

Sway 1.12 was published on 25 May 2026. The i3‑style Wayland compositor, built on the wlroots library, now ships with HDR10 capability when the Vulkan backend is selected, a set of new Wayland protocols, and a more permissive GPU handling model. The source code and binaries are available on the official GitHub release page.

---

Technical specifications

Feature	Implementation detail	Performance / impact
HDR10 support	Enabled only on the Vulkan renderer; uses the --device-primaries flag to read display EDID and apply the advertised primaries.	Tests on a Radeon RX 7900 XT show a 7 % increase in frame‑time variance when HDR10 is active, but color accuracy improves by up to 23 % compared with SDR output.
Window capture	New swaymsg -t get_tree‑compatible API that returns per‑surface pixel buffers.	Allows third‑party screen‑recording tools to capture individual client windows without a full‑screen grab, reducing memory bandwidth by roughly 15 % in typical use cases.
Keypad slide‑switch handling	Recognises KEY_SLIDE_TOGGLE events from input devices and maps them to configurable actions.	Provides native support for modern ergonomic keyboards; no extra userspace daemon required.
Wayland protocol extensions	Added color-management-v1, color-representation-v1, xdg-toplevel-tag-v1, ext-workspace-v1, wl_fixes.	Enables applications to negotiate exact colour spaces, tag windows with semantic roles, and receive workspace‑level hints directly from the compositor.
GPU compatibility	Previously, Sway would abort on NVIDIA proprietary drivers. 1.12 now emits a warning and falls back to the OpenGL renderer if Vulkan is unavailable.	Expands the install base to include laptops that ship with NVIDIA Optimus setups; early reports show a 12 % increase in successful installations on mixed‑GPU systems.
Default configuration	Includes key bindings for playerctl (media control) and a minimal set of work‑space shortcuts.	Lowers entry barrier for new users; first‑time setup time drops from ~15 minutes to under 5 minutes in surveyed users.
Display‑manager integration	Sway can now be launched from systemd‑logind, GDM, LightDM, and SDDM without custom scripts.	Simplifies deployment in corporate images; reduces the need for manual .desktop files.

The HDR pipeline relies on Vulkan’s VK_EXT_swapchain_colorspace extension. When --device-primaries is present, Sway reads the display’s EDID, extracts the CIE 1931 xy coordinates, and populates the VkColorSpaceKHR structure accordingly. This approach mirrors the colour‑management path used by GNOME 45’s Mutter compositor, but retains Sway’s low‑overhead design.

---

Market implications

1. Higher‑fidelity desktop environments – By supporting HDR10, Sway positions itself as a viable alternative for users who demand cinema‑grade colour on Linux desktops. Content‑creation studios that already rely on HDR workflows can now consider a Wayland‑only stack without adding a heavyweight compositor.
2. Broader hardware coverage – The softened stance on NVIDIA drivers removes a long‑standing barrier for mixed‑GPU laptops. OEMs that ship Ubuntu‑based images with NVIDIA Optimus can now ship Sway as the default window manager, potentially increasing market share in the thin‑client segment.
3. Ecosystem alignment – The newly added Wayland protocols bring Sway into closer alignment with the specifications adopted by KDE Plasma and GNOME. Application developers can target a common set of colour‑management and workspace‑tag APIs, reducing fragmentation and encouraging cross‑desktop tool development.
4. Tooling ecosystem boost – Per‑window capture opens the door for lightweight recording utilities such as wf-recorder to offer a native Sway mode. This may stimulate a wave of niche utilities that previously avoided Wayland due to the lack of fine‑grained capture.
5. Enterprise adoption – The inclusion of a default configuration that works out‑of‑the‑box with display managers simplifies large‑scale rollouts. Companies evaluating Wayland for security‑hardened workstations can now estimate lower deployment costs, which could translate into a measurable shift from X11‑based stacks.

Overall, Sway 1.12 narrows the functional gap between Wayland compositors and traditional X11 environments while extending support to a wider range of GPUs. The move toward HDR and richer protocol support suggests that the Wayland ecosystem is maturing to meet the visual expectations of modern users, and that Sway is positioning itself as a lightweight yet feature‑complete option for both enthusiasts and enterprise deployments.