• websites

Using the Google AMP Cache


The Google AMP Cache stores valid AMPs and provides a consistently fast access to AMPs. It is available for anyone to use.

AMP Cache URL Format


Here is AMP Cache URL for

The converted AMP Cache URL consists of the following parts:

  • amp-dev: the publisher domain converted into a subdomain using the algorithm described above.
  • the AMP Cache domain.
  • c: to indicate that it's an AMP document (there is also i for image and r for resources such as fonts).
  • s: indicating that the AMP Cache fetches the content from the origin using TLS (secure HTTPS).
  • the original URL excluding the scheme.

It is OK for URLs to include parameters in the query string, simply include these in the AMP Cache URL as well.


Cache updates

The AMP Cache uses a one-behind caching model which can be controlled by the max-age cache directive. You can test the behavior with this sample page, which will prints the current date at serving time:

Max-age 15s:

Redirect & Error Handling




$ curl -I

HTTP/1.1 301 Moved Permanently



If you move the location of the AMP Files on your server, make sure to set up a redirect from the old location to the new one.

Not Found



Invalid AMP

When a page is invalid AMP, the AMP Cache will return a 404 status.


Server Errors



Need further explanation?


Go to Stack Overflow
An unexplained feature?


Edit sample on GitHub