Level design is the part of game development that turns a set of mechanics into a place: the route a player runs, the jumps they make, the enemies they meet and the moment they spot the exit. A character that can jump is a feature. A level is what makes that jump interesting. This guide covers what the discipline actually involves, the principles that make levels feel good, a step-by-step process you can follow today, a playable code example, and the tools that speed up each stage.
What is level design?
A level is any play space the player moves through to complete an objective, whether the game calls it a stage, map, mission, zone or dungeon. Wikipedia describes level design as the discipline of making those locales, stages and missions, usually inside a level editor, which is software built for placing geometry, enemies, items and triggers.
In practice, level design sits between game design and art. The game designer decides that the player can double jump and wall slide. The level designer decides where those abilities matter, in what order the player learns them, and how hard each test is. The artist then makes the space look like a forest temple instead of grey boxes. On a small indie team, or when you are making a game solo, you do all three jobs, which is exactly why a clear process helps.
Good level design is often called invisible because players rarely notice it. They notice when they get lost, when a jump feels unfair or when a room drags on. When the level works, they simply feel smart and keep playing.
What a level designer actually decides
- Layout: the large shapes of the space, such as rooms, corridors, platforms, hills and tunnels.
- Ground rules: time limits, weather, day or night, starting resources and which abilities are available.
- Interactive parts: doors, keys, switches, moving platforms, teleporters and hidden passages.
- Placement: where the player starts, where enemies spawn, where coins, health and save points sit, and where the exit is.
- Pacing: how tension rises and falls between fights, puzzles and quiet moments.
The principles of good level design
Every genre has its own rules, but a handful of principles hold whether you are building a platformer, a shooter arena or a puzzle room.
Teach, test, twist
Introduce each mechanic in a safe spot, test it with real stakes, then twist it by combining it with something the player already knows. A small gap with a coin above it teaches jumping. A wider gap over spikes tests it. The same gap with a moving platform and an enemy twists it. Levels that skip the teaching step feel unfair, and levels that never twist feel repetitive.
Guide the player without signs
Players follow light, contrast, movement and pickups. A line of coins says “go this way.” A lit doorway in a dark room says “exit.” Use these cues on the critical path, the main route from start to finish, so players rarely need a text prompt.
Pace the intensity
Alternate tension and release. A hard combat room followed by a short quiet corridor with a health pickup feels deliberate. Five hard rooms in a row feel exhausting. Sketching a simple intensity graph, one bar per section, makes pacing problems obvious before you build anything.
Offer risk and reward
Optional paths should cost something and pay something. A secret ledge that requires a tricky jump should hold a collectible, a shortcut or a view worth seeing. That choice gives experienced players a reason to explore and lets beginners stay on the safe route.
Keep it readable
The player should be able to tell what is solid, what is dangerous and what is background at a glance. This is where the general principles of visual design apply directly: contrast and emphasis make hazards and goals stand out, pattern and rhythm teach through repetition, and unity makes the space feel like one coherent place.

The level design process, step by step
Studios differ, but most professional level design follows the same arc: concept sketches and documentation first, then layout and entity placement in an editor. Here is a version scaled for a solo developer or a game jam.
- Write the level’s goal in one sentence. “Teach the wall jump and end with a short chase.” If you cannot write the sentence, the level has no purpose yet.
- Sketch on paper. Graph paper works well, with one square per tile. Mark the start, the goal, the critical path, each new idea and one or two optional areas. Keep it rough.
- Block it out. A blockout, also called a grey box, is a playable version built from plain shapes with no final art. It answers the only question that matters early: is this fun to move through?
- Playtest. Watch someone else play without helping. Note where they hesitate, die, get lost or get bored. Your own playthroughs lie to you because you already know the route.
- Iterate. Move platforms, cut rooms, add a coin trail. Repeat steps 4 and 5 until new testers stop hitting the same problems.
- Art pass. Only now replace the grey boxes with tiles, props, lighting and sound. Check that the new art has not hurt readability.
The most common beginner error is jumping straight to step 6. Art takes hours, and nobody wants to delete a beautiful room that plays badly. Grey boxes are cheap to throw away, so you throw them away more often, and the level gets better.
A worked example: blocking out a platformer level in code
You do not need a dedicated editor to start. One of the fastest ways to block out a 2D level is to describe it as text, where each character is a tile. The example below uses the open-source Phaser 3 framework. Paste it into an HTML page that loads Phaser and you get a playable grey box: arrow keys to move and jump, red blocks reset the level, the green block is the goal.
const LEVEL = [
"....................",
"....................",
"..........C.........",
".........###........",
"....C...............",
"...###.......C......",
"............###.....",
"P.......E..........G",
"####################"
];
const TILE = 32;
class Blockout extends Phaser.Scene {
create() {
const solids = this.physics.add.staticGroup();
const hazards = this.physics.add.staticGroup();
let goal;
LEVEL.forEach((row, y) => {
[...row].forEach((ch, x) => {
const px = x * TILE + TILE / 2;
const py = y * TILE + TILE / 2;
if (ch === "#") solids.add(this.add.rectangle(px, py, TILE, TILE, 0x555555));
if (ch === "C") this.add.circle(px, py, 8, 0xffd400);
if (ch === "E") hazards.add(this.add.rectangle(px, py, TILE, TILE, 0xd03030));
if (ch === "G") goal = this.add.rectangle(px, py, TILE, TILE, 0x30d060);
if (ch === "P") this.player = this.add.rectangle(px, py, 24, 30, 0x3080ff);
});
});
this.physics.add.existing(this.player);
this.physics.add.existing(goal, true);
this.physics.add.collider(this.player, solids);
this.physics.add.overlap(this.player, hazards, () => this.scene.restart());
this.physics.add.overlap(this.player, goal, () => {
this.add.text(260, 120, "Clear!", { fontSize: "32px", color: "#ffffff" });
this.physics.pause();
});
this.cursors = this.input.keyboard.createCursorKeys();
}
update() {
const body = this.player.body;
body.setVelocityX(0);
if (this.cursors.left.isDown) body.setVelocityX(-160);
if (this.cursors.right.isDown) body.setVelocityX(160);
if (this.cursors.up.isDown && body.blocked.down) body.setVelocityY(-420);
}
}
new Phaser.Game({
type: Phaser.AUTO,
width: 640,
height: 288,
physics: { default: "arcade", arcade: { gravity: { y: 900 } } },
scene: Blockout
});
Why this format is useful for level design work: changing the layout is just editing characters in an array. Move a # two columns to the right, reload, and feel the difference in the jump. That loop of edit, play, adjust is the whole craft at small scale.
Reading the example as a designer
- The coins (
C) sit above the platforms, so they double as a breadcrumb trail that suggests where to jump. - The single hazard (
E) is on flat ground near the start, a safe place to learn that red means danger before any jump depends on it. - The upper platforms are optional. A real version would put a reward up there to justify the climb.
Try one change: add a second hazard right before the goal. Does the ending feel tense or cheap? That judgement, made over and over, is what you are training.





