Arcade Errors
Playable HTTP error pages—one .html file per status code
Start new thread
Volker Geith

Arcade Errors - Playable HTTP error pages—one .html file per status code

by•
35 fully playable arcade games, one per HTTP error code. Drop-in HTML files, zero dependencies. For nginx, Apache, Caddy and any web server.

Add a comment

Replies

Best
Volker Geith
Maker
📌
Hi PH — I built Arcade Errors because default error pages are where good UX goes to die: users hit a dead wall of plain text and leave. So I shipped 35 re-imagined, playable micro-games, one per HTTP status (4xx + 5xx). Each is a single static .html file — no build, no framework, no dependencies. Point nginx / Apache / Caddy (or any static host) at the file and you’re done. One 502 game is free forever on the site so you can try before you buy. Paid bundles run through Paddle; if you’re grabbing a bundle this launch window: 20% off with APRILFIRST in the discount field (through 18 April 2026). Happy to answer setup questions, server configs, or what to add next (WordPress plugin / npm are on the roadmap). What error code would you turn into a game first?