Tips and known limitations

Follow these tips to ensure your AMP emails render correctly and consistently across all platforms and browsers that Gmail supports.

  • The summary text displayed next to the subject line when viewing emails in your inbox (preheader) is based on the text/html or text/plain part of your email and doesn't take the text/x-amp-html part into account.

  • Gmail's search feature currently doesn't index the dynamic parts of the email. Make sure the text/html or text/plain part of the email contains the most important keywords to ensure users can find your emails easily.

  • Email Markup and Promotions Annotations are parsed from the text/html part of the email and ignored in the text/x-amp-html part.

  • Avoid using viewport units (vw, vh, vmin and vmax) anywhere in your CSS and HTML. Since AMP emails render inside an iframe, the viewport of the email doesn't match the browser's viewport.

  • When using amp-carousel, ensure the controls attribute is set. This lets users on touchscreen devices such as smartphones to navigate the carousel.

  • When using amp-form, keep in mind not all input types are supported on iOS. Refer to Supported Input Values in the Safari HTML Reference for more information.

  • Not all autocomplete attribute values are supported across different apps and browsers. Assume that autocomplete isn't available to your users and keep the forms short.

  • Different browsers have different default CSS styling. Test your emails on all supported platforms and use a CSS library that normalizes styles if needed. For more information about default styles, style normalization and a list of available libaries, see Reboot, Resets, and Reasoning.