How to Share Email Previews with Clients Without Sending Test Emails
The Problem with Sending Test Emails
If you work in email design or development — whether at an agency, in-house, or as a freelancer — you've probably experienced the approval workflow that goes like this: you finish an email template, send a test to the client, the client opens it on their phone in Gmail, sees something that doesn't quite look right due to a font fallback, and replies that "the font looks different from the mockup." Then begins a back-and-forth where you're trying to understand what they're seeing, they're struggling to describe it, and you're not sure if it's a real bug or a client-side rendering difference that doesn't affect real subscribers.
This workflow has several fundamental problems:
- Context collapse: The client sees the email in one specific client (whatever they use), not the full cross-client picture. A broken render in Outlook goes undetected because the client doesn't use Outlook.
- Slow iteration: Every change requires a new test send. Even small copy edits mean another email in their inbox.
- Inbox pollution: Multiple test emails clutter the client's inbox and make it hard to know which version is current.
- Unrepresentative feedback: Clients give feedback based on their personal device and email setup, not on how real subscribers will see it.
- Professionalism signals: Receiving a barrage of half-finished test emails makes your work process feel disorganized, even if the final result is excellent.
The solution is shareable preview links — a direct URL that shows cross-client renders of your email to anyone with the link, no account required.
What Makes a Good Email Preview Link
Not all preview links are equal. A useful client-facing preview link should:
- Show multiple email clients simultaneously — not just one. The client can see how it looks in Gmail, Outlook, Apple Mail, and mobile clients all at once, giving them a realistic picture of what their subscribers will experience.
- Include both desktop and mobile renders — most email opens happen on mobile. A preview that only shows desktop is missing half the story.
- Require no account or login to view — friction for the client means delayed feedback. They should be able to click the link and immediately see the renders without creating an account.
- Show the current version — if you update the email, the preview link should either update or clearly show the version date so everyone knows they're looking at the right thing.
- Load quickly — clients have short patience. A preview that takes 30 seconds to load will be abandoned.
How Postdrop.io Makes This Effortless
This is the workflow where Postdrop.io is at its best. Here's how the process works:
- Build or paste your email in Postdrop.io. The integrated editor gives you a live preview as you code, and handles CSS inlining automatically.
- Generate cross-client renders. Postdrop renders your email across Gmail (web, iOS, Android), Outlook (multiple versions), Apple Mail, iOS Mail, Samsung Mail, and other major clients. The renders update in real time as you make changes.
- Click "Share Preview" to generate a shareable link. One click creates a public URL that shows all your cross-client renders to anyone who visits it — no login, no account required.
- Send the link to your client. Paste it in an email, a Slack message, a project management tool — anywhere. The client clicks the link and sees exactly how the email renders across all the clients you've chosen to include.
The client sees the same cross-client render panel you see. They can toggle between email clients, switch between desktop and mobile, and give specific, informed feedback: "The CTA button looks great in Gmail but can you check Outlook 2019?" That's far more useful feedback than "the font looks different."
Building an Approval Workflow Around Preview Links
A structured approval workflow built around preview links looks like this:
Phase 1: Design Review
Send the preview link when the email is visually complete but before any copy review. Ask specifically for visual feedback: "Does this match the brand guidelines? Does the layout work on mobile? Any visual changes before we finalize?"
By separating visual review from copy review, you avoid getting entangled in both simultaneously. Clients tend to focus on copy when they see it in a realistic email context — setting up a dedicated design review stage first keeps the feedback focused.
Phase 2: Copy Review
Share a preview link (or a Google Doc) for copy review. Mark this round explicitly: "This is copy review only — please focus on the text and messaging, not the layout or design, which were approved in the previous round."
Phase 3: Final Approval
Send a final preview link with all changes incorporated. Request explicit written approval ("Does this look good to send?") rather than assuming silence means approval. The preview link serves as a record of exactly what was approved and when.
When to Use Test Sends
Preview links replace most test sends, but test emails remain useful for specific checks:
- ESP-specific rendering: After importing your HTML into Mailchimp or Klaviyo, send a test within the ESP to catch any issues introduced by the import (tracking link wrapping, CSS re-processing, etc.).
- Personalization verification: Confirm that merge tags render correctly with real subscriber data, not just placeholder values.
- Link checking: Click every link in a test send to verify they all redirect correctly through your ESP's tracking system.
- Final pre-send check: One test email to yourself or a team member immediately before the real send, as a final sanity check.
Communicating Preview Links to Clients
When sending a preview link, provide context that helps the client review it effectively:
Hi [Client],
Here's the preview of the June newsletter across email clients:
[Postdrop.io preview link]
Things to check:
- How it looks on mobile (toggle to iOS Mail or Gmail iOS in the preview)
- The CTA button at the bottom — does the color match your brand guidelines?
- Any copy you'd like to adjust
Please reply with feedback by [date] and I'll have the final version ready for send by [send date].
Thanks,
[Your name]
Providing specific things to check focuses their review and surfaces the feedback that actually matters. Without guidance, clients tend to give vague feedback ("looks good" or "can we change something but not sure what"). Specific prompts lead to specific, actionable responses.
The shift from test-email-based approvals to preview-link-based approvals is one of the highest-leverage workflow improvements available to email developers and designers. It saves time, reduces friction, produces better feedback, and presents your work professionally. If you're still doing approval rounds via test emails, try the Postdrop.io preview link workflow on your next project — the difference is immediately apparent.