GNOME’s Mutter compositor just gained official support for a standardized way for applications to request background blur. The change landed in the code for GNOME 51. It closes years of user requests and workarounds.
The feature relies on the ext-background-effect-v1 protocol. KDE’s Plasma already implemented it months ago. Now both major Linux desktop environments share a common path for frosted-glass visuals on Wayland.
From Hacky Extensions to Native Protocol Support
Developers and users have wanted this capability since at least 2023. The GNOME Mutter issue 3023 outlined clear use cases. Blurred sidebars. Video player controls with translucent overlays. Terminals that show a soft backdrop instead of plain transparency. Popovers in dense interfaces. The request called for GPU-accelerated blur handled by the compositor.
Early attempts relied on extensions. Blur My Shell became popular. It applied effects across the desktop but introduced bugs and performance trade-offs. Some users turned to forked versions of Mutter itself. Those patches added rounded corners and blur yet broke with updates and carried stability risks. One such project, mutter-rounded, saw its maintainer walk away. Community forks appeared. None delivered a clean, upstream solution.
Discussions on the GNOME Discourse forum in January 2026 highlighted the gap. One developer asked whether GTK applications could tap Clutter’s existing BlurEffect. The answer came back blunt. The effect must happen on the compositor side. Applications lack knowledge of what sits behind them. Only the compositor can capture and process that content efficiently.
Meanwhile KDE moved forward. Plasma 6.7 added support for the new protocol. It revived elements of the old Air theme with proper blur. The protocol itself reached the Wayland Protocols repository in May 2025 after talks that began in early 2024. KDE developer Xaver Hugl drove much of the specification work. The initial version targets blur but leaves room for future effects.
Phoronix first covered the protocol merge. Then reported GNOME’s adoption. Michael Larabel noted on July 4, 2026 that the feature arrived for GNOME 51 following the alpha release. The implementation came from Kristof Imerir. His merge request landed in Mutter just days earlier.
The code follows the protocol’s state model closely. Clients create one background-effect object per wl_surface. They set or clear a surface-local blur region. Changes apply as double-buffered state on the next commit. Mutter clips the region to the surface bounds before it reaches the actor. Blur paints before the surface contents. The compositor captures the framebuffer behind the requested area, blurs it offscreen, then composites the result back into the surface-local region.
Redraw logic tracks the sample region. This keeps clipping and culling accurate so only necessary pixels update. Tests inside a nested Mutter instance confirmed the behavior. The protocol global appears when queried with wayland-info. Blur stays attached while windows move. It respects rounded corners and other clipping. The merge request explicitly closes the long-standing issue 3023.
But don’t expect every GNOME application to gain blur overnight. The protocol support sits in Mutter. Toolkits must adopt it next. A GTK feature request now exists. Libadwaita discussions continue around transparency and legibility. Shell overrides remain under review in another merge request. Hard-coded values in the current implementation will need refinement for user control and accessibility.
Performance questions surfaced repeatedly in the original issue thread. Jeff Fortin, active in those talks, pushed back on concerns. “GPUs could do this trivially back in 2006,” he wrote. Modern hardware should handle the load without noticeable impact even on battery. Still, the design keeps the effect optional. Applications request it per surface rather than forcing global changes. GNOME Shell visuals stay untouched for now. This avoids breaking existing themes or introducing unexpected overhead.
Other compositors watch closely. A Hyprland discussion from late 2025 already asks for support. The protocol’s region-based approach lets developers blur precise areas. A rounded notification can have its background blurred while keeping a clean drop shadow outside that region. Terminals gain a true frosted look without the full-window cost of older extensions.
Recent articles reinforce the momentum. Phoronix detailed the Mutter merge hours ago. OMG! Ubuntu covered a clever but limited workaround in December 2025. The 2 Wallpapers extension swaps desktop backgrounds so transparent apps appear to sit over a pre-blurred image. It avoids real-time compositing expense yet cannot match dynamic content or moving windows. The new native path renders such hacks obsolete for supported applications.
So the ground has shifted. What lived in fragile extensions now rests in a shared protocol. Applications can request blur without knowing the full scene behind them. Compositors decide how to render it. Users gain consistent, hardware-accelerated effects across desktops. Developers face less fragmentation.
Full integration will take time. GTK bindings, design guidelines, accessibility settings, and performance tuning remain. Yet the core piece sits merged. GNOME 51 will ship with the foundation in place. Expect toolkits and apps to follow. The frosted-glass aesthetic many Linux users have chased for years just became a first-class citizen.
WebProNews is an iEntry Publication