Why games have named stages
A game is rarely finished in one step. It starts as an idea, becomes something playable, grows into something complete and is finally polished until it can ship. Teams use shared names for these stages so that programmers, artists, producers, publishers and testers know roughly what state a version is in. These build milestones are a convenience, not a law. There is no industry standard body that defines them, so every studio and publisher draws the lines a little differently.
That caveat matters for everything below. Treat the definitions as common patterns, and expect to see exceptions.
Prototype and pre-production
A prototype is a rough, disposable version built to answer a question: is this idea fun, or can this mechanic work? It often uses temporary art and may be thrown away. Some teams build a paper version first, since cheap tests reveal problems early. The period around prototyping is often called pre-production, when the team decides what the game is and how it will be made.
A vertical slice is a short, polished portion of the game that shows final-quality art, sound and play. It is used to convince publishers, funders or the team itself that the whole game can reach that standard. It is called a slice because it cuts through every layer (design, art, audio, code) rather than showing one layer in full. Some people call a similar demonstration a proof of concept, though that term usually means a less polished test of feasibility.
Alpha
Alpha usually means the game is playable from beginning to end, or close to it, but still incomplete. Major features exist, though some may be rough, missing or temporary. Bugs are common and large changes are still possible. Alpha builds are typically shared inside the team, with a publisher or with a small group under confidentiality.
Many studios tie alpha to being feature complete: all planned systems are in the game, even if they are unpolished. After this point, the team generally stops adding new features and focuses on finishing and fixing. Some teams use “first playable” for an earlier stage with only a basic version of the core experience.
Beta
Beta usually means the game is content complete or nearly so and the focus has shifted to fixing problems and polishing. Beta is often when outside players are invited. In a closed beta, access is limited by invitation or sign-up. In an open beta, anyone who wants to can join. Both are forms of beta testing, and what testers are asked to examine varies: stability, server capacity, balance or general feedback.
Some points on how the term is used:
- Beta testing helps find problems that internal teams miss, because many different devices and play styles are involved.
- Beta access can also act as marketing, which is one reason the label is sometimes used loosely.
- A beta does not always lead to a launch on a fixed date. Schedules can move.
- Early access, where the public buys a game still in development, is a different commercial arrangement even though the builds can look similar.
Players should also know that progress in a beta may be erased. Developers often reset accounts and save data before launch, so check the announcement before investing a lot of time.
Code freeze, release candidate and gold
Near the end, teams usually apply a code freeze: a point after which only essential fixes are allowed, to avoid introducing new problems. The team then prepares one or more release candidates, builds that could be the final version if no serious bugs turn up. Each candidate goes through intensive quality assurance, including checks that earlier fixes did not break anything. This is the reason regression testing matters so much at this stage.
Gold (also written gone gold or gold master) means the version has been approved as final for release. The term comes from the era of physical discs, when a master copy was sent to be manufactured. Today most sales are digital, but the phrase survives and generally means the build is locked for launch. It is a statement about the build, not a guarantee that it is bug-free.
After gold: day-one patches and updates
Going gold does not mean development stops. Because manufacturing and certification take time, teams often keep working on fixes during that interval. These fixes can be released as a day-one patch, available when the game launches. Later, post-launch updates continue, and the game patches that follow range from small hotfixes to larger content or balance changes. When you buy a game, you are often getting the gold version plus everything released since.
Reading milestone words on a store page
Here are practical ways to use this vocabulary:
- If a page says “alpha” or “pre-alpha,” expect missing features, crashes and possible changes of direction.
- If it says “beta,” expect a nearly complete game with some bugs and possible resets.
- “Release candidate” and “gold” are rarely public labels, but they appear in developer posts and news.
- Be cautious when an unfinished game is sold at full price. A milestone name tells you the developer’s description of the build, and it does not promise what will be finished.
Different studios may name stages differently, such as “pre-alpha,” “closed alpha,” “technical test” or “stress test.” When in doubt, look for a plain description of what is playable and what is not. Clear communication matters more than the label itself, and the label’s meaning is worth checking each time.