You’ve designed a beautiful email. Now what? The Email Love plugin gives you multiple ways to export your work, from downloading raw code to pushing directly to your email service provider. The export dropdown now offers 40 destinations. Here’s an overview of every export option.
Export Methods
Download as HTML
Export your email as a standalone HTML file that you can open in a browser, send as a test, or import into any email platform manually. This is the most universal option.
- When to use: When your ESP doesn’t have a direct integration, when you need to share the code with a developer, or when you want to run the HTML through a third-party testing tool.
Download as MJML
Export the raw MJML source code. This is useful if you want to modify the MJML directly before compiling to HTML, or if your development team uses MJML in their workflow.
- When to use: When you have a developer who wants to customize the code further, or when you’re using a custom MJML build pipeline.
Push your email directly to your email service provider. The plugin connects via API and creates a template, campaign, or content block in your platform, ready to use. Pick your destination from the export dropdown (start typing to filter), save your API credentials once, and click Export.
Many integrations also support Updatable Templates: turn the toggle on and re-exporting the same Figma frame updates the existing template in place instead of creating a duplicate.
Webhook & Automation
Send your email to any URL or automation platform. The plugin POSTs the email (name, subject, preheader, and HTML) so you can wire it into your own systems.
- Custom Webhook: POST to any endpoint, with optional custom headers and extra JSON. A “Use Proxy” option routes through the Email Love backend to avoid browser CORS limits.
- Zapier and Make: pre-labeled flavors of the same webhook mechanism for those automation platforms.
Email Love Builder
Sync designs into Email Love Builder, Email Love’s companion product, in two ways:
- Design System Sync: push selected Figma components into a Builder Email Design System as reusable blocks.
- Email Template: create individual email templates in a Builder workspace, with subject and preheader.
See Sync your emails to Email Love Builder.
Supported Destinations
Bold destinations have a dedicated step-by-step guide. Where a platform isn’t yet linked, the export works the same way: pick it from the dropdown, save your API key, and export.
| Destination | Export Type |
|---|
| Klaviyo (HTML + Editable D&D) | Templates via API |
| Braze • Braze Content Block | Templates & content blocks via API |
| Iterable • Snippets | Templates via API (multi-locale supported) |
| Customer.io (Design Studio) | Editable drafts via API |
| HubSpot | Templates via API |
| Salesforce Marketing Cloud | Content blocks via API |
| Adobe Marketo | Templates via API |
| ActiveCampaign | Templates via API |
| Brevo | Templates via API |
| Mailjet | Templates via API |
| MailerLite • Classic | Draft campaigns via API |
| Postmark | Templates via API |
| Sailthru | Templates via API (updatable) |
| Emarsys | Emails via API |
| Salesforce Pardot (Account Engagement) | Templates via API (updatable) |
| SendGrid | Dynamic templates via API |
| SendX | Templates via API |
| Airship | Templates via API |
| MoEngage • MoEngage Content Block | Templates & content blocks via API |
| Netcore | Templates via API |
| OneSignal | Templates via API |
| Loops | Templates (images via zip) |
| Blueshift | HTML export (manual import) |
| Stripo | Templates via API |
| Parcel | Export to Parcel |
| MailChimp | Templates via API |
| Dotdigital | Templates via API |
| Shopify | Templates via API |
Webhook & automation
| Destination | Export Type |
|---|
| Custom Webhook | POST to any URL |
| Zapier | Webhook to Zapier |
| Make | Webhook to Make |
Code & Email Love Builder
| Destination | Export Type |
|---|
| HTML | Standalone HTML file |
| MJML | Raw MJML source |
| HTML Content Blocks (ZIP) | One standalone HTML file per top-level section, as a ZIP |
| Email Love Builder (Design System + Email Template) | Sync to the Builder |
Don’t see your platform, or it isn’t linked above? It still works the same way: pick it from the export dropdown, save your API key, and export. If you need a walkthrough, reach out and we’ll help.
Before You Export
Check for Issues
Always check your email structure before exporting. Use Copilot to catch structural issues, missing alt text, invalid nesting, and other problems that would cause rendering issues. Make it part of your workflow: Check → Fix → Export.
Preview
Use the Preview tab to check desktop and mobile rendering, font fallbacks, and dark mode appearance. The preview isn’t pixel-perfect but catches major issues.
Select Your Frame
Make sure you have the email frame selected (the top-level frame, not a component inside it). The plugin exports the entire selected frame.
Image Hosting
When you export, the plugin automatically uploads your images to the Email Love CDN and inserts the hosted URLs into your HTML. You don’t need to host images separately. Prefer your own storage? You can connect a custom provider (Amazon S3, Cloudflare R2, Google Cloud Storage, and more) and exports will upload images there instead. See the Image Hosting article for details on both options.
After Export
Once your email is exported or uploaded to your ESP:
- Send a test email to yourself and your team
- Test across email clients using Litmus, Email on Acid, or InboxMonster
- Check links, merge tags, and dynamic content
- Verify images load correctly
- Test on both desktop and mobile
