What is a game design document (GDD)?
A game design document (GDD) describes a game’s vision, rules, systems and content for the team that builds it.
How it works
Studios long wrote one large GDD before production, as Tim Ryan’s 1999 guide in Game Developer describes. Most teams now keep a living GDD: a short overview that links to one document per system, character or level, each with an owner.
A GDD serves design, art, code, audio and production at once, so it works best when each part is easy to find, dated, and clear about what is decided and what is still being explored.
An example
A small team’s GDD has an overview page linked to documents for combat, the economy, the main characters and the first level. The economy document holds the balance sheet the designers tune, not a copy of it.
Common mistakes
- Writing one long document nobody reads past the first pages.
- Letting the GDD and the game drift apart without dating changes.
- Keeping balance numbers in a separate spreadsheet the GDD only describes.
In Nodary
In Nodary, a GDD is a set of linked documents on the project’s map, with balance sheets that compute, branching dialogue, string tables, moodboards and picture review in the same workspace. A free GDD template of linked Markdown files, in 12 languages, imports in one step.
What Nodary does not do: dialogue conditions and variables are not modelled: branching dialogue is written, played through and exported to Yarn Spinner.
Game design document software · Free GDD template
Try it on your own documents. The Free plan needs no card.
Create a free workspace