Every SaaS reinvents the same 15 emails. Welcome. Verify. Magic link. Password reset. Receipt. Trial ending. Each one takes a day to design, another day to bulletproof against Outlook, and then you find out Gmail's dark mode is broken on the CTA button. This pack does all of that work, in three formats, with working senders for the five most common services.
30 production-ready email templates across two categories — transactional (welcome, verify, magic link, password reset, receipts, invoices, trial-ending, payment-failed, team invite, etc.) and marketing (onboarding sequence, digest, product update, newsletter, promo, webinar invite + reminder, case study, re-engagement, referral, milestone, NPS, churn win-back). Every template is mobile-responsive, Outlook-safe (table-based + MSO conditionals around the CTA button), and dark-mode aware.
Three formats per template: a typed React Email TSX component, a MJML source file, and a pre-inlined HTML file. Same designed email — you pick the format by your stack (Next.js / ESP / anything else).
Five working integration examples: Resend (passes the React component directly), Postmark, Mailgun, AWS SES (SDKv3), and Nodemailer (generic SMTP — works with OpenLiteSpeed/CyberPanel, Postfix, Brevo, Mailtrap, anything that speaks SMTP). Each is a self-contained TypeScript module — copy it into your project, set the env vars, send your first email in under 10 minutes.
Local preview server: pnpm preview in /preview-server opens React Email's dev server at localhost:3000 with all 30 templates pre-loaded. Iterate on copy and design without an actual send.
Designed deliverability PDF: a real guide covering SPF / DKIM / DMARC setup, the deliverability signals that get you flagged, when to pick React Email vs MJML vs HTML, a CAN-SPAM / GDPR compliance checklist, and the full 30-template visual index. Not filler — the thing you'd actually want before going to production.
<table> layouts and Outlook's VML buttons and decided life is too short.Sending services (you bring your own — Resend, Postmark, Mailgun, SES, or SMTP). DNS setup (we explain SPF / DKIM / DMARC in the guide; you set the records). A web UI for marketers to edit copy without code (this is a code pack — pair with a CMS if your team needs that workflow).
All three — every template ships in React Email (TSX, type-safe props using @react-email/components), MJML (4.x source, compiles with the mjml CLI or any MJML-accepting ESP), and pre-inlined HTML (table-based layout, inline styles, MSO conditionals, dark-mode media query). The three produce the same designed email — you pick the format that matches your stack, not the look.
Yes — Outlook compatibility is the #1 cross-client failure point and is what most of the work in this pack went into. Every template uses table-based layout, and every CTA button is wrapped in an MSO conditional that produces a VML button for Outlook (so it renders as a real colored button, not blue underlined text). The HTML files are also pre-inlined so Outlook's older renderers don't have to interpret a <style> block.
Yes — a preview server is included in /preview-server/. Run `pnpm preview` and React Email's dev server starts at localhost:3000 with all 30 templates pre-loaded in the sidebar. Each renders live; edit any template's TSX in /templates/<slug>/react-email/ and re-preview to see the change. There's also a per-template thumbnail PNG in /templates/<slug>/preview/.
Working integration examples are included for Resend (passes the React component directly — the simplest setup), Postmark, Mailgun, AWS SES (SDK v3), and Nodemailer (generic SMTP — works with OpenLiteSpeed/CyberPanel, Postfix, Brevo, Mailtrap, anything that speaks SMTP). The pre-compiled HTML format works with literally any service that accepts an HTML string.
Yes — the license covers unlimited personal AND client work. Use the templates in projects you deliver to clients, customize the branding for each, bill normally. The only restriction is you can't resell this pack itself as a competing email template pack. See LICENSE.txt for the exact terms.
Every template's footer includes an unsubscribe placeholder and a physical-address line — both required under CAN-SPAM and many other jurisdictions. The deliverability PDF guide has a full section on CAN-SPAM, GDPR, and CASL requirements plus the difference between transactional and marketing emails for opt-in purposes. You're responsible for actually wiring up a working unsubscribe handler and the real physical address; we give you the slots.
The deliverability guide covers SPF, DKIM, and DMARC — the three records Gmail's bulk-sender policy requires for senders doing more than 5,000 emails/day to Gmail addresses. We also cover one-click unsubscribe via the List-Unsubscribe header (also required for high-volume senders). The pack doesn't auto-set your DNS — that's on your domain — but the guide is enough to get it right the first time.
Yes — each format exposes the accent as a single value near the top of every file. Change one hex value per template, or find-and-replace across the pack. For more invasive customization (logo, footer copy, heading font), the per-template README points to the exact spot to edit in each format.
