UGC — customer photos, legally safe
In plain English
A photo of a real customer using your product will out-convert your professional product photography. That's consistently true and most shops know it.
What most shops get wrong is the legal part. Someone posts a lovely photo of your product on Instagram. You repost it, or worse put it on your product page. You didn't ask. That's someone else's copyrighted work being used commercially, and brands get billed for it regularly — sometimes for a lot.
"But they tagged us" is not permission. Neither is a comment saying "love it!" You need the person to actually agree that you can use their photo.
This screen is the system that keeps you safe. Every photo has a box recording whether you have permission. And the rule is enforced by the software, not by someone remembering: a photo without recorded permission cannot appear on your storefront, even if someone approved it.
So you get the conversion benefit of real customer photos without the risk of using them improperly.
How to use it
- Click "Growth Science" in the left-hand menu, then "UGC."
- Add a photo. Paste the image link, note who it's from, and which product it shows.
- Tick the permission box only if you actually have permission — a written reply, a signed release, or a submission form where they agreed to the terms.
- Review pending photos and mark each approved or rejected.
- Mark your best photos as "featured" — those can appear across your site, not just on one product.
- Check the dashboard counts to see how many approved photos are actually publishable.
⏱ ~10 min/week · 💳 Pro+ · 🎯 Real customer photos, without the legal risk
Why this matters for your business
Two things are true at the same time, and most shops act on only one of them.
The first: customer photos work. People trust other buyers more than they trust you, and a photo of your product in a real home, on a real person, in real light, answers questions your studio photography can't. Conversion lifts on product pages with genuine customer imagery are consistently large.
The second: using someone's photograph commercially without permission is copyright infringement. The person who took it owns it. Tagging your brand isn't a licence. There are agencies whose entire business is finding brands doing this and invoicing them, and the bills are not small.
Most shops resolve the tension by doing it anyway and hoping. That works until it doesn't.
This tool resolves it properly. You collect photos, you record whether permission exists, and the system refuses to publish anything without it. The safety isn't a policy someone has to remember on a busy Friday — it's a rule the software enforces every time.
What this typically unlocks
| What you get | Typical result |
|---|---|
| Conversion on pages with customer photos | Typically +15 to +30% |
| Risk of publishing an unlicensed image | Removed — enforced, not advisory |
| Time spent chasing permissions | Lower — it's recorded as you go |
| Content cost vs. studio shoots | Dramatically lower |
| Audit trail if challenged | Complete — permission recorded per photo |
What you actually get
The three states
| State | Meaning |
|---|---|
| Pending | Submitted, not yet reviewed |
| Approved | You've reviewed it and it's fine to use |
| Rejected | Not suitable — wrong product, poor quality, inappropriate |
The permission record
Separate from approval, and this separation is the important part.
| Permission | Approved | Can it go on your storefront? |
|---|---|---|
| ✓ Yes | ✓ Yes | Yes |
| ✓ Yes | ✗ No | No — not reviewed yet |
| ✗ No | ✓ Yes | No — and this is the case that saves you |
| ✗ No | ✗ No | No |
Row three is the whole point. Someone on your team can love a photo and approve it, and it still won't publish without recorded permission. Human enthusiasm can't override the legal check.
Featured photos
Approved, rights-cleared photos can be marked featured. Those appear more widely — across your site rather than only on the product they show — and sort to the top.
Use it for your genuinely best few: clear, well-lit, on-brand, showing the product in real use.
What counts as permission
| Counts | Doesn't count |
|---|---|
| A written reply agreeing you can use it | They tagged you |
| A signed release form | They commented positively |
| A submission form where they accepted terms | It's public on their profile |
| A review submission that included usage terms | They follow you |
A DM saying "sure, go ahead" is fine and is what most brands rely on. Save it. The record here is your note that it exists.
The safest route is collecting photos through a submission form where agreeing to the terms is part of submitting — then permission is captured at source and never needs chasing.
Your dashboard counts
| Count | What it tells you |
|---|---|
| Total | Everything in the library |
| Pending | Waiting for your review |
| Approved | Passed review |
| Featured | Your best, shown site-wide |
| With permission | How many are actually publishable |
Watch the gap between "approved" and "with permission." A big gap means your team is approving photos you can't legally use — a signal to fix how you collect permission, not how you review.
Security details worth knowing
Two protections that matter and cost you nothing:
- Only secure image links are accepted. Insecure links and anything that isn't a plain image address are rejected, which blocks a common category of malicious submission.
- Our servers never fetch the image. The link is stored and displayed to your browser. It's never followed server-side, which removes a whole class of security risk when you accept links from the public.
How it works (without the technical bits)
Real merchant scenarios
Scenario A — The invoice that didn't arrive
Setup. Apparel brand had been reposting customer Instagram photos on product pages for two years. No permissions recorded.
A competitor received a claim for the same practice — reportedly a five-figure settlement for a handful of images.
Audit of their own library: 340 customer photos in use. 11 had any kind of written permission.
Action. Pulled the 329 without permission. Contacted every photographer they could identify.
| Outcome | Count |
|---|---|
| Gave permission when asked | 187 |
| Never replied | 128 |
| Declined | 14 |
187 of them said yes immediately. They'd have said yes two years earlier if anyone had asked. The risk had been carried for nothing.
Now: every new photo goes through the library with permission recorded at submission.
Scenario B — Approval and permission are different
Setup. Homeware brand, new marketing assistant, told to "approve the good ones."
They approved 84 photos in an afternoon. All genuinely good. None had permission recorded, because nobody had explained that part.
What the system did. All 84 sat as approved-but-not- publishable. None reached the storefront.
How it was caught. The dashboard showed 84 approved and 0 with permission — a gap impossible to miss.
Why this matters. Under a system where approval alone published, all 84 unlicensed images would have gone live that afternoon. The separation caught a training gap before it became a legal one.
Scenario C — Collecting permission at source
Setup. Skincare brand chasing permissions by DM. Roughly 30% replied, and each took days.
Change. Added photo upload to their post-purchase review request, with a clear line — "tick here to let us use your photo on our site and social" — and terms on the form.
| DM chasing | Collected at source | |
|---|---|---|
| Photos collected per month | ~12 | ~90 |
| With permission | ~4 | ~90 |
| Staff time per month | ~6 hours | ~30 min |
Every photo arrived rights-cleared. No chasing at all.
Product page effect. Pages with customer photos converted 24% better than those without.
Scenario D — Featured photos on the wrong products
Setup. Merchant marked 40 photos as featured, thinking it just meant "good."
Effect. Featured photos appear site-wide, so a photo of a garden bench started showing on kitchenware pages.
Confusing for customers, and it diluted the effect on the pages where those photos genuinely belonged.
Fix. Cut featured down to six — genuinely brand-defining images that made sense anywhere. Left the rest approved and product-scoped.
Result. Conversion improved on both the featured photos' own pages and everywhere else.
The lesson. Featured means "represents the brand anywhere," not "we like it."
Best practices
✅ Collect permission at submission. Scenario C is the whole answer — never chase again.
✅ Watch the approved-vs-permission gap on your dashboard. A large gap means a process problem.
✅ Keep featured to a handful. Site-wide means site-wide.
✅ Save the actual permission message somewhere retrievable. The record here says it exists; keep the evidence.
✅ Prefer photos showing real use over photos of the product alone — you already have product photography.
✅ Review pending weekly. Submissions go stale and enthusiasm fades.
❌ Don't assume a tag is permission. It isn't, anywhere.
❌ Don't tick the permission box "to unblock things." That box is your legal defence; a false tick is worse than no system at all.
❌ Don't feature everything. Scenario D.
❌ Don't repost from social without asking. It's the exact practice this tool exists to replace.
Plan tiers
| Capability | Free | Starter | Pro | Agency | Enterprise |
|---|---|---|---|---|---|
| UGC library | — | — | ✓ | ✓ | ✓ |
| Permission record per photo | — | — | ✓ | ✓ | ✓ |
| Approve / reject moderation | — | — | ✓ | ✓ | ✓ |
| Featured photos | — | — | ✓ | ✓ | ✓ |
| Enforced publish gate | — | — | ✓ | ✓ | ✓ |
| AI-written captions | — | — | ✓ | ✓ | ✓ |
| Multi-store library | — | — | — | ✓ | ✓ |
Frequently asked
Is a tag or a mention really not permission? Correct — it isn't, in any major jurisdiction. Tagging shows they're a customer. Using their photograph commercially needs their agreement.
Is a DM saying "sure" enough? For most brands, yes, and it's what's normally relied on. Save the message. For high-value campaigns, a short written release is safer.
What if someone withdraws permission later? Untick the permission box. The photo stops being publishable immediately.
Can I import photos from Instagram automatically? Photos are added with their link and permission status. Automatic import would mean bulk-collecting images you don't have rights to — which is the problem, not the solution.
Why won't my approved photo appear? Almost certainly no permission recorded. Check the permission box on that photo.
What image links are accepted? Secure image addresses only. Insecure or non-image links are rejected automatically.
Do you store the actual image? No — the link is stored and shown to your visitors' browsers. Our servers never fetch it.
How many photos should I aim for? Enough for your top products to have a few each. Quality and relevance beat volume.
See also
- Growth Science overview — all eight tools
- Positioning — makes AI captions sound like you
- Reviews & CRO audit — collecting photos alongside reviews
- Urgency & social proof — other social-proof widgets
- Star rating — review display
- Social publishing — sharing rights-cleared photos
- Image optimizer — making them load fast
- GDPR & consent — the wider consent picture