AMP Email: What It Is, How It Works, and What Most Guides Won't Tell You

What Is AMP Email?

AMP email is an open-source framework that adds interactive functionality to emails. Instead of static images, text, and links, AMP lets recipients fill out forms, browse product carousels, expand accordions, and take real actions without ever opening a browser.

Google originally created AMP (Accelerated Mobile Pages) for web pages back in 2015. In 2019, they expanded it to email. The project is now fully open-source and Google doesn't exclusively own or control it.

Here's how it differs from a normal HTML email.

A standard email is like a printed flyer. You can look at it, but you can't interact with it. An AMP email is more like a mini website that lives inside your inbox. You click buttons, select options, submit data. All without leaving the message.

What AMP Email Can Do

The framework includes a library of built-in components:

• Forms and surveys: Collect feedback, run NPS scores, or gather preferences right in the inbox

• Image carousels: Let recipients swipe through product photos without a landing page

• Accordions: Expand and collapse content sections (perfect for FAQs or product details)

• Live content updates: Pull real-time data like pricing, inventory levels, or shipping estimates

• Multi-step selectors: Let customers pick sizes, colors, or options before clicking through

The common thread? Every one of these removes a click. And in email marketing, every removed click means fewer drop-offs.

How Does AMP Email Work?

Under the hood, an AMP email is a standard email with an extra layer.

Every email you send already contains multiple versions, called "MIME parts/types." There's a plain text version for bare-bones clients and a HTML version for everything else. AMP adds a third: text/x-amp-html.

When someone opens your email in a client that supports AMP (like Gmail), it renders the AMP version. If their client doesn't support it? They see the regular HTML version. The recipient never notices the switch.

The Technical Requirements

Sending AMP emails isn't quite as simple as hitting send on a regular campaign. There are a few requirements:

Authentication: Your sending domain needs SPF, DKIM, and DMARC authentication. If you're sending marketing email at any scale, you probably have these already. If not, your ESP can help you set them up.

Google registration: To send AMP emails that render in Gmail, you need to register your sending domain with Google. The process requires a production-quality email (no test content), a minimum of 5,000 emails per month from your domain, and low spam complaint rates. Google typically responds within 5 - 10 business days.

Size limits: AMP emails must stay under 200KB. That sounds small, but it's usually plenty. Text and interactive components are lightweight. Heavy images are what usually eat space.

Fallback required: Every AMP email must include a HTML fallback. This isn't optional. If a recipient's client doesn't support AMP, they need to see something useful. The good news: most tools that support AMP generate this fallback automatically.

Which Email Clients Support AMP?

This is the question everyone asks first. And honestly, the answer is a bit more complicated than most guides let on.

Currently Supported Clients

AMP email renders interactively in these clients:

• Gmail (desktop, Android app, iOS app)

• Yahoo Mail

• Mail.ru

• FairEmail

That's the full list. If you're thinking "that's it?", you're not wrong to feel underwhelmed.

The Numbers Behind It

According to Litmus email client market share data, Gmail and Yahoo account for roughly 29% of email opens globally. That's significant, but it also means 71% of your audience won't see the AMP version.

Here's where most AMP-only guides stop, but they're missing the bigger picture.

Interactive HTML/CSS: The Other Half

Apple Mail accounts for roughly 51.5% of email opens. It doesn't support AMP, but it does support interactive HTML/CSS. That means buttons that trigger API calls, live content updates based on user actions, and CSS-powered animations. For the end user, the experience looks and feels nearly identical to AMP.

When you combine AMP (for Gmail and Yahoo) with interactive HTML/CSS (for Apple Mail), you're covering 80%+ of your audience with interactive experiences. The remaining ~19% (mostly Outlook and older clients) get a static HTML fallback.

Source: Litmus, Kinetic docs

AMP is one piece of this puzzle. HTML/CSS interactivity is another. Together, they cover most of your list. Alone, neither gets the job done.

What Can You Do With AMP Email? Real Examples

Here's some examples of what happens when brands actually put interactive AMP emails to work:

Dr. Emi Arpa Skin: +188% More Responses, 7x ROI

Dr. Emi Arpa Skin, a German premium skincare brand, wanted to collect customer preferences for personalized email marketing. Their original approach was the industry standard: send an email with a link to a web-based form.

The problem? Most customers never made it to the form.

They ran an AB test: same questions, same flow, same send volume. One version linked out to a form on a landing page, the other let customers answer right in the email, using AMP for Gmail recipients and interactive HTML/CSS for Apple Mail.

The results:

But the real payoff came after. With nearly 3x more response data, they were able to build targeted segments based on their customer’s interests. Two campaigns sent to that segment saw +49% open rates, +225% click rates, and +50% placed order rates compared to brand averages.

This worked so well because the interactive form reached customers in both Gmail and Apple Mail. AMP alone would have covered only ~29% of their list. The combination covered 80%+.

AMP was a tool in the toolbox, implemented in a useful and targeted way.

Razorpay: 257% More Survey Responses

Fintech company Razorpay embedded NPS surveys directly in their emails using AMP instead of linking to an external form. The result: a 257% increase in email response rate, plus an 87% jump in lead generation for their Thirdwatch product and a 45% increase in engagement for product awareness campaigns.

The Pattern

Each of these examples follows the same logic. Remove a step, get more responses. Whether it's a preference form or an NPS survey, keeping the action inside the email reduces friction. That's what AMP (and interactive email broadly) really does. It removes the click that loses your customer.

5 AMP Email Myths Debunked

Search any email marketing forum and you'll find strong opinions about AMP email. Some are outdated. Some were never true. Let's sort through the noise.

Myth 1: "AMP Email Is Dead"

This one pops up constantly, especially after Google deprioritized AMP for web pages in 2021. But AMP for web and AMP for email are different products with different trajectories.

Gmail still fully supports AMP email. Google uses it in their own products. Yahoo supports it (kind of). The official AMP project continues to maintain the email specification. And the number of no-code tools that support AMP email building has grown from almost zero in 2019 to over a dozen today.

AMP for email isn't dead. It just doesn't get the press it used to because it quietly works in the background for the brands using it.

Myth 2: "Only Gmail Supports It, So Why Bother?"

Partly true, mostly misleading. Yes, AMP client support is limited to Gmail, Yahoo, Mail.ru, and FairEmail. But that ~29% of email opens is still a real audience.

More to the point: you don't send AMP emails instead of regular emails. You send them with an HTML fallback. Everyone on your list gets something. AMP-supported clients get the interactive version. Everyone else gets the standard version you would have sent anyway. There's no downside, only upside for the segment that sees it.

And when you pair AMP with HTML/CSS interactivity for Apple Mail, you're covering up to 80% of your list with interactive experiences. The "limited support" argument assumes AMP has to stand alone. It doesn't.

Myth 3: "It's Too Hard to Implement"

This was true in 2019. You needed developers who understood AMP's strict markup requirements, its unique CSS limitations, and Google's whitelisting process.

In 2026? Not so much. No-code email builders handle AMP automatically. You drag, drop, and send. The builder generates the AMP version, the interactive HTML/CSS version for Apple Mail, and the static fallback. You don't touch code.

The Google registration process still takes about 5 - 10 business days. Kinetic also handles this for you when you sign up, so there is no heavy lifting on your end.

Myth 4: "You Can't Track Clicks in AMP Emails"

Half right. Traditional link click tracking doesn't work the same way for in-email actions, because the user isn't clicking a link to a new page. They're interacting inside the email.

But you don't lose measurement. You gain different data. Instead of "they clicked a link," you get "they completed the form," "they selected Product B," "they rated us 9 out of 10." Form completion rates, time-to-complete, and specific answer data are richer metrics than a click-through rate ever was.

You still track opens (as far as that is possible in this day and age). You still track clicks on any standard links in the email. The only thing you miss is how many clicks happened inside your email, which would be a nice metric, but in 99% of cases shouldn’t be a deal breaker.

Myth 5: "AMP Emails Are a Security Risk"

This might be the most backwards myth on the list. AMP for email is actually more restrictive than standard HTML email.

No arbitrary JavaScript. No third-party scripts. No external tracking pixels beyond what's standard. Google vets every sender through a registration process before they can send AMP emails to Gmail users. Every AMP email requires SPF, DKIM, and DMARC authentication.

Standard HTML emails have far fewer restrictions. AMP's security model is tighter, not looser.

AMP Email vs. Interactive HTML/CSS: Why You Need Both

AMP gets all the headlines. But it's only half the interactive email story.

There are two technologies that make emails interactive, and they serve different clients.

AMP for Email

• Where it works: Gmail, Yahoo, Mail.ru, FairEmail

• What it does: Forms, live data feeds, JavaScript-powered interactions, server-side data processing

• Strengths: Can pull real-time data (pricing, inventory, stock levels). Can send form data back to a server. Most capable interactive framework for supported clients.

• Limitations: Works in ~29% of inboxes. Requires Google registration. 200KB size limit. All styles must be declared in the header using AMP-specific tags.

Interactive HTML/CSS

• Where it works: Apple Mail (macOS and iOS)

• What it does: In-email button clicks that trigger API calls, live content updates based on user actions, CSS animations

• Strengths: Covers ~51.5% of email opens. No registration required. Broader CSS support (up to full CSS vs. AMP's 50KB limit).

• Limitations: Can't pull live external data the same way AMP can. Less capable for complex multi-step interactions.

Why the Best Strategy Uses Both

If you only use AMP, you're interactive for 29% of your audience. Only use HTML/CSS interactivity, and you cover 51.5%. Use both, and you hit 80%+. The remaining ~19% get a clean static fallback.

This is exactly what happened in the Dr. Emi Arpa Skin case study. Their interactive form worked in both Gmail (AMP) and Apple Mail (HTML/CSS). If they'd gone AMP-only, they would have missed the majority of their audience. The +188% response uplift came from reaching customers across both technologies.

AMP is a powerful tool. But it belongs as an option in your toolbox, not as the sole strategy. The real goal isn't "use AMP." It's "make your emails interactive for as many people as possible." AMP is how you get there for Gmail. HTML/CSS is how you get there for Apple Mail. You need both.

How to Get Started With AMP Email

If you're ready to try AMP email, here's the practical path forward.

Step 1: Check Your ESP

Your email service provider needs to support sending the AMP MIME part. Most major ESPs like Klaviyo, Braze, and Salesforce Marketing Cloud can do this, though the setup varies. Check your ESP's documentation for "AMP" or "dynamic email" support.

Step 2: Set Up Email Authentication

AMP emails require SPF, DKIM, and DMARC authentication on your sending domain. If you're already sending marketing email at scale, you likely have these configured. If not, your ESP's support team can walk you through it. This is standard email hygiene that benefits deliverability regardless of AMP.

Step 3: Register With Google

Submit a production-quality email to Google's AMP for Email registration. You'll need:

• A live sending domain with at least 5,000 emails per month

• Low spam complaint rates

• A real, production-quality example email (not a test or placeholder)

• SPF, DKIM, and DMARC in place

Google typically responds within 5 - 10 business days. Yahoo has a similar but separate registration process.

Step 4: Build Your First AMP Email

You have two paths.

No-code route: Tools like Kinetic, Dyspatch, and others offer drag-and-drop builders that generate AMP, HTML/CSS interactive, and static fallback versions automatically. No developer needed. For Klaviyo users specifically, Kinetic pushes interactive templates directly into your account.

Custom code route: Build directly using AMP's component library at amp.dev. Full control, but requires developers familiar with AMP's strict markup and CSS restrictions.

For most eCommerce and D2C teams, the no-code route is faster and more practical.

Step 5: Test Across Clients

Before sending to your list, test in:

• Gmail (desktop and mobile) for the AMP version

• Apple Mail (macOS and iOS) for the HTML/CSS interactive version

• Outlook for the static fallback

Send test emails to real inboxes. Previews inside your ESP don't always catch rendering issues across different clients.

The Bottom Line on AMP Email

AMP email works. Razorpay saw a 257% jump in survey responses. Dr. Emi Arpa Skin got 188% more form completions and a 7x ROI. These aren't theoretical numbers.

But AMP alone covers roughly 29% of inboxes. That's not enough to build an entire strategy around.

The brands getting the biggest wins treat AMP as one tool in a broader interactive email approach. AMP for Gmail. HTML/CSS interactivity for Apple Mail. Static fallback for everyone else. That combination is what gets you to 80%+ interactive coverage.

So if you're evaluating AMP, the right question isn't "should I use AMP?" It's "how do I make my emails interactive for the most people possible?" AMP is part of that answer. Not the whole thing.

If you want to see what that looks like in practice, Kinetic makes it easy to add interactive forms, quizzes, and product recommendations inside your emails, covering Gmail, Apple Mail, and Static fallback with no code required.