How to Compare Two Screenshots Side by Side

QA and design reviews need two pictures in one field of view: before and after, staging and production, last build and this build. Win+V can hold both bitmaps for a little while. It cannot overlay them, blink them, or measure a 2-pixel shift. Treat the clipboard as a collector. Treat comparison as an image job.

Windows history remains what Microsoft documents: 25 items, 4 MB each, text / HTML / bitmap, unpinned items gone after restart. A pair of 4K captures may never enter history at all.

Collect without losing the first snip

Last-copy-wins will destroy the before-image the moment the after-image is copied, unless something else stored the first one.

Reliable collection order:

1. Capture before. Save immediately as feature-before.png in a working folder.
2. Capture after. Save as feature-after.png in the same folder.
3. Only then open a comparison tool on those two files.

Session-only shortcut:

1. Turn on clipboard history (Win+V → Turn on) if it is off: How to Enable Clipboard History in Windows 11.
2. Capture before. Confirm the card in Win+V. Pin it if a reboot is possible before the after shot.
3. Capture after.
4. Paste each card into files anyway. Pins are not a test artifact.

If either bitmap is over 4 MB, skip history and save from Snipping Tool. Huge snips silently skip the list: Windows Clipboard 4 MB Cap: What Gets Dropped.

Name the files before comparing. Untitled Screenshot (18).png pairs get swapped. Naming: Turning a Copied Image Into a Named Asset.

Side-by-side with software already on the PC

Photos (Windows 11)

1. Open the folder in Explorer.
2. Open feature-before.png in Photos.
3. Open feature-after.png in a second Photos window (right-click → Open, or drag the file onto the desktop and open).
4. Snap the windows to left and right (Win+Left, Win+Right).

This is enough to see a missing button or a color change. It is not a pixel diff. Zoom both to the same percentage or the “shift” is just different zoom.

Paint (cheap overlay)

1. Open the after image in Paint.
2. Ctrl+A, Ctrl+C.
3. Open the before image in a second Paint window (or File > New and paste before, then paste after as a second step in an editor that supports layers — classic Paint does not).
4. For a true overlay, use Paint 3D or an editor with layers and set the top layer’s opacity down.

Classic Paint is a poor overlay tool. Use it to crop both images to the same region before a real diff, so scroll position and window chrome do not register as changes.

PowerPoint or Word (review with arrows)

1. Insert both pictures on one slide.
2. Align tops.
3. Add arrows or a red box around the delta.

This is for a human review, not automation. Export the slide if the review must be attached to a ticket.

Browser (two local files)

1. Drag feature-before.png into one Edge tab.
2. Drag feature-after.png into another.
3. Use Edge’s split view if available, or two windows snapped.

Local file:// images do not need a server. Do not upload customer screens to a random public compare site.

Pixel-level diffs (when “looks the same” is not enough)

Side-by-side misses a 1-pixel hairline. For regression:

A typical ImageMagick check, once the tool is installed:

magick compare feature-before.png feature-after.png feature-delta.png

The delta image is the artifact to attach. The clipboard never needs to hold all three.

If the screenshots are baselines that must survive months, they belong in git (or git-LFS), not in history: When a Screenshot Belongs in Git, Not in History.

Make the two captures comparable

Most “false diffs” are capture hygiene:

• Same crop. Include or exclude the Windows taskbar on both shots.
• Same theme. Dark mode versus light mode is not a bug unless that is the test.
• Same data. A clock, unread badge, or “3 minutes ago” will always differ.
• Same HDR treatment. An HDR before and an SDR after will look like a wash-out bug: HDR and Wide-Color Screenshots on the Clipboard.
• Same scale. 100% OS scaling, same monitor.
• No cursor unless the cursor is the subject. Snipping Tool can hide it.

Redact secrets before attaching to a ticket. A clipboard card of an admin page may still be sitting in Win+V after the ticket is filed. Delete that card: Win+V → … → Delete. Clearing: How to Clear Clipboard History on Windows 11.

A QA loop that does not fight the clipboard

1. Create qa/<ticket-id>/ with before.png and after.png (and delta.png if generated).
2. Capture with Snipping Tool auto-save on, then move and rename. Do not keep working from Pictures\Screenshots.
3. Use history only as a safety net for the last few copies of error strings and URLs that go into the ticket.
4. Paste text into the ticket with Ctrl+Shift+V or Keep Text Only so the write-up does not inherit random HTML: How to Paste Without Formatting on Windows.
5. Attach the files. Do not paste 4K bitmaps into the ticket body if the tracker will recompress them.

For getting a keepable snip into Photoshop without a second copy hop: How to Get a Screenshot Into Photoshop Without Recopying.

Optional staging

A local shelf can hold the two files so they can be dragged into the ticket or the compare folder without hunting Pictures. Edge-Drop is built for that drag. It will not blink the two images or produce a delta PNG. If the team already uses ShareX, save before/after with a patterned filename and stage only the keepers: Using ShareX After-Capture Plus a Clipboard Shelf.

Ticket write-up that matches the pictures

A visual pair without a sentence is a Rorschach test. After the files exist, write four lines in the ticket before attaching:

1. Expected — what the after image should show if the fix is correct.
2. Actual — what still differs, in one clause (“the primary button is 8px lower”).
3. Environment — OS scale, theme, build number, account type.
4. Not a bug — clock, unread counts, sample data that will always move.

Paste those lines with Keep Text Only so the ticket does not inherit Snipping Tool HTML. Then attach before.png, after.png, and delta.png if one was generated. Do not paste 4K bitmaps into the description if the tracker will recompress them to a blur.

If the review is a design critique rather than a regression, say so. Designers need the pair at 100% scale; they do not need a red ImageMagick delta of anti-aliasing.

What “done” looks like

The review packet is two named files (and optionally a delta), a one-sentence description of the expected change, and no dependence on Win+V still showing the cards tomorrow. After restart, unpinned history is empty. The files should still open.

That limit is unpacked in Favicons and Tiny Images That History Tools Ignore.

Related reading

• When a Screenshot Belongs in Git, Not in History
• How to Get a Screenshot Into Photoshop Without Recopying
• How to Paste Without Formatting on Windows
• How to Enable Clipboard History in Windows 11

Sources

• Using the clipboard (Microsoft Support) — 25-item, 4 MB, bitmap limits; why history cannot be the compare store.
• Use Snipping Tool to capture screenshots (Microsoft Support) — capture and save the two files.
• How to use clipboard history in Windows 11 (Microsoft) — pin as a session safety net only.
• ImageMagick compare documentation — official pixel-comparison command for local deltas.

Copy. Stack. Drop.

Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.

Download for Windows Get from Microsoft Store

How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge-Drop vs Win+V · Support