PasteJump tells you when it has started. A tray-only program gives no sign of being there - no window, and the notification area is the one place nobody is looking as they sign in - so the honest answer to “is it running?” used to be to go and hover the icon. It says so itself now, briefly, in the corner.

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 unchanged and is still the whole of the idea.

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.

Upgrading from 2026.3 or earlier: unzip this over your existing folder, or beside it. Your data folder - clips, history, blobs and settings - is untouched either way.

This is a patch release. Nothing about the gesture changes, and someone on 2026.3 who skips it loses nothing they were relying on: what is here is one small, optional capability and two fixes to things PasteJump said rather than to anything it did. The notes are short on purpose.

New: it says when it has started

• A brief notice in the corner, naming the version you are running and the chord to paste with. It never takes focus, so it cannot interrupt whatever you are typing as you sign in.
• Three answers, under Settings, System. Every time it starts is the default and is what somebody who stops and starts PasteJump themselves wants. Only after an update is silent from day to day and speaks up once when the version actually changes - the one moment the program has genuinely become something else. Never is what every release before this one did.
• It says so when capture is paused, or when PasteJump is disabled, rather than simply claiming to be running. That matters more than it sounds: pausing survives a restart, so you can sign in to a PasteJump that is running and recording nothing, and nothing else on screen would tell you.
• A splash screen during start-up was considered and rejected on a measurement rather than a preference: about 171 ms of a 286 ms warm start happens before any of PasteJump’s own code runs, so a splash could only cover the last third of it and would flash.

Fixed

• A range copied from Excel was labelled a picture while pasting as text, which is the most confusing thing this program can do - the label disagreeing with what pasting produces. Nothing was ever lost: such a clip carries 26 formats and every paste was already perfect. Excel publishes a bitmap rendering of the cells beside the cells themselves, and the old rule asked “is there a picture?” before “is there text?”. Text wins now, and a clip is called a picture only when there is no text at all - which is exactly a screenshot, the case the old order existed for. Clips already captured are repaired at start-up, since the label is stored rather than worked out each time. The preview is unaffected either way: it shows a picture whenever the clip has one, whatever the label says.
• PasteJump offered to import your Clipjump history over a store that already had clips in it. Reported from a new laptop: the whole installation was copied across, and PasteJump asked anyway while a data folder holding 1,000 clips and 5,919 history entries sat beside the executable. Being asked was the mild half - answering yes would have merged a legacy archive into a live history. The offer now looks at the store, not only at whether the question has been asked before on this machine.
• The manual no longer describes a download that does not exist. Its first page recommended the single-file …-win-x64.zip, retired in 2026.3, and advised against the archive that actually ships.
• Three screenshots were missing from the compiled manual entirely - the lock-open overlay, the key list and the filtered history - because they were never listed in the help project file. The compiled manual reports the same image count either way, so this was found by decompiling it rather than by reading its build output.

The manual

• Every page now carries a picture of what it describes. Getting started, The tray icon, Troubleshooting, Coexisting and Two stores had none; the tray menu had never been shown at all, on the page about the tray menu.
• A generated Settings reference, listing all 71 settings with their defaults, types and the tab each one lives on. Generated from the source rather than written out, so it cannot fall behind the program.
• The sidebar and page order now follow the same shape as the website.

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 is published with the release.