1. The game must be playable

Playable means the game offers a real action loop. The player can start, interact, receive feedback and reach either progress, failure, victory or a clear next objective. A black screen, frozen canvas, instant draw, instant fall or static scene with no meaningful interaction is not enough. It might be a prototype, but it is not a published game.

During review, we look for the first thirty seconds. Does the player know what to do? Do controls respond? Are hazards visible before they damage the player? Does the first level introduce the core idea safely? Does a restart or next level work after success or failure? Many bugs appear only after the first win, so we check progression, not only initial load.

2. The description must match the game

Accurate descriptions are part of content quality. If a hotel manager page says you can move guests to rooms, that action must exist. If a fire station game mentions fire trucks, the trucks should appear as usable game objects. If a bridge builder help panel promises materials, the interface needs materials or the text should be rewritten. Players quickly lose trust when a game title and help text describe a better game than the one on screen.

For Community Games, the submitted short and long descriptions must explain the actual game. Marketing fluff is not useful. A good description tells players what they do, what makes the game interesting, which controls matter and whether the game is desktop-first or mobile-friendly.

3. Controls must respect the page

Browser games live inside a document, so they must cooperate with the page around them. Keyboard handlers should not break comment forms, submission forms or normal browser behavior unless the player is actively controlling the game. Spacebar should not scroll the page while a ship is flying. At the same time, a text field should be able to type a space. This balance is essential.

Touch controls are reviewed separately. Joysticks and buttons should not cover key hazards, dialogue choices or the player character. On mobile, large controls are useful, but they need safe zones. A game that is technically "mobile friendly" but hides the game under buttons is not ready.

4. Difficulty must be human

Some games are meant to be hard, but difficulty should create decisions instead of confusion. Time management games should not spawn orders faster than a new player can understand the interface. Easy difficulty should be noticeably easier. Platformers should start on solid ground. Runners should align visible platforms with collision platforms. Strategy games should give setup time before enemies arrive.

When a game fails too quickly, the first fix is usually pacing. Add a countdown, reduce first-wave speed, increase safe distance, create a training objective or make the first round longer. Difficulty should rise after the player learns the verbs.

5. Safety and external links

Supagames browser games should play in the browser. Community submissions may link to external sites, but they should not require suspicious downloads, misleading installers, forced extensions or unsafe redirects. External game links are treated as user-generated content and may use link attributes that signal moderation and reduce abuse.

We also reject adult content, hate content, malware-like behavior, deceptive ads and games that primarily exist to collect data unrelated to play. A simple creator credit is fine. A page that makes players hand over sensitive information before playing is not a fit for the directory.

6. Original value matters

A familiar genre is allowed. Snake, Pong, Minesweeper and platformers are classics for a reason. But a submission should still offer some original value: a clean implementation, a theme, a level set, a polished control scheme, a useful learning example, a strong art direction or a clever variation. Renaming the same weak prototype twenty times does not help players.

For internal Supagames pages, this standard also guides fixes. If five games use the same action loop, each game should earn its title with different enemies, objectives, visual identity and progression. A vampire hunt should not feel like a robot shooter with different text. A dungeon game should use exits, floors, items and enemies that fit the theme.

Moderation statuses

Moderation is not meant to punish creators. It protects the directory and gives serious submissions a better chance to be seen. When possible, a needs-changes decision is better than rejection because it tells the creator what to improve.