Know a company with years of records? Refer it and earn up to $100K
Game development resource

Game Design Document: Template, Format and Examples

What a game design document (GDD) is, the sections a GDD template needs, which format to use, published examples and a sample outline to adapt.

Short answerChecked

A game design document (GDD) is the written plan for a video game: what the game is, who it is for, how it plays and what the team must build. A typical GDD covers the vision and logline, player experience goals, the game world, mechanics, characters and story, user interface, audio and prototype plans. Most teams now keep it as a living wiki or a set of linked pages rather than one long file.

Concept document length
One to two pagesTim Ryan, Game Developer
Who writes the GDD
The lead designerTechnical spec: senior programmer
Common home today
A living wiki or linked docs
An open loan file with a closing checklist and a house key
Key points
  • A GDD says what the game is and what it is not, so every discipline builds the same game.
  • Lead with a vision statement, a logline and a gameplay synopsis; describe each player action by its input, limitation and outcome.
  • Pick the format your team will actually read: a living wiki, linked documents, one-page diagrams or slides.
  • Date every version and keep the history. Old design documents explain why the game turned out the way it did.

What is a game design document?

A game design document, or GDD, is the plan the whole team works from. Game Developer describes design documents as the "blueprints" for putting together a game (Game Developer). In 1999, designer Tim Ryan put the job this way: "The purpose of design documentation is to express the vision for the game, describe the contents, and present a plan for implementation" (Game Developer).

A video game design doc has many readers. The 2023 guide says your GDD "needs to be crystal clear to artists, animators, engineers, systems designers, level designers, sound designers, musical composers, marketers, producers" (Game Developer). That is why it should say plainly what the game is, and also what it is not. Solo developers benefit too: "If you are a solo developer, you may still find a GDD helpful as a reference for yourself".

A GDD is a plan, not a promise. Cornell's CIS 3152 game course tells student teams that their early gameplay specification is not final: "you should not consider this a binding document" (Cornell CIS 3152). The document records the current design, and the design changes after every round of playtesting.

Which documents make up a game design document?

On larger projects the design is split across several documents. Ryan wrote that "Design documents come in stages that follow the steps in the development process": a concept document and a game proposal first, then "the functional specification, technical specification and level designs" (Game Developer). Many teams now simply call the functional specification the GDD.

DocumentWhat it answersUsual authorTypical length
Concept documentWhat the game is, and why it stands outDesigner or creative leadOne to two pages
Game proposal or pitchWhy the game is worth making: audience, platforms and scopeDesigner with a producerA short document or deck
Game design document (functional specification)How the game plays: mechanics, world, characters, interface, audioLead designer, with input from every disciplineAs long as needed, kept current
Technical design documentHow the team will build it: engine, systems, tools, data formatsSenior programmer or technical directorA separate document
Level designsLayout, flow, encounters and goals of each levelLevel designersOne per level or area

Ryan describes the concept as "a one- to two-page document that's necessarily brief and simple in order to encourage a flow of ideas", with an introduction, an optional background, a description, key features, genre, platforms and optional concept art. The lead designer writes the design documents; the technical specification is "written by the senior programmer or technical director" (Game Developer).

Game design document template: what sections should a GDD include?

There is no single correct GDD template. Game Developer notes that veteran designers "discourage their peers from blindly copying other GDD formats" (Game Developer). Use the sections below as a checklist, drop the ones your game does not need, and link the sections to each other so a reader can follow a mechanic to the level that teaches it.

GDD template sectionWhat to writeTip
IntroductionA vision statement, a one-sentence logline and a short gameplay synopsisWrite it last; keep it to one page
GoalsPlayer experience goals: what the player should feel; any business goalsUse them to settle design arguments
Game worldHow the world is divided (levels, hubs, an overworld) and how the player moves through itA rough map and reference art beat long paragraphs
Mechanics and actionsEach player verb: its input, its limits, its outcome and how central it isDiagram the core loop
Characters and storyWho the characters are, how they relate, and the plot outline or a link to the scriptScale it to how story-driven the game is
User interface and controlsThe control scheme, HUD and menus, and a flow chart of screensList the UI art the team must make
AudioMusic, sound effects and voice needs, with referencesA media list helps the audio team plan
Prototype planWhich unproven mechanics to test first, on paper or in the enginePrototype the riskiest idea first
Technical notes and scopeEngine, platforms, target hardware and what is out of scopeLink the technical design document

The table follows the 2023 guide. Its author, a game design teacher, writes: "I suggest that they lead with a vision statement, a logline, and a gameplay synopsis." The goals section "is an excellent place to define player experience goals", one approach for the interface is to "map out the control scheme of your game", and for audio "A media list can also be helpful here" (Game Developer).

For mechanics, Cornell's course asks four questions of every player action: "What is the input to activate this action? What are the limitations (if any) for the action? What is the immediate outcome for this action? How important is this verb to your game?" (Cornell CIS 3152).

What format should a game design document use?

The best game design document format is the one your team reads and keeps current. Four formats are common:

  • A living wiki or a set of linked pages. One developer told Game Developer: "In my studio work, living docs and wikis are paramount." Another said: "I don't care if it's in google docs, notion, confluence, or a folder full of html files in dropbox" (Game Developer).
  • One-page designs. In a GDC 2010 talk, designer Stone Librande argued that "no one" reads long documentation and that "wikis often break the core relationships between elements". His answer: "annotated diagrams or other visuals that fit on one page that accurately and concisely illustrate a game's design" (Game Developer).
  • A short document frozen at production. One studio writes a GDD to bring the team up to speed, and "Once production has started, we no longer update the GDD, all new ideas go straight into the board" (Game Developer).
  • Slides, or no GDD at all. "Not every developer who commented has a use for GDDs," the 2023 guide reports; one designer says, "I prefer to use a slideshow as an outline" (Game Developer).

Whatever you choose, make it searchable, put a date and version on it, and give one person the job of keeping it current.

How do you write a game design document?

A practical order of work, whether you are a student, a solo developer or a lead designer:

  • Write the logline first: one sentence with the title, genre, platform, setting and what sets the game apart.
  • List three to five design pillars, the experiences every feature must support, and rank them so the team knows what to cut first.
  • Describe the core loop: what the player does every minute, every session and across the whole game.
  • Write each mechanic as an action with its input, limitation and outcome, and mark which ones are unproven.
  • Add the world, characters, story, interface and audio only to the depth the team needs right now.
  • Ask every discipline to comment. Ryan wrote that "Design documentation should be a team effort, because almost everyone on the team plays games and can make great contributions to the design" (Game Developer).
  • Playtest, then update the document the same week, with a new date and version number.

Game design document example: a one-page outline (illustrative)

Below is an illustrative GDD outline for a fictional small game, written for this page. You can use it as a game design doc template: keep the left column and replace the right.

SectionExample entry for "Lantern Keeper" (fictional)
LoglineLantern Keeper is a calm puzzle adventure for PC and consoles in which a lighthouse keeper relights a fogbound island, one lantern at a time.
Pillars, ranked1. Calm, never punishing. 2. Every puzzle uses light. 3. The island changes as you restore it. Pillar 3 is cut first if time runs short.
Player experience goalQuiet satisfaction, like finishing a hard crossword.
Core loopExplore a fogged area, find its lantern, solve the light puzzle, watch the fog lift and a new path open.
Action: carry lightInput: hold the interact button. Limitation: the lantern dims after 20 seconds away from a flame. Outcome: lights any wick in range. Importance: core verb.
Action: turn mirrorInput: rotate with the right stick. Limitation: only mirrors on rails turn. Outcome: redirects a beam. Importance: core verb, unproven, prototype first.
WorldFive areas around one lighthouse; a rough map and 12 reference images attached.
Interface and audioNo HUD except a lantern glow meter. Media list: 5 music tracks, 30 sound effects, no voice.
Out of scopeCombat, online play, a second island.

A real GDD would link each row to fuller pages, sketches and test builds, with the date and version at the top of the page.

Where can you see real game design document examples?

Most studio documents stay private, but some have been published. Game Developer points to the puzzle design document for LucasArts' Grim Fandango, which "walks through the entire game's flow, mapping out story, puzzles and solutions". It adds that "The original Deus Ex Design document is another treasure trove of 90s game design (and GDD) inspiration", and that "the developers of Monaco: What's Yours is Mine surfaced the original design doc on their Facebook page" (Game Developer).

Read them for structure and tone, not as a template. Each was written for one game, one team and one moment in that project.

Common mistakes in game design documents

Most failed GDDs are not badly written; they are unread or out of date.

  • Writing a long document nobody opens. Put the most important thing on the first page.
  • Letting it go stale. Cornell moved its gameplay specification out of the course wiki after finding "no one ever actually updated their wiki, even as their gameplay changed over the semester" (Cornell CIS 3152).
  • Undated versions. Librande's advice for printed designs is to "make sure to date them (so you actually know what the most up-to-date versions are)" (Game Developer).
  • Copying a famous template section by section, including parts your game does not need.
  • Describing mechanics as feelings ("combat feels punchy") instead of inputs, limits and outcomes.
  • No out-of-scope list, so features creep in one meeting at a time.
  • Decisions made in chat or meetings that never make it back into the document.

How should a studio keep its design documents?

Treat them as project records. Keep the full version history, not only the final page, and link each version to the build it described. Store concept art, prototypes and playtest notes next to the pages that refer to them. When a project ships or is cancelled, export the wiki or document folder with its history before the tool subscription ends; if it lives in Confluence, see exporting Jira and Confluence data.

Check who owns them. Under US copyright law, a work made for hire arises "(1) when the work is created by an employee as part of the employee's regular duties and (2) when a certain type of work is created as a result of an express written agreement", and then "the party that hired the individual is considered both the author and the copyright owner of the work" (U.S. Copyright Office, Circular 30). Design pages written by an outside contractor without a signed assignment may not belong to the studio, and a publishing agreement may give the publisher the design along with the game. This is general information, not legal advice.

Are a studio's design documents part of a data asset?

They are part of one. AI data buyers have asked Origin for game studio archives: gameplay recorded with the player's inputs and the engine state, 3D assets and scenes in source format, animation and motion capture, and source code with its full version history. Design documents are not on that list by themselves, but they explain the archive: what each level, system and asset was meant to do, and why it changed. A studio that kept them alongside its builds and repositories can describe its archive far more clearly.

What must come out first: anything a publisher owns, assets bought from stores whose licenses bar AI training, licensed music and middleware, performer captures without the performer's consent, and recordings of players. Licensing game studio data covers each of these checks, selling source code covers the code, and exporting records before closing covers a studio that is winding down.

Origin is an independent data partner. Your studio decides what is shared and signs any license itself, and a buyer may pay Origin when a deal closes.

Does your company hold records like these? See what your data is worth.

Common questions

In game development, what is a GDD?

A GDD, or game design document, is the shared plan for a game: the vision and logline, player experience goals, the world, the mechanics, characters and story, interface, audio and prototype plans. Designers write it so artists, engineers, audio, production and marketing build the same game. Most teams keep it as a living wiki or linked pages and update it after playtests.

What should a game design document include?

A game design document should include a vision statement and logline, player experience goals, the game world, the mechanics written as player actions, characters and story, the user interface and controls, audio needs and a prototype plan. Add technical notes and an out-of-scope list. Drop sections your game does not need, and link the sections so readers can follow a mechanic through the game.

How long should a game design document be?

As short as it can be while still answering the team's questions. A concept document is one to two pages. The full GDD grows with the project, but most teams now split it into linked pages so each reader finds one topic quickly. If a section is longer than anyone will read, replace it with a diagram, a table or a one-page design.

Who writes the game design document on a game team?

The lead designer usually owns and writes it, with input from art, engineering, audio, production and level design. The technical design document is separate and is usually written by the senior programmer or technical director. On a small indie team, whoever holds the vision writes the first draft and everyone else comments on it before production starts.

What is the difference between a game design document and a technical design document?

The game design document says what the game is and how it plays: mechanics, world, characters, interface and audio. The technical design document says how the team will build it: engine, architecture, systems, tools and data formats. Designers own the first; senior programmers or technical directors own the second. Each should link to the other.

Do game studios still use game design documents?

Many do, but rarely as one long file. Studios tend to keep living wikis or linked documents that change with playtesting, while some teams freeze a short GDD when production starts and track new ideas on a task board. A few skip the GDD and use slides and prototypes. Every team still needs a shared, current record of the design.

What is a one-page game design document?

A one-page design is an annotated diagram that explains one part of a game, such as a level, a system or the core loop, on a single sheet. Designer Stone Librande made the case for them in a 2010 GDC talk, arguing that people actually read them. Date every sheet so the team knows which version is current.

What is a good GDD template for a small indie game?

Start short: a logline, three to five ranked pillars, the core loop, a table of player actions with input, limitation and outcome, the world, the interface and controls, an audio media list, a prototype plan and an out-of-scope list. That fits on a few pages. Add story and character sections only if your game needs them, and update the template after each playtest.

Who owns a game design document written by a freelance designer?

Under US copyright law, work an employee creates as part of their regular duties belongs to the employer. A freelancer's work usually belongs to the freelancer unless a signed written agreement assigns it or, for certain types of work, makes it a work made for hire. Check the contract, and any publishing agreement, before relying on the document.

Sources and further reading

What is your company’s data worth?

AI companies pay $20K to $5M for company records. Six questions, no files.