What
A Game Design Document is the shared spine of the team: what the game is, who it is for, what the core loop is, and how it ships.
Game Development
A Game Design Document is the shared spine of the team: what the game is, who it is for, what the core loop is, and how it ships.
Fill the four sections, load the sample if you need a template, keep docs in the browser, and copy Markdown when ready to share.
High concept, genre, platforms, audience, and differentiators.
What makes this game different?
Story, characters, and the feel of the world.
Name + short role
Core loop, mechanics, controls, progression, and levels.
Playable rules
Art, audio, monetization, tech, milestones, and risks.
Measurable delivery points
What could break the core
Guide
A Game Design Document is the shared spine of the team: what the game is, who it is for, what the core loop is, and how it ships.
Without a short GDD, teams scatter into details before the core loop is clear.
Fill the four sections, load the sample if you need a template, keep docs in the browser, and copy Markdown when ready to share.
Go deeper
Need a short, shareable GDD? This tool gathers the classic design-doc sections so your team can align on the core — no extra software and no signup.
Start a blank doc or load the Echo Drift sample as a template.
Cover concept, narrative, gameplay, and production; use lists for USPs, mechanics, and milestones.
Copy Markdown when ready, or keep the doc in your browser for later.
Capture the core loop and audience before building a prototype.
Art, audio, and engineering work from one shared spine.
Students practice writing a GDD without a blank Word template.
In your browser (localStorage); nothing is required to upload to a server.
No — a living short doc beats a locked 100-page tome. Add detail after the core loop is proven.