Check one email
Paste rendered HTML, inline its CSS and review static issues. Download the output for your own sending provider.
Open CSS PlaygroundStart here · no account needed
What do you need to check?
Choose the workflow closest to your email. Start with synthetic examples, then use your rendered output. Browser previews send HTML for checks; they do not send email or approve a release.
Protect business content and links
Check expected totals, roles, expiry text and conditional sections. Try receipt, invitation or reset examples, then edit their requirements.
Check email requirementsCheck every template variation
Check business data across currencies, languages and branches. Use workflow or React Email/MJML examples, repair your source and compare the next preview.
Check template scenariosReview target-client evidence
Choose email clients and inspect recorded CSS support, test dates and conditions. Review actual layouts separately.
Review client compatibilityFrom a check to a repeatable workflow
- Review the findings and repair your source template.
- Render the same scenarios again. On the matrix page, use Update rendered output to keep your selected rules and required IDs, then preview again.
- Download the readable report for review. Download the separate input manifest when you need the rendered HTML for reuse. Review both before sharing.
- For React Email or MJML, download a complete source + CI ZIP from the matrix page. For an existing repository, use its custom GitHub setup.
When you need shared rules and CI
Projects record rule snapshots and release evidence. Saved business rules and matrix CI checks require Pro or Enterprise, a configured project and repository credentials. Check current checkout availability on Pricing before planning a paid rollout.
Static checks and recorded compatibility evidence do not prove Gmail/Outlook rendering, delivery or inbox placement. This Beta has no uptime SLA.