The first stable release. Six pre-releases, a run of real bugs found by using it daily, and every one of them fixed and covered by a test. This is the same program 2026.1-pre6 was, with the pre-release label taken off.

Hold Ctrl, tap V to walk back through what you have copied, release to paste. No window, no mouse, no hands leaving the keyboard. That gesture is the whole of the idea; everything else exists to support it.

The website shows it in a minute. The manual is readable on GitHub as well as shipping inside the program, and there is an architecture reference if you want to see how it works.

Which download

Take the first unless you have a reason not to. Windows 10 or 11, 64-bit. Nothing is installed and nothing is written outside the folder you unzip into, unless you move the data location yourself. The same files are mirrored, byte for byte, to SourceForge.

What PasteJump does

• The gesture. Ctrl+V steps back through the clip stack with a small overlay showing what you are about to paste. Release Ctrl and it pastes. Nothing to learn beyond the chord you already use.
• Search without leaving the keyboard. Press F mid-gesture and type; the stack narrows as you go. No letter is an action while you are typing a query.
• Every clipboard format is kept, so a paste into Word arrives as it left Word, and an Excel range pastes back into Excel with its formatting intact — 24 of 25 formats byte-identical on a real Excel round trip, the one difference being a locale field Windows regenerates itself.
• Pin what you reach for, filter the stack by kind, mark several clips and paste them joined.
• A history window with full-text search over everything you have copied, image previews that zoom and pan, and per-row actions.
• Nineteen themes, or write your own — a theme is a small JSON file of named colours, and a three-line one that recolours the accent is legal and complete.
• Portable, and yours. One executable, no installer, no account, no network except when you ask it to check for updates.

Since 2026.1-pre6

Nothing in the program. This release exists to stop being a pre-release: with a stable release published, the Stable update channel — the default — finally has something to find, so an existing copy will now be told when a new version is out.

Everything else in this release is described in the pre-release notes: pre6 brought the working update check, update channels and the Credits window; pre3 carried the bulk of the bug fixes.

Honest about what is not verified

Everything below is tested by 1130 automated tests, a UI harness that renders every window in both themes, and daily use on one machine. Three things rest on that daily use rather than on a measurement, and are worth knowing:

• Multi-monitor mixed-DPI placement of the overlay has not been measured, because both monitors on the development machine report the same scaling.
• Focus retention across a wide range of applications is verified by use, not by instrumentation.
• Shift+Insert, the documented way to coexist with another clipboard manager, is a different chord and a few applications bind it elsewhere.

Known limitation worth reading if you are on a managed machine

On some corporate machines, endpoint data-loss-prevention policy routes one application’s keyboard input — a browser, usually — through a component with more privilege than PasteJump has. Windows then hides that input from PasteJump’s keyboard hook by design, and Ctrl+V does nothing in that one application while working everywhere else. Copying keeps working, which makes it look like a PasteJump fault.

It is not one, and no version of this program can work around it: a low-level hook, raw input, a registered hotkey and injected keystrokes were all measured equally blind there, and three unrelated programs — including the original Clipjump — fail identically in the same application. Ticking Always Run as Administrator restores it. Failing that, the clipboard history window is unaffected — press Copy there and paste with your own Ctrl+V. See Troubleshooting.

Windows will warn you

This build is not signed with a paid certificate, so SmartScreen will report an unknown publisher on first run — choose More info, then Run anyway. That is a deliberate, settled decision rather than an oversight: a signature that fails to validate looks worse than none at all. The SHA256 of each file: