How it works

Compose, refine, export.

Three steps from a sentence to a production-ready email.

How AI email templates work, in four steps. Set up once, compose every email.

  1. Set up.

    Save your brand kit once — every email after uses it.

    Add what makes your sends look and sound like yours. Brand colors and fonts. Logo and image assets. A tone-of-voice profile so the copy actually reads like your brand, not like ChatGPT. The legal footer — business name, registered address, unsubscribe text — saved once and stitched onto every send. Once the kit is in, every composition the studio returns is brand-fit by default.

    EmailTemple studio brand-kit setup — colors, fonts, logo, voice and footer fields filled in for one brand.

    Your brand kit

    • Colors Saved
      Brand palette, dark-mode variants, accent rules.
    • Fonts Saved
      Web-safe stack with Google Fonts fallback.
    • Logo & assets Saved
      Wordmark, mark, hero imagery, social icons.
    • Brand voice Saved
      Tone profile so the copy sounds like you.
    • Legal footer Saved
      Business name, address, unsubscribe text.

    Multi-brand kits per account on the roadmap.

  2. Compose.

    Describe the email you want — your offer, your audience, your action.

    Type a brief in plain language. The studio composes a production-ready, dark-mode-safe HTML template — typographically tuned, brand-kit-aware, ESP-safe. ESP context is baked in: Mailchimp's merge-tag syntax, MailerLite's variable syntax, and ActiveCampaign's snippet system are handled at compose time, not bolted on at export. Your saved brand kit applies automatically.

    EmailTemple studio composing a welcome email from a plain-language brief — brand-kit-aware, dark-mode-safe HTML draft on the right.
    YOU 2:14 PM

    Welcome email for a paid newsletter. Audience: small-business operators who just paid $19/mo. Tone: warm, direct, not bro-y. Offer: "here's what you'll get," and a CTA to read the most-popular issue.

    STUDIO 2:14 PM

    Composing — drafting layout, applying brand kit, checking dark-mode contrast.

    STUDIO 2:14 PM

    ✓ Welcome email drafted. 312 words, 4-block layout, primary CTA in amber, footer with unsubscribe and brand line. Dark-mode rendering validated. Ready to refine.

  3. Refine.

    Iterate via chat — "tighten the second paragraph." "make the CTA bronze, not amber."

    Refinement is a conversation, not a settings panel. Each turn that calls the model counts as one generation; on the Free tier you have three a month. The studio keeps your brand kit, ESP, and prior turns in context — you don't re-explain. Subtle diff visualization shows what changed. Stop refining when the email reads like you wrote it.

    EmailTemple studio refine view — chat refinement turns showing CTA color and paragraph edits applied to the email draft.
    YOU 2:16 PM

    Make the CTA bronze, not amber. Tighten the second paragraph by ~30%.

    STUDIO 2:16 PM

    ✓ CTA color → bronze (#A57D2C). Para 2 trimmed from 84 → 58 words. Hierarchy preserved. Dark-mode contrast still passes WCAG AA.

    YOU 2:17 PM

    Add a one-line preheader: "the first thing you should read."

    STUDIO 2:17 PM

    ✓ Preheader added. 42 chars. Renders before the open in inbox previews.

  4. Export.

    One click to your ESP. Production-ready HTML, paste-or-import.

    Pick an export target. Live today: Mailchimp, MailerLite, ActiveCampaign — with Klaviyo, ConvertKit, Beehiiv and Ghost on the roadmap (and any other platform that allows custom HTML upload). The studio outputs ESP-specific HTML — merge tags resolved for Mailchimp, variable syntax for MailerLite, snippet-aware blocks for ActiveCampaign — so the import works the first time.

    EmailTemple studio export panel — one-click export to Mailchimp, MailerLite or ActiveCampaign with ESP-specific HTML output.

    Export to

    • Mailchimp Live
    • MailerLite Live
    • ActiveCampaign Live

    On the roadmap: Klaviyo, ConvertKit, Beehiiv, Ghost.

    Download HTML Copy to clipboard

A real session

What it actually looks like.

A welcome email for a paid newsletter. Three turns and an export. Total time: four minutes, two generations consumed.

YOU 2:14 PM

Welcome email for a paid newsletter. Audience: small-business operators who just paid $19/mo. Tone: warm, direct, not bro-y. Offer: "here's what you'll get," and a CTA to read the most-popular issue.

STUDIO 2:14 PM

Composing — drafting layout, applying brand kit, checking dark-mode contrast.

STUDIO 2:14 PM

✓ Welcome email drafted. 312 words, 4-block layout, primary CTA in amber, footer with unsubscribe and brand line. Dark-mode rendering validated. Ready to refine.

YOU 2:16 PM

Make the CTA bronze, not amber. Tighten the second paragraph by ~30%.

STUDIO 2:16 PM

✓ CTA color → bronze (#A57D2C). Para 2 trimmed from 84 → 58 words. Hierarchy preserved. Dark-mode contrast still passes WCAG AA.

YOU 2:17 PM

Add a one-line preheader: "the first thing you should read."

STUDIO 2:17 PM

✓ Preheader added. 42 chars. Renders before the open in inbox previews.

YOU 2:18 PM

Export to Mailchimp.

STUDIO 2:18 PM

✓ HTML exported, merge tags resolved (*|FNAME|*, *|UNSUB|*). Ready to paste into Mailchimp campaign.

Built for the quirks

Each ESP renders email differently. We know.

  • Mailchimp

    Merge tag syntax

    Variables like *|FNAME|* and *|UNSUB|* inserted automatically when you mention personalization in chat.

  • MailerLite

    Variable syntax

    Output uses {$name}-style variables and MailerLite-safe markup when MailerLite is the export target.

  • ActiveCampaign

    Snippet system

    AC-compatible HTML with inline styles where AC requires them. Automation-block-aware rendering.

Begin

Try it on a real email.

Three free generations a month, no card required.