Still a pre-release, and still for trying rather than relying on. It has been used daily on one machine by one person. The headline for this one: Check for Updates actually works now — it never could before, and this build is the first that can tell you a newer one exists.

Hold Ctrl, tap V to walk back through what you have copied, release to paste. The website shows it in a minute; the manual is readable here on GitHub as well as shipping with 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.

Check for Updates works, and there is a channel to choose

It has never once been able to find a release. Two faults, either fatal on its own, both fixed here:

• It asked GitHub for the latest release, an endpoint that excludes pre-releases by definition — and every PasteJump release is a pre-release, so GitHub answered 404. The dialog then said “No releases have been published yet”, which was true the day it was written and false from the first release onwards.
• Even given a release, it compared the tag. 2026.1-pre5 reads as 2026.1.0.0, which is never newer than a running 2026.1.0.223, so the comparison could not fire even when the fetch worked. The version now comes from the archive’s own name, which carries the build number.

Update Channel, under Settings, System, decides what you are offered:

Drafts are never offered on any channel. Nothing is ever downloaded or installed for you — the check reports, and opens the release page if you want it.

Also new

• About has a Credits button. It opens the credits and the third-party notices: what PasteJump is made of, and the licences that travel with it. Clipjump is deliberately not in that list, because none of it is in this program — it is in the credits as an acknowledgement instead, which is where a debt of ideas belongs.
• The manual reads in a column instead of running the full width of the browser, which is hard to read on a wide monitor. It now sits in the same centred column the front page always used, both on the website and in the copy inside the program.
• The author’s name in About links to lokeshgovindu.github.io rather than to a GitHub profile.

Nothing about the gesture itself changed. If you skipped straight here, the 2026.1-pre3 notes are the ones describing the current behaviour — a run of real fixes found by using it.

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 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. The SHA256 of each file: