Blockout Level Design: Why It’s the Most Critical Step in Building Gameplay Spaces

A blockout is the first playable version of a level, built using simple geometry like cubes, planes, and basic shapes. It is the single most important step in the blockout level design pipeline, and the one that separates designers who understand gameplay from those who are decorating spaces. No detailed props. No materials. No polished lighting. Just the raw spatial framework that lets you answer the questions that actually matter early in development: Does the layout create interesting decisions? Does the level flow naturally from one objective to the next? Are combat encounters engaging? Can players understand where to go without becoming frustrated?

If you are a level designer, an indie developer, a game design student, or anyone building gameplay spaces, this guide is for you. Whether you work in Unreal Engine, Unity, Godot, or any other engine, the principles are the same: build the gameplay first, let the visuals support it, and iterate before art production locks you into decisions that are expensive to reverse.

Throughout this article, we will break down what a blockout is (and what it is not), walk through the complete process from pre-production to playtesting, examine common mistakes that derail level design work, and explain how a strong blockout can be the difference between a portfolio that gets you hired and one that gets ignored.

What Is a Blockout in Level Design?

A blockout is the first playable version of a level, constructed entirely from simple geometry: cubes, planes, cylinders, and basic placeholder shapes. There are no detailed props, no materials, no lighting design, and no polished art. The environment consists of untextured primitives rendered in uniform neutral tones, usually gray, which is why the process is also called greyboxing. The focus is entirely on the level’s foundation: its layout, scale, flow, pacing, and the gameplay decisions it creates for the player.

As Epic Games explains in their official Unreal Engine blockout documentation, this design phase involves “building the rough spaces in your level with simple shapes that represent walls, pathways, and functional obstacles.” The purpose is not to make the level look finished. The purpose is to make it playable, testable, and iterable before a single final art asset enters production.

A blockout exists to answer design questions cheaply. Can the player reach the objective without confusion? Does jump distance feel fair? Are combat arenas the right size for the enemy count and cover options? Does the camera see critical ledges and threats? These are spatial questions that no design document can fully answer. They require a body in the space, a player character moving through the geometry, making decisions, failing, and trying again.

Blockout vs. Greybox vs. Whitebox: Understanding the Terminology

The terms blockout, greybox, and whitebox are used largely interchangeably across the game development industry. Different studios and communities adopt different labels, but the core practice remains the same: build a playable level from primitive shapes before committing to final art.

The terminology has subtle distinctions in some contexts. Greyboxing specifically emphasizes the uniform neutral palette, flat gray materials applied to all geometry to eliminate visual distractions during testing. This approach helps designers focus on spatial relationships, flow, and pacing without being influenced by color, texture, or material variation. As one studio’s explanation of whitebox describes it, houses, walls, and trees are all placed with “primitive proxy models to build up the space” so the team can test the location in-engine before art time goes into dressing it with final assets.

Whiteboxing sometimes refers to a slightly more refined iteration, where placeholder props have basic color coding to distinguish gameplay elements (enemies, cover, objectives) from background geometry. Some developers trace the term back to Naughty Dog’s Uncharted GDC presentations, where it described the very first blockout stage with no detailed assets. The iteration with at least somewhat detailed props and color was then labeled whitebox.

None of these distinctions change the fundamental principle. Whatever you call it, the goal is the same: test gameplay before art. If the level does not play well as a blockout, adding art will not fix it, it will only make an unfun level look expensive.

What a Blockout Is Not

A blockout is not about visual fidelity. It is not about technical polish. It is not about impressing anyone with how your level looks. These points are worth stating explicitly because they are the most common source of confusion among designers entering the field.

A blockout is not a design document. You cannot playtest a document. You cannot feel pacing in a spreadsheet. You cannot evaluate whether a jump is fair by reading about it. The blockout is the first point in the pipeline where you can truly play your level, and playing reveals things that planning never will.

A blockout is also not a final layout. It is a hypothesis. Every room, every corridor, every combat space is a proposed solution to a design problem, and playtesting will tell you whether that solution works. Some will. Many will not. That is the process.

Why Blockouts Matter: The Core Benefits

The value of a blockout comes down to timing. It is the cheapest point in the development pipeline to discover that your level does not work, and the last point where fixing it costs almost nothing.

Testing Gameplay Before Art Production

When you build a blockout, you are testing the things that determine whether your level is fun: navigation, pacing, combat flow, sightlines, scale, and player guidance. None of these require final art. A corridor that is too narrow is too narrow whether its walls are gray boxes or detailed brick textures. A combat arena that is too large for its enemy count is too large regardless of how many props dress the space. A jump that is impossible is impossible whether the ledge is a placeholder cube or a sculpted stone platform.

Professional pipelines start with greybox levels precisely because they answer spatial questions cheaply. As one comprehensive guide to level design puts it, “When blockout is fun, art amplifies it. When blockout is confusing, art only hides the problem briefly.” Art can enhance a level, but it cannot fix poor gameplay. That distinction is the entire reason blockouts exist.

The blockout stage validates three critical dimensions before any hero asset enters production: spatial proportion (does the space feel right at player scale?), level design logic (does the layout support the intended gameplay flow?), and visual composition (do sightlines, focal points, and camera angles work?). If any of these fail, the fix is a drag-and-drop operation. After art production ramps up, the same fix can mean rebuilding modular pieces, reworking lighting, and re-dressing entire sections.

Answering Design Questions Early

A blockout allows designers to answer the questions that actually matter early in development. These include:

• Does the layout create interesting decisions for the player?
• Does the level flow naturally from one objective to the next?
• Are combat encounters engaging and fair?
• Do players understand where to go without becoming frustrated?
• Are the spaces scaled correctly for movement, traversal, and gameplay?

Each of these is a question about player experience. You cannot answer them by looking at a top-down map. You cannot answer them by reading a design document. You answer them by putting a player character in the space, running through it, and watching what happens. The blockout is the first point in the pipeline where that is possible.

Every playtest reveals something new. Players take routes you did not anticipate. They miss objectives you thought were obvious. They find shortcuts you never intended. They struggle with jumps you thought were trivial. That information is the raw material of iteration, and it is only available once the level is playable.

The Economics of Early Iteration

The beauty of a blockout is that it is inexpensive to change. If a room does not work, delete it. If a hallway feels too narrow, widen it. If an encounter is not fun, redesign the space around it. Those changes might take minutes during the blockout stage. Once the environment has been fully modeled, dressed, lit, and polished, the same changes can take days or even weeks.

This is why experienced teams spend so much time iterating before art production ramps up. The goal is not to make the level look finished. It is to make sure the gameplay feels great and to confirm the team’s ideas before committing production resources that are difficult and expensive to reverse.

Consider what happens when you skip the blockout. You spend weeks modeling detailed geometry, placing props, texturing surfaces, and lighting the environment. Then you playtest it for the first time. Players get lost in the first room. The combat arena is too cramped. The critical path is unclear. Now you have to change the layout, but the layout is buried under finished art. Every wall you move means reworking modular pieces. Every corridor you widen means rebuilding collision. Every encounter you redesign means re-placing every prop in the affected area. You are paying art-level costs for design-level decisions.

The blockout exists to prevent exactly this scenario. It front-loads the cheapest, fastest, most informative iteration in the entire pipeline.

The Blockout Process: How to Build One

Building a blockout is not a single action. It is a sequence of decisions that begins long before you open your engine and continues through multiple playtest-and-revise cycles. The process below covers the full progression from concept to validated layout.

Pre-Production: Planning Before You Build

Before you place a single cube, you need to know what you are building and why. This starts with a one-sentence level goal: what the player must accomplish and what they should feel doing it. That sentence becomes the filter for every decision that follows. If a room, encounter, or route does not serve the goal, it gets cut.

From the goal, map the critical path: the minimum sequence of spaces and objectives the player must pass through to finish the level. Everything in the level is either on the critical path, an optional reward for exploration, or a detour. Detours that do not serve the goal or the intended emotion dilute the level and cost time you do not have.

Next, sketch a rough 2D plan. Use paper, a whiteboard, a diagram tool, or a top-down layout. Mark entrances, exits, major encounters, checkpoints, landmarks, locked doors, shortcuts, and important sightlines. The output of this stage is not art. It is intent.

A level design document (LDD) can formalize this planning. An LDD defines a level’s goal, intent, routes, mechanics, pacing, difficulty, rewards, and design risks. It serves as the single source of truth for everyone working on that level, and it gives the blockout phase a clear set of requirements to validate.

Establishing Player Metrics First

This is the step that separates designers who have worked in production from those who have not. Before building any geometry, you need to know your player metrics.

Player metrics are the numerical values that define how a player interacts with the game: movement speed, jump height, jump distance, crouch height, sprint speed, combat engagement range, enemy aggro radius, and interaction distance. These numbers dictate everything about how your levels play. A 60-meter hallway at 6 meters per second takes 10 seconds to traverse, is that intentional flow or accidental boredom? A jump gap set wider than the player’s maximum jump distance is unplayable. A combat arena sized for ranged weapons becomes chaotic when enemies close to melee range.

As level design educator Nathan Kellman explains, drawing on his experience reviewing over 1,500 level design portfolios: “Player movement speed. Jump height. Combat engagement range. Enemy aggro radius. These numbers dictate everything about how your levels play.” He describes the consequence of skipping this step: “Jumps I thought were challenging became impossible. Hallways I thought felt spacious became cramped. Combat arenas I thought were tactical became chaotic. I wasn’t designing for reality. I was guessing.”

The Valve Developer Community maintains a detailed reference of player dimensions for Half-Life 2 and Counter-Strike: Source that illustrates how granular these values get: door width (48 units), player collision height standing (62 units), crouch height (36 units), running speed (190 units per second), sprinting speed (320 units per second), and maximum jump height (56 units with a jump-crouch). Every spatial decision in the level is built on top of these numbers.

Establish your metrics before you build. Write them in your LDD. Every door width, corridor width, step height, jump distance, and cover piece dimension should be derived from them.

The Roughout: Your First Spatial Hypothesis

The roughout is the first pass of level construction using basic shapes. No detail. No metrics-accurate geometry. Just layout and flow testing. This is where you figure out if the bones of your level actually work.

In the roughout, you are answering fundamental questions: Can players navigate the space? Is the pacing readable? Do combat areas have the right flow? Are sightlines pointing where they should? The roughout is deliberately rough, fast to build, fast to test, and fast to throw away if the concept does not hold up.

One common practice is to start big and go small. Place large chunks of simple geometry first to define the overall shape of the level, then zoom in and refine specific areas. The roughout should be easy to change and should not hurt to scrap sections here and there. If a whole area does not work, delete it and try a different approach. The cost is minutes, not days.

Refining Into a Metrics-Accurate Blockout

Once the roughout proves that the layout works, the next step is refining it into a metrics-accurate blockout. This means replacing loose shapes with geometry that respects your established player metrics: doorways at the correct width, corridors wide enough for two characters plus a camera, platforms at reachable jump heights, and cover pieces sized for the intended combat style.

At this stage, you introduce elevation changes, define spaces more clearly, and add placeholder gameplay elements: enemy spawn points, item locations, interaction triggers, and objective markers. You also begin thinking about verticality. As legendary designer John Romero once advised, “Always change floor height when changing floor textures.” Even in a blockout, subtle changes in elevation add depth and rhythm to a space, making combat more interesting and helping players reorient themselves.

The blockout should already be understandable without final assets. If players cannot navigate the graybox, decoration will not solve the problem. A well-tested blockout can feel immersive even without art and can guide players without UI.

Working With Modular Kits and Grid Snapping

Modular kits are sets of reusable, grid-aligned geometry pieces: walls, floors, corners, doorways, stairs—that snap together cleanly. They are the backbone of efficient blockout work, enabling rapid iteration and ensuring that spaces remain consistent in scale and proportion.

The key to modular kits is grid discipline. Every piece’s dimensions should be multiples of a base unit: commonly 100 units (1 meter in Unreal Engine), though smaller kits may use 50 or 25 units. This power-of-two convention makes subdivision easy and ensures that walls, floors, and corners fit together without gaps, overlaps, or manual nudging.

Pivots matter as much as dimensions. Place pivots at a consistent corner or edge of each piece’s bounding box, typically the bottom-front-left corner for architectural pieces. This convention ensures that snapping one piece against another aligns both position and orientation automatically. Floor pieces need their pivot at the same height reference as wall base pieces, or floor-to-wall connections develop visible gaps that are tedious to catch in isolation and obvious the moment the kit is assembled at scale.

Grid snapping in the engine enforces this discipline. Unreal Engine’s editor toolbar provides Grid Snap (positional, default 10 units), Rotation Snap (default 10 degrees), and Scale Snap. Unity offers similar Snap Settings. When enabled, dragged pieces jump to the grid, preventing the misalignments that accumulate over a long blockout session.

Playtesting Your Blockout

Playtesting is where level design becomes real. Your first layout will almost never be correct. Players will get lost, ignore the route you expected, exploit unintended shortcuts, misread jumps, avoid combat spaces, or fail to notice clues. That feedback is not failure. It is the process.

When to Start Playtesting

The answer is simple: as soon as the blockout is playable. Not after the art pass. Not after the lighting is done. Not after you have polished the geometry. As soon as a player character can move through the space and interact with the core mechanics, you should be playtesting.

Usability research from the Nielsen Norman Group found that testing with about five users uncovers most of the obvious problems in an interface. The same logic applies to level design. You do not need a hundred playtesters to find the major issues. A handful of fresh players will reveal the majority of navigation problems, pacing issues, and confusion points.

Playtest greyboxes with placeholder audio and final input bindings. Do not wait for animation polish. The goal is to find out whether the space works, not whether it looks good. A blockout that plays well with gray boxes and placeholder sounds will play well with final art. A blockout that confuses players will still confuse them after art, just more expensively.

How to Run an Effective Playtest

The most important rule of playtesting: sit down, stay quiet, and watch. Do not explain the goal. Do not point the right way. Do not defend your choices. Note every hesitation, every backtrack, every moment a player tries something you did not expect. Those moments are the design flaws speaking.

During the playtest, observe specific behaviors:

• Where do players stop moving?
• Where do they look confused?
• Which routes do they choose?
• Which spaces do they ignore?
• Do they understand the objective?
• Does difficulty rise too quickly?
• Do they run out of resources?
• Does a puzzle have unintended solutions?
• Is the level too long or too short?

These observations are more valuable than any opinion the player offers afterward. A player saying “I liked it” tells you almost nothing. A player who spent forty seconds walking in circles in your second room tells you everything.

Questions That Reveal Design Problems

After the playtest, ask questions that surface the player’s reasoning rather than their preferences:

• What did you think the goal was?
• Where did you expect to go next?
• What made you choose that route?
• Which part felt easiest?
• Which part felt unfair?
• What did you notice first in this room?

These questions produce actionable revision notes. “The player did not understand the objective” is a design problem with a clear fix. “The player thought the game was okay” is not.

Then revise one problem at a time. Change the layout, adjust a sightline, move an objective, or add a visual cue. Test again. Good level design is iterative, the first blockout is a hypothesis, and playtesting reveals whether that hypothesis works.

Regression Testing After Art

One of the most overlooked aspects of playtesting happens after the art pass. Final meshes change collision, lighting affects visibility, and sightlines shift when detailed geometry replaces placeholder cubes. A ledge that was obvious in the blockout may disappear behind a prop. A corridor that felt spacious may become cramped with dressed walls. A combat encounter that was balanced in graybox may break when cover pieces change shape.

Re-test critical paths after art, lighting, and audio land. The blockout validated the layout. The art pass can invalidate it if you are not paying attention.

Iteration: The Heart of Blockout Development

Iteration is not a phase. It is the entire point of building a blockout. The blockout exists so you can change things cheaply, test the result, and change them again. Every iteration cycle: build, playtest, revise, re-test, moves the level closer to something that feels right.

The Three-Phase Progression: Roughout, Blockout, Polish

Nathan Kellman, drawing on his production experience, describes a three-phase progression that every level goes through. He has seen designers fail not because they lack skill, but because they skip the roughout phase and jump straight to detailed blockout.

Phase 1: Roughout. Basic shapes. No detail. Just layout and flow testing. This is where you figure out if the bones of the level work. Can players navigate it? Is the pacing readable? Do combat spaces have the right flow? At Lost Boys Interactive, entire levels were built in roughout using nothing but boxes and cylinders. Fast to build, fast to test, fast to throw away if needed.

Phase 2: Blockout. Add metrics-accurate geometry. Introduce elevation changes. Define spaces more clearly. Now you are refining what the roughout proved works. You are not guessing anymore. You are building on tested foundations.

Phase 3: Final/Polish. Lighting, visual scripting, detailed geometry, enemy placement. This is where most juniors start. It should be where you finish. By this point, you have already playtested the layout multiple times. You know it works. Now you are making it look and feel professional.

The critical insight is that each phase builds on the validated output of the previous one. Skipping the roughout means building detailed geometry on an untested foundation. If the foundation is wrong, every hour of detailed work is at risk of being thrown away.

When to Iterate vs. When to Start Over

Knowing when to keep iterating on a specific section and when to scrap it entirely is one of the hardest judgment calls in level design. The general principle: if playtesters consistently fail at the same problem after three or four iterations targeting that specific issue, the problem is probably structural, not surface-level.

A structural problem means the layout itself is wrong, not the details, but the fundamental arrangement of space. No amount of nudging walls, adjusting sightlines, or moving cover will fix it. The solution is to delete the problem area and rebuild it from a roughout. That feels painful in the moment, especially after investing hours into a blockout. But starting fresh with a new hypothesis is almost always faster than dragging a flawed concept across ten more iterations.

Small deltas beat full rewrites. Move one landmark, widen one choke, add one light, then re-test. One change at a time lets you isolate what works. Changing five things at once means you cannot tell which fix actually helped.

Documenting Your Iteration Process

Documenting your iterations is not optional for professional-level work. It is the evidence that your level design process is deliberate, data-driven, and repeatable. Keep an iteration log that records:

• What version you tested (with dates in the level name, e.g., Forest_2026-08-22)
• What playtest findings emerged
• What you changed and why
• Before-and-after screenshots

This log serves two purposes. During development, it helps you track what works and revert when a change breaks flow. When you present your work, in a portfolio, in a job interview, or to a team, it demonstrates that you can think systematically, iterate based on feedback, and defend your decisions with evidence rather than instinct.

Version your blockouts with dates. When a change breaks flow, you can revert to a known-good state. Small, documented iterations are how professional level designers work. Blind iteration, changing things without recording what changed or why, produces levels that feel polished but cannot be explained or reproduced.

Common Blockout Mistakes to Avoid

The mistakes that derail blockouts are remarkably consistent across designers, studios, and experience levels. They all stem from the same root cause: treating the blockout as a visual exercise rather than a design exercise.

Rushing to Art Too Early

This is the most expensive mistake in level design. It is also the most common.

Beginners rush the art pass because decorated space feels like progress. It is the opposite. Polishing visuals on a layout players abandon after two minutes is the most expensive way to find out your layout is wrong. Every hour spent on art before the gameplay is proven may be thrown away when playtesting reveals fundamental problems.

The principle is simple: prove the layout first, decorate it second. Once a level is covered in final art, early design mistakes get locked in, because changing the layout means throwing away finished work.

A blockout that is not fun will not become fun when you add textures. It will only become a beautiful level that is not fun. Build the gameplay first. Let the visuals support it, not carry it.

Ignoring Player Metrics

Designing spaces based on feel rather than numbers is a mistake that catches almost every designer early in their career. You build a hallway that feels spacious in the editor, then the engineer implements real movement values and suddenly it is cramped. You design a jump that looks challenging, then discover the player’s jump arc cannot clear it.

Metrics constrain design in productive ways. They tell you how wide a corridor needs to be for two characters plus a camera. They tell you how far apart platforms can be before a jump becomes impossible. They tell you how large a combat arena needs to be for the engagement range of your weapons. Without these numbers, you are designing for a theoretical player who does not exist.

Over-Detailing in the Roughout Phase

The roughout exists to test ideas quickly. When you spend hours adding detailed geometry, lighting, and props before validating the core layout, you create a sunk-cost problem. The more time you invest in a roughout, the harder it becomes to scrap it when it does not work.

Keep the roughout rough. Use boxes and cylinders. Do not add materials beyond flat gray. Do not place detailed props. If the roughout does not work with simple shapes, adding detail will not save it. If it does work, you can always add detail later, on a foundation you have already proven.

Not Playtesting Enough

Designers are the worst judges of their own difficulty and flow. You have played your level dozens of times. You know where every enemy is, where every objective sits, which path is fastest, and which jumps are tricky. Your players do not.

Not playtesting enough means shipping a level that makes sense only to the person who built it. The symptoms are predictable: players get lost, miss objectives, take unintended routes, or quit in frustration. These are not player failures. They are design failures that playtesting would have caught.

Playtest early, playtest often, and watch in silence. The level tells you what is wrong through the behavior of the people playing it, you just have to be in the room to see it.

Blockouts and Portfolio Strategy

A blockout is not just a development tool. It is also the strongest portfolio piece a level designer can present. Understanding what hiring managers actually look for changes how you build, document, and present your work.

What Hiring Managers Actually Look For

Studios do not need to see complete games. They want proof that you understand level design fundamentals and can think clearly about player experience. They are looking for design thinking, iteration, problem-solving, and an understanding of the player experience, not visual polish.

As Nathan Kellman notes, reflecting on his experience reviewing over 1,500 level design portfolios: “Most candidates sending these portfolios are talented. They’re trying. They just haven’t been shown how to think through levels like a designer, so they fall back on aesthetics and hope it’s enough.”

The portfolios that stand out demonstrate an understanding of spatial design, player psychology, and iteration. They show the “why” behind every spatial decision. Why does that corner exist? Why does the path narrow here? Why does this space create pressure and that one gives relief?

A portfolio full of beautiful environments with weak layouts tells a very different story than a portfolio with thoughtful, well-tested levels. Art can enhance a level, but it cannot fix poor gameplay. A strong blockout demonstrates the skills studios actually hire for.

Showing Process Over Product

The single most effective portfolio strategy for level designers is showing process, not just final output. This means documenting your work at every stage and presenting it as evidence of how you think.

Include the following in your portfolio case studies:

• A top-down layout map with annotations showing flow, encounters, and sightlines
• Before-and-after screenshots from playtest iterations
• A design intent statement explaining the level’s goal and emotional target
• A pacing plan or beat sheet showing how tension rises and falls
• Playtest findings and the specific changes you made in response
• A brief explanation of why you made each major spatial decision

Your documentation does not need to be a lengthy essay. A few screenshots, a top-down layout, and five to eight bullet points explaining what changed and why will often outperform a one-hour playthrough video.

As one guide to level design recommends, show your thinking process. A simple graybox with clear documentation can be more valuable than a beautiful but unplayable environment. When a hiring manager asks, “Why did you do this?” you should be able to walk them through your reasoning like a professional, not freeze, or say “it seemed cool.”

One Deep Project Beats Ten Shallow Ones

Nathan Kellman’s breakdown of the portfolio project that got him hired illustrates this principle. He was applying to AAA studios with a portfolio full of half-finished projects, lots of ideas, zero depth. Then he built one project differently, and everything changed.

The project was a single 12-minute action-adventure level built in Unreal Engine 4. Not a full game. Just one focused level. But he built it like a professional:

• Complete documentation including a design intent document, beat sheet with time-stamped pacing, and iteration log showing what changed after each playtest
• Visible iteration process with eight or more versions, each including before-and-after comparisons, identified problems, and implemented solutions
• Professional presentation including a video walkthrough with commentary, before-and-after visuals, LDD documentation, and playtest feedback
• Design thinking made visible, every major decision had an explanation tied to pacing data or playtest findings

The result: three interview callbacks in two weeks. One deep, well-documented project outperformed ten shallow ones because it proved he could think systematically, iterate based on data, and show his process. Studios hire designers who can defend their decisions with evidence.

Tools and Techniques for Blockouts

Blockouts work in any engine. The principles, simple geometry, metrics-driven layout, early playtesting, iterative refinement, transfer regardless of your toolchain. What changes is the specific workflow, toolset, and speed of iteration each engine offers.

Unreal Engine

Unreal Engine is widely used for 3D level design because its editor supports blockouts, terrain, lighting, Blueprints, modular environments, and large-world workflows. Epic Games’ official documentation walks through the complete process of project setup and level blockout, including the use of Blocking Volumes, invisible walls that close off unwanted areas and keep the player in the level.

Unreal’s modeling tools in UE5.6 and later include brush modeling modes that allow direct geometric editing within the viewport, making blockout iteration fast and intuitive. The engine’s Grid Snap system enforces modular alignment, and its Blueprint system allows designers to prototype interactive elements: doors, elevators, triggers without leaving the editor.

Unity

Unity is a flexible engine for both 2D and 3D projects. Its scene editor, prefab workflow, tilemaps, and plugin ecosystem make it suitable for prototypes, stylized games, mobile projects, and small-team production. Unity’s blockout workflow follows the same progression: simple shapes first, gameplay testing, then art replacement.

The Unity Asset Store offers dedicated blockout tools, including modular blockout kits and grid-snapping utilities that streamline the placement of placeholder geometry. Unity’s prefab system makes it easy to swap placeholder meshes for final art assets once the layout is validated.

Godot and Other Engines

Godot is a free, open-source engine with approachable 2D and 3D workflows. It is especially useful for smaller projects, rapid prototypes, tile-based games, and developers who prefer a lightweight editor. Godot’s tilemap system supports 2D level blockouts with physics layers, collision masks, and navigation regions.

For 2D level design specifically, dedicated tools like Tiled and LDtk provide standalone editors for tilemaps, object layers, collision shapes, and gameplay markers. These tools work well for platformers, top-down RPGs, and retro-style projects, and can export level data to any engine.

Planning Tools Before the Engine

Not every level begins inside an engine. Early planning often happens in lightweight tools that make it easy to sketch routes, encounters, pacing, and objectives before building a playable blockout:

• Paper sketches and whiteboards for quick layout ideas
• Diagram tools for routes, branching paths, and quest flow
• Spreadsheets for encounter pacing, asset lists, and difficulty planning
• Image editors for top-down maps and annotated screenshots

The most effective level design tool is the one that lets you test an idea quickly. A rough map made in a diagram tool is more useful than a polished environment plan that has never been played.

Documented Practitioner Perspectives

The principles in this article are not theoretical. They come from practitioners who have shipped games, reviewed thousands of portfolios, and presented their processes at industry conferences. Below are perspectives from three designers whose public work directly informs blockout practice.

Nathan Kellman on Metrics and Portfolio Depth

Nathan Kellman is a level design educator who has reviewed over 1,500 level design portfolios since 2020. His public LinkedIn posts provide some of the most specific, data-backed guidance available on what separates hireable portfolios from ignored ones.

On metrics: Kellman emphasizes that gameplay metrics are not an afterthought, they are the foundation of every spatial decision. “Player movement speed. Jump height. Combat engagement range. Enemy aggro radius. These numbers dictate everything about how your levels play.” He describes the common failure pattern: “I designed spaces based on feel. Then engineers implemented real movement and suddenly jumps were impossible, hallways felt cramped, and combat arenas collapsed into chaos. I wasn’t designing for reality. I was guessing.”

On portfolios: “Your real job isn’t just making spaces. It’s guiding gameplay through those spaces and shaping a moment-to-moment experience that feels good to play. That’s what studios are actually looking for.” His portfolio advice is direct: one deep, well-documented project outperforms ten shallow ones. Show your process. Show your iterations. Show why.

Marcelo Vianna on Blockout Pipeline

Marcelo Vianna, a level designer who shares blockout resources during the annual Blocktober community event, outlines a practical pipeline that many working designers follow:

• Start with sketching points of interest, then a bubble diagram, then a map layout, before opening the engine
• In engine, start big and go small: large chunks of simple shapes first, then zoom in and polish
• The blockout should be easy to change and should not hurt to scrap sections
• Focus on composition, not detail: check cinematic flow, wow moments, and whether players look where you want them to, when you want them to
• “Show the door before the key”, let the player encounter a locked path before giving them the tool to open it
• Build the skateboard first: rough out the full level from start to finish early, then scale one step at a time

His guidance on verticality is particularly relevant to blockout work: “Make subdivisions using small changes in height. Verticality adds depth and rhythm to your level. It can make combat more interesting, help players reorient, or simply create better visual compositions.”

Dan Taylor’s Ten Principles for Good Level Design

Dan Taylor’s GDC talk, “Ten Principles for Good Level Design,” remains one of the most cited framework references in the level design community. His principles, inspired by Dieter Rams’ design philosophy, directly inform how blockouts should be evaluated:

• Good level design is fun to navigate, the player should always know where to go
• Good level design does not rely on words, it communicates through space
• Good level design tells the player what to do, not how to do it
• Good level design constantly teaches the player something new
• Good level design is surprising, it subverts expectations
• Good level design empowers the player
• Good level design offers easy, medium, and hard paths
• Good level design is efficient, it works within constraints
• Good level design creates emotion through spatial design
• Good level design is driven by mechanics, everything serves gameplay

These principles provide a checklist for evaluating your blockout. Does your layout create interesting navigation? Does it communicate without text? Does it teach mechanics through space? Does it offer multiple paths of varying difficulty? If the answer to any of these is no, the blockout is where you fix it: cheaply, quickly, and before art production makes the fix expensive.

Steve Lee, whose GDC talk on holistic level design in Dishonored 2 is another widely referenced resource, also produced a video on common problems in level layouts and blockouts. His work emphasizes intentionality in spatial design, every element should serve a purpose, and every sightline should be deliberate.

Article Key Takeaways

• A blockout is the first playable version of a level, built from simple geometry, its purpose is to test gameplay, layout, scale, and flow before art production begins.
• Changes during the blockout stage take minutes; the same changes after art production can take days or weeks. Front-load your iteration where it is cheapest.
• Player metrics (movement speed, jump height, combat range) must be established before building:these numbers dictate every spatial decision in the level.
• Playtest early with fresh players, stay silent, and watch where they hesitate. About five testers will reveal most navigation and flow problems.
• A strong blockout demonstrates design thinking, iteration, and problem-solving:the skills studios hire level designers for. Build the gameplay first; let the visuals support it, not carry it.

Conclusion

A blockout is where design thinking becomes visible. It is the first point in the pipeline where you can play your level, the cheapest point to change it, and the strongest evidence you can present that you understand how gameplay spaces work. Every hour spent iterating on a blockout saves days of rework after art production locks in decisions that are expensive to reverse.

The principles are consistent across engines, genres, and team sizes. Define your metrics before you build. Rough out the full level before detailing any section. Playtest as soon as the space is playable. Iterate one problem at a time. Document every change. And never rush to turn your blockout into a fully dressed environment because you think it will impress someone. Art can enhance a level, but it cannot fix poor gameplay.

Build the gameplay first. Let the visuals support it, not carry it. That is what experienced teams do, what hiring managers look for, and what separates a level that players remember from one that looks good in screenshots but falls apart the moment someone picks up a controller.

Ready to put these principles into practice? Pick one level concept, define your metrics, sketch the critical path, and start blocking out. The best time to begin iterating is now.

Quiz Blockout in level design

FAQ Block Tutorial: level blockout essentials

What is a blockout in level design?

A blockout is the first playable version of a level, built using simple geometry like cubes, planes, and basic shapes. It contains no detailed props, materials, lighting, or polished art. The focus is entirely on testing the level’s gameplay, layout, scale, and flow before investing time in visual production.

What is the difference between a blockout, greybox, and whitebox?

These terms are largely interchangeable across the industry. A blockout uses primitive shapes to define playable space. Greyboxing emphasizes a uniform gray palette to reduce visual distractions during testing. Whiteboxing sometimes refers to a slightly more refined iteration where some props have basic color. The core principle is the same: test gameplay before final art.

Why is playtesting important during the blockout stage?

Playtesting a blockout reveals navigation problems, pacing issues, unfair difficulty spikes, and unintended shortcuts before art production locks the geometry. Changes that take minutes during blockout can take days or weeks once the environment is fully modeled and dressed. Testing early makes iteration cheap and effective.

What should a level design portfolio show?

A level design portfolio should show design thinking, iteration, and problem-solving, not just beautiful environments. Include documentation of your process, before-and-after screenshots from playtests, pacing plans, and explanations of why you made specific design decisions. One well-documented project outperforms ten shallow ones.

What are player metrics and why do they matter for blockouts?

Player metrics are numerical values that define how a player interacts with the game: movement speed, jump height, combat engagement range, and interaction distance. These numbers dictate room sizes, corridor widths, jump distances, and arena dimensions. Establishing metrics before building a blockout ensures spaces are playable from the start.

Can I skip the blockout stage and go straight to art?

Skipping the blockout is the most expensive mistake a level designer can make. Once a level is covered in final art, changing the layout means throwing away finished work. If the space does not play well as a blockout, adding art will not fix it, it will only make an unfun level look expensive.

What is a level blockout and how does it differ from a white box or blockmesh?

A level blockout (or blockout level) is an early-stage layout of a game level using simple geometric shapes to establish scale, flow, and gameplay. It is often called a white box or blockmesh when the same process uses plain geometry instead of detailed 3D models. The blockout focuses on gameplay mechanics and playability rather than visual fidelity, giving the game designer and level editor the ability to iterate quickly before committing to final level art.

How do I approach blockout level design in Unreal Engine 5?

Start in your game engine or level editor by blocking out the whole map with simple volumes to test sightlines, cover, and traversal. In Unreal Engine 5 you can use basic BSP brushes or static meshes as blockmesh placeholders, then iterate with a tutorial series or LD workflow to ensure flow well and cohesive gameplay. Integrate playtesting early: prototype gameplay mechanics and adjust geometry until the level plays like you want before adding 3D model detail or finishing art.

What tools and techniques do game designers use during a blockout tutorial?

Common tools include the level editor in your chosen game engine, modular 3D model kits, and movement or collision probes. Techniques involve sketching the whole map first, creating readable geometric shapes for routes, and using a white box to validate pacing and balance. Many designers follow tutorial series from the World of Level Design or Epic developer community and tag progress with the blocktober hashtag; blocktober is an event where creators share blockout work and get feedback.

When is a blockout ready to become a final level or receive detailed 3D models?

A blockout is ready for conversion to final level when core gameplay mechanics work reliably, player flow is clear and cohesive, and playtesting shows consistent fun and balance across runs. Confirm that navigation, sightlines, and pacing suit the intended experience and that LD feedback is incorporated. Once the blockout proves the design, replace blockmesh with detailed 3D models and polish visuals in the game engine for the final level.

Can I follow a blockout tutorial series if I’m a solo developer, and where should I look for community support?

Yes. many tutorial series are geared toward solo game designers and provide step-by-step guidance for creating a level blockout, from basic geometric shapes to refined gameplay spaces. For support, join the Epic developer community forums, World of Level Design resources, and social channels that use the blocktober hashtag to share work and receive critique. These communities help you iterate faster and ensure your level flows well from blockout to finished product.

Matthew Dogherby( Game Developer & Business Development Director )

Game Developer | Designer | Creative Storyteller

Matt Dogherby is a passionate game developer and designer based in Brisbane, Australia. With a career spanning over 15 years, Matt combines technical skill with a deep love for storytelling to create games that captivate and inspire. His unique perspective is shaped by the laid-back energy of Brisbane and his lifelong connection to the ocean, where he often trades coding sessions for surf sessions.