Stop translating your design system by hand. Paste a Figma URL and your email theme builds itself in Dyspatch. Convert Figma to email in minutes, no plugin required.
Dyspatch Pulls Your Brand Directly from Figma
Here's a scenario most email teams know well. Your brand just updated its design system. New primary color, refreshed typography, updated button radius. Looks great in Figma. Now someone has to go into the email builder and redo everything by hand.
Dyspatch now imports styles directly from a Figma file URL. Paste the link, pick what you want to bring in, and your theme is done. No plugin, no exporting, no copy-pasting hex codes.
How it works (it's fast)
You're in the Dyspatch theme editor. Instead of setting everything manually, you click "import from Figma" and paste a link to your Figma file. This can be your main design system file, a component library, any file where your brand styles live. The result is Figma to email: Dyspatch will convert Figma to email by creating your brand.
Dyspatch reads the file and surfaces everything it finds, organized by type. You see previews of each style candidate before anything gets imported. You pick what belongs in email, leave out what doesn't, hit import. Done.
One important thing: this is not a Figma plugin. You don't install anything in Figma. You don't need dev mode access. You don't need to ask your design team for anything except a link. Dyspatch does the analysis on its end.
That's intentional. Competitors have built plugins that live inside Figma. We went a different direction because plugins aren’t as straightforward of an option for design teams. We didn’t want teams to have to export emails from Figma, which is clunky and time-consuming. Going from Figma to email with a URL is simpler, and it works.
What you can bring in
When Dyspatch analyzes a Figma file, it surfaces style candidates organized by type:
- Body styles bring in background and layout styles that inform your email's outer container and structure.
- Text styles pull typography definitions including font, size, weight, line height, and color. Dyspatch maps these to the text roles in your theme (headline, body, accent, secondary, and so on).
- Link styles carry over link color and treatment from your Figma file, so anchor text in your emails matches your brand.
- Button styles pull from your existing Figma file to set your custom padding, border style, radius, and colors.
- Pill styles create custom flourishes to call out product categories, tags, and other promotional materials.
- Images and logos are component images that Dyspatch can pull directly into your theme assets, including logos and image assets.
You review each candidate before importing. If Dyspatch surfaces something that doesn't belong in your email theme (a text style from a web component, for example) you leave it unchecked. You're in control of what makes it from Figma to your email templates.
Why email has always had this problem
On the web, a design system change propagates automatically. Update a single component, and everything that uses it reflects the change.
Email doesn't work like that. Every template is effectively its own island. Colors are hard-coded. Fonts drift. Someone's button is a slightly different shade of the brand blue and nobody noticed until the CMO did.
The reason this keeps happening is simple: there's no live connection between Figma (where the truth lives) and email (where the templates live). You bridge it with documentation and careful copy-paste work, and it still breaks the moment something changes.
Dyspatch’s Figma to email converter closes that gap. Your Dyspatch theme is your brand, reflecting what's actually in your design system. When the system updates, you re-import. The connection is repeatable and follows your Figma email design system every step of the way.
What this looks like for a real team
Say you're at an agency managing email for eight brands. Every time a new client onboards, or a rebrand kicks off, someone on your team spends the first few hours just recreating the brand in Dyspatch: finding the hex codes, matching the fonts, uploading logos, getting the button styles right. It's tedious work that has nothing to do with actually building good emails.
With Figma Email Import, that setup collapses to minutes. The client shares their Figma file. You paste the URL, pick the styles that belong in your email design system, and have a properly branded theme live in the workspace before you've written a single brief.
For a team managing eight brands, that's hours back every month. More importantly, it means the emails you ship actually look like they came from the design system, because they did.
Getting started
Figma import is available in Dyspatch now. You'll find it in the theme editor under import options. If you want to see the flow before you try it yourself, book a demo and we'll walk through it with your actual Figma file.
