Cloudflare Pages includes a number of "good defaults" for serving your Pages sites. This page details some of those decisions, so you can understand how Pages works, and how you might want to override some of the default behaviors.
If an HTML file is found with a matching path to the current route requested, Pages will serve it. Pages will also redirect HTML pages to their extension-less counterparts: for instance,
/contact.html will be redirected to
/about/index.html will be redirected to
Not Found behavior
You can define a custom page to be displayed when Pages can't find a requested file by creating a
404.html file. Pages will attempt to find the closest 404 page, that is, if one isn't found in the same directory as the route you're currently requesting, it will continue to look up the directory tree for a matching
404.html file, ending in
/404.html. This means that you can define custom 404 paths for situations like
/404.html, and Pages will automatically render the correct one depending on the situation.
Single-page app (SPA) rendering
If your project doesn't include a top-level
404.html file, Pages assumes that you're deploying a single-page application. This includes frameworks like React, Vue, and Angular. Pages' default single-page application behavior matches all incoming paths to the root (
/), allowing you to capture URLs like
/help and respond to them from within your SPA.
Caching and performance
Pages includes good caching defaults. That means that every time you deploy an asset to Pages, it remains cached on our CDN until your next deploy. As much as possible, Pages sets
If-None-Match headers to allow clients to also cache content in their browsers — for more details on these behaviors, check out the MDN . Pages will also serve Gzip and Brotli responses whenever possible.