# Review Screenshots With Clients: A Workflow That Works

*October 27, 2026 · 13 min read*

Review screenshots with clients without email chains: prepare the image, pin comments on the exact spot, resolve each pin and record approval in one place.

![](https://usepinhub.com/blog/media/synced-1792928645661_clients-reviewing-a-website-screenshot-together-105f1915.jpg)

The cleanest way to review screenshots with clients is to send one link to one current image, let them comment on the exact spot they mean, and track every comment until it is resolved. Everything else in this guide supports that loop: preparing the image, choosing how clients comment, handling conflicting opinions and recording the final approval.

Most review trouble does not come from clients being difficult. It comes from feedback that arrives as “the button on the right looks off,” in three different emails, about a screenshot that is no longer the latest. A better process fixes that without asking clients to learn anything new.

Pinhub

Keep Screenshot Feedback in One Place

Pinhub lets clients pin comments directly to screenshots, discuss each point in a thread, and track open feedback until it is resolved.

[Try Pinhub](https://app.usepinhub.com/login)

## TL;DR

- Crop and clean each screenshot before sending it, and check it for personal or production data.
- Have clients comment directly on the spot in question, not in a separate email that describes the spot.
- Keep one link and one version at a time, so everyone reviews the same thing.
- Treat every comment as a task with an owner and a status: open or resolved.
- Record approval on the same page where the feedback lives, then move on to the next round.

## Table of Contents

- [Prepare the screenshot before the client sees it](#prepare-the-screenshot-before-the-client-sees-it)
- [Make commenting easy for clients](#make-commenting-easy-for-clients)
- [Help clients give precise feedback](#help-clients-give-precise-feedback)
- [Build a workflow from first comment to resolved](#build-a-workflow-from-first-comment-to-resolved)
- [Handle multiple reviewers and conflicting feedback](#handle-multiple-reviewers-and-conflicting-feedback)
- [Our perspective: feedback belongs on the image](#our-perspective-feedback-belongs-on-the-image)
- [Share screenshots securely](#share-screenshots-securely)
- [Document final approval](#document-final-approval)
- [Common mistakes to avoid](#common-mistakes-to-avoid)
- [Review screenshots with Pinhub](#review-screenshots-with-pinhub)
- [FAQ](#faq)
- [Sources](#sources)

## Prepare the screenshot before the client sees it

A review is only as good as the image under review. Before you share anything, decide who will look at it, where they will see it and what you want from them. A screenshot meant to get approval on a layout needs different framing than one meant to report a bug.

The [Chatwoot product handbook](https://www.chatwoot.com/hc/handbook/articles/guidelines-taking-product-screenshots-screencasts-21) gives a practical baseline: capture only the relevant area, remove browser or window content that adds nothing, and use realistic or staging data. It also asks you to confirm that no personally identifiable information or production data is visible. That last check matters most when the screenshot comes from a live account.

A short pre-send checklist:

1. **Crop to the question.** If you want an opinion on the pricing section, do not send the whole page with the footer and a cookie banner.
2. **Remove noise.** Hide bookmarks bars, unrelated tabs and notifications.
3. **Use safe data.** Swap real customer names, emails and order numbers for staging content.
4. **Name the file clearly.** A name such as `homepage-hero-v2` tells the client, and you, which round this is.
5. **State the ask.** One sentence in the message: “Please check the headline and the call to action.”

If the page is long, split it into sections rather than shrinking a full-page capture until the text is unreadable. Several focused screenshots are easier to review than one tall image.

### Capture web pages as screenshots

When the work lives on a website, you need a screenshot of it first. In Pinhub you can capture a page from its URL or with the Pinhub Chrome extension, and the result becomes a regular screenshot your client comments on. Pinhub does not annotate the live site. It works on the captured image, which also means the client always reviews a fixed moment, not a page that keeps changing underneath them.

We cover the difference between capturing a page and recording it in [when a screenshot beats a screen recording](https://usepinhub.com/blog/screenshot-vs-screen-recording/).

## Make commenting easy for clients

Clients are rarely designers. If leaving feedback takes an account, a tutorial and a password reset, many will fall back on replying to your email. Reduce every step between opening the link and leaving the first comment.

What works in practice:

- **No account required.** Guests should be able to open the link and comment immediately.
- **One link per review.** A single URL for a screenshot, or for a set of related screenshots, beats a folder of attachments.
- **Comments anchored to the image.** A pin on the exact spot removes the need to describe where something is.
- **Threads, not side conversations.** Replies stay attached to the pin they discuss.

In Pinhub, reviewers open a share link and click the spot they mean to drop a pin, then type their comment. You and your team reply in the thread. Unlimited guest reviewers can comment without creating an account, including on the Free plan. If the work is not meant for public eyes, paid plans let you protect the link with a password.

For reviewing several related screens together, such as a homepage, a pricing page and a checkout step, Collections put multiple screenshots on one link. The Free plan includes 1 collection. Pro and Team plans include unlimited collections with up to 20 screenshots each.

## Help clients give precise feedback

Vague feedback is the most common review problem, and it is rarely the client’s fault. You can shape what you receive by how you ask.

### Ask for one thing per pin

A pin that says “change the colors, fix the spacing and make the text bigger” cannot be resolved cleanly. Ask clients to place one pin for each change. It is easier to answer, easier to assign and easier to check off.

![Separate visual pins each indicate one design change](https://usepinhub.com/blog/media/synced-1792928709886_separate-visual-pins-each-indicate-one-design-change-26de621f.jpg)

### Show what good looks like

Send one sample comment with your first request. For example:

| Vague comment | Useful comment |
| --- | --- |
| “This feels off.” | “The headline wraps onto three lines here. Can we shorten it to two?” |
| “Fix the button.” | “This button reads ‘Submit.’ We would like ‘Request a quote.’” |
| “Wrong image.” | “Please use the team photo from the January shoot in this slot.” |
| “Spacing is weird.” | “The gap between this card and the next feels larger than the others.” |

When the pin sits on the headline, the button or the gap, the comment itself can be short. The location does the explaining. For more on marking up images quickly, see our guide to [annotating screenshots fast and clearly](https://usepinhub.com/blog/annotate-screenshots/).

### Separate opinions from problems

Ask clients to label their comment as a must-fix or a preference, even informally, by starting with “Must:” or “Idea:”. This tiny habit helps you prioritize without a second meeting.

### Set a clear review window

Tell clients when you need feedback and what happens next. Do not promise a specific turnaround you cannot keep, but do say “we start the revision on Thursday, so comments by Wednesday evening go into the next version.” Giving a recurring rhythm, such as one consolidated round per week, keeps reviews from drifting.

## Build a workflow from first comment to resolved

A review is a small project with a beginning, a middle and an end. A simple workflow keeps it from sprawling.

| Stage | What happens | Who owns it |
| --- | --- | --- |
| Prepare | Crop, clean and name the screenshot | You |
| Share | Send one link with a one-line ask | You |
| Collect | Client and reviewers pin comments | Client |
| Triage | Group comments, flag conflicts, assign owners | You |
| Revise | Make changes and upload a new version | Designer or developer |
| Resolve | Mark each pin resolved, with a note on what changed | You |
| Approve | Client confirms the final version | Client |

The triage step is where many teams lose time. Read every comment once before touching the design. Group related pins, spot contradictions and decide who handles each item. Our post on [turning client design feedback into assignable tasks](https://usepinhub.com/blog/client-design-feedback/) walks through this in more detail.

In Pinhub, open pins stay tracked until they are resolved, so the question “what is still outstanding?” always has a visible answer. On paid plans, the AI summary turns open feedback into an action checklist, which is a quick way to see the list of changes before you start revising.

### Keep versions straight

Outdated screenshots cause more arguments than bad design. A client comments on version one while you have already moved to version three, and now the thread makes no sense.

Upload each revision as a new version of the same screenshot rather than as a new file with a new link. On paid plans, Pinhub keeps version history, so earlier rounds and their comments remain available to look back on. Clients always land on the current version, and you can show them what changed since the last round.

If a revision is part of a larger project, such as a [website redesign timeline](https://picshaw.com/blog/website-redesign-timeline) with several review milestones, plan one review round per milestone and name each version after it.

## Handle multiple reviewers and conflicting feedback

One client contact is simple. Three stakeholders with different tastes is where reviews stall.

**Name a decision maker.** Before the first round, ask the client who has final say. Other reviewers can comment, but one person approves.

**Let everyone use the same link.** When all reviewers see each other’s pins, they notice contradictions themselves. Two pins on the same headline asking for opposite things often resolve with a single reply in the thread.

**Do not resolve conflicts silently.** If two comments disagree, reply in the thread and tag the decision maker with a clear choice: “Option A keeps the longer headline. Option B shortens it. Which should we use?” Keep the question short enough to answer in one line.

**Write down the decision.** Once settled, add a final comment such as “Decided: Option B, per Maria,” then resolve the pin. When the topic comes back in a later round, the answer is on the page.

**Limit rounds.** Agree up front on how many consolidated rounds a deliverable includes. The number depends on your contract, not on a universal rule. Our guide to [web design feedback for agencies](https://usepinhub.com/blog/web-design-feedback/) goes deeper on setting these expectations.

## Our perspective: feedback belongs on the image

We built Pinhub around a simple observation: the longer a comment lives away from the thing it describes, the more likely it is to be misread. An email that says “the third card” forces the designer to translate the words back into a location. A pin removes that step.

That is why we focus on a few things and keep them in one workspace. Comments are pinned on the exact spot of a screenshot or design. Guests can comment without an account, because asking a client to sign up is a reliable way to lose their feedback. Each pin carries its own thread and its own status, so nothing is open by accident and nothing is closed by assumption.

We also think a review tool should be honest about what it does. Pinhub works on screenshots, images and design files, including web pages captured into screenshots and Figma frames. It does not annotate live sites or install anything on them. That boundary is deliberate: a fixed image is the same for everyone, today and next month.

The best review process is the one clients actually use. If it takes more than a minute to leave the first comment, simplify it.

> *— Pinhub*

## Share screenshots securely

Client work is often confidential, so sharing deserves a moment of thought before you hit send.

### Remove sensitive content first

Anything visible in the image is shared with everyone who has the link. Check sidebars, headers, footers, browser tabs and the edges of a crop. If you must hide text, cover it with a solid block instead of a light blur, and share a new exported copy, not the original. The [HappyImg redaction guide](https://happyimg.com/guides/redact-screenshot-before-sharing) describes this approach: copy first, cover with solid blocks, check edges and export a clean image.

### Limit what a link can do

For unauthenticated links in general, US government guidance is conservative. CISA’s baseline for Microsoft OneDrive for Business says [anonymous “Anyone” links should be disabled where possible](https://www.cisa.gov/sites/default/files/publications/Microsoft%20OneDrive%20for%20Business%20M365%20Minimum%20Viable%20SCB%20Draft%20v0.1.pdf). If they are enabled, it recommends that links expire, gives thirty days as the baseline, and limits permissions to view. That document concerns a specific product, but the principle carries over: share the least access that gets the job done.

For review links, that means:

- Use a password on sensitive work. Password-protected share links are available on Pinhub’s paid plans.
- Share the link only with the people who need it, and send the password separately from the link.
- Do not reuse the password across projects. CISA notes that [password reuse lets an attacker who compromises one password reach multiple systems](https://www.cisa.gov/sites/default/files/2023-09/CISA_CEG_Implementing_Strong_Authentication_FINAL%20Aug-23%20Revision.pdf).
- Stop using a link once the project is approved, and start a fresh one for the next project.

### Think about accessibility

If screenshots end up in documentation, emails or a client portal, they should be usable by people with screen readers. Section508.gov explains that [alternative text conveys an image’s meaning](https://www.section508.gov/create/alternative-text/) to screen reader users, should be short and focused, and should not repeat the surrounding text. Its [accessible web design guide](https://www.section508.gov/develop/guide-accessible-web-design-development/) adds that teams should avoid images of text when ordinary text can carry the information. When a screenshot shows a design under review, put the key copy in the message too.

## Document final approval

Approval that lives only in a phone call or a casual “looks good!” is hard to defend three weeks later. Make the end of the review as explicit as the start.

1. **Confirm every pin is resolved.** Check the list of open pins. If any remain, either fix them or note why they are deferred.
2. **Upload the final version.** Make sure the version the client sees is the one you will build or publish.
3. **Ask for a clear sign-off.** A plain message works: “Please confirm that version 4 of the homepage is approved for development.”
4. **Keep the confirmation with the work.** A final comment on the screenshot, or in the Collection, records who approved what and when, next to the history of changes.
5. **Archive the link.** Once approval is recorded, stop using the share link for new feedback.

Developers and QA teams can use the same pattern in reverse. After a visual bug is fixed, attach a new screenshot as a fresh version and resolve the original pin, so the report and the fix sit side by side.

## Common mistakes to avoid

- **Sending attachments in email.** Every attachment becomes a separate version nobody can find later. Share one link instead.
- **Collecting feedback in several places.** If comments arrive by email, chat and calls, copy them onto the screenshot as pins so the list is complete. Team plans can connect Slack for notifications, which keeps conversation near the work.
- **Reviewing the wrong version.** Name versions and keep only the latest as the active review.
- **Skipping the resolve step.** An unmarked pin looks the same as an ignored one. Resolve each pin and add a short note on what changed.
- **Asking for “any feedback”.** Open requests produce opinions about everything. Ask about the headline, the layout or the color, and state what is off limits for this round.

## Review screenshots with Pinhub

If you are ready to try this process, Pinhub puts it in one workspace: upload a screenshot or design, capture a page from a URL or with the Chrome extension, or import a Figma frame, then share one link and let clients pin their comments.

Here is how the plans are structured:

| Plan | Price | Members | Good for |
| --- | --- | --- | --- |
| Free | $0 | 1 | Light, solo use with 3 active screenshots, unlimited guest reviewers and 1 collection |
| Pro | $19/month, or $15/month billed yearly | Up to 3 | Freelancers and small studios |
| Team | $39/month | Up to 10 | Agencies and product teams |
| Team | $79/month | Up to 20 | Larger teams |
| Team | $129/month | Up to 50 | Large organizations |

Team pricing is flat for each tier. Paid plans add features such as password-protected links, Figma import, URL and Chrome extension capture, version history, AI summaries, forms and polls, and whiteboards. You can start on the Free plan and see the full plan list on the [Pinhub home page](https://usepinhub.com/).

## FAQ

### Do clients need an account to comment on a screenshot?

No. With Pinhub, guests open the share link and comment without creating an account. You can invite as many guest reviewers as you like, including on the Free plan. This keeps the barrier low for clients who only review occasionally.

### How do I stop clients from commenting on an old version?

Upload each revision as a new version of the same screenshot, so the share link always shows the current one. Name versions clearly in your message, such as “version 3, after round two.” On paid plans, version history keeps earlier rounds available for reference.

### How should I handle feedback that contradicts itself?

Reply in the thread of the conflicting pins and ask the designated decision maker to choose between clear options. Record the decision in a final comment and resolve the pins. This leaves a visible answer if the topic returns later.

### Is a screenshot enough, or should I record a video?

For most visual reviews, a screenshot is enough and easier to comment on precisely, because everyone sees the same fixed image. Pinhub focuses on screenshots, images and design files and does not record screen sessions. Our comparison of [screenshots and screen recordings](https://usepinhub.com/blog/screenshot-vs-screen-recording/) covers when each fits.

### How do I keep a client review link private?

Remove sensitive data from the image before sharing, send the link only to the people who need it, and add a password on a paid plan. Stop using the link once the project is approved and use a new one for the next review.

## Sources

- [Chatwoot: Guidelines for taking product screenshots](https://www.chatwoot.com/hc/handbook/articles/guidelines-taking-product-screenshots-screencasts-21)
- [Section508.gov: Authoring Meaningful Alternative Text](https://www.section508.gov/create/alternative-text/)
- [Section508.gov: Guide to Accessible Web Design and Development](https://www.section508.gov/develop/guide-accessible-web-design-development/)
- [CISA: Microsoft OneDrive for Business security baseline](https://www.cisa.gov/sites/default/files/publications/Microsoft%20OneDrive%20for%20Business%20M365%20Minimum%20Viable%20SCB%20Draft%20v0.1.pdf)
- [CISA: Implementing Strong Authentication](https://www.cisa.gov/sites/default/files/2023-09/CISA_CEG_Implementing_Strong_Authentication_FINAL%20Aug-23%20Revision.pdf)
- [HappyImg: Redact screenshots before sharing](https://happyimg.com/guides/redact-screenshot-before-sharing)

## Recommended

- [How to Share Designs with Clients: A Secure Guide](https://usepinhub.com/blog/share-designs-with-clients/)
- [Client Design Approval: A Practical Guide for Design Teams](https://usepinhub.com/blog/client-design-approval/)
- [Designers: Turn Client Design Feedback Into Assignable Tasks](https://usepinhub.com/blog/client-design-feedback/)
- [Creative Review Workflow: A Practical Playbook for Teams](https://usepinhub.com/blog/creative-review-workflow/)

[All articles](https://usepinhub.com/blog/)

---

- [Home — what Pinhub is and how it works](https://usepinhub.com/)
- [FAQ](https://usepinhub.com/faq/)
- [About](https://usepinhub.com/about/)
- [Contact](https://usepinhub.com/contact/)
- [Blog](https://usepinhub.com/blog/)
- [Terms of Service](https://usepinhub.com/terms/)
- [Privacy Policy](https://usepinhub.com/privacy/)
