How to Collect Client Feedback Screenshots in One Place

Review weeks produce a second design file nobody named: twenty marked-up screenshots of the client's UI, their customers' data, and a competitor's checkout. Those shots land in Win+V, in the Screenshots folder, in Slack, and on the desktop. Then the project ends and the shots stay. That is both a workflow problem and a privacy problem.

The playbook is a single project inbox, a capture habit that writes files, and a wipe when the work is invoiced. Clipboard history can stage three crops during a call. It cannot be the archive. Microsoft's list is 25 items, 4 MB each, text / HTML / bitmap, and unpinned items clear on restart — but pins remain, and a pin of a client's admin panel is a pin of their admin panel.

Why history is the wrong review album

• A 1440p markup with red arrows often exceeds 4 MB as a bitmap and never joins Win+V, even though it still pastes once. Why Your Huge Screenshot Never Appears in Win+V
• The 26th snip drops the first. The missing shot is always the one with the actual bug
• Restart (or some updates) wipes unpinned history. The call notes vanish; the Slack thread does not reconstruct them
• History has no project name. Last week's hospital portal sits next to a meme
• Cloud sync, if enabled, uploads text tied to a Microsoft or work account. It is the wrong feature to have on while copying client emails and ticket IDs

Clipboard History on a Shared Family PC and Should You Disable Clipboard History on a Work Laptop? cover the shared-machine case. Agency machines that see multiple clients should default to sync off and a short memory.

Capture into a folder, not into "the clipboard"

Windows gives three honest capture tools. Microsoft documents Snipping Tool and Win+Shift+S. Use them as file producers:

1. Create client-acme/review-2026-08-18/ before the call
2. Snip with Win+Shift+S or Snipping Tool
3. If the snip is only on the clipboard, open Snipping Tool and save, or paste into the review folder via an image editor and save. Do not leave it as the live clipboard item
4. Name immediately: nav-overflow-mobile.png, checkout-tax-wrong.png, not Screenshot 2026-08-18 144203.png

Annotation belongs on the saved file. Snipping Tool can mark up. So can the Photos markup, or a dedicated tool. The marked file goes back in the same folder. How to Annotate a Screenshot Before You Reuse It.

Figma comments and FigJam stamps are better when the work already lives in Figma. Export a frame with Export (official Figma export help) and drop that PNG into the review folder if stakeholders are not in the file. Do not screenshot a zoomed canvas if an export exists. Figma Desktop vs Figma Web: Paste Behavior Differs only matters for paste; export avoids the split.

During the call: a tiny stage is allowed

A review call is one of the few times a 3–5 item clipboard stage is correct:

• The current crop the client is describing
• A hex they dictated
• A URL to the staging site (text)

Pin nothing that contains PII, medical data, or credentials. Unpin at hangup. Win+V > … > Delete on each, or Clear all, or Settings > System > Clipboard > Clear clipboard data.

If more than five shots will be compared, stop using history as the light table. Put the PNGs in the folder and use Explorer large icons, or drop them into PureRef for the hour. PureRef is a mood-board canvas, not a DAM, but it beats 25 anonymous thumbnails. Mood Boards in PureRef vs a Clipboard Shelf.

After the call: one place, one index

The inbox folder gets a README.txt or a one-page note:

2026-08-18 call
- nav-overflow-mobile.png — burger covers search at 375
- checkout-tax-wrong.png — VAT missing on B2B
- owner: alex
- figma: comments on Checkout / v12

That note can live in the tracker ticket instead. The rule is shots plus words in one system, not shots in history and words in chat.

Handing those shots to engineering is a named-file problem. How to Hand Assets to a Developer Without Slack Soup. Slack can distribute the PNG; it should not become the only copy. Slack help documents file add, and inline image previews have size thresholds. The original upload is what to download later — if the workspace still has it.

Do not leave client UI in history after the project

End-of-project wipe:

1. Unpin every review image and every token that was pinned "just for the sprint"
2. Clear clipboard data
3. Empty Recycle Bin if the review folder was deleted locally after archive
4. Remove the shots from Uploads in Canva, from an Eagle inbox, and from a personal Discord DM with yourself
5. Confirm the archive lives in the client drive / DAM with the retention the contract requires
6. If Windows clipboard sync was on, turn it off and understand that already-synced text may exist on other devices — clear those too

End of Project Wipe Checklist is the broader list. How to Wipe Clipboard Data Before Selling a PC is the hardware-exit version.

Healthcare, finance, and education jobs may require more than a habit. Official product docs will not bless a clipboard as a HIPAA control. Default to do not capture more than the ticket needs, and do not pin. Healthcare and Finance Clipboard Rules of Thumb.

Tools that are not the inbox

• Win+V pins — not a review album
• Desktop — not a review album
• Personal sticker kit — keep emotes out of client folders. Building a Personal Sticker and Icon Kit
• Creative Cloud Libraries — fine for the client's *approved* logo, wrong for a screenshot of their unfinished admin
• Figma comments — best for in-file critique; still export a pack for stakeholders who will not open Figma
• A hover shelf — optional during the call to drag three crops into the ticket UI. Edge-Drop can stage those files locally. Wipe it with the rest of the project. A shelf that keeps client UI for months is a worse leak than Win+V

Best Clipboard Setup for Photoshop Users if markup happens in Photoshop. Export the annotated PNG back to the review folder; do not leave the only copy as a layer in an unsaved PSD.

A one-page policy for the studio

• Review shots live in client/project/review-YYYY-MM-DD/
• Capture, save, name, then markup
• History holds at most a handful of unpinned previews during a live call
• Sync off
• No pins of client UI
• Slack is a notification, not the archive
• Project end = clear history + archive or delete the folder per contract

Worked example: a 45-minute design QA call

Before: create acme/checkout/review-2026-08-18/ and a ticket stub with the call time.

During:

1. Client says the tax line is wrong. Snip, save as checkout-tax-wrong.png, mark the line in Snipping Tool or the editor, overwrite the same name.
2. Copy the staging URL as text. Pin it only if the URL is not a secret token.
3. Client shares their own screenshot in Zoom. Save their file if they drop one; if they only screen-share, snip and name client-supplied-tax.png.
4. Do not pin their admin screenshot.

After:

1. Drop the two PNGs plus a four-line note into the ticket
2. Duplicate the same files into the review folder (or only the ticket, if the tracker is the archive)
3. Win+V > Clear all
4. Slack the ticket link, not a third recapture

Troubleshooting

Marked-up shots are evidence. Evidence has a folder, an owner, and an end date. The Windows clipboard has twenty-five anonymous bitmaps and a restart button. Use it for the call, then put the pictures away.

Related reading

• How to Hand Assets to a Developer Without Slack Soup
• Color Palettes: Hex Lists vs Visual Swatches
• Best Clipboard Setup for Photoshop Users
• Best Clipboard Habits for Developers in 2026

Sources

• Using the clipboard (Microsoft Support) — history limits, clear, pins, restart wipe.
• How to use clipboard history in Windows 11 (Microsoft) — Win+V, pin guidance, sync as optional text.
• Use Snipping Tool to capture screenshots (Microsoft) — official capture and save path.
• Export static designs from Figma — prefer export over a zoomed screenshot for reviews.
• Add files to Slack — files versus inline preview; do not treat chat as the vault.

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