cdown/clipmenu
FreeClipboard management using dmenu
FreeFree tier
About cdown/clipmenu
Clipmenu is a lightweight clipboard manager for X11 that passively monitors clipboard selections (PRIMARY, CLIPBOARD, SECONDARY) using XFixes (no polling). It stores clipboard history and allows users to quickly select and paste from previous clips via a dmenu, rofi, or similar launcher. Features include configurable max clips (default 1000), deduplication of repeated clips, ability to ignore clipboard changes from specified applications (e.g., password managers), and tools for interactively deleting clips (clipdel, clipdelmenu) and toggling monitoring (clipctl). It is extensible via configuration file and can pass custom arguments to the launcher. Installable via official packages (Arch, Nix) or manual build with Makefile.
Key Features
Passively monitors X11 clipboard selections (PRIMARY, CLIPBOARD, SECONDARY) using XFixes – no polling
Configurable maximum number of stored clips (default 1000)
Deduplicates repeated clips, keeping only the newest
Ability to ignore clipboard changes from specified applications (e.g., password managers)
Clipctl utility to enable/disable clipboard monitoring at runtime
Clipdel and clipdelmenu for deleting individual clips or interactive deletion
Supports any dmenu-compliant launcher: dmenu (default), fzf, rofi
Transparently passes all arguments to the launcher for customisation
Systemd user service included for easy daemon management
Customisation via configuration file (clipmenu.conf) and environment variables
Pros & Cons
Pros
- Efficient passive monitoring using XFixes instead of polling, saving CPU
- Highly configurable via configuration file and environment variables
- Supports multiple launchers (dmenu, rofi, fzf) for flexible integration
- Includes dedicated tools (clipdel, clipdelmenu, clipctl) for fine-grained management
- Simple and lightweight – no heavy dependencies beyond dmenu/rofi and X
- Well-documented with man pages and config examples
- Actively maintained with a clean codebase (C) and MIT license
Cons
- X11 only – no native Wayland support (may work via XWayland but not ideal)
- Relies on external launcher (dmenu, rofi, etc.) for selection; no built-in GUI
- Clipboard history is stored as plaintext files; no encryption at rest
- Not a full-featured clipboard manager with advanced features like image support or cloud sync
Best For
Power users who frequently copy/paste and need quick access to clipboard historyDesktop workflows with dmenu, rofi, or similar launchers as primary interaction methodIntegrating clipboard management with minimal resource usage on X11 systemsAvoiding accidental storage of sensitive data by ignoring specific applications (e.g., password managers)Environment where a lightweight, open-source clipboard manager is preferred over GUI-heavy alternatives
FAQ
How does clipmenu work?
clipmenud passively monitors X11 clipboard selections (PRIMARY, CLIPBOARD, SECONDARY) for changes using XFixes without polling. Changes are written to storage with a hash filename. clipmenu reads the index and uses dmenu (or a configured launcher) to let the user select a clip, which is then put onto the PRIMARY and CLIPBOARD X selections.
Can I use a launcher other than dmenu?
Yes. Set the CM_LAUNCHER environment variable or configuration option to any dmenu-compliant launcher such as rofi or fzf. All arguments passed to clipmenu are transparently dispatched to that launcher.
How do I disable clipboard monitoring temporarily?
Use the clipctl utility: clipctl disable stops monitoring and clipctl enable resumes it. This is useful when you don't want to store sensitive data.
Can I prevent certain applications from being stored?
Yes. The configuration file (clipmenu.conf) allows you to specify applications to ignore, such as password managers, so their clipboard changes are not recorded.