We screenshot your email across providers

Email clients render HTML inconsistently. A template that looks great in Gmail can break in Outlook (hello, conditional comments and image scaling), and a transactional receipt in ProtonMail can display as a wall of fallback text. Screenshots across providers, captured for every placement test, are the fastest way to catch it.

What screenshot inspection catches that scoring doesn't

• Broken fallback fonts — a brand font not allowed by the provider, rendered as Times.
• Oversized images on Outlook desktop (image scaling rules).
• CTA button outlines that collapse on dark backgrounds.
• Unrendered CSS — gradients or custom properties the provider strips.
• Tracking pixels that render as a visible 1×1 white dot on certain clients.
• Conditional Outlook HTML that triggers unexpected fallback paths.
• Right-to-left / bidirectional text rendering bugs.

How it works

• Seed mailbox receives the message.
• A rendering worker logs in (using service credentials), opens the message in the web client.
• Screenshot captured deterministically at specified viewports.
• Image + metadata attached to the placement report.

Use cases

• QA before a campaign goes out — “does it look right everywhere?”
• Regression when a designer changes a template — diff screenshots pre/post.
• Client-facing proof for agencies — “here is what the email looks like in their provider”.
• Debugging customer complaints — “my email is broken” means little until you see the screenshot.

FAQ