A game design document (GDD) is the shared blueprint of your game. It keeps designers, artists, developers and clients aligned. The best GDDs are living documents – short, visual and constantly updated – not 200-page novels nobody reads.

1. Vision in one page

  • Elevator pitch: one or two sentences.
  • Target audience and platforms.
  • Genre and references: "like X meets Y".
  • Unique hook: why players will choose this game.
  • Business model: premium, free-to-play, ads, client-funded.

2. Core loop

Describe what the player does again and again, for example: explore → collect resources → craft upgrades → beat harder levels. A clear core loop is the single most important part of the GDD.

3. Mechanics and controls

  • Player actions and controls per platform (touch, mouse, controller)
  • Rules, win/lose conditions
  • Physics, camera behaviour
  • Enemy or obstacle behaviour

4. Progression and economy

  • How players advance: levels, XP, unlocks, story chapters
  • Currencies (soft and hard), sources and sinks
  • Rewards, difficulty curve and balancing targets

Economy tables in a spreadsheet are often clearer than prose.

5. Content plan

  • Number of levels, worlds, characters, items
  • Level design principles and a sample level layout
  • Narrative outline and dialogue style, if any

6. User interface and flow

Screen flow from launch to gameplay: splash, main menu, level select, HUD, pause, shop, settings. Simple wireframes are enough.

7. Art and audio direction

Mood boards, colour palette, character style, UI style, music genre and sound-effect list. Include technical limits such as polygon budgets for mobile.

8. Monetisation and live-ops

Store items, ad placements, battle pass or events – and the rules that keep it fair. Plan analytics events now so you can measure retention and conversion later.

9. Technical requirements

Engine, target devices, minimum specs, online features (accounts, leaderboards, multiplayer), save system, localisation and accessibility.

10. Scope and milestones

Prototype, vertical slice, alpha, beta and launch – with the features each milestone contains.

Keep it alive

Store the GDD in a wiki or shared document, link to prototypes and update it after every playtest. A GDD that reflects the real game is worth far more than a perfect document from day one.

Planning a game? Our AI assistant asks the key GDD questions and turns your answers into a first brief for our team.

Planning a project like this? Our AI project assistant asks the right questions for your field and turns your answers into a clear brief – then our team near Munich sends a free, non-binding quote within 24 hours on business days. Start now or read the complete Game Development guide.
#Game design#GDD#Pre-production