Video Game Development: How Games Are Made

Game development is the process of designing, building, and shipping interactive software — a discipline that pulls together programming, art, music, writing, and project management into a single product that has to work and be fun at the same time. That second requirement is harder than it sounds. This page covers the full development pipeline, from early concept to final release, including how studios of different sizes approach the process and where projects most often go wrong.

Definition and scope

At its core, video game development is software engineering with a creative brief attached. The International Game Developers Association (IGDA) defines game development as encompassing pre-production, production, quality assurance, and post-launch support — though those phases look dramatically different depending on whether a 4-person indie studio or a 3,000-employee publisher is running them.

The scope of the industry is significant. The Entertainment Software Association (ESA) reported in its 2023 Essential Facts About the Video Game Industry that the US video game industry generated over $57 billion in revenue in 2022. That figure isn't a coincidence — it reflects an ecosystem where development budgets have scaled accordingly, with AAA titles (the industry term for major publisher productions) commonly exceeding $100 million in development costs before marketing.

For a broader sense of how development fits into the larger landscape — platforms, genres, business models, and the companies involved — the Video Game Authority covers those dimensions across the full topic set.

How it works

A game moves through five recognizable phases, regardless of studio size:

1. Concept and pre-production — The team defines the core loop (what the player does repeatedly), the target platform, genre, and rough scope. A design document is drafted, often running 20–numerous pages for mid-size projects.
2. Prototype — A stripped-down playable version is built to test whether the core mechanic is fun. This phase intentionally uses placeholder art and temporary code. Many projects die here, which is the correct outcome.
3. Production — The longest phase. Assets are created at scale — environments, characters, animations, audio, UI. Code branches multiply. Bug counts climb before they fall.
4. Alpha and beta — Alpha marks feature-complete status (everything is in, nothing is polished). Beta is content-complete and shifts work to QA (quality assurance) testing. External betas may involve public players.
5. Gold and post-launch — "Going gold" is the moment a build is locked and sent to manufacturing or certification. Post-launch patches and downloadable content (DLC) have become standard practice across the video game business models that now dominate commercial releases.

The video game development process page examines each phase in more technical depth, including milestone structures and certification requirements for console platforms.

Common scenarios

Three development scenarios account for most games shipped:

AAA studio production — A major publisher funds a team of 200–1,000+ people over 3–7 years. Marketing budgets sometimes equal or exceed development costs. Red Dead Redemption 2 (Rockstar Games, 2018) reportedly employed over 1,600 people across 8 studios during peak production. Quality is high; risk is existential — a single commercial failure at this scale can restructure a studio.

Mid-tier and AA development — Studios of 20–150 developers, often publisher-backed but with tighter budgets. This tier is where genre innovation often lives, since teams are large enough to execute ambitious scope but small enough to take creative risks.

Indie development — Studios of 1–15 people, self-funded or grant-supported. Tools like Unity and Unreal Engine (both offer free tiers with revenue-share or licensing thresholds) made this viable at scale. The indie games page examines this sector, including how games like Stardew Valley — developed solo by Eric Barone over 4.5 years — reached over 20 million copies sold (per ConcernedApe's public statements).

The video game publishers and developers page maps the commercial relationships between studios and the companies that fund and distribute their work.

Decision boundaries

Not every game concept belongs to every development model. Four factors tend to determine which path fits:

Scope vs. team size — Open-world games with voiced dialogue and physics simulations require hundreds of specialists. A puzzle platformer with hand-drawn art does not. Mismatching scope to team size is the most common cause of "development hell" — the industry term for a project that keeps shipping and missing dates for years.

Platform target — Console certification (Sony, Microsoft, Nintendo) adds formal QA requirements and submission windows that PC or mobile development doesn't impose. This affects scheduling and budget allocation in ways that catch new studios off guard.

Engine choice — Unreal Engine 5 offers photorealistic rendering pipelines but has a steep learning curve; Unity favors faster prototyping across 2D and 3D; proprietary engines give studios full control at significant maintenance cost. Engine choice at pre-production shapes every subsequent technical decision.

Business model — A free-to-play game designed around live-service updates requires a different production pipeline than a premium single-purchase title. The ongoing content cadence of live-service games means development never fully ends post-launch, which has significant implications for team structure and video game careers within those studios.

Understanding the difference between a well-scoped indie project and an underfunded AAA attempt can explain why games with smaller budgets sometimes deliver more coherent experiences than productions with 100 times the resources — ambition and execution don't always scale together.