Still a pre-release, and still for trying rather than relying on. It has been used daily on one machine by one person. What this build is for is that a run of real bugs found by using it are fixed — several of them cases of the program doing something with a clip nobody chose, which is the class that matters most in a clipboard manager.

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 now 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.

Fixed since 2026.1-pre2

• The overlay sometimes opened on a bare V. Ctrl was tracked from key events, so a release that never reached us — a UAC prompt, a lock, another program’s hook — left it stuck down, after which the trigger key opened the gesture on its own and took an unmodified letter away from whatever you were typing into. All four modifiers are now read live from the keyboard.
• Typing in the search box fired actions. Pressing F and typing output opened the clip in an editor, because holding Ctrl is what keeps the gesture open and the guard was “unless Ctrl is held”. While the search box is up, no letter and no digit is an action; the arrows step through matches.
• The overlay appeared on the wrong monitor. It anchored to the mouse pointer when an application exposed no text caret — which is most of them, every browser included — so it could be 1,900 pixels from the window you were pasting into. It now centres on that window, and steps aside into a corner for surfaces Windows draws above everything, such as the Start menu.
• Pasting could end with a “Same as the last copy” notice, and a paste could be stored back as a new clip. Both were the same shape of fault: a clipboard write does not read back as what was written, because Windows regenerates the derived text formats from the pasting thread’s locale. Recognising our own writes no longer depends on those.
• One copy became two clips, or announced itself as a repeat. An OLE writer publishes in two steps and some applications publish again a fifth of a second later with more formats; the second publish now enriches the clip in place, silently.
• A closing application announced a repeat copy. Rendering its formats on the way out republishes byte-identical content, and only the clipboard’s owner tells that from somebody copying again.
• A screenshot could be stored as an 8-byte binary clip, from reading the clipboard between an OLE writer announcing its data and rendering it.
• Ctrl+V could silently stop working until PasteJump was restarted, if Windows dropped the keyboard hook — which it does, without telling anyone, when a callback exceeds its deadline. A watchdog now repairs the hook and releases a stranded overlay.
• The history window’s picture preview was blurry at 100%, its scroll bars did not respond to the mouse, and image clips in the Clips view never previewed at all.

New in this build

• Where the overlay appears is yours to choose — beside the caret, centred on the window, at the pointer, or a fixed point — with a Show Me button that puts it there. The copy notification has the same choice, separately.
• The overlay says when the clip was copied, at the right of its facts row, in your own Windows date and time format.
• Its font can be chosen, labels and clip text together.
• The tray menu has two ticked toggles: Run at Startup, and Always Run as Administrator — the second registers a logon task, and exists for the case below.
• PasteJump says when it cannot see the keyboard in one program, once, naming it, instead of leaving Ctrl+V looking broken there.
• The history window filters by kind, gives every row a right-click menu, remembers its size and its splitter, and says what a delete removed.
• A magnifier in every search box, a GitHub Dark theme to pair with GitHub Light, and an animated tour of the gesture inside the help file.
• Two logs that ship: logs\gesture.log records what the hook received and what the recognizer did with it, and logs\capture.log one line per capture decision. They are what made most of the fixes above findable.

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: