AMP Plugin for WordPress 1.1 Adds Experimental PWA Plugin Integration, Pre-release of AMP Stories Editor Available in 1.2-alpha

Version 1.1 of the AMP Plugin for WordPress was released this week after four months in development and 125 merged pull requests from contributors. It includes CSS tree shaking improvements that restore AMP compatibility for WordPress’ default Twenty Nineteen theme, reducing the size of its stylesheet by 53%.

In an effort to get more users opting for the Native mode option, the plugin’s development team has rebranded the template modes:

In this release the Paired mode has been rebranded as Transitional mode. One reason for this is that the classic mode was also a paired mode (where there are separate parallel URLs for the AMP version). But more importantly, the goal for this mode is to help facilitate a transition a site to being AMP-first, where there is no separate AMP-specific URLs. So the goal of the Transitional mode is to be a path to Native mode.

The team has also decided to rebrand Classic mode to “Reader” mode, instead of deprecating it. It provides a basic AMP template for getting started that doesn’t necessarily match the site’s theme. Users can can add an “Exit Reader Mode” to the header of their sites with a setting in the Customizer.

Version 1.1 introduces compatibility with the PWA feature plugin, bringing support for the service worker to AMP pages. It extends the service worker to cache AMP CDN assets, images, and Google Fonts. Since the PWA feature plugin is still under active development, the service worker integration is still considered experimental.

Support for creating AMP Stories in WordPress is the next major feature coming to the plugin. A pre-release of the AMP Stories editor is available in 1.2 alpha 1, which also requires the latest version of the Gutenberg plugin. It uses the Gutenberg editor to allow users to build AMP stories with rich media capabilities.

Amp stories

A preview of the AMP Stories editor was unveiled at AMP Conf 2019 in Tokyo, Japan. Check out the video below to see Alberto Medina give a quick demonstration of how it will work in the upcoming version 1.2 of the AMP for WordPress plugin.

Would you like to write for WP Tavern? We are always accepting guest posts from the community and are looking for new contributors. Get in touch with us and let's discuss your ideas.


  1. Awesome! I uninstalled AMP couple weeks ago after it keep showing certain error I could not fix for every mew post. I hope the issue will be fixed with this release.


  2. Awesome news! This is a great update. AMP technology which is properly paired together with service worker makes a perfect match for speeding up overall performance and user experience.


  3. That’s a great news. I am also using amp plugin in my website and I am also facing some issues but hope this version can resolve that.


  4. I tried several amp plugins and they always have errors with data structure in Google test , anyone else have same issue


    1. Yes, Same Here.. I actually created my own code to fix the schema issue. But Can anyone suggest me some good amp plugin?


  5. How can we use AMP and be GDPR compliant with opt out for user?


      1. How does this plugin add an opt out possibility for AMP?

        A simple notice is not enough for GDPR compliance.


      2. How can user opt out from sending his/her personal data like IP address to third party servers like

        Can’t see how some generic cookie plugin would be able to handle this.


  6. Amp is anti web, anti standards, and most importantly unneccessary. The WordPress community should not support this project in any way.


Comments are closed.