Stay organized with collections
Save and categorize content based on your preferences.
Before you send a AMP-powered dynamic email, you can test it to verify its
contents and behavior.
There are two options for testing your dynamic emails in Gmail:
Use Gmail’s AMP for Email Playground to
draft AMP emails, see a live preview, and have your emails sent to your own
Gmail account for testing.
Navigate to Gmail Settings > General > Dynamic email and click
Developer settings. This opens a dialog where you can whitelist
an email address that can send you dynamic emails for testing purposes.
The AMP version of emails sent from the listed address to your account
are rendered, even if the email address is not registered with Google. This
lets you test your dynamic emails on your own accounts before registering to
ensure they are working as expected.
Delivery requirements
For your AMP email to be delivered to any account, the email must meet the
following conditions:
The email must contain a fallback HTML version (text/html) or plain text
version (text/plain) in addition to the AMP MIME part (text/x-amp-html).
This fallback version is displayed in situations where the AMP MIME part
cannot be displayed, such as when the mail client is offline or 30+ days after
the email was received by Gmail.
[null,null,["Last updated 2025-08-28 UTC."],[],[],null,["# Test your AMP emails in Gmail\n\nBefore you send a AMP-powered dynamic email, you can test it to verify its\ncontents and behavior.\n\nThere are two options for testing your dynamic emails in Gmail:\n\n1. Use Gmail's [AMP for Email Playground](https://amp.gmail.dev/playground/) to draft AMP emails, see a live preview, and have your emails sent to your own Gmail account for testing.\n2. Navigate to Gmail **Settings \\\u003e General \\\u003e Dynamic email** and click\n **Developer settings**. This opens a dialog where you can whitelist\n an email address that can send you dynamic emails for testing purposes.\n The AMP version of emails sent from the listed address to your account\n are rendered, even if the email address is not registered with Google. This\n lets you test your dynamic emails on your own accounts before registering to\n ensure they are working as expected.\n\n | **Note:** In order to send AMP emails to your own account from the [AMP for Email Playground](https://amp.gmail.dev/playground/), you need to whitelist `amp@gmail.dev` in the **Developer settings** dialog.\n | **Note:** Make sure to test delivering your email from your production system using option 2 above. This helps verify that the email you send in production meets all the delivery requirements, and helps test for potential modifications to your email made by your [ESP](https://amp.dev/support/faq/email-support/). See [validate delivered emails](https://amp.dev/documentation/guides-and-tutorials/learn/validation-workflow/validate_emails/?format=email#validate-delivered-emails) for more details on how to verify whether the email still contains valid AMP after modifications by your ESP.\n\nDelivery requirements\n---------------------\n\nFor your AMP email to be delivered to any account, the email must meet the\nfollowing conditions:\n\n- The [AMP for Email security requirements](/workspace/gmail/ampemail/security-requirements) must be met.\n- The email must contain a fallback HTML version (`text/html`) or plain text version (`text/plain`) in addition to the AMP MIME part (`text/x-amp-html`). This fallback version is displayed in situations where the AMP MIME part cannot be displayed, such as when the mail client is offline or 30+ days after the email was received by Gmail.\n- The AMP MIME part must contain a [valid AMP document](https://amp.dev/documentation/guides-and-tutorials/learn/validation-workflow/validate_emails/?format=email).\n- The email should include the AMP MIME part before the HTML MIME part.\n- The `From` and `To` header fields of the email must contain different email addresses."]]
