Export Your First Email
Understand the export options in PostBrix, the difference between HTML and MJML outputs, and how to verify your export.
Key Takeaways
- Export options: Direct .html file download, raw .mjml file download, or one-click clipboard copy.
- HTML export produces email-compatible markup with MSO comments, VML graphics, and mobile media queries.
- Dynamic tags ({{var}}, {{#if}}, {{#each}}) can be exported intact for use with dynamic ESPs or hydrated with static sample data.
- MJML export provides raw source code for teams using automated developer CI/CD pipelines.
The Export Modal#
When you click Export in the top navigation bar, the export modal provides two primary format tabs:
1. HTML Export (Recommended for Most Workflows)
Compiles your visual blocks through the PostBrix MJML engine into email-compatible HTML.
- Download .HTML: Saves the complete file to your computer.
- Copy HTML: Copies the compiled markup to your clipboard for instant pasting into Mailchimp, SendGrid, or other platforms.
- Minification Option: Removes unnecessary whitespace and comments to keep the email payload under 100 KB (preventing Gmail clipping).
2. MJML Export (For Developers)
Exports clean, semantic MJML markup. Ideal if your engineering team has an existing Node.js or Python backend that uses mjml directly as part of a build system.
Dynamic vs. Static HTML Export#
If your template contains Handlebars merge tags (like {{firstName}} or {{#each items}}), PostBrix gives you two ways to export:
- Dynamic HTML (Preserved Syntax): Retains all
{{variable}}and loop tags verbatim inside the HTML. Use this when sending through platforms that support Handlebars or when passing the template to a custom backend renderer. - Static HTML (Hydrated Data): Injects your configured sample test data into the template, resolving all variables into static text. Ideal for one-off marketing announcements or manual client sign-offs.
ESP Merge Tag Warning
Frequently Asked Questions
Should I choose HTML or MJML export?
Choose HTML export if you are pasting code into an Email Service Provider like Mailchimp or Klaviyo. Choose MJML export if your engineering team compiles templates inside their own backend build pipeline.
Why does my HTML export still contain a <style> block?
PostBrix inlines all core element styles for desktop Outlook compatibility while intentionally preserving responsive media queries inside the <head><style> block so mobile columns can stack fluidly.