An email brand kit sets palette, fonts and buttons once for the workspace so new title, text and button blocks land on-brand. You still rewrite copy and move the layout, send a Test, then export HTML or MJML or push a Zoho draft. The kit does not replace reading the email or ESP compliance.
Why emails drift off-brand
It usually starts with restyling each campaign in the ESP editor. One email gets a slightly different blue. The next gets the editor's default button. The font is "close enough".
For a small team or an agency, that adds up. A welcome, a promo and a newsletter sent in the same month can look like three different brands.
Fix the brand before you export, not after you import. For the full trade-off between a studio and your ESP, see design then export versus build in your ESP.
What an email brand kit is
Palette, fonts, and buttons
In Milo Email Studio a brand kit is three things: palette, fonts and buttons for the workspace. That's enough for most marketing and agency emails. It's not an enterprise rules engine, a design-token system or a multi-brand CMS.
If you're using the AI designer and worried about AI drafts drifting, keep AI-drafted email blocks on-brand covers that. This guide is about how blocks inherit the kit.
New blocks pick them up
Title, text and button blocks all land in your kit's styles. You still write every line, though. The kit won't check the offer, the legal footer or the tone for you.
So your time goes on the words and the layout, and colour and type take care of themselves. You only override a style when you mean to.
Set the kit, then reuse it
The payoff of a kit is that brand decisions stop being per-email decisions. Palette, fonts and buttons get set once, before you start filling the canvas. Free includes one brand kit.
You can also start a kit From a website: Milo reads the site (Read site) and proposes palette, fonts and buttons you can tune, then Use this setup saves them.
Every new email starts on-brand. Describe the email to the AI designer or open a starter you know (Welcome, Promo, Newsletter or Event). Both routes use the same kit, and there's no separate brand setting for each starter.
You can see it working straight away. The headline, supporting copy and shop button all land in your brand styles. A Promo makes a good check: offer, end time, one shop button, with your brand colour already on it.
Your edits stay about content. Rewrite anything that sounds off and move blocks if the layout's wrong. The kit styles hold unless you mean to override them.
Consistency comes from reuse. Using the same kit on your Welcome and your Promo is what makes your brand look consistent. Don't assume that changing the kit will restyle every older email, though. Set it up before new work, and check older emails if you change the styles later.
Sign-off and handoff don't undo it. A Test goes to an address on your account, with a subject that starts with Test, so you can check the colours, type and button before you export. For width, images off and the rest of the before-you-send list, see the HTML email checklist. A teammate or client can approve the email from a preview link without needing to log in to the studio. Then you take HTML or MJML ready for your ESP, or connect Zoho Campaigns and push a draft. See design a branded email and export and Zoho draft push.
What the brand kit does not do
| Brand kit / studio | Your ESP | |
|---|---|---|
| Palette, fonts, buttons on new blocks | Yes, kit inheritance | Often re-styled if you rebuild in the native editor |
| Edit copy and layout | Yes, on the canvas | Possible, but you are past the design studio |
| Test / proof the draft | Studio Test + optional preview link | Final ESP test after import |
| Export-ready handoff | HTML / MJML file | Import, then send |
| Replace reading the email | No. You still own words, legal, and offer accuracy | Compliance, merge tags, and segments live here |
When the AI brand-kit piece is the better read
This guide is the practical side: set your palette, fonts and buttons once and keep lots of templates consistent.
The AI brand-kit read is for a slightly different problem, where the AI drafted your blocks and they drifted off-brand, and the kit is what keeps them in line.
Questions
What is an email brand kit?
In Milo, it's the palette, fonts and buttons for your workspace. New blocks pick them up automatically.
What usually goes in one?
Those three things: palette, fonts and buttons. It isn't a token export, a Figma sync or a matrix of locked overrides.
How do new blocks inherit the kit?
New title, text and button blocks use the kit's styles. You rewrite the words and move the layout, while colour and type stay with the kit unless you override them.
Why do emails drift when you rebuild in the ESP editor?
The ESP's editor has its own defaults, so every rebuild is a chance to end up with a new blue, a new button or a fallback font. Setting the kit before you export means you skip that step.
Do I still edit after the kit applies?
Yes. Rewrite the copy and move blocks around. Colour and type stay with the kit unless you override them.
Will every old email update if I change the kit?
Don't count on it. Set up the kit before you describe new work to the AI designer, and if you change the styles later, open your older emails and check them.
Is this the same as the AI brand-kit article?
No. That one's about AI-drafted blocks and keeping them in check. This one explains how the kit itself works.
Where does the campaign go after export?
Your Test goes to an address on your account. Then export the HTML or MJML for your ESP, or push a Zoho Campaigns draft, and send from there.
Where does the file go after export?
Into your ESP, as HTML or MJML. For most ESPs, you import the file rather than pushing it with one click. The steps are in design a branded email and export.
Set the kit, then start
Set the kit once. Describe the email to the AI designer or open a starter, send a Test if you want a proof, then export HTML or MJML or push a Zoho draft. You send from your ESP. You can start on Milo whenever you're ready.