Figma to Klaviyo: 4 ways to move an email design (2026)
7 October 2026 · 7 min read
You have a finished email in Figma. Now it has to become a Klaviyo template that sends looking the same as the design. There are four ways to get it there, and they trade off speed, how editable the result is in Klaviyo, and how closely it matches what you designed.
The short answer
| Method | What you get in Klaviyo | Cost | Best for |
|---|---|---|---|
| Rebuild it in Klaviyo | Native Klaviyo blocks: editable text, buttons and images | Free | Text-heavy emails, or a few emails a month |
| Klaviyo’s Figma plugin | Your Figma frames as images in Klaviyo’s image library; you assemble the template | Free | Teams happy to slice in Figma and lay out in Klaviyo |
| An HTML export plugin | A coded HTML template, built from the plugin’s own components | Plugin subscription | Designs built for the plugin from the start, edited in code |
| Carvr | A native drag-and-drop template, sliced, compressed, linked, with alt text | Free for 5 a month; paid from $48 | Finished, image-led designs, agencies sending many a week |
If the email is mostly images and you send a lot of them, auto-slicing is the fastest route. If it is mostly live text and product blocks, build it in Klaviyo. The sections below explain each one.
1. Rebuild the design in Klaviyo’s editor
The manual route. Export the images from Figma at 2x (1200px wide for a 600px email), upload them to Klaviyo, then recreate the layout block by block in the drag-and-drop editor: images, text, buttons, spacers and columns. Add a link and alt text to every image, then test on desktop and mobile.
Good: everything is native, so copy can be edited in Klaviyo later and personalisation works anywhere. Not so good: it is the slowest route, and rebuilt emails drift from the design, because Klaviyo’s blocks bring their own fonts, padding and spacing.
2. Klaviyo’s own Figma plugin
Klaviyo has an official, free Figma plugin. You select frames, groups or components in Figma and send them to your Klaviyo image library as PNG or JPG images, in batches and to more than one Klaviyo account. It saves the export and upload steps, and it is the simplest option if you already cut the design into separate frames yourself.
Good: free, official, and easy to set up. Not so good: it moves images, not emails. You still decide where to slice, and you still build the template, add the links and write the alt text in Klaviyo. It sends to Klaviyo only.
3. An HTML export plugin
Plugins such as Emailify, Email Love and Marka turn a Figma design into a coded HTML email. The design has to be built their way: from the plugin’s own components (Emailify, Email Love) or with Auto Layout (Marka). The result is an HTML template you import into Klaviyo, or push with the plugin’s integration.
Good: real text throughout, responsive layouts, and one design that can go to many email platforms. Not so good: a coded template is edited in code, not Klaviyo’s drag-and-drop editor, and the design has to follow the plugin’s structure. A flat design from Photoshop or Canva needs rebuilding first. We compare these tools in detail in the best Figma to Klaviyo tools in 2026.
4. Auto-slice it with Carvr
Carvr starts from the finished design, whatever it was made in. In Figma, you select the frame and click Send to Klaviyo in the Carvr plugin. From Photoshop, Canva or anything else, you upload one full-length image in the web app. Carvr then:
- finds where to cut the design into sections, the way a person would, and lets you move any line;
- compresses each image and adds its link, from your Figma prototype links or the brand’s default;
- writes alt text for every section with AI;
- builds a native drag-and-drop template in Klaviyo, so your team edits it in the editor they already use. The same design can go to Omnisend or Mailchimp instead.
Good: it takes about 30 seconds an email, the result is pixel-identical to the design, and there is no file structure to follow. It also sends text-only sections as editable Klaviyo or Omnisend text if you turn on live text blocks, and keeps animated GIFs animated. Not so good: text inside an image section is part of the image, so copy changes go back through the design, and dynamic content such as product feeds is still added in Klaviyo.
The step-by-step version is in the Figma plugin guide, and for a design that isn’t in Figma, slicing emails in the web app.
Before you send: four Figma tips for Klaviyo
- Design at 600px wide. Export at 2x, so 1200px, for sharp images on high-density screens.
- Give each button its own row. Every image section gets one link, so a call to action that sits alone in a row can link somewhere different from the hero above it.
- Mind Klaviyo’s image limit. Klaviyo accepts about 100 image uploads a day per account, and every section is one image. See Klaviyo’s 100 images a day limit.
- Keep real text where it matters. Subject line, preview text and alt text carry the message when images are blocked.
Frequently asked questions
Can you import a Figma file directly into Klaviyo?
Not as a template. Klaviyo cannot open a .fig file. You either bring the design in as images (exported from Figma, or sent with a plugin) and lay them out in Klaviyo’s drag-and-drop editor, or you turn it into HTML and import that. Carvr does the image route for you: it slices the design and builds the drag-and-drop template in Klaviyo.
Should I create my email templates in Figma or in Klaviyo?
Design in Figma when the email is visual and brand-led: you get exact control and a design your client can approve. Build in Klaviyo when the email is mostly text, product feeds or personalised blocks. Most teams do both: the designed sections come from Figma, and dynamic content stays native in Klaviyo.
What size should a Figma email design be for Klaviyo?
Design at 600px wide, the standard email width, and export at 2x (1200px wide) so images stay sharp on high-density screens. The Carvr plugin exports at exactly 1200px. Very tall designs are fine: the plugin handles frames up to 25,000px tall at export scale, and the web app takes uploads up to 30,000px tall.
Are image-based emails bad for deliverability?
Not by themselves, but an email made only of images has no real text for spam filters, screen readers or clients that block images. Give every image descriptive alt text, keep the subject, preview text and key messages meaningful, and use live text where text matters. Carvr writes alt text for every section and can send text-only sections as editable text blocks.
Does this work for Mailchimp and Omnisend too?
Klaviyo’s own Figma plugin is Klaviyo only. Carvr sends the same design to Klaviyo, Omnisend or Mailchimp, depending on which platform the brand is connected to.
Why does my email look different in Klaviyo than in Figma?
Usually because the design was rebuilt with Klaviyo blocks, which use their own fonts, spacing and padding. Image sections keep exactly what was designed. If a rebuilt email drifts, compare the block padding and font sizes with the Figma file, or send the designed sections as images.