AMP HTML source code, samples, and documentation. See below for more info.
JavaScript HTML Python CSS Java Protocol Buffer Other
Latest commit 07b6bdc Feb 21, 2017 @muxin muxin committed on GitHub Add viewer integration script based on amp_js_v (#7703)
Failed to load latest commit information.
.github Create a pull request template for the project. (#7193) Jan 25, 2017
3p Added AdThrive ad support (#7584) Feb 17, 2017
ads Added AdThrive ad support (#7584) Feb 17, 2017
build-system Add viewer integration script based on amp_js_v (#7703) Feb 21, 2017
builtins Ensure that it's not lost that amp-img supports sizes (#7496) Feb 11, 2017
contributing Information about & new folder (#7469) Feb 21, 2017
css Measure document height when necessary and send to viewer (#7327) Feb 17, 2017
examples Add viewer integration script based on amp_js_v (#7703) Feb 21, 2017
extensions Allow allowpaymentrequest attribute on amp-iframe (#7693) Feb 21, 2017
screenshots/test/manual Updated screenshots Jan 27, 2016
spec Add copyright to managing user state doc (#7697) Feb 21, 2017
src Replace CLICK_X and CLICK_Y in anchor href for amp-inabox. (#7660) Feb 21, 2017
test Add viewer integration script based on amp_js_v (#7703) Feb 21, 2017
testing Ensure that parent is always set in FakeWindow (#7435) Feb 8, 2017
third_party Support <amp-social-share type="system"> (#6688) Jan 31, 2017
tools Send expected errors to expected bucket (#7650) Feb 21, 2017
validator Make some ValidatorRulesMakeSense errors more verbose (#7620) Feb 17, 2017
.babelrc add destructuring to babel transform whitelist (#4206) Jul 26, 2016
.eslintrc Forbid assignments inside a conditional (#7486) Feb 10, 2017
.gitignore Implementing amp-playbuzz extension (#6106) (#6351) Dec 12, 2016
.travis.yml Revert "Fix build breakage" (#6568) Jan 26, 2017
AUTHORS Initial commit Sep 2, 2015 Establish a code of conduct for the AMP open source project. Oct 15, 2015 Update CONTRIBUTING Weekly Status & Design Review sections with the l… Feb 7, 2017
CONTRIBUTORS Update contributors. (#7313) Feb 2, 2017 Design principles for development on AMP (#4170) Jul 23, 2016 Update (#7294) Feb 1, 2017 Update core comitters May 9, 2016
LICENSE fix(license): fix incorrect search and replace done on LICENSE file Sep 10, 2015
OWNERS.yaml test owners files (#4863) Sep 8, 2016
Procfile Allow binding to specific hostname or IP, default to localhost (#4422) Aug 9, 2016 Fix broken shields (#7051) Jan 18, 2017 add new tick events (#4593) Aug 23, 2016
gulpfile.js Removes amp-tabs since we are doing it as an example using amp-select… Feb 15, 2017
package.json Fix locally failing tests. (#7535) Feb 14, 2017 add custom closure compiler pass (#2593) Apr 22, 2016
yarn.lock Fix locally failing tests. (#7535) Feb 14, 2017

Build Status


AMP HTML is a way to build web pages for static content that render with reliable, fast performance. It is our attempt at fixing what many perceive as painfully slow page load times – especially when reading content on the mobile web.

AMP HTML is entirely built on existing web technologies. It achieves reliable performance by restricting some parts of HTML, CSS and JavaScript. These restrictions are enforced with a validator that ships with AMP HTML. To make up for those limitations AMP HTML defines a set of custom elements for rich content beyond basic HTML. Learn more about how AMP speeds up performance.

How does AMP HTML work?

AMP HTML works by including the AMP JS library and adding a bit of boilerplate to a web page, so that it meets the AMP HTML Specification. The simplest AMP HTML file looks like this:

<!doctype html>
<html ⚡>
    <meta charset="utf-8">
    <link rel="canonical" href="hello-world.html" >
    <meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1">
    <style amp-boilerplate>body{-webkit-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-moz-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-ms-animation:-amp-start 8s steps(1,end) 0s 1 normal both;animation:-amp-start 8s steps(1,end) 0s 1 normal both}@-webkit-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-moz-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-ms-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-o-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}</style><noscript><style amp-boilerplate>body{-webkit-animation:none;-moz-animation:none;-ms-animation:none;animation:none}</style></noscript>
    <script async src=""></script>
  <body>Hello World!</body>

This allows the AMP library to include:

  • The AMP JS library, that manages the loading of external resources to ensure a fast rendering of the page.
  • An AMP validator that provides a way for web developers to easily validate that their code meets the AMP HTML specification.
  • Some custom elements, called AMP HTML components, which make common patterns easy to implement in a performant way.

Get started creating your first AMP page.

Full docs and reference.

The AMP JS library

The AMP JS library provides builtin AMP Components, manages the loading of external resources, and ensures a reliably fast time-to-paint.

The AMP Validator

The AMP Validator allows a web developer to easily identify if the web page doesn't meet the AMP HTML specification.

Adding "#development=1" to the URL of the page instructs the AMP Runtime to run a series of assertions confirming the page's markup meets the AMP HTML Specification. Validation errors are logged to the browser's console when the page is rendered, allowing web developers to easily see how complex changes in web code might impact performance and user experience.

It also allows apps that integrate web content to validate the web page against the specification. This allows an app to make sure the page is fast and mobile-friendly, as pages adhering to the AMP HTML specification are reliably fast.

Learn more about validating your AMP pages. Also see additional choices to invoke the validator.

AMP HTML Components

AMP HTML Components are a series of extended custom elements that supplement or replace functionality of core HTML5 elements to allow the runtime to ensure it is solely responsible for loading external assets and to provide for shared best practices in implementation.

See our docs and reference for more info.


We push a new release of AMP to all AMP pages every week on Thursday. The more detailed schedule is as follows:

  • Every Thursday we cut a green release from our master branch.
  • This is then pushed to users of AMP who opted into the AMP Dev Channel.
  • On Monday we check error rates for opt-in users and bug reports and if everything looks fine, we push this new release to 1% of AMP pages.
  • We then continue to monitor error rates and bug reports throughout the week.
  • On Thursday the "Dev Channel" release from last Thursday is then pushed to all users.

You can always follow the current release state of AMP on our releases page. The release used by most users is marked as Latest release and the current Dev Channel release is marked as Pre-release.

AMP Dev Channel

AMP Dev Channel is a way to opt a browser into using a newer version of the AMP JS libraries.

This release may be less stable and it may contain features not available to all users. Opt into this option if you'd like to help test new versions of AMP, report bugs or build documents that require a new feature that is not yet available to everyone.

Opting into Dev Channel is great to:

  • test and play with new features not yet available to all users.
  • use in Q&A to ensure that your site is compatible with the next version of AMP.

If you find an issue that appears to only occur in the Dev Channel version of AMP, please file an issue with a description of the problem. Please always include a URL to a page that reproduces the issue.

To opt your browser into the AMP Dev Channel, go to the AMP experiments page and activate the "AMP Dev Channel" experiment. Please subscribe to our low-volume announcements mailing list to get notified about important/breaking changes about AMP.

Further Reading

If you are creating AMP pages, check out the docs on and samples on

These docs are public and open-source: See something that's missing from the docs, or that could be worded better? Create an issue and we will do our best to respond quickly.



Technical Specifications:

Who makes AMP HTML?

AMP HTML is made by the AMP Project, and is licensed under the Apache License, Version 2.0.


Please see the CONTRIBUTING file for information on contributing to the AMP Project, and the DEVELOPING file for documentation on the AMP library internals and hints how to get started.

Security disclosures

The AMP Project accepts responsible security disclosures through the Google Application Security program.

Code of conduct