What is a vertical slice?

A small portion of a game built to final quality across every discipline — art, audio, design, code, interface — rather than a larger portion built roughly. It is the single most important artefact in getting a game funded or greenlit.

Why "vertical". Most prototypes are horizontal: a lot of the game at low fidelity, with placeholder art and no audio. A vertical slice cuts down through all the layers of one small area, so what you see is genuinely representative of the finished product.

What it is for:

Proving the game to funders, who cannot evaluate a document. A publisher decides on the basis of playing something.

Proving it to the team, by forcing every discipline to work together early and revealing integration problems while they are still cheap.

Establishing the quality bar, so everyone knows what "finished" looks like.

Producing accurate estimates, since having built one polished area to completion tells you what the rest will cost — which is the only reliable way to estimate a game.

Marketing material, since it is the first thing that looks like the game.

The trap, which is well known. A vertical slice is enormously expensive relative to its size and is frequently built with shortcuts that do not scale — hand-placed content, hard-coded behaviour, special-case logic. Studios then discover that the slice is not a foundation but a facade, and that building the full game requires redoing the underlying systems properly. Treating a slice as the first 5% of the game rather than as a demonstration is the standard mistake.

Related terms: a prototype tests whether a mechanic is fun, at low fidelity and fast; a proof of concept tests whether something is technically possible; a demo is built for the public; and a playable build is simply the current state.

What makes a good one: a short, self-contained experience with a beginning and end; the core mechanic shown at its best; no tutorial dependency, since it will be played cold by someone who has read nothing.