
Copy a tracking number in the morning, a code snippet at lunch, a long address in the afternoon — and by evening, Windows can't show you any of them. The built-in clipboard history behind Win+V holds only the last 25 items, each capped at 4 MB, and everything unpinned vanishes the moment you reboot. For anyone who treats the clipboard as a scratchpad, that's not a history; it's a memory with amnesia scheduled.
So a developer on the Chinese forum LINUX DO did what developers there often do: built exactly the tool he wanted. The result is clipkeep, an open-source Windows clipboard manager shipped as one portable exe. It keeps unlimited history, adds real search, favorites, and groups, lets you edit long entries in place — and can beam a snippet to another PC on the same LAN over an encrypted direct connection. MIT licensed, built with Rust, Tauri 2, and Vue 3, and posted to GitHub in mid-October 2026.
Everything about clipkeep starts from three hard limits in Windows' own clipboard history. Microsoft's support documentation confirms them plainly: the history holds at most 25 entries (older ones drop off unless pinned), each item is capped at 4 MB, and a restart wipes everything except pinned items. It's a rolling buffer, not an archive.
clipkeep inverts every one of those limits. Instead of counting entries, it caps by total capacity — 500 MB by default, adjustable, or set to unlimited. Records survive reboots. And instead of a flat chronological list, you get real-time search across everything you ever copied. The forum discussion that introduced it reads like a checklist of paper cuts: the author found Win+V's count limit annoying and missed search; he tried Ditto and CopyQ but didn't click with their interfaces; he liked the look of EcoPaste and PasteBar but found them sluggish. Nothing fit, so he wrote his own. That arc — picky about UI, unwilling to install a suite for a simple job — will be familiar to anyone who lives in their clipboard.
The design brief, straight from the project's README, is admirable in its specificity: download one file, double-click, keep pressing Win+V. Nothing to learn, no new muscle memory. Under the hood it does a lot more:
Two honest caveats come straight from the project's own FAQ: data lives in a local SQLite database that isn't encrypted yet, so don't treat it as a vault for secrets; and the app runs with administrator rights (one UAC prompt on manual launch) because that's the only way Windows lets a program inject paste keystrokes into admin windows and read clipboard changes made inside them. Both are reasonable tradeoffs for the feature set — and both are disclosed upfront rather than discovered later.
Most clipboard managers stop at history. clipkeep's signature move is LAN transfer: pair two PCs with a one-time pairing code, then right-click any text entry and send it to the other machine. The connection is direct between the two computers — no server, no account — and the payload is encrypted with ChaCha20-Poly1305. The receiver gets it as a history entry, not as a hijack of their current clipboard.
The pairing flow is deliberately low-friction: the receiving side enables receiving and copies a pairing code; the sender pastes it under "add device"; from then on it's a context-menu item. Traffic runs on TCP port 45788, so a corporate firewall might need an allow rule. It's the kind of feature you'd build exactly when you have two machines on a desk — a dev PC and a test laptop, or a desktop and a living-room HTPC — and you're tired of emailing yourself snippets.
The author's README includes its own comparison table with Ditto, CopyQ, EcoPaste, and PasteBar. Summarized (per the author's table, not independently re-tested):
| clipkeep | Ditto | CopyQ | EcoPaste | PasteBar | |
|---|---|---|---|---|---|
| Stack | Rust + Tauri 2 + Vue 3 | C++ / MFC | C++ / Qt | Rust + Tauri 2 + React | Rust + Tauri + React |
| Platform | Windows only | Windows | Win / macOS / Linux | Win / macOS / Linux | Win / macOS |
| Distribution | Installer or single exe | Installer or portable | Installer or portable | Installer | Installer |
| LAN transfer | Built in, encrypted direct | Manual IP config | — | — | — |
| Paste into admin windows | Works by default | Works, UAC as needed | Requires admin run | Setting toggle | Requires admin run |
| License | MIT | GPL-3.0 | GPL-3.0 | Apache-2.0 | CC BY-NC (limited commercial exception) |
Three takeaways for English readers. First, the LAN transfer is genuinely the differentiator — Ditto can approximate it with manual configuration; the others don't try. Second, if you need cross-platform or rich-text and file entries, CopyQ or EcoPaste still win — clipkeep is Windows-only and records text and images only. Third, the license row matters more than it looks: the permissive MIT license plus a Tauri-based modern stack makes clipkeep the easiest of the bunch to fork and hack on.
Setup takes about a minute:
clipkeep_x.y.z_x64-setup.exe (installs to your user folder, no admin needed, auto-start on by default) or clipkeep_x.y.z_x64.exe (drop anywhere and run, toggle auto-start in settings yourself).History and settings live under %APPDATA%\com.clipkeep.clipboard\ — upgrades and uninstalls leave it alone, so your archive survives version bumps; delete the folder manually for a full wipe. One practical note from the project's changelog: v0.2.0 fixed recording of images from screenshot tools like PixPin that only expose bitmap formats, a reminder that clipboard formats are a small minefield of their own.
clipkeep is a textbook example of a recurring pattern in the Chinese developer community: a sharp, single-purpose utility, built to scratch one person's itch, shipped as a portable executable with zero ceremony. The forum it surfaced on is full of them — the same crowd that trades remote desktop stacks and hunts budget VPS deals treats small native tools as a hobby as much as a utility. The stack choice is part of the pattern too: Rust plus Tauri has become the default answer when a Chinese indie dev wants a modern GUI without shipping an Electron-sized bundle.
Is it production-ready? As of writing it's a fresh project — a few dozen stars, a handful of commits, a young maintainer responding to feedback in the forum thread that launched it. That's exactly the stage where trying it is most fun: the feature set is coherent, the rough edges are documented in the FAQ, and your bug reports actually get read. If your clipboard is your second brain, clipkeep is a worth-a-download experiment in giving that brain a longer memory.