> ## Documentation Index
> Fetch the complete documentation index at: https://help.emaillove.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Export Figma emails to Mailchimp

> Export email designs from Figma into your Mailchimp saved templates with the Email Love plugin.

The Email Love Figma Plugin pushes your email designs straight into Mailchimp's saved templates. No copy-paste required. Save your Mailchimp API key once, click Export, and the template shows up in your Mailchimp account ready to use in a campaign.

[Download the Email Love Figma Plugin here](https://www.figma.com/community/plugin/1387891288648822744/email-love-html-email-builder)

## Prerequisites

Before you begin, make sure you have:

* An active [Mailchimp](https://mailchimp.com/) account
* A Mailchimp **API key**. See [About API keys](https://mailchimp.com/help/about-api-keys/).
* The Email Love Figma plugin installed
* At least one email designed in Figma using the plugin
* An Email Love Footer with an Unsubscribe link in your design (required for export)

<Steps>
  <Step title="Open the Export Panel">
    1. Select the email frame you want to export in Figma
    2. Click the **Export** button in the top right of the plugin
    3. Pick **MailChimp** from the export dropdown. You can also start typing "mail" to filter the list.

    The dropdown is alphabetised, so MailChimp sits in the M section of the A–Z list of ESPs underneath the HTML, MJML, and Email Love Builder options.
  </Step>

  <Step title="Connect Your Mailchimp Account">
    The first time you export to Mailchimp you'll see the API key form. Fill in:

    1. **API Key**: paste your Mailchimp API key ([find it here](https://mailchimp.com/help/about-api-keys/))
    2. **API Key Name**: a friendly name for these credentials (e.g. "Marketing, Production"). You can save multiple Mailchimp keys and switch between them.
    3. Click **Set API Key**

    Your API key is encrypted and stored in the plugin so you only have to enter it once per connection. To swap to a different Mailchimp account later, click **Change API key** in the same panel.

    <Warning>
      Paste the **whole** API key, including the data center suffix after the last hyphen (for example `...-us14`). The plugin reads that suffix to work out which Mailchimp server to call. A key with the suffix stripped off will fail to connect.
    </Warning>
  </Step>

  <Step title="Export Your Email">
    1. With MailChimp selected and your credentials loaded, click **Export**
    2. The plugin sends your HTML to the Email Love backend, which calls Mailchimp's Marketing API to create the template
    3. On success you get a **Successfully exported!** toast. Your template is now in Mailchimp.

    The template name in Mailchimp is your Figma frame name with the export date appended, so `Spring Sale` becomes `Spring Sale_9/17/2026`. Rename the frame before exporting if you want a specific title.
  </Step>

  <Step title="Use Your Template in Mailchimp">
    1. Log into [Mailchimp](https://login.mailchimp.com/) and open the account you exported to
    2. Go to **Campaigns** > **Email templates**, then open the **Saved** tab
    3. Find the template you just exported, named after your Figma frame
    4. Use it in any campaign. When building a new email you'll also find it under the **Saved templates** tab on the template picker.
  </Step>
</Steps>

## Every Export Creates a New Template

Mailchimp exports always create a new saved template. There's no **Enable Updatable Templates** option for Mailchimp, so re-exporting the same Figma frame gives you a second template rather than overwriting the first.

Because the export date is part of the template name, repeated exports are easy to tell apart, but they do stack up. Delete the old ones in Mailchimp when you no longer need them. See [Updatable Templates](/plugin/export/updatable-templates) for the platforms that do support in-place updates.

## Editing Your Template in Mailchimp

An exported template is plain HTML, so Mailchimp's editor treats it as a code template rather than a drag-and-drop layout. You can edit the HTML in Mailchimp, but for ongoing changes we recommend editing in Figma and re-exporting so your Figma file stays the single source of truth.

## What the Plugin Does for You

* **Pushes the template to Mailchimp** via the Marketing API using the saved API key, reading the data center from the key itself
* **Converts the unsubscribe link**: the Email Love Footer's unsubscribe link becomes Mailchimp's `*|UNSUB|*` merge tag. See [Unsubscribe Links](/plugin/links/unsubscribe).
* **Hosts your images** so they render correctly when Mailchimp sends the email
* **Removes Google Fonts `@import` rules**, which Mailchimp does not support. Your type falls back to the fallback stack you set in Figma, so pick one you're happy to send.
* **Generates responsive, deliverable HTML** that renders consistently across major email clients
* **Stores credentials per key**: switch between multiple Mailchimp accounts from the same Figma file via the **API Key Name** dropdown

## Troubleshooting

**Authentication errors / 401:** Check the **API Key** is copied in full from your Mailchimp account, including the `-usNN` data center suffix. Re-open **Change API key** to update it. If the key was revoked or regenerated in Mailchimp, generate a new one and save it again.

**Connection fails and the error mentions the server or an unknown host:** This is almost always a key pasted without its data center suffix. The plugin derives the Mailchimp server from the text after the last hyphen in the key, so the suffix has to be there.

**Wrong account / template went somewhere unexpected:** Each Mailchimp API key is scoped to one account. If you have several (for example Production and Staging), make sure you saved the right key under a clear connection name, then switch between them via the **API Key Name** dropdown.

**Custom fonts aren't showing:** Mailchimp doesn't support the `@import` rule the plugin uses to load Google Fonts, so the plugin strips it on export. This is expected. Recipients see the fallback font, which is also what most Outlook and desktop clients would have shown anyway.

**I can't find the template in Mailchimp:** Look under **Campaigns** > **Email templates** > **Saved**, not the pre-built template gallery. The name has the export date appended, so sort by most recent.

**Duplicate templates piling up:** Expected. Mailchimp exports always create a new template. Delete the ones you don't need in Mailchimp.

**Unsubscribe link not working:** Make sure your design includes an Email Love Footer with an Unsubscribe link pointing to exactly `https://unsubscribe.com`. Without it there's nothing for the plugin to convert to `*|UNSUB|*`.

**Need help?** Join our [Discord community](https://discord.com/invite/ANv9PjVdzP) or reach out to our support team at [hello@emaillove.com](mailto:hello@emaillove.com) for assistance.

## Related Articles

* [Export Overview](/plugin/export/overview): Understand all export options and how the plugin converts your Figma design to HTML
* [Unsubscribe Links](/plugin/links/unsubscribe): How the plugin converts unsubscribe links to each ESP's merge tag
* [Updatable Templates](/plugin/export/updatable-templates): Which platforms support overwriting a template in place
* [Image Hosting](/plugin/images/hosting): How the plugin handles image hosting during export