Overview for game developers
What kind of HTML5 game fits One Game a Day, how each game is hosted on its own isolated origin, and what the platform adds around a published game.
Game package format
The folder format for a game: the entry HTML file, allowed and rejected file types, size limits, path rules, and what the validator checks and warns about.
game.json metadata reference
Complete reference for game.json: every field, its type, limits and meaning, what happens when a field is left out, and full valid examples to copy.
Sandbox and permissions
What a game can and cannot do inside its sandboxed frame, the permissions it can ask for and what each unlocks, and how saves and storage behave.
Publishing workflow
From folder to release day from a developer's point of view: validation, thumbnail, scheduling, going live, and updating a game later with new builds.
Submitting a game
There is no public submission form yet. Games are added by the One Game a Day team; this page gives the technical and quality checklist a game must meet.