About Food Arcade

What Food Arcade is

Food Arcade is a free browser game site built around a single idea: food-themed arcade games, made properly. There are thirty of them, they are all original, they all run directly in the browser, and none of them require an account, a download or a plugin.

Alongside the games there is an editorial library explaining how the mechanics work — how a combo chain converts into a multiplier, why an endless runner's difficulty curve flattens out, how a browser saves a high score. That library exists because the questions are genuinely interesting and because most game directories never answer them.

The site is deliberately small in scope and deliberately deep. We would rather publish thirty games each with a real page explaining how it works than three hundred embedded frames with a paragraph apiece.

What games are available

All thirty games sit in six categories: food platformers, endless food games, food collection games, cooking arcade games, food rush games and food reflex and skill games.

They range from one-button timing tests that last ninety seconds to a twelve-round gauntlet that takes real practice to finish. Every one of them has a start screen listing its controls, on-screen touch buttons where they make sense, four difficulty presets and a local high score.

The food in these games is fictional. Burgers, pizza slices, fruit and ingredients are collectible tokens with point values — game objects, not products. Food Arcade does not sell food, endorse food brands, or offer nutritional, dietary or food-safety guidance of any kind.

Why the site exists

Browser gaming has a quality problem that has nothing to do with the games themselves. The technology is excellent: HTML5 canvas, the Web Audio API and modern JavaScript are more than capable of running a polished arcade game on a mid-range phone. What tends to be missing is care — sites that embed hundreds of third-party games behind aggressive advertising, with no description worth reading and no way to tell whether anything on the page actually works.

Food Arcade is a small argument that the alternative is possible. Original games, written from scratch. Real pages that describe what a game does before you press start. Advertising kept away from the play area. Scores stored on your device instead of behind an account.

How the games are developed

Every game on this site is built with HTML5, CSS3 and vanilla JavaScript. There is no framework, no game engine and no third-party runtime. The whole arcade runs on one shared engine written specifically for it, which is why thirty games load as quickly as one would.

That engine provides the parts every game needs: a main loop with a clamped delta time, canvas scaling that adapts to any aspect ratio, an input layer that unifies keyboard, mouse and touch, a state machine covering loading, ready, countdown, playing, paused, game over and victory, a collectible catalogue, a combo system, six power-ups, a difficulty model and a LocalStorage records layer.

Individual games are then written as configurations of one of eleven gameplay templates plus their own specific twist. Burger Rush and Donut Run share a runner template but differ in theme, food pool, physics tuning and — crucially — in the mechanic layered on top: an ingredient build order in one, a sugar meter in the other.

All artwork is drawn at run time from canvas primitives and standard system emoji. All sound is synthesised at run time with the Web Audio API. No image files, no audio files, no third-party assets — which means nothing on this site infringes anyone's artwork and the whole arcade downloads in well under a megabyte.

How the games are tested

Before a game is published it is played to a game-over state on all four difficulty presets, on a desktop browser and on a phone, in both portrait and landscape. That test confirms the basics: controls respond, collisions register, the score and combo readouts match what happened, pause and restart work, the local high score is written and read back, and the touch buttons never overlap the score display.

• Fairness — every generated gap is checked against the character's real jump reach at the current speed, so a level can never ask for a jump the physics cannot deliver.
• Difficulty ceilings — every ramp is confirmed to flatten out. A curve that rises forever stops measuring skill.
• Frame-rate independence — movement is expressed per second, not per frame, and the loop clamps long frames so a stutter cannot teleport the player into a hazard.
• Error handling — if a game fails to start, the page says so and offers a reload and a route back to the arcade. A blank canvas is treated as a bug.
• Accessibility — keyboard-only play, visible focus states, controls listed as text outside the canvas, and reduced-motion support that genuinely reduces motion.

How editorial content is produced

Guides are written by Alex Morgan, the site's editorial persona, under a published editorial policy and fact-checking policy.

The core rule is that claims about this site's games are verified against this site's game code. When an article says the combo multiplier steps up at four, nine, sixteen, twenty-five, thirty-eight and fifty-five items, those are the actual thresholds in js/game/scoring.js. When it says the magnet power-up has a radius of 190 units and a pull strength of 480, those are the values in js/game/powerups.js.

Claims about web technology are checked against primary documentation — the relevant specification or MDN — and linked where a reader would benefit. We do not cite studies we have not read, we do not quote people who did not say the thing, and we do not publish statistics we cannot source.

Originality standards

Every game, every line of code, every description and every article on this site is original to it. We do not embed third-party games, we do not reuse other sites' copy, and we do not recreate the mechanics, characters, levels, music or interfaces of existing commercial games.

Genre conventions are shared — jumping, collecting, combo multipliers and order tickets belong to everyone. Specific creative work does not. Where our games use familiar arcade ideas, they use them the way every arcade game does, with their own characters, their own art and their own systems.

Accessibility commitment

Games are difficult to make accessible, and we do not claim to have solved it. What we have done is concrete and testable:

• Every game is fully playable with a keyboard alone. Arrow keys and WASD move, Space and Enter act, P and Escape pause, R restarts, M mutes.
• Every game's controls are listed as text on the page, outside the canvas, where a screen reader can read them.
• Touch targets are 58–64 px, well above the 44 px minimum, and are positioned away from the score display.
• Reduced-motion preference is respected in the CSS and in the games themselves: particle budgets drop to a quarter, background parallax stops and celebration effects are suppressed.
• Focus states are visible everywhere, at a 3 px outline that does not rely on colour alone.
• Colour is never the only carrier of meaning — hazards have distinct shapes and glyphs as well as distinct colours.
• One-Tap Food Catcher is playable with a single discrete input, which makes it usable with most switch-access hardware.

If something on this site is inaccessible to you, tell us. That feedback is more useful than any audit.

Privacy principles

Food Arcade has no user accounts, no login, no newsletter and no server-side profile. Your scores, favourites and play history are stored in your own browser using LocalStorage and never leave your device. There is no global leaderboard on this site because there is no server that could build one.

The privacy policy and cookie policy describe exactly what is stored, under what key and why — and describe advertising honestly rather than vaguely.

Who runs the site

Food Arcade is an independent site operated by a small team. We are not a studio, a publisher or part of a network, and we make no claims about company size, funding, awards or credentials, because unverifiable claims are worth nothing to a reader.

What we can tell you is what is checkable: the games are ours, the writing is ours, the code runs in your browser where you can inspect it, and the contact address on the contact page is read by a person.

Frequently Asked Questions