You can see the clip you want before you reach it. The overlay has three views now - one clip at a time as before, a numbered list of the clips either side, or thumbnails with a picture of every screenshot - and while it is open the mouse can scroll, click and point. And a clip is on disk the moment you copy it: a crash or a power cut no longer takes the day’s clips with it.
Hold Ctrl, tap V to walk back through what you have copied, release to paste. No window, and no mouse needed. That gesture is unchanged and is still the whole of the idea; everything below is for the moment you want more than the next clip.
Which download
| File | What is in it | Needs |
|---|---|---|
PasteJump-2026.4.0.353-win-x64-unpacked.zip |
The whole program with the .NET runtime unpacked beside it, plus the manual, the licence and the readme. Nothing to install. Portable: its data folder appears beside the executable, so a USB stick carries your history with it. | Nothing |
PasteJump-2026.4.0.353-win-x64-net10.zip |
PasteJump’s own files only, about 4 MB. The shape where a .NET security update reaches PasteJump from Windows rather than from a new release. | .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. The same files are mirrored, byte for byte, to SourceForge.
Upgrading from 2026.3.1 or earlier: use Check for updates on the tray menu, or unzip this over your
existing folder. Your data folder - clips, history, blobs and settings - is untouched either way. Nothing
changes until you choose a view: the overlay opens exactly as it did.
Fixed first, because it is the one that mattered
- A crash or a hard reset could lose every clip copied since PasteJump last closed. Each clip was committed as it arrived, but a commit was not yet a save: the database waited for the system to write it out, and the only time PasteJump made sure was when it exited. On the machine this was found on, a hard reset took a day’s clips with it while the log recorded every one as stored. Every clip is now written to disk as it is copied, and the capture log says so at each start. Nothing about the speed of copying changes.
- And a copy of the whole store is kept for each of the last seven days, in
data\backups, taken ten minutes after start and again each day on a machine that is never restarted. The manual’s Troubleshooting page says how to restore one.
New: three ways to see the stack
- List: the current clip with its neighbours above and below, one line each. Each row is numbered with the
digit that jumps to it - press
3and you are there - and the list goes round the ends of the stack, as stepping does. Optionally, the current clip’s preview sits in a pane beside the list instead. - Thumbnails: every clip a tile - the picture for a screenshot, the first lines of text, the names of copied files - each labelled with its kind and size, so a path, a file and a picture can be told apart at a glance. Four tile sizes, up to 320 by 240. The arrows move as they look: down is the tile below. Pictures are loaded and shrunk in the background, so a held key never waits for a large screenshot.
- A Style tab in Settings, with a card for each view. The gear on a card opens that view’s own options - rows for the list, tile size and tiles per row for the thumbnails - without choosing it.
Wswitches the view for one paste, and the button on the overlay’s top line, which names the view and its key, does the same. The next paste opens in the view you chose in Settings.- The overlay keeps still. The list and thumbnails are one size throughout. A single clip fits each clip, but where the overlay is centred - programs with no text cursor for it to sit beside - its top-left corner stays put, so it grows and shrinks from the bottom and right. Keep the Overlay One Size holds it fixed.
New: the mouse, while the overlay is open
The mouse is only listened to while the overlay is up. At every other moment your clicks and the wheel are your
programs’ own, and Ctrl+wheel still zooms your browser.
- The wheel steps through clips, towards you for older and away for newer.
- Click the overlay to paste the clip it shows, or click any row or tile to paste that one. Pointing alone changes nothing, so a pointer resting on the overlay can never change what you paste.
- Right-click for a menu of every action, each with its key beside it - your own letters - so the menu
teaches the keys. Opening it locks the overlay, so you can let go of
Ctrl. - Everything explains itself: rest the pointer on a tile, a row, any chip on the top line or any key in the hint along the bottom, and a tooltip says what it is and which key changes it.
- Settings from the overlay: the gear at the end of its top line, or
Ctrl+,- the shortcut most programs use for their settings. Either closes the overlay first, pasting nothing.
Both the wheel and the clicks can be switched off, separately, on the Paste Mode tab.
Also fixed
- Holding
Ctrl+Vmade the list and thumbnails views glitch: the list changed height by a few pixels as it went round the end of the stack, a large screenshot could make a step slower than the key repeats, and after switching views withWthe overlay moved out and back on every repeat. All three are gone; the overlay now draws only the newest frame when the key outruns it, rather than falling behind. - The first backup of the day no longer competes with signing in: it waits ten minutes after start.
The manual
- Two new pages: The overlay’s views and Using the mouse. Clips and history explains what reaches the disk and when, and the backups; Troubleshooting says how to restore one.
- Every screenshot is regenerated from the program, and the tour video on the website shows the new views, the mouse and the Style tab.
- The settings reference lists 82 settings, generated from the source so it cannot fall behind.
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.