Introducing the AMP Roadmap


The AMP Project is fast approaching its 100th release, which means 100 releases where stuff has changed—new features added, enhancements provided, and bugs fixed. Since its launch at the end of last year, the engagement from people across the industry has been incredible. It is clear that many are united in improving the mobile web, and your code submissions, feature requests, and support have been invaluable. But we all recognize that it can be tricky to stay fully up to date on AMP, which basically requires being plugged into each new issue and conversation in the project’s issue tracker.

Today, based on the guidance and feedback of the broader AMP community, we have compiled and are posting the AMP Roadmap on our project site. It is designed to help you understand at a quick glance the project’s current status and where it is heading.

Read the full AMP Roadmap at

This is something that many people who are interested in AMP have asked for. The AMP Roadmap is designed to encourage transparency and provide a shared sense of priorities to anyone using or supporting the AMP library. There is no formal process for the creation of the roadmap—instead consider it a guide, a non-exhaustive summary of the existing higher-volume, public information sources such as the GitHub issue tracker, mailing list, Slack channel for AMP developers, @amphtml Twitter updates, and others.

A tour of the AMP Roadmap

The AMP Roadmap presents information relating to AMP’s four main focus areas, which are: Format, Analytics, Ads, and Access.

  • Format covers visual elements like carousels and lightboxes, widgets like social embeds, video players, how AMP generally works, and basically anything not covered by the below areas.
  • Analytics covers the ways to collect analytics data from a web page, particularly by using features like amp-pixel or amp-analytics, and providing interoperability with data analysis solutions.
  • Ads covers anything related to enabling ads on AMP pages, providing interoperability with ad technology providers, and driving ad ecosystem innovation with the AMP format.
  • Access covers the amp-access element and anything related to providing content access controls to enable subscription and paid content support in AMP pages.

For each area, three sections offer a quick summary of what’s important to know:

  • Themes for the current quarter will tell you about high-level goals and feature plans. This area won’t be the place to look to learn about which specific feature has been built to support a particular use case, but it will help you get a sense for the types of features that are receiving development emphasis.
  • Status for the current quarter will give you a listing of the largest planned projects for the quarter and their progress, as of the most recent update to the roadmap.
  • The outlook for upcoming quarters will provide a summary of some of the projects being considered and that we expect to get further attention in the next six months.

Anything listed is subject to change, and you should expect greater change to listings that are mentioned for upcoming quarters.


The AMP Roadmap will be updated twice each quarter:

  • An update in the middle of the quarter will provide that quarter’s first detailed listing of projects and their status.
  • Around the end of the quarter the status of projects in the just-ended quarter will be updated, as well as any necessary changes to priorities forecasted for upcoming quarters.

Help shape AMP

To weigh in on the AMP Roadmap, suggest features or come talk to us. And of course, you are encouraged to contribute features or enhancements to the AMP Project anytime, even if they are not among the projects highlighted in the roadmap.

We hope you’ll find the AMP Roadmap helpful to your work involving AMP and look forward to your feedback.

Posted by Rudy Galfi, Product Manager