MiN8T All Insights
Guide 10 min read

How to Test and Export AMP Emails with MiN8T

M
MiN8T Team
Email Engineering
April 12, 2026

AMP for Email lets you build interactive, dynamic emails with real-time content, in-email forms, carousels, and accordions. MiN8T supports creating AMP emails visually and handles the technical complexity — 3-part MIME assembly, AMP script injection, and CORS-compliant data endpoints — automatically.

This guide covers how to test your AMP emails, export them for sending, and what happens behind the scenes.

1 AMP Blocks in MiN8T

MiN8T supports four AMP block types that you can use in the visual editor:

i

AMP blocks are added from the block palette on the left sidebar, just like any other block. The Data Source connection is configured in the Data tab of the property panel for containers, structures, or stripes.

2 Testing AMP Emails

Before sending AMP emails to your audience, always test them in Gmail (the largest AMP email client).

Step 1: Send a Test Email

  1. In the MiN8T editor, click the "Send" button in the top toolbar
  2. Enter your Gmail address in the test email modal
  3. Click "Send Test"
  4. MiN8T sends a 3-part MIME email (plain text + AMP + HTML) via SMTP through Resend

The test email is sent from noreply@min8t.com. When your template contains AMP blocks, MiN8T automatically includes the AMP version alongside the HTML fallback.

Step 2: Enable Dynamic Email in Gmail

  1. Open Gmail and go to Settings (gear icon) → See all settings
  2. Under the General tab, find "Dynamic email"
  3. Check "Enable dynamic email"
  4. Click "Developer settings"
  5. Add noreply@min8t.com as a trusted sender for testing
  6. Click Save Changes
!

Important: Before each new test, delete the previous test email from the same sender. Gmail aggressively caches AMP content — if you don't delete the old email, you'll see stale content even after making changes.

Step 3: Verify AMP Rendering

  1. Open the test email in Gmail
  2. If AMP is working, you'll see interactive elements (forms respond to input, carousels swipe, accordions expand)
  3. To verify the MIME structure: click the three dots → "Show original" → look for text/x-amp-html in the raw source

Step 4: Verify HTML Fallback

Forward the same email to an Outlook or Apple Mail account, or view it in any email client that doesn't support AMP. You should see the static HTML version with no broken AMP tags or missing content.

3 Exporting as HTML

When you export your template as HTML, MiN8T automatically handles AMP:

  1. Click "Export" in the editor toolbar
  2. Select "HTML" from the format dropdown
  3. If your template contains AMP blocks, the export includes:
    • CSS inlined for email compatibility
    • HTML minified (20-40% size reduction)
    • Plain text version
    • AMP version automatically included (3-part MIME)
    • AMP validation runs before export
  4. Click "Export HTML" to download the file
✓

The export modal shows "AMP included automatically when detected" in the HTML format description. You don't need to select a separate AMP option — it's built into the standard HTML export.

AMP validation runs automatically. If there are issues (markup exceeds 200KB, CSS exceeds 50KB, missing boilerplate), the export response includes validation warnings so you can fix them before sending.

4 Exporting to a Connected ESP

If you've connected an ESP (like Brevo, SendGrid, Mailchimp) through the Integrations page, you can push your template directly:

  1. Click "Export" → select "Email Service"
  2. Choose your connected ESP from the grid
  3. Fill in Campaign Name (required), and optionally a Subscriber List and Subject Line
  4. An info box shows what will be sent: "HTML with inline CSS + AMP version (3-part MIME) + plain text fallback"
  5. A yellow reminder suggests running a pre-send validation test before exporting
  6. Click "Export ESP"

MiN8T creates a campaign draft in your ESP account. It does NOT send the email — you finalize the send (schedule, audience, A/B test) from your ESP's dashboard.

i

The subscriber list field says "Associate with list (optional — can be set in your ESP)". You can skip it and assign a list later in your ESP dashboard.

5 Understanding the 3-Part MIME Structure

AMP emails use a multipart/alternative MIME structure with three parts, in this exact order:

  1. text/plain — Plain text fallback (for clients that can't render HTML)
  2. text/x-amp-html — The AMP version (for Gmail, Yahoo, Mail.ru, FairEmail, AOL)
  3. text/html — Standard HTML fallback (for all other email clients)
!

The AMP part must come before the HTML part. Some email clients render the last MIME part, so placing AMP before HTML ensures AMP-capable clients pick it up correctly. MiN8T handles this ordering automatically.

MiN8T assembles this structure in two ways:

AMP Script Auto-Injection

MiN8T automatically detects which AMP components your email uses and injects the required scripts into the AMP <head>:

You never need to manually add scripts — the serializer handles it based on what blocks you've used.

6 Supported Email Clients

Only five email clients currently support AMP rendering:

All other email clients (Outlook, Apple Mail, Thunderbird, Samsung Mail, etc.) will see the HTML fallback version. This is why every AMP email must include a proper HTML part — and MiN8T always generates both.

i

Gmail may stop rendering AMP content after ~30 days. Older emails revert to the HTML fallback. This is by design — AMP is for timely dynamic content.

7 Next Steps

Last updated: April 2026. Based on MiN8T's implementation of the AMP for Email specification.