Some of the best praise you will ever receive arrives in a place you cannot link to: a Slack message from a happy customer, a one-line email reply that says "this saved us hours," a DM after a launch. The instinct is to screenshot it and slap it on the landing page. The instinct is half right. The praise is genuine and worth using — but a raw screenshot, pasted in as-is, often does less for conversion than you expect, and occasionally creates problems you did not see coming.
This is a practical guide to turning a screenshot of praise into something you can actually publish with confidence.
Why a raw screenshot is weaker than it looks
A screenshot feels more authentic than a typed quote — it looks unedited, unfiltered, real. That instinct is why screenshots can work. But the raw image has three quiet problems:
- It is hard to read. Chat screenshots are low-contrast, small, and full of interface clutter — timestamps, avatars, reaction emoji, unrelated messages above and below. On mobile, the text is often unreadable.
- It is unverifiable to a stranger. A visitor cannot tell whether the message is real or mocked up in two minutes. Paradoxically, the "authentic" format invites the suspicion it was meant to dispel.
- It may not be yours to publish. A private message is not the same as consent to put someone's name, face, and words on a sales page. We will come back to this — it is the part teams skip most.
So the goal is not to discard the screenshot. The goal is to preserve what makes it credible while fixing what makes it weak.
Step 1: Verify it is real and attributable
Before anything else, confirm three things: the message genuinely came from a real customer, you can identify who they are, and the praise is about something specific you can stand behind. A screenshot from "Anonymous in Slack" with no traceable identity is not proof — it is a quote you are asking the visitor to take on faith. The whole value of social proof is that a real, nameable person said it.
If you cannot attach a real name, role, and ideally a company, treat the message as a private kindness, not a publishable testimonial. For why anonymous quotes underperform and when they are still worth using, see our guide on how to use a testimonial when the customer wants to stay anonymous.
Step 2: Get explicit permission
This is the step that turns a screenshot from a liability into an asset. A message someone sent you privately was not written for publication, and using it without asking is both a trust risk and, depending on your jurisdiction, a legal one once you attach their name and company.
The ask is short and almost always says yes:
"This made our week — would you be okay with us featuring it on our site, with your name and title? Happy to link to your company, and happy to leave anything out you'd rather we not include."
Notice what the ask does: it gives them control (leave anything out), offers them something (a link to their company), and frames it as a compliment, not a favor. For the full set of permission scripts — including how to ask to use a job title and company name — see how to ask permission to use a customer's job title and company name in a testimonial.
Once you have a yes, you have a choice to make about format.
Step 3: Decide — keep the screenshot or transcribe it?
You now have two ways to publish, and the right one depends on the message.
Keep the screenshot when the authenticity of the format is the proof — for example, an unprompted, emotional reaction in a public channel, or a message whose visible context (a real avatar, a recognizable workspace) adds credibility. In that case, clean it up: crop tightly to the relevant message, remove unrelated messages and clutter, keep the sender's name and avatar visible, and make sure the text is large enough to read on mobile. Do not edit the words inside the image — cropping is fine, rewriting is not.
Transcribe it when the message is long, the formatting is messy, or you want the quote to sit cleanly next to a specific claim on the page. A transcribed quote — with a real photo, name, title, and company beside it — is easier to read, easier to place, and just as credible because you have attribution. The screenshot's job was to prove a real person said it; once a named, photographed person is attached, the typed version carries the same weight and reads far better.
A strong hybrid: transcribe the quote for readability, and offer the original screenshot as a small, optional "see the original" element for anyone who wants to verify. You get clean design and visible authenticity at once.
Step 4: Trim without distorting
Screenshot praise is often rambling — "omg this is amazing, we were drowning in spreadsheets before, the team is obsessed, also do you have a dark mode coming?" The publishable version is the middle: the specific, outcome-focused sentence. Cut the greeting, cut the unrelated feature request, keep the substance.
The rule is that trimming must never change what the customer meant. Removing filler is fine; stitching two separate thoughts into a stronger-sounding claim is not. For the line between honest editing and misrepresentation, see how to trim a long testimonial without changing what the customer meant.
Step 5: Place it where the doubt lives
A cleaned-up screenshot testimonial is still just a testimonial, and placement decides whether it converts. A quote about onboarding speed belongs next to your setup claim; a quote with a hard number belongs next to your pricing. Do not bury it in a generic carousel where no quote sits near the objection it answers. For the full section-by-section logic, see where to place testimonials on a landing page.
The takeaway
A screenshot of praise is real proof, but the raw image is rarely the publishable asset — it is the raw material for one. Verify the sender is real and nameable, get explicit permission before you attach their identity, then decide deliberately between keeping a cleaned-up screenshot (when the format itself is the proof) and transcribing a clean, attributed quote (when readability and placement matter more). Trim for substance without changing meaning, and put the result where the matching doubt actually appears. Done that way, a throwaway Slack message becomes one of the most credible testimonials on your page.