Your design team can turn around a campaign in an afternoon.
Then it sits in a queue for three days because someone has to export the Figma file, upload it, rebuild the email in the platform, and hope nothing shifts along the way.
Sound familiar? A small copy change on a live promo shouldn’t take longer than the design itself did, but for a lot of teams, it still does. You can’t put all the blame on your email design systems either.
Braze Creative Studio is Braze’s answer to that gap.
Announced in April 2026, it pulls the Media Library Figma integration into Braze, Templates, Content Blocks, and Brand Guidelines into one workspace and adds direct integrations with Figma and Canva on top.
And here’s the real point we want to make in this post: Creative Studio automates a lot of the busywork around building an email. It doesn’t remove the need for developers who actually understand custom-code HTML email. It just moves them to a different part of the job: less repetitive coding, more rendering checks, and logic building.
Let’s cut to the chase and explore Braze Creative Studio, what it has automated in terms of templates. And why HTML email coding still matters, where developers will be needed.
What is Braze Creative Studio, really?
Creative Studio isn’t a brand-new tool bolted onto Braze. It’s a unified interface for capabilities Braze already had: Media Library, Templates, Content Blocks, Brand Guidelines, now sitting under one roof, with design-tool syncing added on.
Braze’s own framing for why now is straightforward: AI has made generating content cheap. Everyone can produce more assets, faster. So the real bottleneck moved downstream, to execution, getting that content built, approved, and live without it stalling in handoffs.
Braze describes three goals for the product: simplify asset management, speed up campaign creation, and streamline marketing operations. The first two are where the “automation” claim actually lives, so that’s where we’re spending most of this post.
What’s actually automated: The Figma and Canva integrations
Here’s how the Figma side works. A design gets synced straight from the Figma integration into Braze, and the fonts, spacing, and layout come with it. That approved file turns into an editable campaign without anyone re-creating it by hand.
Canva works the same way, just from the other direction. The moment an asset is finished in Canva, it lands in the Media Library. No export, no manual upload, no waiting on someone to remember to do it. This Canva integration into Braze can be fruitful in putting your design systems in place.
Crumbl, one of the customers Braze features, put it plainly: the integrations “finally stopped the constant file wrangling that used to consume our design team’s time.” Their designers now trust that fonts and spacing will stay exactly as built.
Picture a travel brand launching a seasonal promo. They pull finished assets straight from Figma and Canva into Braze and activate the campaign across email and in-app messaging in the same sitting, no rebuild step in between.
Worth being precise about what this is: it’s automating file transfer and formatting. It is not automating email coding. That distinction matters for everything we cover below.
One home for every asset
Brand guidelines, product catalogs, external content, promo codes, and the campaign calendar all used to live scattered across different corners of the platform. Creative Studio puts them in one place.
Catalogs and Connected Content are the pieces doing the heavy lifting here. They let a team pull in dynamic product data, loyalty balances, or live external content without a manual build for every single campaign.
Canva, which uses Braze as its own engagement platform, is the proof point Braze leans on hardest. By using Braze’s centralized asset management, Canva’s team saved around 1,000 hours of production time while running 25 features across more than 200 variants. That’s not a rounding-error kind of number.
There’s also a built-in check that verifies AI-generated copy matches a brand’s voice guidelines automatically, instead of someone reading every send by hand.
Content blocks and the new production workflow
Content Blocks are modular snippets, such as headers, footers, or promo modules, that update once and automatically propagate everywhere they are used. Modify a block once, and the change automatically appears in templates and future campaigns that use it.
Reusable templates work the same logic across channels, not just email. Build the layout once, reuse it everywhere it fits.
Luxury Escapes is the case Braze points to for this one. They cut hours of coding per campaign and scaled across 27 markets with Braze reusable content blocks to update creative and content dynamically.
The shift here is simple to describe and genuinely useful in practice: Teams increasingly assemble campaigns out of pre-approved modules instead of coding each email from scratch.
Why HTML coding still matters
Here’s the tension underneath all of it. Templates and drag-and-drop tools handle structure well. They don’t solve rendering. Every major email client still interprets HTML and CSS its own way, and that gap is the actual hard problem in email production, not Braze’s centralized asset management.
Take Outlook. Desktop Outlook has rendered HTML through Microsoft Word’s engine since 2007, not a browser engine. Word was never built to read modern CSS, which is exactly why background images, padding, and other everyday styles routinely break, and why developers still lean on table-based layouts and VML workarounds to get around it.
Gmail brings its own version of the same problem. It clips any email once the HTML passes roughly 102KB, hiding everything below that point, including, sometimes, the unsubscribe link. Apple Mail, generally considered the most standards-compliant client out there, still needs its own separate handling.
Dark mode is a live example of how unpredictable this gets. Roughly 35% of measurable email opens now happen in dark mode, up from about 28% a year earlier. But clients don’t agree on how to handle it. Some fully invert colors, some adjust partially, and some leave the email untouched. A template that looks great in one client can turn illegible in another.
No visual builder predicts or patches engine-level quirks like these on its own. That’s still hand-coded conditional logic, tested across real inboxes, one client at a time.
Developer’s role is changing, not disappearing
The shift for developers isn’t less work, but it’s different work. Less time hand-coding routine promotional emails from scratch. More time building the base templates, Content Blocks, and personalization logic, the Liquid and Connected Content rules, that the rest of the team reuses over and over.
Think about a subscription brand’s onboarding email. A developer builds one template, tests for rendering and dark mode, and breaks it into Braze reusable content blocks. From there, marketers assemble dozens of campaign variants without touching a line of code.
Developers stay irreplaceable for the parts that automation can’t touch:
- Complex personalization logic built on Liquid, Connected Content, and Catalogs, where one wrong tag breaks the whole send.
- Cross-client QA, actually opening the email in Outlook, Gmail, and Apple Mail before it goes out, not just previewing it once.
- Accessibility fixes that a template alone won’t catch.
- Diagnosing exactly which client and engine is causing a specific broken send, instead of guessing.
Automation compresses the repetitive part of the job. It doesn’t compress the engineering problem of getting HTML to render the same way everywhere.
Wrapping up
That brings us to the business end of this article, where it’s fair to say that Braze Creative Studio genuinely automates asset transfer, centralization, and reuse, and the results back that up. Real hours saved, with real customers seeing it.
But templates and integrations sit on top of an HTML rendering problem that hasn’t gone anywhere. Faster asset assembly doesn’t mean the underlying code writes and tests itself.
If you’re running Braze or thinking about it, take a real look at your own email production workflow. Figure out where automation could take busywork off your team’s plate, and where you still need a developer’s eye on the actual code before you hit send.
That’s exactly the kind of audit we do with clients at Email Mavlers, figuring out where your stack can move faster and where it still needs a hands-on developer. If you’d like a second pair of eyes on your setup, we’re happy to help. Let’s talk.
Ahmad Jamal | Content writer
