Which Clipboard Managers Work on Linux (for Dual-Booters)?

Edge-Drop is Windows-only. There is no Linux build planned, and pretending otherwise sets the wrong expectation. Dual-boot users who run Windows for some workflows and Linux for others need a Linux clipboard manager that holds its own on the Linux side, and they need to know how it maps to what they use on Windows. This guide covers the four Linux clipboard managers worth knowing — CopyQ, GPaste, Klipper, and Clipman — plus the Wayland command-line tools that sit underneath them. For related reading, see Windows equivalents if you used Paste, Maccy, or Raycast, Android clipboard history vs desktop history, keeping clips on the device, and why some clipboard apps will never sync.

The Linux clipboard is two clipboards

The first thing to know is that Linux has two clipboards, not one. The X11 selection model has:

• PRIMARY — selected text is immediately available for middle-click paste.
• CLIPBOARD — explicit Ctrl+C / Ctrl+V copies and pastes.

Wayland collapses these into a single clipboard per seat, but most apps still treat them separately. A Linux clipboard manager has to handle both, or it will miss half of what the user copies. This is different from Windows, where there is one clipboard and one set of formats.

The practical consequence: on Linux, you might select text in a terminal, expect it in your clipboard manager, and not find it, because the manager only watches CLIPBOARD, not PRIMARY. The fix is configuration, not a different tool.

CopyQ: the cross-platform workhorse

CopyQ is the same tool Windows users know. It is GPL-3.0, Qt-based, and runs on Linux, macOS, and Windows. On Linux it integrates with both X11 and Wayland (with caveats), and its scripting surface is the same everywhere.

• Best-fit: developers and power users who want scripted transformations and a single tool across their dual-boot setup.
• Strength on Linux: mature, cross-platform, full-featured.
• Weakness on Linux: Qt on a GNOME desktop is visually out of place; Wayland support has historically required extra setup.
• Windows counterpart: itself. CopyQ is the same tool on both sides.

For dual-boot users who want one clipboard manager everywhere, CopyQ is the closest thing to a universal answer. The cost is configuration complexity, which is the same cost on Windows.

GPaste: the GNOME native

GPaste is a clipboard manager designed for GNOME. It is GPL-3.0, written in C with Vala bindings, and ships as a GNOME Shell extension plus a daemon. It is the default-feeling choice on a stock GNOME install.

• Best-fit: GNOME users who want something that fits the desktop.
• Strength on Linux: native GNOME integration, keyboard shortcut support, clean UI.
• Weakness on Linux: GNOME-only; does not feel right on KDE or XFCE.
• Windows counterpart: none directly. The closest is Win+V for the basic list, or Ditto for more history.

GPaste is the right answer for a GNOME user who wants the clipboard to feel like part of the desktop. For more on GNOME Shell extensions, see the GNOME Extensions documentation linked in Sources.

Klipper: the KDE native

Klipper is the clipboard manager built into KDE Plasma. It is GPL-2.0 (or later, depending on the version), written in C++ with Qt, and ships with every KDE Plasma install. There is nothing to install; it is there.

• Best-fit: KDE Plasma users.
• Strength on Linux: zero install, deep Plasma integration, configurable actions on copied items.
• Weakness on Linux: KDE-only; the configuration UI is dense.
• Windows counterpart: none directly. The closest is Ditto, which has similar density.

Klipper is the right answer for a KDE user. Its strength is that it is already there: no extra install, no extra daemon. The configuration UI takes an evening to learn, and the actions system lets you run scripts on copied items, which is closer to CopyQ's scripting than most users realise.

Clipman: the XFCE native

Clipman is the clipboard manager for XFCE. It is GPL-2.0, written in C with GTK, and ships as a panel plugin. It is lighter than the others and fits the XFCE aesthetic.

• Best-fit: XFCE users on older hardware.
• Strength on Linux: light, simple, fits the desktop.
• Weakness on Linux: XFCE-only; fewer features than Klipper or CopyQ.
• Windows counterpart: Win+V is the closest in spirit — simple, light, gets out of the way.

Clipman is the right answer for an XFCE user who wants something that does not get in the way. For low-RAM Linux setups, it is hard to beat.

The Wayland command-line layer

Underneath the GUI clipboard managers, Linux has two command-line tools for clipboard access on Wayland:

• wl-clipboard — wl-copy and wl-paste. The standard Wayland clipboard utilities.
• xclip / xsel — the X11 equivalents, still widely used.

A clipboard manager that works on Wayland has to talk to wl-copy / wl-paste (or use the libwayland clipboard protocol directly). A manager that only knows X11 will not work on a pure Wayland session. This is a real compatibility issue and is worth checking before installing a manager on a Wayland desktop.

The official wl-clipboard documentation is linked in Sources. For users who script their clipboard from the terminal, wl-copy and wl-paste are the building blocks.

A summary table for dual-boot users

For dual-boot users, the only cross-platform option is CopyQ. If you do not need cross-platform, pick the manager that matches your Linux desktop environment.

How this maps to the Windows side

Dual-boot users typically want one of two patterns:

1. Same tool on both sides. Install CopyQ on Linux and Windows. Sync the config file via a cloud drive or git. The history does not sync, but the configuration does. This is the simplest mental model.
2. Best-of-breed on each side. Edge-Drop on Windows (for the hover shelf), Klipper or GPaste on Linux (for native integration). No shared config; no shared history. This is more work but gives a better experience on each OS.

Edge-Drop is honest about being Windows-only. It does not run on Linux, does not have a Linux build planned, and does not pretend otherwise. For Linux, the answer is one of the tools above. For Windows, the answer is in the open-source clipboard landscape in 2026.

The WSL middle-ground

Many dual-boot users do not actually dual-boot; they run Windows with WSL2 for Linux workflows. WSL2 is a Linux VM, not a separate boot, which means the clipboard question changes shape. Windows owns the clipboard; WSL2 talks to it through clip.exe (Windows-side) and powershell.exe Get-Clipboard (Linux-side, via interop). A native Linux clipboard manager running inside WSL2 does not see the Windows clipboard directly — it sees the WSL2 VM's clipboard, which is bridged to Windows through the interop layer.

The practical pattern is: use the Windows clipboard manager (Win+V, Ditto, Edge-Drop) as the primary, and treat WSL2 as a terminal that copies into the Windows clipboard. For terminal-only workflows, wl-copy and xclip are not relevant inside WSL2; clip.exe and powershell.exe Get-Clipboard are the right tools. For users who script their clipboard from a Linux shell, aliasing pbcopy and pbpaste to those interop commands gives the macOS-style clipboard command pattern on Windows.

The honest summary: WSL2 is not Linux for clipboard purposes. It is Windows with a Linux userspace, and the clipboard is owned by Windows. For a real Linux clipboard experience, dual-boot or run a Linux desktop. For a Linux shell experience with the Windows clipboard underneath, WSL2 is fine.

A note on cross-OS clipboard sync

Dual-boot users often want clipboard content to follow them across the reboot. The options:

• KDE Connect — syncs clipboard between a KDE Plasma desktop and an Android phone, and between two KDE desktops. Does not sync to Windows directly.
• Phone Link — Microsoft's tool, syncs Android phone clipboard to Windows. Does not sync to Linux.
• Manual paste into a notes file — the honest fallback for cross-OS clipboard content that no tool syncs.

There is no first-party tool that syncs clipboard between a Linux desktop and a Windows desktop over a local network. Third-party options exist but carry their own privacy trade-offs. For most dual-boot users, the realistic answer is "copy again on the other side." For more, see why some clipboard apps will never sync.

That limit is unpacked in Chrome Extensions Are Not a Desktop Clipboard.

Related reading

• Android Clipboard History vs Desktop History
• Chrome Extensions Are Not a Desktop Clipboard
• What Local-First Software Means for Clipboard Apps
• How to Enable Clipboard History in Windows 11

Sources

• CopyQ — GitHub README — official CopyQ source, license, and platform support including Linux
• GPaste — GitHub project — official GPaste source and GNOME Shell extension documentation
• KDE Plasma — Klipper documentation — official Klipper documentation in the KDE Plasma manual
• XFCE — Clipman documentation — official Clipman documentation from the XFCE project
• wl-clipboard — GitHub README — official Wayland clipboard command-line utilities, the building block for Wayland clipboard managers

Copy. Stack. Drop.

Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.

Download for Windows Get from Microsoft Store

How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge-Drop vs Win+V · Support