Endless Runner Arcade is an independent browser gaming site built around one idea: that the endless runner is a genre worth taking seriously, and that a site about it should be made of games you can actually play rather than links to games somewhere else.
What this site is
Every game here was written for this site. There are 30 of them, spread across 6 categories, and all of them run directly in your browser using HTML5 Canvas and JavaScript. There is nothing to install, no account to create, no plugin to enable and no paywall. You open a game page and you are playing within a second.
Alongside the games there is an editorial section: strategy guides, mechanical explanations and design write-ups covering how runners work and how to get better at them. Those are written by the same people who built the games, which means when a guide describes how a difficulty curve or a procedural generator behaves, it is describing a system we implemented and tuned rather than one we read about.
Everything here is original
This matters enough to state plainly. Every game, character, environment, obstacle, collectible, sound effect and piece of artwork on Endless Runner Arcade was created for this site.
- No game here is a clone or recreation of any commercial title.
- No copyrighted characters, sprites, environments, logos or level designs are used anywhere.
- All sound is synthesised at runtime with the Web Audio API — there are no audio files, sampled or licensed, in the project at all.
- All artwork is generated procedurally from code or produced specifically for this site.
The games are inspired by the endless-runner genre as a whole — forced forward motion, a small verb set, rising difficulty — in the same way that any platformer is inspired by platformers. They are not inspired by, based on, or derived from any specific commercial game.
How the games are built
All thirty games run on a single shared engine written in plain JavaScript with no framework, no build step and no dependencies. A game is a configuration: a mode (lane, side-view, platform, flight or vertical), a palette, a list of abilities, a set of hazards, a collectible and a handful of tuning numbers.
That architecture is deliberate. It means a new game is a data change rather than a new codebase, it means a fix to collision or input improves every game at once, and it means the whole site stays small enough to load instantly on a phone. The trade-off is that games here share a family resemblance in how they feel, which we think is a fair price.
If you want the detail, How Endless Runner Games Work walks through the engine, and How Procedural Generation Works in Runner Games covers the level generator.
What we do not do
A few commitments that shape the site:
- No fabricated numbers. You will not find invented player counts, star ratings, review totals or "trending" rankings anywhere on this site. We do not have that data, so we do not display it.
- No global leaderboards. Scores are stored in your own browser using LocalStorage and are never uploaded. Anywhere a ranking appears it is labelled "Local High Scores", because that is exactly what it is.
- No accounts. There is nothing to sign up for, which means there is no personal data for us to hold.
- No ads over gameplay. Advertising, where present, sits in clearly marked containers outside the play area. Nothing covers the canvas, the controls or any button.
- No dark patterns. No fake close buttons, no misleading download prompts, no ads disguised as game controls.
Editorial standards
Guides on this site are written to be genuinely useful rather than to hit a word count. Where we make a factual claim about gaming history or technology we say what our basis is, and where something is a matter of interpretation — like which game "started" the endless runner genre — we say that too rather than presenting a tidy answer that does not exist.
We do not invent statistics, studies or expert quotes. If a number is not something we measured or can point to, it does not appear. Our full approach is set out in the Editorial Policy and the Fact-Checking Policy.
Accessibility
Canvas content is invisible to assistive technology, so everything a player needs to know exists as real HTML outside the canvas: controls, objectives, obstacle explanations, scoring rules and tips are all on the page. Interactive controls are real buttons with labels and focus states, the site is fully keyboard navigable, no game requires two simultaneous inputs, and decorative animation respects prefers-reduced-motion.
We are not claiming full WCAG conformance — a real-time action game has inherent barriers we cannot remove — but we take the parts that can be done properly seriously. If something on the site is not usable for you, we would genuinely like to hear about it via the contact page.
Who makes this
Editorial content is published under the byline Alex Morgan, Browser Games Editor. Alex Morgan is an editorial persona representing the site's team rather than a single named individual, and we say so openly rather than inventing a biography. Full details are on the author page.
Get in touch
Corrections, bug reports, accessibility issues and general feedback are all welcome. The contact page explains how to reach us and is honest about what the form on that page does and does not do.
Last updated: 15 septembre 2026