You've got a screenshot open — a design comp, a config panel from another machine, a step in a tutorial — and you need to look at it while you work in a different app. The default move is alt-tabbing back and forth, or shrinking two windows side by side and losing screen space to both. Pinning solves this differently: it turns the screenshot into a small floating window that stays on top of everything else, so it's visible no matter what you click into underneath it.
It's a narrow feature, but it shows up in a specific, recurring kind of work: following a setup guide step by step, rebuilding a UI from a design reference, comparing a "before" screenshot against a live page, or copying values out of an old email while filling out a form. Here's what pinning actually does, how to get it without a screenshot tool, and how the dedicated versions differ.
What Pinning Actually Does
A pinned screenshot is a small, borderless, always-on-top copy of an image that floats above your other windows. It's not a second monitor and it's not split-screen — it sits in a fixed spot (usually a corner) while you work normally underneath and around it. Most implementations let you:
- Move it anywhere on screen
- Resize it larger or smaller
- Zoom in on part of the image without resizing the window itself
- Close it or send it back to an editor when you're done
The point is to remove the cost of checking a reference. Alt-tabbing breaks your position in whatever you were doing — you lose your scroll position, your cursor focus, sometimes your mental place in a multi-step process. A pinned window is just there, in your peripheral vision, the whole time.
Where This Actually Helps
Following a tutorial or setup guide. If you're working through a step-by-step guide with screenshots — configuring a server, setting up a new tool, following someone else's SOP — pinning the guide's screenshot next to the app you're configuring means you're not scrolling a browser tab back into view every ten seconds.
Rebuilding a design from a reference. Developers turning a Figma export or a design screenshot into actual UI, or writers matching a layout from an old version of a document, benefit from having the target visible at all times rather than switching apps to check spacing or copy.
Comparing two states. Before/after bug reports, A/B design reviews, or checking whether a fix actually matches a mockup — a pinned "before" or "target" image next to the live result makes the comparison direct instead of remembered.
Copying values without retyping from memory. Pulling numbers, IDs, or text out of a screenshot (an old invoice, a config dump, a chat message with instructions) while typing them into another app is faster with the source visible than with it buried in a background window.
None of these are exotic workflows — they're the ordinary friction of needing to see two things that live in different apps at the same time.
What's Built Into Your OS (Not Much)
Neither macOS nor Windows ships a built-in way to pin an image on top of other windows. What each platform has instead is partial:
On macOS, Preview and Stickies can float small windows, but neither is built for this — Preview's image windows behave like normal windows, and Stickies is meant for text notes, not screenshots. Third-party utilities like Helium exist specifically to keep an image or webpage floating on top, and work, but they're another separate app to install and manage.
On Windows, Microsoft's PowerToys utility includes an "Always on Top" module (default shortcut Win+Ctrl+T) that pins whatever window is currently active above everything else. It's useful, but it pins windows, not a cropped screenshot — so pinning a screenshot this way means opening it in an image viewer first, then pinning that viewer window, which carries its own title bar and chrome along for the ride.
Neither OS gives you a purpose-built, borderless, screenshot-sized floating window out of the box. That gap is what dedicated screenshot tools have picked up.
Dedicated Pin Features
A handful of screenshot tools build pinning directly into the capture workflow, so a screenshot goes from "just taken" to "floating on screen" in one action instead of a save-then-open-then-pin sequence.
CleanShot X (macOS only) has a "Pin to Screen" feature that's become one of its more talked-about capabilities: take a screenshot, click the pin icon in the capture preview, and it becomes a floating, resizable, opacity-adjustable overlay. Multiple screenshots can be pinned at once.
Shottr (macOS only) has a similar pin option that turns a captured or imported image into a minimal always-on-top window, aimed at the same "keep a reference visible" use case.
Both are solid implementations — but both are Mac-only, which matters if your team, or you personally, split time across Windows and macOS.
Savvyshot includes a pinned windows feature that works the same way on both platforms: from the editor, Ctrl/Cmd+P (or the pin action in the editor's footer) turns the current canvas into a floating, always-on-top window. You can drag it anywhere, hold Ctrl (Windows) or Cmd (macOS) and scroll to zoom in on part of it, and use footer controls for original size, fit-to-window, or a custom zoom level. Multiple screenshots can be pinned simultaneously, each as its own window, and double-clicking a pinned window sends it back to the editor if you need to make further edits. On Windows, closing a pinned window means hovering the top-right corner to reveal a close control; on macOS it uses the standard window close button. This is a licensed feature — it requires an activated Savvyshot license rather than being available on the free tier.
The practical difference from the OS-level workarounds isn't capability so much as friction: a screenshot tool with pinning built in turns "capture → pin → reference while working" into one continuous action, instead of capture, save, open in a viewer, then pin the viewer.
Getting More Out of a Pinned Window
A pinned window is simple, but a few habits make it noticeably more useful:
Resize it to just what you need visible. A full-screen pinned screenshot defeats the purpose — it blocks as much as it reveals. Crop before pinning, or resize the pinned window down to the specific region you're actually referencing.
Park it somewhere that doesn't cover your controls. A corner near your cursor's resting position beats dead center. If you're referencing a screenshot while typing in a form, put the pin near the field you're filling, not over your toolbar.
Zoom instead of resizing tiny text. Shrinking a pinned window to fit in a corner often makes text inside it unreadable. Use a zoom control (where available) to enlarge the content within a small window frame instead of stretching the window itself.
Pin more than one when comparing states. If you're checking a "before" against a "target," pin both rather than toggling one image back and forth — side-by-side floating windows are faster to compare than a single window you're mentally updating.
Close it when you're done. Pinned windows are meant to be temporary reference tools, not a permanent second monitor. Leaving several open indefinitely adds clutter that defeats the "stay focused" point of pinning in the first place.
Is a Dedicated Pin Feature Worth Having?
If pinning is something you'd use rarely — checking a reference image once a week — a free system-level workaround (Stickies, Helium, PowerToys) is enough, and installing another tool just for this one feature isn't worth it.
If it's a regular part of how you work — matching designs, following multi-step guides, comparing states across two apps several times a day — the difference shows up in how little friction is between "I need to see this" and "it's visible." A screenshot tool where pinning is one keystroke away from the capture you just took removes a few seconds of setup each time, which adds up when it's a daily habit rather than an occasional one. The cross-platform question matters here too: if you or your team move between Windows and macOS, a pin feature that only exists on one of them is a workflow you can't rely on consistently.
