Your error page.
One file. Ready to play.

Start with a 404

1. Choose a game below and download its 404 file.
2. For GitHub Pages, rename it 404.html and put it in your published site's root. For other hosts, upload it and select it in your host's error-page settings.
3. Visit a made-up, nested URL on your site. Check that the game appears and the response still says 404.

For nginx or Apache, the full download includes configuration examples for 403, 404, 500, 502, 503, and 504.

What works without a connection?

Once this file has loaded, the game needs no further network requests. A 404 means the server answered but could not find the page. A completely offline first visit cannot receive an error page. Offline navigation needs a previously installed service worker and cached fallback; that is a separate integration.

For an application outage, serve these files from a working web server or proxy. For a CDN error, configure the page at the CDN. An unavailable server cannot deliver its own error page.

Choose your error and game

35 error-code templates, with five of our existing games for each. These are page templates; your host determines which errors can use them. The game artwork may still contain a 404 motif.