Inside the MailCraft Email Builder

One design, two outputs, always in sync

Every email you build is stored as a structured design — a tree of blocks with their settings — and MailCraft generates the HTML body and a plain-text fallback from that same tree every time you save. There's no separate "edit the text version" step to forget, and no drift between what the visual editor shows and what actually goes out. If you need to hand-edit the generated HTML for an edge case, you still can; the design stays the source of truth for the next visual edit.

Blocks that cover what campaigns actually need

Heading, text, image, button, divider and social blocks cover most emails on their own. Columns let you build side-by-side layouts without writing table markup by hand. A video block drops in a clickable thumbnail that links out to the hosted video — email clients don't reliably play inline video, so faking that with a fragile embed isn't worth the trade-off.

• Column layouts for side-by-side content without hand-written HTML tables.
• Header and footer variations you can swap without rebuilding the rest of the email.
• A live drop preview while dragging, so you see exactly where a block will land before you release it.
• Starter layouts for common structures — announcement, newsletter, receipt — as a starting point rather than a constraint.

Save your own blocks once, reuse them everywhere

Once you've built a footer with your social links and unsubscribe language, or a header with your logo and nav, save it as a block for your team. Every future campaign starts from your actual brand components instead of a blank canvas, and a fix to your footer only has to happen in one place.

A team asset library, not per-email uploads

Images you upload live in a shared team asset library rather than being tied to whichever campaign you were editing when you uploaded them. Reuse a logo or a product shot across a dozen campaigns without re-uploading it a dozen times, and everyone on the team is pulling from the same set of approved images.

Built for the send path, not just the editor

The builder isn't a separate product bolted onto MailCraft — a template built in the editor is the same template your API calls, campaigns and automation steps send. There's no "export and re-upload" step between designing an email and using it in production, because the design and the sendable template were never two different things.