Device previews
Review how email renders across devices and clients before signing off on a send.
Device previews help teams answer a simple question with real confidence: what will recipients actually see in the clients and viewports that matter to us?
Why teams use device previews
Use device previews when:
- the same email needs to look good across mobile and desktop clients
- stakeholders want visual approval before launch
- QA needs evidence that a rendering issue is fixed
- marketers are comparing campaign variants before send
What to review
Focus on the things that break real launches:
- layout shifts between clients
- image scaling and spacing problems
- CTA visibility and tap targets on mobile
- typography or fallback styling differences
- dark or light client behavior if relevant to your audience
Available render targets
Use the render target catalog to choose the email clients and device contexts that should be included in a device preview run.
Device preview target catalog
Current render targets for native email client previews. Availability can vary during maintenance or capacity changes.
| Client | OS | Credits |
|---|---|---|
| Apple Mail | macOS | 1 |
| Gmail | Android | 1 |
Recommended review flow
- Render the message in the device and client combinations that matter most.
- Check the hero, CTA, body copy, footer, and any legally required content.
- Fix the template or content if a high-impact rendering issue appears.
- Pair the visual review with Email audit when links and images also need validation.
Where this fits
- before campaign approval
- before transactional template releases
- after a bug fix to confirm the issue is actually resolved
- alongside Campaign Probe for live-campaign review