Crunch, Explained: Why Game Studios Still Ship This Way and What's Actually Changing
The extended-hours push before a launch is one of the industry's oldest problems, and one of its slowest to actually fix.
"Crunch" refers to sustained, often mandatory overtime in the weeks or months leading up to a game's release, when a studio works far beyond a normal schedule to hit a ship date. It has been a recognizable pattern in game development for decades, and despite years of public criticism, it has not disappeared.
Part of the reason is structural. Games are creative products that are difficult to scope accurately at the start of a project; features get prototyped, cut, redesigned, and re-added as development reveals what actually works, which makes early estimates unreliable. That uncertainty tends to get absorbed at the end of the schedule rather than the beginning, because ship dates are frequently locked in early for reasons that have nothing to do with development progress, like a marketing campaign, a retail season, or a platform holder's release slot.
Staffing plays a role too. Studios often size their teams for the middle of a project rather than for the crunch-heavy final stretch, since hiring purely for a temporary peak is expensive and hard to reverse afterward. Certification deadlines imposed by console platform holders add a hard, external cutoff that cannot simply be negotiated away, which compresses the final bug-fixing window even further.
What has genuinely started to shift is visibility and leverage. Unionization efforts at individual studios and industry-wide organizing have put crunch conditions into contract negotiations for the first time in many companies' histories, rather than leaving them purely as internal policy. Media coverage of crunch at high-profile studios has made the practice a reputational risk that recruiting and retention teams now have to answer for, which gives internal advocates for sustainable scheduling more weight than they had a decade ago.
Live-service game structures have changed some of the underlying incentives as well. When a game ships as a smaller, evolving base that grows through post-launch updates instead of one enormous release, studios can spread crunch-inducing pressure across many smaller milestones instead of concentrating it all at a single launch date. That does not eliminate overtime, but it changes its shape.
None of this means crunch is solved. It remains common at smaller and mid-size studios with less bargaining power, tighter budgets, and less public scrutiny than the largest publishers face. The pattern is shifting from an accepted cost of doing business toward something studios feel pressure to justify, but the underlying scheduling and staffing problems that produce crunch in the first place have not gone away.
