How to Design a Sense of Scale

A sense of scale—making a structure feel towering, a vista feel vast, an enemy feel colossal—is a powerful tool for awe and impact, and it's achieved through contrast and reference points that let the player feel size relative to themselves. Designing for scale means making size felt through perspective and comparison, not just built large.

Scale is felt through contrast and reference

A sense of scale comes not from something simply being large, but from the player feeling its size relative to themselves, which requires contrast and reference points. A towering structure feels towering because the player, small in comparison, can see how it dwarfs them—the contrast between the player's smallness and the structure's size is what makes the scale felt. Reference points provide this contrast: familiar-sized elements (the player, doorways, objects of known size) next to the large thing let the player perceive the size by comparison, so a colossal enemy feels colossal because the player can see how tiny they are beside it. Without contrast and reference, even a large thing doesn't feel large, because there's nothing to perceive its size against; with them, the size becomes felt through the comparison. Designing for scale, then, means deliberately creating contrast between the player (or familiar reference points) and the large thing, using the player's smallness against the large to make the scale viscerally felt, rather than just building things big and hoping they feel big.

Perspective, framing, and the moment of revelation are what maximize a sense of scale. Beyond contrast and reference, perspective and framing amplify scale: how the large thing is presented to the player—the angle, the framing, the way it fills or towers over the view—shapes how its size is felt. Looking up at a towering structure from below, with it filling the sky, conveys its height far more than seeing it from a distance; framing a vista so it stretches beyond the horizon conveys vastness. Using perspective and framing to present the large thing in a way that emphasizes its size—towering over the player, stretching beyond view, dwarfing the frame—maximizes the sense of scale. The moment of revelation is a powerful technique: revealing the scale of something at a dramatic moment—rounding a corner to suddenly see the colossal structure, the camera pulling back to reveal the vast landscape, the moment the towering enemy is unveiled—creates a powerful impact of scale, because the sudden perception of the size lands dramatically. Designing these moments of scale revelation, where the player suddenly perceives the vastness or size, creates the awe and impact that scale can provide. Combining contrast and reference (that make size felt relative to the player) with perspective and framing (that present the large thing to emphasize its size) and moments of revelation (that reveal scale dramatically) is what creates a powerful sense of scale—making things feel genuinely vast, towering, or colossal through the player's felt perception of their size, rather than just building them large and hoping. A sense of scale, achieved through contrast, perspective, and dramatic revelation, is what creates the awe and impact of the epic and the vast, making the player feel small against the towering and the colossal, which is one of the most powerful emotional effects a game's spaces and presentation can achieve. Designing for scale—felt through contrast and reference, amplified by perspective and framing, revealed at dramatic moments—is what makes the vast and the towering genuinely awe-inspiring.

Consistency beats intensity

Indie development is a long game, and it rewards steady, sustainable effort more than heroic bursts. A little progress made consistently — on the game, on the marketing, on the community — compounds in a way that last-minute sprints never do. The developers who finish and find an audience are usually the ones who kept showing up, not the ones who worked themselves into the ground for a week and then burned out.

Build a pace you can sustain, and protect it. Momentum is fragile and expensive to rebuild, so steady forward motion is worth more than any single intense push.

Let real players be the judge

It's remarkable how differently real players behave from how you imagine they will. The tutorial you think is obvious confuses them; the feature you agonised over goes unnoticed; the thing you almost cut becomes their favourite. None of that is visible from inside your own head, which is why watching real people play is the single highest-leverage thing most developers under-do.

Watch without intervening, resist the urge to explain, and pay attention to what players do as much as what they say. Their confusion and their choices are data, and acting on that data is what turns a game that works for you into one that works for everyone.

Polish where players actually look

Polish is not evenly valuable. Players form an impression in the first minutes and spend most of their time in the core loop, so effort spent there returns far more than effort spread thin across content few people reach. The opening, the moment-to-moment feel, and the things every player touches are where polish converts directly into how good the game feels.

Be deliberate about it. Make the first impression strong and the core interactions satisfying before widening out, because a great core with less content almost always beats a sprawling game that never feels good to play.

Scope is a decision, not an accident

Almost every overscoped game got that way one reasonable addition at a time, with no single decision ever feeling like the mistake. The finish line recedes a little with each new feature, and because the project always feels nearly done, the developer rarely notices how far the goal has drifted until they're exhausted and the game still isn't out.

Treat scope as something you actively decide rather than something that happens to you. Write down what the finished game contains, make every addition a conscious trade against that, and keep most new ideas in a backlog where they belong — because a small game you finish beats a large one you abandon.

Measure before you optimise

Intuition about what's slow, what's confusing, or what's driving players away is usually wrong, and acting on it wastes effort on problems that don't matter while the real ones persist. The developers who improve their games efficiently are the ones who measure first — profiling performance, watching real sessions, capturing actual errors — and let the data set their priorities.

It's slower than trusting your gut, but it's the only approach that reliably improves the game instead of just changing it. Find the biggest real problem, fix that, and measure again, rather than optimising guesses.

A sense of scale comes from contrast and reference points that let the player feel size relative to themselves, amplified by perspective, framing, and dramatic revelation. Make scale felt through the player's smallness, not just built large.