As of August 16, 2026, Xfce’s path to Wayland compatibility is real but unfinished: Xfce 4.20 added experimental Wayland support to most core components, yet xfwm4 remains X11-only and the planned native compositor, xfwl4, is not usable. Wayland is suitable for testing, not as a drop-in replacement for X11 Xfce.
That apparent contradiction matters. Many Xfce applications can now run under Wayland, and an experimental Xfce session can be assembled with an external compositor such as labwc or Wayfire. However, launching Thunar, the panel, and the settings manager is not the same as having a complete Xfce Wayland desktop.
The missing piece is the window-management and compositor layer traditionally provided by xfwm4. Xfce is no longer trying to turn xfwm4 into a dual X11/Wayland component. Instead, the project is developing a separate Wayland compositor, xfwl4, while preserving xfwm4 for the established X11 session.
Key takeaways
- Xfce 4.20 introduced experimental Wayland support across most core components while retaining X11 support.
xfwm4remains an X11 window manager; it is not becoming Xfce’s Wayland compositor.xfwl4is the planned native Wayland compositor, written from scratch in Rust with Smithay, but the current roadmap describes it as early and unusable.- Users can test an experimental Wayland session with an external compositor such as labwc or Wayfire.
- Panel-plugin isolation, workspace behavior, screenshots, power keys, settings, status trays, and some application features remain incomplete or compositor-dependent.
What does Xfce Wayland compatibility actually mean?
Xfce Wayland compatibility can mean four different things, and confusing those levels creates most of the inaccurate claims about Xfce’s progress.
#1 Best Overall
- Intel Core i5-1335U Processor (12M Cache, 12 Threads, up to 4.6 GHz) - 256GB Solid State Drive - 16GB DDR4 SDRAM
- 15.6" FHD (1920x1080) Non-Touch Anti-Glare Display - Intel UHD 620 Integrated Graphics - Stereo Speakers
- 720p HD Webcam with Privacy Shutter. Integrated Microphone - Intel Dual Band Wireless-AC (2x2) 8265, Bluetooth Version 4.2
- I/O Ports: 2x USB 3.0, 1x USB 3.1 Type-C 3.1, Headphone/Mic Combo Port, 4-in-1 Card Reader, HDMI, Kensington Mini-Lock Slot
- Linux Mint (Cinnamon) 64-Bit - Keyboard with Full NumberPad - Fast Charging
- Wayland-capable application: An application can connect to a Wayland display instead of requiring an X11 display.
- Wayland code path: An Xfce component contains implementation work for Wayland-specific interfaces and behavior.
- Runnable Xfce session: A collection of Xfce components can start inside a third-party Wayland compositor.
- Integrated Wayland desktop: Xfce provides its own compositor and reproduces the important behavior and features of its mature X11 session.
Xfce has largely reached the first two levels for many components and can reach the third level experimentally. Xfce has not reached the fourth level. The Xfce Wayland roadmap and Xfce’s Wayland documentation both describe a component-by-component migration rather than a finished desktop release.
The practical formula is:
Xfce component
+ Wayland protocol support
+ compositor implementation
+ application or plugin port
= actual user-visible behaviorA component marked as having Wayland support may still behave differently under labwc, Wayfire, another compositor, or the future xfwl4. “Supported” therefore does not automatically mean “feature-complete,” “integrated,” or “production-ready.”
What changed in Xfce 4.20?
Xfce 4.20 supplied the architectural groundwork for Wayland. The release added experimental Wayland support across most core components while continuing to support X11. The Xfce 4.20 changelog identifies Wayland-related dependencies including Wayland 1.20, Wayland Protocols 1.25, and GTK Layer Shell 0.7.0.
A central part of that work is libxfce4windowing. The library provides abstractions for concepts such as screens, monitors, workspaces, and top-level windows across X11 and Wayland. Instead of forcing every Xfce component to assume that an X11 display is present, the library gives components a common interface with backend-specific implementations.
Recommended Free Tools
That is an important engineering step, but it is not the same as delivering a finished Wayland session. Much of the Xfce 4.20 work moved X11 assumptions out of libraries and applications or supplied alternative Wayland paths. The component that still owns the deepest window-management assumptions—xfwm4—remained the major exception.
Which Xfce components work on Wayland?
Most Xfce core components and several applications have Wayland support in the project’s roadmap or development documentation. The following table summarizes the broad status while preserving the distinction between a port and full feature parity.
| Area | Examples with Wayland work | Important qualification |
|---|---|---|
| Core libraries and infrastructure | exo, libxfce4ui, libxfce4util, libxfce4windowing, xfconf, Garcon, Tumbler |
Shared abstractions do not provide a compositor or guarantee identical behavior. |
| Desktop and session | xfce4-session, xfdesktop, xfce4-panel, xfce4-settings, xfce4-power-manager |
Several functions depend on compositor protocols that are still incomplete or compositor-specific. |
| File and application utilities | Thunar, xfce4-appfinder, thunar-volman, Mousepad, Catfish, Ristretto, Xfburn |
Individual application features may still be unavailable even when the application launches. |
| Desktop tools | xfce4-terminal, xfce4-notifyd, xfce4-taskmanager, xfce4-mixer, Parole, xfce4-screenshooter, xfmpc |
The roadmap records component-level progress, not a guarantee of X11-equivalent operation. |
| Window manager | xfwm4 remains the X11 component; xfwl4 is the planned Wayland counterpart |
xfwm4 is not a Wayland compositor, and the current xfwl4 work is not usable. |
The roadmap’s component table describes a mixture of Xfce 4.21 or development-tree work, while stable user-facing material discusses Xfce 4.20. A feature present in git or a development branch may not be present in the stable package supplied by a particular distribution. Check the package version and distribution build before treating a roadmap entry as available on an installed system.
Why is the Xfce Wayland transition taking so long?
Xfce’s slower progress is primarily an architectural and compatibility problem, not simply a matter of adding Wayland support to individual applications. Xfce is attempting to preserve a mature X11 desktop while adapting components to a protocol model in which some responsibilities move from applications and window managers to the compositor.
The main constraints are:
xfwm4contains substantial X11-specific window-management behavior.- Wayland does not define one universal replacement for every facility that X11 applications historically used.
- Workspace management, top-level-window lists, screenshots, keyboard handling, power keys, panel embedding, and other desktop functions may require separate protocols or compositor extensions.
- Xfce has historically prioritized modularity, stability, and support for varied or older systems.
- Xfce is maintaining X11 support instead of making a clean, immediate break.
- Source code can be ported while the complete user experience remains unavailable because the compositor and relevant protocols do not yet provide the required behavior.
Xfce developer Alexx Cons describes the difficulty of adapting the existing window manager and the risk of destabilizing established X11 behavior in an explanation of the decision to develop a separate Wayland compositor. The pace is better understood as conservative and dependency-sensitive: the project is building foundations incrementally while protecting the working X11 desktop.
Why is xfwm4 not simply being ported to Wayland?
Xfce decided that adapting xfwm4 to serve both X11 and Wayland would create too much architectural and regression risk. The initial direction involved modifying xfwm4 to support both display systems. Developers later concluded that the window manager was too deeply organized around X11 concepts to refactor safely and cleanly.
Rank #2
- Intel Core i5-10210U (up to 4.2GHz) - 1TB PCIe NVMe + 1TB HDD - 32GB DDR4 SDRAM
- 17.3" HD+ (1600x900) Display, Intel UHD Graphics 620
- Built in HD 720p Webcam with Microphone - Bluetooth Version4.2
- I/O Ports: 2x USB 3.1 (Data Only), 1x USB 2.0, 1x HDMI, 1x Headphone/Microphone Combo Jack
- Linux Mint Cinnamon 64-Bit - 6-Row Keyboard w/ Full Numberpad
Several differences make a direct port difficult:
- Some X11 window-management concepts have no direct Wayland equivalent.
- Wayland compositors own responsibilities that were distributed differently under X11.
- A single dual-backend codebase would force Wayland behavior through abstractions designed for X11.
- Large-scale refactoring could introduce regressions into the mature X11 window manager.
- The original approach would have committed the project to a C and wlroots-oriented design rather than allowing a new Wayland-native architecture.
| Established X11 path | Planned Wayland path |
|---|---|
xfwm4 |
xfwl4 |
| Mature X11 window manager | New Wayland compositor |
| Existing C implementation | Rust implementation using Smithay building blocks |
| Preserves the current X11 workflow | Recreates as much of that workflow as Wayland permits |
The separate-component approach costs Xfce an additional implementation to maintain, but it protects xfwm4 from being reshaped around Wayland’s assumptions. xfwl4 is not a renamed or lightly modified xfwm4; it is intended to be a new compositor with behavior inspired by the Xfce window manager.
What is xfwl4?
xfwl4 is Xfce’s planned native Wayland compositor and the project’s answer to the missing window-management layer. The January 27, 2026 announcement describes a compositor being written from scratch in Rust with Smithay, rather than an extension of the existing C-based xfwm4.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallThe planned goals include:
- Reproducing the functionality and behavior of
xfwm4as closely as Wayland allows. - Reusing existing
xfwm4configuration dialogs where practical. - Reusing Xfconf settings where possible.
- Adapting session startup to Wayland’s compositor-centered model.
- Supporting the
xdg-session-managementprotocol. - Adding XWayland support for applications that still require X11 compatibility.
- Eventually producing development releases for testing.
The announcement expressed an expectation of a development release around mid-2026, but that statement was a development target rather than a verified release date. The controlling status is the current Xfce roadmap, which describes xfwl4 as very early, under heavy development, and not usable. Xfce 4.22 is described as a stabilization stage rather than a promise of complete X11 feature parity, and the roadmap does not identify a known release in which the full Wayland transition will occur. The roadmap also leaves open the possibility that a complete transition may never happen.
The Xfce January 2026 announcement provides the project’s strategic direction, while the roadmap provides the more cautious current usability status. Those statements are compatible: xfwl4 is the chosen direction, but it is not yet a replacement that ordinary users can install and rely on.
What is still incomplete on an Xfce Wayland session?
An experimental session can start while still missing important parts of the established X11 experience. The largest gaps are concentrated around window management, compositor-owned behavior, protocol availability, and older plugin integration.
Window management and workspaces
xfwm4 cannot act as the Wayland compositor. Until xfwl4 becomes usable, Xfce must run inside another compositor such as labwc or Wayfire.
Workspace behavior also depends on suitable Wayland protocol support. The roadmap references the wlr-workspace-unstable-v1 protocol as part of the work needed to expose workspace management. A workspace feature can therefore depend on both the Xfce component and the compositor implementing the same protocol.
Window lists and desktop window information
Functions that appear simple under X11—such as listing every top-level window, displaying window icons on the desktop, or building a window-list menu—need Wayland-specific abstractions. The roadmap references wlr-foreign-toplevel-management-unstable-v1 for this type of information. Support may vary with the compositor and protocol version.
Panel plugins and process isolation
Panel-plugin compatibility is a particularly important limitation for existing Xfce users. Wayland removes the old GTK GtkSocket/GtkPlug mechanism used to embed external panel plugins as separate processes.
The current workaround runs plugins internally in the panel process. That can allow more plugins to appear, but it changes the failure model: a crashing plugin can take down the entire panel instead of failing independently. The roadmap discusses reproducing some of the old arrangement through layer-shell and D-Bus, but that is not equivalent to native external embedding. A working Wayland panel therefore does not imply that every existing Xfce panel plugin is safe or compatible.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsRank #3
- [ULTRA-RUGGED DESIGN] MIL-STD-810G and IP65 certified. Built to survive 6-foot drops, heavy rain, and extreme vibrations. Features a magnesium alloy chassis with an integrated carry handle for maximum portability
- [4G LTE - WORK ANYWHERE] Integrated 4G LTE Multi-Carrier Mobile Broadband. Stay connected to the internet in remote areas or on the road without relying on Wi-Fi or phone hotspots. True mobile freedom for field professionals
- [1200-NIT SUNLIGHT READABLE] 13.1" XGA Touchscreen with CircuLumin technology. At 1200 nits, it is nearly 4x brighter than a standard laptop, ensuring perfect visibility under direct, intense sunlight
- [LINUX UBUNTU PRE-INSTALLED] Fast, secure, and bloatware-free. Optimized for developers, network engineers, and diagnostic software that thrives in a stable, open-source environment
- [LEGACY SERIAL PORT] Features a native RS-232 Serial Port, HDMI, and USB 3.0. Essential for connecting directly to industrial machinery, CNCs, and automotive diagnostic tools without unreliable adapter
Settings and input controls
Display settings have received a Wayland port, but keyboard, mouse, and some workspace controls remain partly compositor-specific. Wayland does not provide one universal desktop-environment protocol for every setting that Xfce’s settings manager historically controlled through X11.
This means that the Xfce settings manager may launch successfully without being able to configure every behavior of the compositor hosting the session. Users should not interpret a visible settings panel as proof of complete settings parity.
Power management and hardware keys
Basic inactivity monitoring and display power management have been restored through Wayland protocols. Keyboard-driven functions such as brightness keys and suspend keys remain compositor responsibilities and are not fully restored by the current Xfce components.
Users who depend on laptop hotkeys should treat this as a practical test criterion rather than assuming that a successful login proves that power management works. Behavior can also vary with the compositor, hardware, driver, and distribution configuration.
Free tools Windows power users keep installed
One-click scans. No signup required.
Screenshots
The Xfce Wayland documentation describes full-screen screenshots through a wlroots screencopy protocol, while rectangle selection and active-window screenshots were unavailable in the described state. The roadmap also discusses newer image-capture protocols and the possibility that older wlroots screencopy support may eventually be dropped.
Screenshot behavior is therefore version- and compositor-dependent. “Screenshots work” is too broad; full-screen capture may work while region selection or active-window capture does not.
Other unavailable or partial areas
The project’s tour and roadmap identify limitations involving Xfdashboard, xfce4-screensaver, xfce4-windowck-plugin, xfce4-xkb-plugin, and xfce4-embed-plugin. Some task-manager features, Parole features, status-tray behavior, keyboard shortcuts, and window-identification operations are also incomplete or dependent on the compositor.
| Requirement | Current practical status | What to verify |
|---|---|---|
| Basic Xfce applications | Many have Wayland code paths and can run in an experimental session. | Check the installed Xfce version and the application’s current feature status. |
| Native Xfce window manager | Not available on Wayland; xfwm4 remains X11-only. |
Which compositor is actually hosting the session? |
| Panel plugins | Incomplete compatibility and reduced process isolation. | Test every plugin; a plugin crash may affect the panel. |
| Workspaces and window lists | Protocol- and compositor-dependent. | Test workspace switching, window lists, task buttons, and desktop window information. |
| Power and keyboard controls | Basic power behavior exists; several key-driven controls remain incomplete. | Test brightness, suspend, keyboard shortcuts, and mouse settings. |
| Screenshots | Full-screen capture may work through wlroots protocols; region and active-window capture may not. | Test the exact capture modes your workflow requires. |
| Legacy X11 applications | Ported Xfce components do not require XWayland, but legacy applications may. | For a future native compositor, confirm XWayland availability and configuration. |
Does Xfce Wayland support require XWayland?
Ported Xfce components do not require XWayland merely to run under Wayland. XWayland is relevant when an application still speaks X11 or depends on X11-specific behavior.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Those are separate claims. Xfce’s Wayland-capable applications can use Wayland directly, while the planned xfwl4 roadmap includes XWayland support to preserve compatibility with legacy X11 applications. Saying that XWayland is unnecessary for all Xfce Wayland use would therefore be inaccurate.
How can you test Xfce on Wayland today?
The documented testing route is an experimental Xfce session launched inside a wlroots-based compositor, preferably labwc or alternatively Wayfire. The Xfce roadmap says a wlroots compositor is close to a prerequisite for exposing most of the Wayland features that Xfce has ported.
Rank #4
- THE POWER TO STAY PRODUCTIVE – Looking to make your everyday work and home life more manageable without breaking the bank? The Lenovo V15 Gen 4 offers long-term reliability with top-of-the-line features to make you your most productive self.
- CRUSH YOUR TO-DO LIST – The AMD Ryzen CPU pairs quiet performance and enhanced operating power to crush your high-demand workday. It optimizes performance and allows for seamless multitasking.
- TRUE-TO-LIFE VISUALS – The 15.6” FHD IPS display is anti-glare with 300 nits brightness to see your best outside or in. Its 88% screen-to-body ratio makes viewing detailed applications like spreadsheets a breeze.
- SEAMLESS COLLABORATION – Lenovo Smart Appearance enhances your camera effects to protect your privacy and to make you the focus of every video conference. Intelligent noise cancelation minimizes distraction and Dolby Audio provides an elegantly sonorous experience.
- BUILT TO WITHSTAND – Built for military-grade toughness, the V15 Gen 4 is tested to withstand harsh temperatures, pressure, humidity, vibrations and more. Keep your work safe from the board room to your living room and everywhere in between.
Prerequisites
- A sufficiently recent Xfce environment with the relevant Wayland support.
- A Wayland compositor, preferably labwc or Wayfire.
- A working display manager or access to a text console (TTY).
- An X11 session that remains installed and selectable.
- Enough troubleshooting experience to recover from a session that fails to start or behaves incorrectly.
Because distribution packages differ, do not assume that a stable Xfce package includes every feature listed in the development roadmap. Record the Xfce version, compositor version, distribution, GPU, graphics driver, and panel plugins before testing.
Start with labwc
From a TTY, the documented command is:
startxfce4 --waylandThe documented behavior is that startxfce4 --wayland launches xfce4-session through labwc.
Start with Wayfire
For Wayfire, use:
startxfce4 --wayland wayfireWayfire does not provide labwc’s --startup option. The roadmap therefore instructs users to add a session autostart entry to ~/.config/wayfire.ini:
[autostart]
session = xfce4-sessionOther compositors may need different session-startup adaptations. A compositor that can launch a Wayland application is not automatically a compositor that supplies every protocol expected by the Xfce session.
Use a display manager
Xfce provides an xfce-wayland.desktop session file for display managers such as LightDM. The compositor command in that session file may need to be changed when the system uses a compositor other than the default one.
Display-manager configuration is distribution-dependent. Keep the established X11 session available before changing the default session or editing display-manager files.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Recover if the graphical session fails
- Keep an X11 session installed and selectable in the display manager.
- Use a separate user account for initial testing when possible.
- Switch to a TTY, commonly with Ctrl+Alt+F3 through F6, if the graphical session becomes unusable.
- End the failed test session from the TTY and log back into the X11 session.
- Do not replace working X11 configuration files until the Wayland session is stable.
- When reporting a bug, include the compositor, Xfce version, GPU, driver, distribution, and plugin set.
The commands and session-file details come from the official Xfce roadmap. Retaining an X11 fallback is a practical safety measure because the documented Wayland path remains experimental.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Should you run Xfce on Wayland now?
Run Xfce on Wayland now if you want to test development work and can tolerate missing features; stay with X11 if you need a dependable, complete Xfce workstation. The decision depends more on workflow and recovery options than on whether a few applications launch successfully.
| Your situation | Recommended choice | Reason |
|---|---|---|
| You want to help test Xfce development. | Try Wayland experimentally. | Testing exposes compositor, protocol, plugin, and session-startup issues that developers need to find. |
| You have an X11 fallback and do not depend on many legacy panel plugins. | Wayland testing is reasonable. | A limited workflow can make the current experimental session manageable. |
You need a production workstation with mature xfwm4 behavior. |
Stay with X11. | The native Wayland compositor is not usable and the external-compositor session lacks parity. |
| You rely on panel-plugin isolation, keyboard power controls, complete workspaces, or full window lists. | Stay with X11 for now. | These are known incomplete or compositor-dependent areas. |
| You require a polished integrated Wayland desktop today. | Evaluate a more mature Wayland desktop. | Xfce’s current path is experimental and does not yet provide an integrated native compositor. |
| You have a sensitive GPU or driver setup. | Test cautiously with an X11 fallback. | Results depend on the GPU, driver, compositor, distribution, and date; Xfce’s roadmap specifically notes problems with proprietary NVIDIA support in its testing context. |
Users who specifically value Xfce’s workflow, modularity, low-overhead design, or familiar tools may reasonably wait rather than switch permanently. Users who want a finished Wayland experience should compare desktops on the features they actually need—such as scaling, capture, gestures, global shortcuts, settings integration, and compositor behavior—rather than assuming that one desktop is universally superior.
Why is Xfce choosing a separate compositor?
The separate xfwl4 strategy trades short-term speed for protection of the established X11 desktop and a cleaner Wayland architecture.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Best Value
- Powerful Linux Laptop: This IdeaPad Slim 3 Laptop comes pre-installed with Ubuntu Linux, offering fast performance, robust security, and a clean, user-friendly experience. Enjoy full customization, seamless hardware compatibility, and access to thousands of open-source apps. Whether you're working, creating, or coding, it's built to keep up with everything you do.
- A Multitasking Master: The latest AMD Ryzen 7 5825U processor (up to 4.5 GHz) delivers powerful performance with 8 cores and 16 threads for smooth multitasking. Integrated AMD Radeon Graphics provide crisp visuals for streaming, browsing, photo editing, and casual gaming. With smart machine intelligence, it adapts to your needs for a fast, responsive experience.
- 15.6" Full HD Display: The IdeaPad Slim 3 boasts an 88% screen-to-body ratio for a floating, edge-to-edge visual experience. TÜV Low Blue Light certification reduces eye strain, making it perfect for long work or study sessions.
- Military-Grade Durability: The smart IdeaPad Slim 3 combines portability and durability, letting you work, study, and play on the go. With a profile 10% slimmer than the previous generation, it's lightweight yet military-grade rugged, ready for anything, anywhere.
- Versatile Connectivity: Enjoy the security of a built-in webcam with a privacy shutter. Connect effortlessly with multiple ports: 2x USB A, 1x USB C, 1x HDMI, 1x SD Card Reader, 1x Headphone/Microphone combo. Bundle comes with Stylus Pen, 256GB Portable SSD and 5-in-1 Docking Station.
Benefits
- Wayland development is less likely to destabilize mature
xfwm4behavior. xfwl4can use a Wayland-native design instead of forcing Wayland through X11 abstractions.- Rust and Smithay provide a different implementation foundation for the compositor.
- The project can make compositor-specific design decisions without constraining the X11 codebase.
- X11 users can continue using
xfwm4while Wayland work develops independently.
Costs
- Xfce must maintain two window-management implementations.
- Configuration parity must be recreated deliberately rather than inherited automatically.
- Behavior and bugs may diverge between X11 and Wayland.
xfwl4must reproduce years of accumulatedxfwm4behavior.- A new language and toolkit increase the project’s development and maintenance surface.
The result is slower than replacing the entire desktop with a new Wayland-first design, but it is consistent with Xfce’s long-term emphasis on modularity, stability, and continued X11 compatibility.
What does the Xfce roadmap say about the finish line?
The roadmap does not promise a specific release for complete Wayland parity. Xfce 4.22 is described as focusing on stabilization rather than complete X11 feature parity, and the release in which Xfce might target a complete Wayland transition is not yet known. The roadmap also acknowledges that a complete transition may not happen at all.
That uncertainty should not be mistaken for inactivity. Xfce 4.20 established the application and library foundation, development work has expanded Wayland support across many components, and xfwl4 gives the project a defined compositor strategy. The uncertainty concerns the scale, compatibility burden, protocol gaps, and final usability of the transition—not whether the project has begun the work.
Xfce also intends to retain X11 compatibility for the foreseeable future. The project is not following a forced schedule in which the complete X11 session disappears as soon as Wayland development begins.
Bottom line: is Xfce moving to Wayland?
Yes, Xfce is genuinely moving toward Wayland, but Xfce does not yet offer a production-ready native Wayland desktop. Xfce 4.20 made most core components Wayland-aware, and an external compositor can host an experimental session. The decisive limitation is that xfwm4 remains X11-only, while the replacement compositor xfwl4 is still early and unusable according to the current roadmap.
The most accurate description is a multi-stage migration: port the libraries and applications, provide a workable compositor environment, build an Xfce-native compositor, close protocol and integration gaps, and then approach feature parity. Until those stages are complete, X11 remains the complete and dependable Xfce experience, while Wayland is best treated as a deliberate experiment for advanced users.
Frequently Asked Questions
Does Xfce support Wayland now?
Xfce supports Wayland experimentally at the component and session-hosting levels, but Xfce does not yet provide a complete native Wayland desktop. Most core components have Wayland work, while xfwm4 remains X11-only and users must currently rely on an external compositor such as labwc or Wayfire.
Is xfwm4 being replaced by xfwl4?
xfwl4 is intended to be Xfce’s Wayland counterpart to xfwm4, while xfwm4 continues to serve X11 users. The two components are being developed separately; xfwl4 is a new Rust and Smithay compositor rather than a direct Wayland port of xfwm4.
Free tools Windows power users keep installed
One-click scans. No signup required.
Can I use Xfce on Wayland as my daily desktop?
You can test Xfce on Wayland, but the current session is recommended mainly for advanced users rather than production use. Missing or compositor-dependent functionality includes panel-plugin isolation, some workspace and window-list behavior, keyboard power controls, screenshot modes, status-tray features, and support for particular plugins.
How do I start the experimental Xfce Wayland session?
With labwc, the documented command is startxfce4 --wayland. With Wayfire, use startxfce4 --wayland wayfire and add [autostart] to
session = xfce4-session~/.config/wayfire.ini; retain an X11 session as a fallback.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
