How to Export AMP HTML Emails
1 How AMP Export Works
When your template contains AMP blocks (carousel, accordion, form, or amp-list via Smart Elements), MiN8T automatically generates the AMP HTML version alongside the standard HTML. There's no separate "AMP export" button. AMP is included in every HTML export when AMP content is detected.
The export modal shows an info note explaining that AMP content will be included automatically. The export produces:
- HTML file, standard email HTML with table-based layouts, VML for Outlook, and responsive CSS
- AMP HTML, a valid AMP4Email document with
<!doctype html>,<html amp4email>, AMP boilerplate, and all required component scripts - Plain text, auto-generated text-only fallback
2 3-Part MIME Structure
For AMP emails to work, the email must be assembled as a multipart/alternative MIME message with parts in a specific order:
Content-Type: multipart/alternative; boundary="..."
--boundary
Content-Type: text/plain; charset="UTF-8"
[Plain text version]
--boundary
Content-Type: text/x-amp-html; charset="UTF-8"
[AMP HTML version]
--boundary
Content-Type: text/html; charset="UTF-8"
[Standard HTML version]
--boundary--The order matters: text/plain → text/x-amp-html → text/html. Email clients that support AMP render the AMP part. Clients that don't fall back to HTML. Clients that don't support HTML fall back to plain text.
MiN8T assembles the 3-part MIME automatically. When sending via a connected ESP or through the test email modal, the correct MIME structure is generated using Nodemailer's amp field.
3 AMP Validation
Before including the AMP part, MiN8T runs the AMP Validation Service to check:
- DOCTYPE, must be
<!doctype html> - Root element, must have
<html amp4email>or<html ⚡4email> - Charset, must declare
<meta charset="utf-8"> - AMP boilerplate, required
<style amp4email-boilerplate> - AMP runtime, must include
amp.js - Size limits, total document under 200KB, CSS under 50KB (75KB for sender-whitelisted)
- Forbidden content, no
<script>(except AMP components), no<form>(use<amp-form>), no external stylesheets - Component scripts, every
<amp-*>tag must have its corresponding<script>in the head
Validation results are included in the export response. If validation fails, the AMP part is still included but flagged with warnings so you can fix issues before sending.
4 Sending via ESP
When sending through a connected ESP (Brevo, Mailchimp, SendGrid, etc.), MiN8T includes the AMP HTML in the export payload. The ESP must support AMP emails for the dynamic content to render. Most major ESPs support the text/x-amp-html MIME part.
Your sender domain must be whitelisted with Gmail and Yahoo for AMP emails to render. Without whitelisting, recipients see the standard HTML fallback even if the MIME structure is correct.
5 Next Steps
- How to Test and Export AMP Emails, the complete testing workflow
- AMP Email Whitelisting Guide, get approved for AMP sending
- How to Preview and Test Templates, pre-send validation checks
Last updated: April 2026. All details verified against MiN8T's actual codebase implementation.