If you use a Linux desktop, something significant has been changing beneath the surface for years, and most users never notice it until something breaks or suddenly works better than it ever did before. The shift from X11 to Wayland is one of the most consequential infrastructure changes in the Linux desktop world in decades, and it is now well past the point of being a niche developer concern.
What X11 Actually Is, and Why It Became a Problem
X11, more formally the X Window System, has been the foundation of graphical Linux desktops since the 1980s. It handles the communication between your applications and your display hardware, telling your monitor what to draw and routing your mouse clicks and keystrokes to the right windows. For a long time, it worked well enough that few people questioned it.
The problem is that X11 was designed for a computing world that no longer exists. It was built with the assumption that you might be running applications across a network, displaying them on a remote machine, and security was not a primary concern. In practice, this architecture means that any application on your desktop can, by default, read what you type in another application’s window. It can also capture screenshots of your entire screen without asking permission. For a modern operating system handling banking apps, password managers, and private communications, that is a significant structural weakness.
X11 also struggles with modern display hardware. High-resolution screens, fractional scaling (displaying at 125% or 150% to make things sharper on dense screens), and variable refresh rates are all areas where X11’s age shows. Workarounds exist, but they tend to be fragile.
How Wayland Changes the Model
Wayland was designed from scratch to address these problems. Rather than a separate server that all applications talk to, Wayland makes the compositor (the software that manages windows and composites them onto your screen) the display server itself. This tighter design means applications are isolated from one another by default. One app cannot snoop on another’s keyboard input without explicit permission from the user or the system.
The Wayland protocol began development around 2008, and its reference compositor, Weston, gave developers something to build against. Major desktop environments took years to follow. GNOME moved to making Wayland its default session in version 3.22, released in 2016. KDE Plasma took a more cautious path, given its reputation for broad hardware and configuration support. KDE declared Plasma’s Wayland session ready for general use with Plasma 6, released in early 2024, a milestone the project described as the product of years of sustained engineering work.
That shift in KDE matters because Plasma is one of the most widely used Linux desktop environments, particularly among users who want fine-grained control over their setup. Its endorsement of Wayland carried real weight in the community, and Plasma 6.8 has since gone Wayland-only.
Where Things Stand for Everyday Users
For most users on mainstream distributions, Wayland is already the default. Fedora has shipped GNOME on Wayland by default since Fedora 25 in 2016. Ubuntu followed. If you have been using a modern Linux desktop without tweaking session settings, there is a reasonable chance you have been running Wayland for some time without realizing it.
The remaining friction points are real but narrowing. Screen sharing in video calls was a persistent pain point for years, requiring specific portal support that not all applications provided. Nvidia GPU users faced driver compatibility issues that lingered longer than AMD or Intel users experienced. Remote desktop workflows, which X11 handled natively, require different tooling under Wayland.
Some users with specialized needs, particularly those using older accessibility tools or certain professional applications, still find X11 more reliable. Some distributions still offer an X11 session as an option at login, but the major desktops are retiring it: GNOME 50 (March 2026) removed its X11 session, and KDE Plasma 6.8 (October 2026) dropped the X11 session too. X11 applications still run through XWayland.
The transition is not quite finished, but the direction is settled. The Linux desktop community has committed to Wayland as its future, and the ecosystem of compatible applications and tools has grown substantially. For users who have held off on switching, the gap between X11 and Wayland compatibility has closed considerably, and for many workflows it has closed entirely.
If you are curious about your own setup, your desktop environment’s settings or system information panel will typically tell you which display server your current session is using. It is a small detail, but knowing it helps you understand what your system can and cannot do.