About Monster Arcade

What Monster Arcade is

Monster Arcade is a browser gaming site built around one narrow idea: original monster-themed arcade games that start instantly, run entirely in your browser, and are worth coming back to. There are thirty of them across six categories, and a library of guides explaining how they work and how to get better at them.

Everything on this site was made for this site. The games, the creatures, the artwork, the sound effects, the difficulty curves and the articles are all original work. We do not host third-party games, we do not embed games from portals, and we do not use characters, sprites, music or trademarks belonging to anyone else. That is unusual for a free browser game site and it is the single decision that shapes everything else about how we work.

Why the site exists

Free browser game portals mostly work by aggregating other people's games. That model produces enormous libraries and almost no accountability: when a game is broken, unfair or simply uninteresting, nobody at the portal can do anything about it, and the articles written about those games are necessarily written from the outside.

We wanted the opposite arrangement. Because we write the code that decides how fast an enemy moves or how wide a timing window is, we can tell you those numbers, explain why they are what they are, and change them when playtesting shows they are wrong. Almost every guide on this site contains something that could only be written by the people who built the game.

The second reason is quality of experience. A browser game should load in under a second, work the same on a phone as on a desktop, be usable with a keyboard, respect a reduced-motion preference, and never interrupt you. Those things are achievable but they require somebody to actually care about them, which is easier when there are thirty games rather than three thousand.

How the games are made

Every game runs on a shared HTML5 engine we wrote in plain JavaScript — no frameworks, no game engine, no build-time dependencies. The engine handles the canvas, the game loop, input, collision, particles, audio, game states, personal bests and touch controls. Each individual game is a small configuration object plus its own update and draw functions.

That architecture is why the library is consistent. Pause works the same way in all thirty games. So does the sound toggle, the restart key, the tab-visibility pause and the way a personal best is recorded. A player who learns the controls of one game has learned most of the controls of all of them.

Artwork is drawn procedurally on canvas with primitives rather than loaded from sprite sheets. That keeps the whole site small and resolution-independent, and it means every creature on the site is defined in code we wrote rather than in an asset we acquired.

• No downloads. Every game runs in the page you are already on.
• No accounts. There is nothing to sign up for and no profile to create.
• No server. The site is fully static, which is why there are no global leaderboards — a score we could not verify would be meaningless.
• No third-party game code. Nothing here is embedded from elsewhere.

How the content is made

Articles are written and edited under a single editorial byline, and every one of them is reviewed against the game code before publication. If a guide says a combo window is two seconds, somebody has checked that number in the source rather than estimated it from playing.

We publish under a documented editorial policy and a fact-checking policy, both of which describe our process honestly — including where AI tooling is used and where it is not. If we get something wrong, the correction process is described there too.

We do not publish fabricated statistics, invented player counts, fake reviews or made-up awards. Where a guide needs a number, it is either a number from our own code or it is clearly attributed and linked. Where we do not know something, the article says so.

Accessibility and performance

Accessibility is treated as part of the build rather than an afterthought. Every page is semantic HTML with a skip link, visible focus states, labelled controls and a keyboard path through everything that matters. Games can be paused, restarted and muted from real buttons, and the whole site honours the operating system's reduced-motion setting by cutting animations and particle effects.

We are not claiming the site is perfect. Fast arcade games have real accessibility limits, and some of ours are harder to play with a screen reader or with limited motor control than we would like. Where we know about a gap, we would rather say so than imply it does not exist — and reports from people who hit one genuinely shape what we build next. The contact page is the fastest route.

On performance, the target is simple: every page interactive in under a second on a mid-range phone. No web fonts, no frameworks, no tracking scripts, inline SVG rather than icon fonts, and artwork drawn in code rather than downloaded.

How the site is funded

Monster Arcade is intended to be supported by display advertising. That is why there are clearly-marked advertising containers on some pages. Advertising here is subject to rules we set for ourselves: never over a game, never over a control, never between you and a button you were about to press, and never styled to look like navigation or game content.

The games themselves are free and will stay free. There is no premium tier, no paid unlock, no in-game purchase and no virtual currency with any real-world value. Collectibles in the games are scoring objects and nothing else.

Contact

Bug reports, factual corrections and accessibility barriers are the three things we would most like to hear about, and they get handled first. The contact page explains what to include and how the form actually works — including a plain statement that, because this is a static site, the form cannot send mail on its own.