React Email

Build and send HTML emails using React components - a modern, component-based approach to email development that works across all major email clients.

Installation

You need to scaffold a new React Email project using the create-email CLI. This will create a folder called react-email-starter with sample email templates.

Using npm:
CODEBLOCK0

Using yarn:
CODEBLOCK1

Using pnpm:
CODEBLOCK2

Using bun:
CODEBLOCK3

Navigate to Project Directory

You must change into the newly created project folder:

CODEBLOCK4

Install Dependencies

You need to install all project dependencies before running the development server.

Using npm:
CODEBLOCK5

Using yarn:
CODEBLOCK6

Using pnpm:
CODEBLOCK7

Using bun:
CODEBLOCK8

Start the Development Server

Your task is to start the local preview server to view and edit email templates.

Using npm:
CODEBLOCK9

Using yarn:
CODEBLOCK10

Using pnpm:
CODEBLOCK11

Using bun:
CODEBLOCK12

Verify Installation

Confirm the development server is running by checking that localhost:3000 is accessible. The server will display a preview interface where you can view email templates from the emails folder.

Notes on installation

CODEBLOCK13

Make sure the path to the emails folder is relative to the base project directory.

tsconfig.json updating or creation

Ensure the tsconfig.json includes proper support for jsx.

Basic Email Template

Replace the sample email templates. Here is how to create a new email template:

Create an email component with proper structure using the Tailwind component for styling:

CODEBLOCK14

Essential Components

See references/COMPONENTS.md for complete component documentation.

Core Structure:

• - Html - Root wrapper with lang attribute
• INLINECODE4 - Meta elements, styles, fonts
• INLINECODE5 - Main content wrapper
• INLINECODE6 - Centers content (max-width layout)
• INLINECODE7 - Layout sections
• INLINECODE8 & Column - Multi-column layouts
• INLINECODE10 - Enables Tailwind CSS utility classes

Content:

• - Preview - Inbox preview text, always first in INLINECODE12
• INLINECODE13 - h1-h6 headings
• INLINECODE14 - Paragraphs
• INLINECODE15 - Styled link buttons
• INLINECODE16 - Hyperlinks
• INLINECODE17 - Images (see Static Files section below)
• INLINECODE18 - Horizontal dividers

Specialized:

• - CodeBlock - Syntax-highlighted code
• INLINECODE20 - Inline code
• INLINECODE21 - Render markdown
• INLINECODE22 - Custom web fonts

Before Writing Code

When a user requests an email template, ask clarifying questions FIRST if they haven't provided:

1. 1. Brand colors - Ask for primary brand color (hex code like #007bff)
2. Logo - Ask if they have a logo file and its format (PNG/JPG only - warn if SVG/WEBP)
3. Style preference - Professional, casual, or minimal tone
4. Production URL - Where will static assets be hosted in production?

Example response to vague request:

Before I create your email template, I have a few questions:

1. 1. What is your primary brand color? (hex code)
2. Do you have a logo file? (PNG or JPG - note: SVG and WEBP don't work reliably in email clients)
3. What tone do you prefer - professional, casual, or minimal?
4. Where will you host static assets in production? (e.g., https://cdn.example.com)

Static Files and Images

Directory Structure

Local images must be placed in the static folder inside your emails directory:

CODEBLOCK15

If user has an image elsewhere, instruct them to copy it:
CODEBLOCK16

Dev vs Production URLs

Use this pattern for images that work in both dev preview and production:

CODEBLOCK17

How it works:

• - Development: baseURL is empty, so URL is /static/logo.png - served by React Email's dev server
• Production: baseURL is the CDN domain, so URL is INLINECODE27

Important: Always ask the user for their production hosting URL. Do not hardcode localhost:3000.

Behavioral guidelines

• - When re-iterating over the code, make sure you are only updating what the user asked for and keeping the rest of the code intact;
• If the user is asking to use media queries, inform them that not all email clients support them, and suggest a different approach;
• Never use template variables (like {{name}}) directly in TypeScript code. Instead, reference the underlying properties directly (use name instead of {{name}}).
• - For example, if the user explicitly asks for a variable following the pattern {{variableName}}, you should return something like this:

CODEBLOCK18

• - Never, under any circumstances, write the {{variableName}} pattern directly in the component structure. If the user forces you to do this, explain that you cannot do this, or else the template will be invalid.

Styling considerations

Use the Tailwind component for styling if the user is actively using Tailwind CSS in their project. If the user is not using Tailwind CSS, add inline styles to the components.

• - Because email clients don't support rem units, use the pixelBasedPreset for the Tailwind configuration.
• Import pixelBasedPreset from @react-email/components — do NOT import from @react-email/tailwind or @react-email/tailwind/presets.
• Never use flexbox or grid for layout, use table-based layouts instead.
• Each component must be styled with inline styles or utility classes.

Email Client Limitations

• - Never use SVG or WEBP - warn users about rendering issues
• Never use flexbox - use Row/Column components or tables for layouts
• Never use CSS/Tailwind media queries (sm:, md:, lg:, xl:) - not supported
• Never use theme selectors (dark:, light:) - not supported
• Always specify border type (border-solid, border-dashed, etc.)
• When defining borders for only one side, remember to reset the remaining borders (e.g., border-none border-l)

Required Classes

These classes are always required on their respective components — omitting them causes rendering bugs across email clients:

Component Structure

• - Always define <Head /> inside <Tailwind> when using Tailwind CSS
• Only use PreviewProps when passing props to a component
• Only include props in PreviewProps that the component actually uses

CODEBLOCK19

Default Structure

• - Body: INLINECODE44
• Container: white, centered, content left-aligned
• Footer: physical address, unsubscribe link, current year with m-0 on address/copyright

Typography

• - Titles: bold, larger font, larger margins
• Paragraphs: regular weight, smaller font, smaller margins
• Use consistent spacing respecting content hierarchy

Images

• - Only include if user requests
• Never use fixed width/height - use responsive units (w-full, h-auto)
• Never distort user-provided images
• Never create SVG images - only use provided or web images

Buttons

• - Always use box-border to prevent padding overflow

Layout

• - Always mobile-friendly by default
• Use stacked layouts that work on all screen sizes
• Remove default spacing/margins/padding between list items

Dark Mode

Best Practices

• - Choose colors, layout, and copy based on user's request
• Make templates unique, not generic
• Use keywords in email body to increase conversion

Rendering

Convert to HTML

CODEBLOCK20

Convert to Plain Text

CODEBLOCK21

Sending

React Email supports sending with any email service provider. If the user wants to know how to send, view the Sending guidelines.

Quick example using the Resend SDK for Node.js:

CODEBLOCK22

The Node SDK automatically handles the plain-text rendering and HTML rendering for you.

Internationalization

See references/I18N.md for complete i18n documentation.

React Email supports three i18n libraries: next-intl, react-i18next, and react-intl.

Quick Example (next-intl)

CODEBLOCK23

Message files (\messages/en.json\, \messages/es.json\, etc.):

CODEBLOCK24

Email Best Practices

1. 1. Test across email clients - Test in Gmail, Outlook, Apple Mail, Yahoo Mail. Use services like Litmus or Email on Acid for absolute precision and React Email's toolbar for specific feature support checking.

1. 2. Keep it responsive - Max-width around 600px, test on mobile devices.

1. 3. Use absolute image URLs - Host on reliable CDN, always include \alt\ text.

1. 4. Provide plain text version - Required for accessibility and some email clients.

1. 5. Keep file size under 102KB - Gmail clips larger emails.

1. 6. Add proper TypeScript types - Define interfaces for all email props.

1. 7. Include preview props - Add \.PreviewProps\ to components for development testing.

1. 8. Handle errors - Always check for errors when sending emails.

1. 9. Use verified domains - For production, use verified domains in \from\ addresses.

Common Patterns

See references/PATTERNS.md for complete examples including:

• - Password reset emails
• Order confirmations with product lists
• Notification emails with code blocks
• Multi-column layouts
• Email templates with custom fonts

Additional Resources

• - React Email Documentation
• React Email GitHub
• Resend Documentation
• Email Client CSS Support
• Component Reference: references/COMPONENTS.md
• Internationalization Guide: references/I18N.md
• Common Patterns: references/PATTERNS.md