Game Design Document (GDD)
π Blueprint: A living document that captures your game's vision, mechanics, and production plan. Fill in each section as your design evolves.
Download the Template
GDD Template (PDF)
Download β Download the full Game Design Document template as a PDF.
GDD Template (Google Docs)
Open β Open an editable copy of the GDD template in Google Docs.
1. Overview
- Title: [Game Name]
- Genre: [e.g., Roguelike, Platformer, RPG]
- Platform(s): [PC, Mobile, Console]
- Target Audience: [Age range, player type]
- Elevator Pitch: [2β3 sentences describing the game]
2. Gameplay
Core Loop
[Describe the primary repeated cycle of player actions]
Mechanics
- [Mechanic 1: description]
- [Mechanic 2: description]
- [Mechanic 3: description]
Progression
[How does the player advance? Levels, upgrades, story progression?]
3. Narrative
- Setting: [World, time period, atmosphere]
- Story Synopsis: [Brief plot outline]
- Characters: [Key characters and their roles]
4. Art Direction
- Visual Style: [Pixel art, low-poly, hand-drawn, realistic]
- Color Palette: [Primary colors and mood]
- Reference Games: [Games with similar art direction]
5. Audio
- Music Style: [Chiptune, orchestral, ambient, electronic]
- Key SFX: [List critical sound effects needed]
6. Technical Specs
- Engine: [Godot, Unity, Unreal, etc.]
- Min Requirements: [Target hardware specs]
- Networking: [Single-player, local co-op, online?]
7. Milestones
| Milestone | Target Date | Deliverables |
|---|---|---|
| Prototype | [Date] | Core loop playable |
| Vertical Slice | [Date] | One polished level/area |
| Alpha | [Date] | All content in, playable start to finish |
| Beta | [Date] | Feature-complete, bug fixing |
| Release | [Date] | Launch-ready build |
β οΈ Reminder: A GDD is a living document. Update it as your design evolves β an outdated GDD is worse than no GDD.
