# Level design document template

Five linked documents for one level, from its purpose to its last playtest: the flow and its beats, the layout and the measurements every room is built to, the encounters, and what the playtests changed. Download them as Markdown files: they open in any editor, show their diagram on GitHub and in Obsidian, and import into Nodary as a map.

Free, no account, no email. Use it, change it, share it.

[Download the template (.zip)](https://nodary.ai/downloads/level-design-document-template.zip)

## Read every page before you download

One copy per level. The overview fits on one screen and links to four parts, so the level designer, the artists and the testers each find their page. Italic lines say what to write; the examples come from Saltmarrow, the sample game this site uses everywhere.

- Level design document: One level on one screen: its purpose, the player’s goals, the numbers, and a link to every part.
- Flow and beats: The level as the player lives it: the beats in order, the pacing, and what each one teaches.
- Layout and metrics: The map, the spaces, the measurements every room is built to, and how the player finds the way.
- Gameplay and encounters: The mechanics the level uses, each encounter and challenge, the rewards, and the art and audio notes.
- Playtests and production: The questions each playtest answers, what it showed, the production checklist and what is still open.

### Level design document

_How to use this template: one copy per level. Italic lines are guidance: replace them with your own words, then delete them. Values in square brackets are yours to fill in. Keep this page to one screen._

#### At a glance

| Field | This level |
| --- | --- |
| Level | [Name] |
| Place in the game | [chapter, area, after which level] |
| Main goal | [...] |
| New in this level | [a mechanic, an enemy, a place] |
| Length | [minutes] |
| Difficulty | [1 to 5] |
| Status | [paper, blockout, art pass, final] |
| Owner | [name] |

#### Purpose

_Why this level exists: what the player learns, feels or unlocks here. A level that teaches nothing and changes nothing is a candidate for the cut list._

_Example (Saltmarrow, a sample game): The Archive Steps teaches the dive: the first time the player goes below the tide line, with the horn as their only clock._

[Your level’s purpose]

#### Player goals

- Main goal: [...]
- Optional goals: [...]
- Secrets: [...]

#### The rest of the level

_Each part is its own document. Link to it rather than copy from it, so every fact lives in one place._

- [Flow and beats](https://nodary.ai/templates/level-design-document#doc-flow): the beats in order, the pacing and the story moments
- [Layout and metrics](https://nodary.ai/templates/level-design-document#doc-layout): the map, the spaces, the player’s metrics and the landmarks
- [Gameplay and encounters](https://nodary.ai/templates/level-design-document#doc-encounters): mechanics, encounters, rewards, art and audio notes
- [Playtests and production](https://nodary.ai/templates/level-design-document#doc-testing): playtest questions and results, and the production checklist

_This template is free to use, change and share. It comes from_ [Nodary](https://nodary.ai)_, where these files import as a map of linked documents._

### Flow and beats

**Owner:** [name] · **Status:** draft · **Last reviewed:** [date]

#### Flow

_Replace these beats with the level’s own. If the team cannot draw the flow, the level is not settled yet._

```mermaid
flowchart LR
  n0["Arrival"]
  n1["Learn"]
  n2["Test"]
  n3["Twist"]
  n4["Climax"]
  n5["Exit"]
  n0 --> n1
  n1 --> n2
  n2 --> n3
  n3 --> n4
  n4 --> n5
```
_The level’s beats, about [n] minutes in all_

#### Beats

| Beat | What happens | What the player learns | Minutes | Intensity |
| --- | --- | --- | --- | --- |
| [Arrival] | [...] | [...] | [...] | [1 to 5] |
| [Learn] | [...] | [...] | [...] | [...] |
| [Test] | [...] | [...] | [...] | [...] |
| [Climax] | [...] | [...] | [...] | [...] |

#### Pacing

_Alternate tension and rest. After each peak, give the player a safe moment to breathe, look around and save._

#### Story moments

| Moment | What the player learns | How |
| --- | --- | --- |
| [...] | [...] | [a line of dialogue, an object, the place itself] |

Related: [Level design document](https://nodary.ai/templates/level-design-document#doc-overview) · [Layout and metrics](https://nodary.ai/templates/level-design-document#doc-layout) · [Gameplay and encounters](https://nodary.ai/templates/level-design-document#doc-encounters)

### Layout and metrics

**Owner:** [name] · **Status:** draft · **Last reviewed:** [date]

#### Map

_Draw the map before you describe it: a view from above with the critical path, the landmarks, the checkpoints and the secrets. In Nodary, draw it on a board in this document._

#### Spaces

| Space | Purpose | Size | Leads to |
| --- | --- | --- | --- |
| [...] | [...] | [...] | [...] |
| [...] | [...] | [...] | [...] |

#### Player metrics

_The numbers every room is built to. Agree on them with the programmers before the blockout, and keep them identical in every level._

| Metric | Value |
| --- | --- |
| Walk speed | [m/s] |
| Run speed | [m/s] |
| Jump height | [m] |
| Jump distance | [m] |
| Crouch height | [m] |
| Door width | [m] |
| Corridor width | [m] |

#### Landmarks and navigation

- Main landmark: [what, and from where it is visible]
- The way forward is shown by: [light, color, shape]
- Checkpoints: [where, and how far apart]

_Example (Saltmarrow, a sample game): The lighthouse can be seen from every part of the flats: walk toward it and you are walking home._

Related: [Flow and beats](https://nodary.ai/templates/level-design-document#doc-flow) · [Gameplay and encounters](https://nodary.ai/templates/level-design-document#doc-encounters)

### Gameplay and encounters

**Owner:** [name] · **Status:** draft · **Last reviewed:** [date]

#### Mechanics in this level

| Mechanic | New or known | Where it is taught | Where it is tested |
| --- | --- | --- | --- |
| [...] | [new] | [...] | [...] |
| [...] | [known] | [...] | [...] |

#### Encounters

| Encounter | Where | The challenge | Reward | Difficulty |
| --- | --- | --- | --- | --- |
| [...] | [...] | [...] | [...] | [1 to 5] |
| [...] | [...] | [...] | [...] | [...] |

_Example (Saltmarrow, a sample game): The flooded stair: the water rises one step every 30 seconds, and the player must choose between the crystal at the bottom and the safe exit at the top._

#### Rewards and secrets

| Reward | Where | How it is found |
| --- | --- | --- |
| [...] | [...] | [...] |

#### Art and audio notes

- Mood: [...]
- Art references: [...]
- Music and ambience: [...]
- Sounds that carry information: [...]

Related: [Flow and beats](https://nodary.ai/templates/level-design-document#doc-flow) · [Layout and metrics](https://nodary.ai/templates/level-design-document#doc-layout) · [Playtests and production](https://nodary.ai/templates/level-design-document#doc-testing)

### Playtests and production

**Owner:** [name] · **Status:** draft · **Last reviewed:** [date]

#### Playtest questions

_Write them before the playtest, and watch rather than explain: a player who needs your help has found a problem._

- Do players find the critical path without help?
- Where do they get lost, and for how long?
- Is [the new mechanic] understood before it is tested?
- [...]

#### Results

| Date | Players | What we saw | What we change |
| --- | --- | --- | --- |
| [date] | [number, profile] | [...] | [...] |

#### Production checklist

- [ ] Paper design reviewed
- [ ] Blockout playable from start to end
- [ ] Rooms checked against the player’s metrics
- [ ] Art pass
- [ ] Audio pass
- [ ] Performance budget met
- [ ] Bug pass

#### Open questions

- [ ] [Question], [who answers it], [by when]

Related: [Level design document](https://nodary.ai/templates/level-design-document#doc-overview) · [Gameplay and encounters](https://nodary.ai/templates/level-design-document#doc-encounters)

## How to use it

### Say why the level exists

Fill in the overview first: what the player learns, feels or unlocks here, and the one new thing the level brings. A level that teaches nothing and changes nothing is a candidate for the cut list.

### Agree on the metrics before the blockout

Write the player’s metrics with the programmers: walk speed, jump height, door width. Every room is built to them.

### Draw the map, then the beats

Sketch the layout from above with the critical path and the landmarks, then write the beats in the order the player meets them.

### Let the playtests decide

Write the questions before each playtest and the changes after it. The level that ships is the one the players played, not the one on paper.

## Import it into Nodary as a map

Nodary is an AI-native workspace where a team’s documents link instead of piling up. Import the .zip and the level arrives with its four parts filed under it and its links kept. Draw the layout on a board inside the document, with shapes, arrows, named frames and pictures, and present it frame by frame in a review. Give each level a status and a due date and see on the map what is late. AI agents connected over MCP read the level before they help write it.

1. Open a project’s map and choose Import.
2. Choose the Folder or ZIP tab, then Choose a ZIP.
3. Pick the downloaded file, check the tree, and import.

The Free plan holds ten documents per workspace, the project’s own page included: one level’s five documents leave room for four more. Paid plans have room for every level of your game. Nodary also has a one-page Level Design template built in.

## Writing a level design document the team can build from

A level design document fails when it describes a level nobody can measure, or a level the playtests have already changed. These habits prevent both.

### Paper before blockout

Settle the purpose, the beats and the map on paper. Moving a room on paper takes a minute; moving it in a blockout takes a day.

### Every beat teaches or tests

Each beat introduces something, tests something the player already knows, or gives them a rest. A beat that does none of these is padding.

### Agree on the metrics first

A corridor is only too narrow next to the player’s width. Write the metrics once and build every room to them.

### Guide the eye, not the hand

Show the way forward with light, color and landmarks rather than arrows and walls. Players who choose the right path feel clever.

### Plan the rest

After every peak of tension, give the player a safe moment to look around, read the space and save.

### Let the playtest decide

Write what you will watch for before each playtest and what changed after it. The notes are the level’s real history.

## Questions about level design documents

### What is a level design document?

A level design document, or LDD, describes one level of a game before and while it is built: its purpose, the player’s goals, the flow and beats, the layout and measurements, the encounters and rewards, and what playtests showed. Level designers write it; artists, programmers, writers and testers work from it.

### What should a level design document include?

The level’s purpose and goals, its place in the game, a flow of beats, a map with the critical path and landmarks, the player’s metrics, the mechanics introduced and tested, the encounters and rewards, art and audio notes, playtest questions and results, and a production checklist. This template has a document for each group.

### How is a level design document different from a game design document?

The game design document describes the whole game: its pillars, systems and world. A level design document zooms into one level and must respect what the GDD says. Link the two, so a change to a rule in the GDD reaches every level that depends on it.

### One document per level, or one for the whole game?

One per level, or per area in an open world. Each level has its own owner, its own status and its own playtests, and a short document per level is read; a long one for the whole game is not.

### When should I write it?

Before the blockout, at least the purpose, the beats and the map. The layout details, the encounters and the playtest results fill in as the level is built and tested.

### Can I use the template for a commercial game?

Yes. Use it, change it and share it for any game, commercial or not, with or without a Nodary account. A mention is welcome, never required.

The page: https://nodary.ai/templates/level-design-document