# How to remix an email template and export it to your ESP

Canonical: https://brew.new/blog/how-to-remix-a-real-brand-email-template-and-export-it-to-your-esp
Author: Philip Sørensen
Published: 2026-10-11
Updated: 2026-10-11

Remixing an email template means rebuilding a layout another brand already shipped on your own brand. Someone else has already decided the sections, the image placement and the footer, and tested it on a real list.

Brew's [template gallery](/browse/templates) holds about 5,100 of those emails from 491 brands. Pick one whose structure fits, rebuild it with a prompt, and export it to the ESP you already use.

![The path from a gallery template to a remixed email on your brand to a template in your ESP.](/images/blog/template-remix-export-flow.png)

*Pick a layout, rebuild it on your brand, export it to your ESP.*

## Key takeaways

- The gallery holds about 5,100 real emails from 491 brands, filterable by category or brand, or searchable by meaning.
- A remix keeps layout, spacing, typography and button style, and swaps in your logo, colors, copy, links and images.
- Merge tags do not carry over. Add personalization in your ESP's syntax after export.
- Export pushes the template to 11 ESPs, including Klaviyo, Mailchimp and HubSpot, with each platform's unsubscribe tag swapped in.
- Run Brew's audit before export, then send a test from the ESP, because that is the version readers get.

## Finding a layout worth borrowing

The gallery gives you three ways to narrow it down:

- **Category pills** such as newsletter, product launch, welcome, cart abandonment, event invitation and order confirmation, each with a count
- **The brand filter**, if you already know whose emails you like
- **Search**, which matches on meaning. "Founder-written monthly changelog with a video" beats "changelog"

The order reshuffles hourly. The [templates docs](https://docs.brew.new/create-emails/templates) have more detail.

Ignore the colors. They get replaced with everything else except the structure, so judge the shape. My checks:

- **Count your sections.** Three features to announce fit a template with three feature blocks better than a single-hero layout.
- **Count the buttons.** One call to action adapts more easily than six product tiles, unless you have six products.
- **Check how much lives in images.** A headline baked into a picture is harder to make accessible and harder to edit.
- **Read it on your phone.** Each template has a page at `brew.new/templates/{brand}/{title}` with a full preview.

The template page also shows how many times it has been remixed and credits the designer.

## A worked example: a monthly product update

In the newsletter category you will find [Paper's September changelog](https://brew.new/templates/paper/new-in-paper-faster-performance-agent-reliability-opacity), which is worth studying:

1. A one-line greeting from a named person, then two sentences on what the month was about
2. A large video thumbnail with a play button, linking to a short walkthrough
3. Four feature sections, each a bold heading and a short paragraph, three with a product image
4. A bulleted list of smaller improvements, one line each
5. Two tutorial cards side by side
6. A one-line "up next" teaser and a personal sign-off that invites replies

Big launches get a picture, small fixes get a bullet, and the personal open and close make it read like a note from a person.

To remix it, open the template and write the brief in the prompt box:

> Use this for our October update, signed by our CEO. Feature sections for Slack approvals, Intelligent Send and the new email audit. Put the smaller fixes in the bullet list. Drop the tutorial cards. One button to the changelog.

Brew keeps the shape, from greeting to sign-off, writes copy for your brief, applies your logo, colors and footer, and recreates every image in your brand's style.

A recreated image is not a screenshot of your product. For feature announcements, swap in real screenshots before sending. Readers notice.

## Set up your brand before the first remix

A remix is only as on-brand as what Brew knows about you. Check two pages first:

- **Brand** holds your details, links, logo and the files `email-design.md` and `image-style.md`
- **Email design** holds the design system every generation follows

[Our post on email-design.md](/blog/email-design-md) explains what goes in it and how Brew extracts one from your site. [Importing approved email designs](/blog/import-existing-email-designs-ai) gives Brew a much better start than a website alone. Without a design system, a remix looks like a generic copy of the original.

## What carries over and what does not

| From the template | In your remix |
| --- | --- |
| Layout, section order, spacing | Kept |
| Typography and button styles | Kept |
| Logo, primary color, footer | Replaced with yours |
| Copy and links | Rewritten for your brand and brief |
| Images | Recreated in your brand's style |
| Merge tags | Not carried over |
| Light or dark look | Your design system's theme if set, otherwise the template's |

Three details catch people out.

The remix always builds for the active brand. Name a different brand in the prompt and Brew asks you to switch brands in the top-left and remix again.

The original images never carry over, so you won't ship another company's product photos under your logo.

If the original said "Hi {first_name}", your remix won't. Personalize in your ESP after export.

## The prompt box and the chat

Signed out, submit a brief in the prompt box and Brew saves the text, asks you to sign in and returns you to the template. Attached files are not kept.

Signed in, opening a template starts a chat in the side panel with the template attached. A prompt saved before sign-in goes back into the composer unsent. Each chat holds one template, and leaving the page detaches it.

An empty prompt works too, using what Brew knows about you. It's a quick way to test a layout. Then keep iterating in the same chat: "tighten the intro to two sentences", "swap sections two and three", "make the button full width on mobile".

## Remixing a whole sequence

The [flows gallery](/browse/flows) has 170+ real multi-email sequences, such as signup and newsletter welcome series of 3 to 12 emails. Remixing one builds the sequence as an automation with the same steps and waits, every email rebuilt on your brand.

By default the automation starts on signup or subscribe. Name an event or audience in the prompt to replace that. Audience-started automations run from the **Run** button on the canvas. Publishing needs a verified sending domain. [Email flows](/blog/email-flows) covers flow design.

## Check it before it leaves Brew

Open **Send**, then the **Audit** tab. It catches placeholder links, missing alt text and HTML large enough for Gmail to clip. The [pre-send QA checklist](/blog/pre-send-email-qa-checklist) explains each check.

Findings don't block export, but they travel with the template and are harder to spot in the ESP. Clear them in Brew first.

## Exporting to your ESP

Connect your ESP once from **Integrations**. Then, on the email:

1. Click **Send** in the toolbar.
2. Under Email actions, choose **Export Template**.
3. Pick the destination. Unconnected platforms appear greyed out and link to their integration page.
4. Fill in the name, plus subject and preview text where the platform asks.
5. Click **Export**.

Brew pushes the template through the provider's API. Supported platforms:

| | | |
| --- | --- | --- |
| Klaviyo | Mailchimp | HubSpot |
| Braze | Iterable | Brevo |
| Mailjet | SendGrid | Postmark |
| Mailgun | OneSignal | |

Brew converts the HTML for each platform and swaps in its own unsubscribe tag, for example `*|UNSUB|*` for Mailchimp and `{% unsubscribe_link %}` for Klaviyo. The footer's unsubscribe link works on your first send, no HTML edits.

When it finishes, **See template** opens your ESP in a new tab: the template itself for Brevo, Braze, Mailchimp, Iterable, Postmark and SendGrid, the template list or library for Klaviyo, Mailjet, OneSignal, Mailgun and HubSpot. In HubSpot, look in the `brew-exports` folder. If the connection lacks details for that link, such as a Mailchimp data center or HubSpot portal, the button is hidden. The export still happened.

Platform differences worth knowing:

- **Klaviyo and Mailchimp** receive name and HTML only. Set the subject on the campaign in the ESP.
- **Brevo and Mailjet** need an active sender. With one, Brew picks it. With several, you choose in the export form.
- **Braze** has an option to inline CSS before export.

Setup docs: [Klaviyo](https://docs.brew.new/integrations/export/klaviyo), [Mailchimp](https://docs.brew.new/integrations/export/mailchimp) and [HubSpot](https://docs.brew.new/integrations/export/hubspot).

## In your ESP, before you send

1. Set the subject and preview text if the platform didn't take them at export.
2. Add personalization in the ESP's merge syntax.
3. Send a test from the ESP itself. It adds its own tracking and footer handling, and that is the version readers get.
4. Check that the test's unsubscribe link points to the ESP's unsubscribe page.

## Other ways to get the HTML out

For platforms not on the list, paid plans get **Copy HTML**, **Export HTML** for a download, and **Export PDF** for reviews, all in the email's **More actions** menu.

Developers can export through the API with `POST /v1/emails/{emailId}/export`. It supports a dry run, uses no credits and creates the template without sending anything.

## Frequently asked questions

### Is it okay to borrow another brand's layout?

The remix keeps the structure and replaces the brand, so the logo, colors, copy, links and images are yours. A hero followed by three feature rows is a common pattern. Still, write your own copy and claims, and don't imitate another company's look so closely that readers could confuse the two.

### Can I put my own emails in the gallery?

Yes. Once an email has finished rendering and has a preview, choose **Make public** from its **More actions** menu. You can make it private again later.

### Why does Customer.io not appear in the export list?

Brew's Customer.io integration handles sending, not template export. On paid plans, download the email with **Export HTML** and paste it into Customer.io.