Summary
A vertical slice is a focused, polished portion of a game that demonstrates the key features, gameplay mechanics, visuals, and audio at a quality representative of the intended final product. The term originates in software engineering, where “vertical” refers to cutting through all layers of the technology stack (rather than building one layer horizontally across the whole product). In game development it has come to mean something specific: a short playable experience that communicates the game’s vision, tone, unique selling points, and core loop — at production quality, not prototype quality.
A vertical slice is not a prototype. A prototype tests whether a mechanic works. A vertical slice demonstrates what the final game will feel like.
Key ideas
Purpose of a vertical slice:
- Validate the core loop and mechanics — does the gameplay concept actually work as a cohesive experience?
- Assess technical feasibility — can the team build this at the required quality level?
- Build stakeholder confidence — publishers, investors, and team members need to believe in the project’s viability
- Enable early marketing — vertical slices are often the basis for reveal trailers, E3/trade show demos, and early community building
- Resource assessment — the time, talent, and money required to build a polished slice reveals true production costs
Components
A vertical slice should contain all of these in polished form:
Gameplay elements
- Core mechanics — the game’s fundamental systems demonstrated at full quality. A first-person shooter must include aiming, shooting, and responsive enemy AI; a platformer must include movement, jumping, and hazard traversal.
- Condensed game loop — a complete experience of the loop from objective → action → reward, even if shorter than the final game. Stakeholders must understand what the player’s journey through the full game will feel like.
- Minimal tutorial elements — enough to orient a new player without requiring extensive onboarding. The slice should be understandable to someone who has not read a design document.
Visual and audio assets
- Art style at production quality — not placeholder art. The art style must communicate the final aesthetic, not merely approximate it.
- Integrated sound design — sound effects and background music at final or near-final quality. Audio is often the most underestimated contributor to perceived quality.
- Animation and VFX — polished animations and visual effects elevate perceived quality significantly; unpolished equivalents actively undermine it.
User experience and interface
- Critical UI elements — HUD, menus, inventory systems, and feedback indicators must be present and functional. Their absence suggests the player experience has not been thought through.
- UX considerations — minimise player frustration; incorporate tool tips or contextual help where needed; consider flow and ease of use.
- Feedback systems — scoreboards, health systems, reward notifications — any feedback mechanism central to the play experience.
Narrative (if applicable)
- Brief story arc — a short but engaging sequence that reflects the broader game narrative; enough to establish tone, character, and stakes.
- Character interactions — dialogue and character behaviour that communicate the game’s narrative depth and emotional register.
How to make a vertical slice
Pre-production
- Define scope and objectives — what specifically must the slice demonstrate? Which mechanics, which visual style, which emotional register?
- Create design documents — detailed design docs, storyboards, and audio-visual guidelines serve as a shared roadmap
- Allocate resources — plan time, budget, and skills across programming, art, sound, and design before beginning; scope creep is a primary risk
Development
- Collaborate across disciplines — art, design, programming, and sound must work in parallel; a vertical slice is not a sequential process
- Iterate on prototypes first — individual components are prototyped and tested before integration; the slice is assembled from proven pieces, not built whole
- Use version control — all team members working simultaneously makes version control (see git-github-unity, source-control) essential; conflicts in files can destroy work
Testing
- Internal playtesting throughout — frequent internal tests identify bugs and design problems early, before they become expensive to fix
- User testing — small external playtest sessions with target audience members gather objective data on engagement and usability
- Performance testing — a technically unstable or poorly-performing slice cannot demonstrate the game’s vision regardless of content quality
Stakeholder presentation
- Contextualise before playing — prepare a brief verbal or written introduction that frames what stakeholders are about to see, what the full game will become, and what the slice is designed to demonstrate
- Collect structured feedback — identify specific questions to answer from the presentation; unstructured feedback is harder to act on
Practitioner demo advice
Thomas Brush’s beginner and demo advice reinforces a useful teaching distinction: make rough early projects to learn the production loop, then build a polished demo, vertical slice or pitch once the game’s hook and basic feasibility are clearer. In this framing, the demo is not a random level. It is a proof object that shows the hook, aesthetic promise, first-minute readability and production competence (Brush, Your First Indie Game Should SUCK and 25 Game Dev Tips for Beginners, see source-thomas-brush-indie-game-dev-tips).
For student work, this suggests a practical test:
- Can a new player understand the core action within 30 seconds?
- Does the first minute show the game’s strongest hook?
- Are the first and last moments intentionally designed?
- Has the slice been tested by people outside the team?
- Does the demo avoid promising features the final project cannot support?
The advice is practitioner evidence rather than a universal production rule, but it fits the existing vertical-slice principle: the slice should be honest, playable and representative.
Case studies
BioShock — E3 2006 (success)
The 2006 E3 demo introduced players to Rapture — a dilapidated art deco underwater city — through a short, dense playable sequence. Key elements:
- Atmospheric storytelling: Audio logs scattered through the environment communicated backstory without cutscenes; the environment itself told a tragedy
- Plasmid mechanics: The core power-up system was demonstrated through memorable moments (fire from fingertips, electrocuting water)
- Moral dimension: The Little Sister dilemma — save or harvest — was presented in the demo, immediately establishing the game’s ethical stakes
- Environmental interaction: Using oil slicks, water, and electrical hazards showed the game’s systemic depth in minutes
The demo generated enormous anticipation and accurately represented the final product’s quality and vision.
The Last of Us — E3 2012 (success)
The demo shown at E3 2012 established immediately that this was a different kind of action game:
- Emotional relationship: Joel and Ellie’s interactions were woven into the gameplay itself (Ellie passing health kits mid-combat, reacting to violence)
- Visceral combat: Stealth mechanics, improvised weapons, and hand-to-hand combat communicated the game’s brutal, desperate tone
- Responsive AI: Enemies reacted dynamically to player actions, suggesting a living, believable world
The demo raised enormous expectations and the final game met them.
No Man’s Sky — pre-launch (failure)
No Man’s Sky was presented across multiple events with gameplay footage suggesting procedurally generated planets, unique flora and fauna, seamless multiplayer, and limitless exploration. The promotional material functioned as a de facto vertical slice — but it did not accurately represent the product being built. Upon release:
- Multiplayer was absent despite demonstrations implying it was present
- Many showcased features were underdeveloped or missing
- The gap between the presented vision and the shipped game severely damaged the studio’s credibility
The lesson: a vertical slice that overpromises is worse than no vertical slice. The slice must be honest about what the final game will contain. (Hello Games has since rebuilt No Man’s Sky substantially through updates, but the launch damage to their reputation was real.)
Vertical slice vs. prototype vs. MVP
| Purpose | Quality | Audience | |
|---|---|---|---|
| Prototype | Test whether a mechanic works | Disposable — rough, fast, replaceable | Internal team |
| Vertical slice | Demonstrate what the final game will be | Production quality — polished, representative | Stakeholders, publishers, press |
| **[[minimum-viable-game | Minimum Viable Game]]** | Shippable game with minimum scope | Intentionally complete but minimal |
A good development process typically runs: prototype → iterate → vertical slice → full production.
Related
- prototyping — risk-driven iteration before the vertical slice; tests mechanics the slice will demonstrate
- minimum-viable-game — the smallest shippable game; a different goal from a vertical slice
- overview-full-game-development-pipeline — where the vertical slice sits between early concept work and full production
- publishing-and-funding — why slices matter for publishers, investors, and stakeholder confidence
- game-marketing-fundamentals: how the public-facing hook, trailer and store-page message connect to the slice
- playtesting — the testing process used throughout slice development
- game-design-documentation — the design documents that define what the vertical slice must demonstrate
- game-loops — the core loop the vertical slice must demonstrate convincingly
- source-control — version control is essential for a multi-person vertical slice build
- source-cre133-lectures
- source-thomas-brush-indie-game-dev-tips