If you already have 2026.1-pre3, you do not need this. Not one line of the program has changed since it: src/ is untouched, so this is the same PasteJump with a different version stamp on it. Everything that moved since yesterday was the repository around it — an automated release job, the documentation, and a measurement.

It exists to prove that release job works. 2026.1-pre3 and everything before it were packaged by hand on one machine; from here a tag builds the packages on a clean runner, tests them, hashes them and attaches them. That is worth exercising on a release where nothing is at stake rather than on one where something is.

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.

Still a pre-release, and still for trying rather than relying on. It has been used daily on one machine by one person.

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.

What changed since 2026.1-pre3

In the program: nothing. In the repository:

• Releases are built by CI from a tag rather than by hand, and the packages carry a SHA256 each that the SourceForge mirror checks the bytes against before copying them.
• The keyboard hook was measured on a real keyboard: 691 samples, a p95 of 0.071 ms and no handler faults, against a budget of 1 ms. The previous figure came from twelve injected keystrokes, which is not a p95. This changes no code — it is evidence about code that already shipped in pre3.
• Documentation corrections, including test counts that had drifted.

If you are looking for what actually changed in the program, read the 2026.1-pre3 notes — that release carried the fixes.

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: