Still a pre-release, and still for trying rather than relying on. It has been used daily on one machine by one person. This one is small and honest about it: two things you can see, and no change to how the gesture behaves.
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 online as well as shipping with the program, and there is an architecture reference if you want to see how it works.
Which download
| File | What is in it | Needs |
|---|---|---|
PasteJump-2026.1.0.223-win-x64.zip |
One PasteJump.exe. Portable — its data folder appears beside it, so a USB stick carries your history with it. |
Nothing |
PasteJump-2026.1.0.223-win-x64-unpacked.zip |
The same build with the runtime already unpacked. Starts about four times faster warm (~0.3 s against ~1.3 s). | Nothing |
PasteJump-2026.1.0.223-win-x64-net10.zip |
PasteJump’s own files only, 15 of them, 3.2 MB. | .NET 10 Desktop Runtime |
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.
What changed since 2026.1-pre4
- The manual reads in a column instead of across the whole window. On a wide monitor the published help pages ran a line of text the full width of the browser, which is hard to read and looked broken beside the rest of the site; they now sit in the same centred 1000px column the front page always used. This applies to the manual on the website and to the copy inside the program.
- The author’s name in the About box links to lokeshgovindu.github.io rather than to a GitHub profile.
Nothing else in the program moved. 2026.1-pre4 was a mechanical release with no program changes at all, so if you skipped it, the 2026.1-pre3 notes are still the ones that describe 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: