video game crunch culture why your favorite games 1794864118615

Video Game Crunch Culture: Why Your Favorite Games Keep Costing Developers Their Weekends

The International Game Developers Association’s 2023 survey found that 28% of respondents said their job involved crunch time, while another 25% worked long hours but never called it crunch. Add those together and more than half the people who answered have lived some version of this. So when a studio says the team is “going the extra mile,” check how many miles the spreadsheet added.

The Game Developers Conference’s November 2026 report narrows things to mandatory overtime, and that slice is still ugly. Eight percent of respondents reported it. Within that group, 69% received no extra pay and 63% said the overtime could have been avoided. “Avoidable” is the word that should bother you most. It means the hours were a planning choice, not a natural disaster. Back in 2000, the F.A.K.K. 2 project logged nearly five months of crunch, including a month of seven-day weeks and 12-to-16-hour days. Somebody still signed off on that release date.

Key Takeaways

  • Crunch time is a short sprint before a deadline, but crunch culture is what happens when that sprint never ends and extra hours become a studio’s default way of working.
  • The November 2026 State of the Game Industry report found that 63% of the 8% of respondents who had mandatory overtime said that overtime could have been avoided, so studios that call crunch a natural disaster are really admitting they plan badly.
  • California’s computer-software overtime exemption requires an annual salary above the threshold of $122,573.13 through 2026, rising to $127,108.34 on January 1, 2027, plus primarily software-related duties, so a fat paycheck alone does not make a developer exempt.
  • Electronic Arts paid $15.6 million in 2005 and $14.9 million in 2006 to settle overtime claims at its California studios, so the unpaid hours were never as free as the company pretended.
  • The 2017 Chalmers University research found that teams at studios with routine feature prioritization reported less crunch, so those studios decide what the game isn’t before the release calendar decides for them.

What Is Crunch, Really?

Crunch is extended or uncompensated overtime that studios use to hit a game’s development schedule, and the industry is very good at describing it with softer words. A 2017 ICSE-SEIP research paper from Chalmers University of Technology characterizes game-industry crunch as uncompensated overtime and weekends at the office, which is about as plain as the definition gets. Notice what’s missing: a villain. Crunch doesn’t need a tyrant with a whistle. It needs a release date the plan can’t reach without people giving up their evenings.

Crunch time and crunch culture are not the same thing, and mixing them up is how studios get away with everything. Crunch time is a short sprint near a deadline, when the team is hunting the bug that crashes the final boss or pushing a patch through certification. Plenty of creative and technical fields have a stretch like that. Crunch culture is what happens when the sprint never ends. The “final stretch” is the one that keeps coming back, and extra hours stop being an exception and become the way the studio runs by default.

The everyday forms are rarely dramatic. There’s the weekend at the office that nobody formally assigned but everybody understands is expected. There’s the 11 p.m. message in the team channel that’s “just a quick thing” and then isn’t. There’s the vacation day that somehow gets checked on. And there’s the free pizza on a Saturday, which is often the only overtime anyone ever acknowledges. Salaried status makes all of this easier to hide, because when nobody is clocking hours, nobody has to count them.

Studios avoid the word because it comes with liability attached. So you hear “ownership,” “passion project,” “we’re a family,” and “going the extra mile” instead. Those phrases describe the same hours without the paperwork. Some workers log long hours without ever calling it crunch, and the term gets slippery. If the people doing the work don’t have a name for it, it doesn’t show up in a survey answer, an HR form, or an internal postmortem. And if it doesn’t show up anywhere, nobody has to track it or pay for it.

That slipperiness is why the numbers in this section should be read carefully. Crunch is a label people apply in different ways, and the same schedule can be called a sprint at one studio and a lifestyle at another. The 2017 research also found that crunch takes several different forms, which is a polite way of saying the problem has more than one face. A studio that says it doesn’t crunch might still be asking for the same hours. It just stopped printing the word on the job posting.

Next time a studio promises that the next game will be “built with care,” ask what care costs in hours, and who is paying them.

How Many Developers Actually Crunch?

How Many Developers Actually Crunch?

Depending on how you count, somewhere between a quarter and more than half of game workers have lived through crunch. Only a much smaller slice reports the kind of mandatory overtime that management can’t pretend is optional. The numbers are messy, and the mess is part of the story.

The survey most people quote is the 2023 developer satisfaction survey. It collected 777 valid responses, which is enough to spot patterns and nowhere near enough to speak for everyone who makes games. The organization behind it warns that its sample is self-reported and spread by word of mouth, so it isn’t necessarily representative of the global workforce. That’s a fair warning. Anyone who reads those percentages as a census of the entire industry is reading them wrong.

What a survey like this does well is capture how people describe their own hours. In that 2023 data, 28% of respondents said their job involved crunch time. Another 25% said they worked long or extended hours but never called it crunch. Those two groups are not the same. The first is a studio admitting it has a crunch period. The second is people who decided the label didn’t matter because the schedule felt identical either way. Counting the first group is easy. The second only shows up when someone asks the right question, and it’s bigger than most studio press releases would like.

The November 2026 State of the Game Industry report widened the net. It drew on more than 2,300 professionals, and it didn’t stop at programmers and artists. Marketing staff, executives and investors answered too. That matters, because the people who set release dates often sit outside the teams that absorb the overtime, and they’re rarely the ones checking their inbox at midnight.

Narrowing the question to mandatory overtime shrinks the number fast. Eight percent of respondents reported it, and the follow-up questions are where things get ugly. Within that 8%, 69% received no compensation, and 63% said the overtime could have been avoided. Read that again. Most of the people forced to work extra hours weren’t paid for them, and most say somebody could have planned the schedule differently.

The same report also asked about mental health. In the previous 12 months, 65% of respondents said their job had negatively affected it. Don’t mistake that for a crunch statistic. It measures the job as a whole, not the extra hours in particular. Crunch is one ingredient in that stew. It isn’t the whole recipe.

So what’s the gap between “28% crunched” and “8% had mandatory overtime”? Mostly it’s a definition fight. A studio can truthfully say it doesn’t require overtime while the team still shows up on Saturdays because the schedule and the team chat make it feel required. The numbers tell you what people experienced and what they chose to call it.

If you want to read any industry survey without getting fooled, start with three questions. Who got asked, and how did they find the survey? Does it ask about mandatory overtime, or just long hours? And does it separate the people doing the work from the people deciding the schedule? A survey that only talks to one of those groups tells you one side of the story. In game development, the other side usually has the calendar.

Why Do Developers Work 60-Hour Weeks?

Developers end up working 60-, 80- and 100-hour weeks when a release date gets locked before anyone knows what the game needs, and then the work keeps growing while the date stays put. Nobody has to decide to crunch. The arithmetic does it for them.

It starts on the calendar. A date often gets written down during a pitch or a publisher meeting, months before the team knows how long the combat, levels, or online systems will actually take. Then the features arrive. The combat needs a second pass, the designers want one more area, and marketing wants a boss that wasn’t in the prototype. Each addition sounds small in a meeting, and each one costs hours that never made it into the estimate.

That’s scope creep, and it’s the quiet part of the problem. Late-stage changes are the expensive version. A mechanic gets cut or rebuilt a few weeks before content lock, and everything that depended on it has to be reworked. The team pays twice for the same feature, once to build it and again to tear it out and rebuild the parts around it.

The hour counts add up faster than most people expect. A 60-hour week is twelve hours a day for five days, which means the weekend has quietly stopped existing. An 80-hour week spread across seven days is more than eleven hours every single day, including the one you were supposed to sleep in. At 100 hours, you’re looking at roughly fourteen hours a day with no real off switch.

The 2023 IGDA numbers show these aren’t hypotheticals. Among respondents who reported crunch or long hours, 30% worked more than 60 hours per week. Freelancers had it worse in that group, and 17% of them reported working more than 80 hours per week. Freelancers rarely get overtime pay, and a missed date can mean a missed contract, so they’re the first to say yes and the last to say no.

Now look at what a studio’s history of crunch looks like on paper. A 2023 analysis of game development postmortems in New Media & Society recounts that the 2000 F.A.K.K. 2 project had nearly five months of crunch, including one month of seven-day weeks and 12-to-16-hour days. Five months is not a bad week that got out of hand. It’s a schedule with no room left in it, and the only way to fill the gap was with people’s lives.

That’s the definition of a death march: a project pushed forward at any human cost. The phrase is useful because it names the real problem. A team doesn’t wake up one Tuesday and vote for 100-hour weeks. Those hours come out of a plan that promised a date the work couldn’t meet, and the blame for that plan sits with the people who made it, which is usually planning and leadership.

Crunch gets sold as dedication, and that’s the lie worth calling out. Nobody deserves a medal for a weekend a better schedule would have prevented. A studio that celebrates its team’s sacrifice is usually celebrating its own failure to estimate work. If your plan only works when people quietly give up their evenings, the plan is broken, and calling it “passion” doesn’t fix it.

Is Crunch Legal in California?

Is Crunch Legal in California?

Not for most workers who are entitled to overtime. Under California law, nonexempt employees must be paid extra for long days and weeks, and a studio can’t simply decline to pay them. The catch is a classification known as the computer-software exemption, and it’s where a lot of unpaid crunch hides.

The baseline comes from the California Department of Industrial Relations. For nonexempt workers, time-and-a-half applies to hours over 8 in a workday or 40 in a workweek. Double time kicks in for more than 12 hours in a workday, along with specified hours worked on a seventh day. In practice, a developer who works a 12-hour day is owed four hours at time-and-a-half. Push that day to 13 hours, and the extra hour is paid at double time.

Now the exception. California Labor Code § 515.5 conditionally exempts certain computer-software employees from overtime. The word “conditionally” is doing a lot of work. The exemption isn’t automatic for anyone with a tech-sounding job title. It only applies if the worker meets specific requirements.

Salary is one of those requirements. The state’s October 2026 notice sets the annual salary threshold at $122,573.13 through 2026, rising to $127,108.34 effective January 1, 2027. The state’s computer software page lays out the figures and the rules around them.

Here’s the part studios hope you skip. A high salary doesn’t finish the job. The worker’s actual duties matter too. The exemption is meant for people whose work is primarily software-related. A person paid a big salary who spends most of their week on something else doesn’t get the exemption just because the paycheck is large. Salary is the first gate, and the duties test is the second. Plenty of HR departments only check the first one.

That gap is where the quiet erasure happens. A studio puts everyone on salary, calls the arrangement “flexible,” and suddenly the 70-hour weeks stop being overtime on paper. Nobody clocks in, so nobody counts the hours. The protection overtime rules were built to provide still exists in law, but it can vanish in practice because nobody checked whether the job qualifies. A salary is a number on an offer letter, not a permission slip for unlimited hours.

The January 2027 change adds another wrinkle. A threshold that goes up means a salary that cleared the bar in 2026 might not clear it in 2027 unless the paycheck rises too. Workers who assumed they were exempt on a fixed salary could find themselves on the nonexempt side without anyone announcing it. Studios are usually good at announcing new features. They’re less eager to announce that a pay band no longer qualifies.

California is one example, not a universal rule. Other states and countries write their own overtime laws, with their own thresholds, exemptions, and enforcement habits. A developer in another region can’t assume the California numbers apply, and a studio can’t hide behind the fact that its headquarters sits elsewhere. The question that matters everywhere is the same: is the person doing the work legally protected, or has their job title been used to make the protection disappear? Check your paystub, check your job duties against the rules where you work, and treat “salaried” as a question to ask, not an answer.

What Did EA’s Overtime Settlements Cost?

Electronic Arts agreed to pay $15.6 million in 2005 and $14.9 million in 2006 to settle overtime claims at its California studios. That’s real money, and it came from a company that could have afforded to fix the problem in the first place.

The 2005 deal started with graphic artists. Electronic Arts agreed to settle the California overtime claims of its graphic artists for $15.6 million, and it also agreed to reclassify about 200 entry-level artists as overtime-eligible. For those workers, late nights and weekend pushes could be paid as overtime instead of disappearing into a salaried job title.

Entry-level staff have the least leverage. They’re the ones most likely to be handed the cleanup work, the late-night bug hunt, and the weekend build check, and they’re the least likely to push back. Reclassification doesn’t fix a bad schedule, but it does put a price tag on the hours that the schedule demands. A studio suddenly has to count them.

The claims didn’t stop with the artists. In 2006, the company agreed to pay $14.9 million to settle overtime claims brought by current and former programmers at its California studios. Programmers are often the people who untangle the systems that crunch pushes past their limits, so the claims reached the core of how the games were built.

Put the two settlements side by side and the pattern is hard to miss. Same company, same state, same kind of complaint, and a combined bill of $30.5 million. Overtime disputes can be expensive, and a company that pays that kind of money has learned exactly what unpaid hours cost when someone finally counts them.

That’s the uncomfortable part for the industry. If a publisher can write checks in the millions to settle overtime claims, it already knows the hours are a liability. Ignoring that knowledge is a choice, and it’s a choice that gets harder to defend every year the late nights keep showing up in developer surveys.

Settlements like these are not a cultural reset, and nobody should pretend a lawsuit fixes a broken calendar. But they do show that crunch-era labor practices have been challenged in court, and that the financial stakes were never small. The bill just gets paid after the damage is done.

Does Crunch Actually Make Games Worse?

Does Crunch Actually Make Games Worse?

Crunch isn’t a guaranteed recipe for bad games, so the argument against it is about cost and risk rather than a promise that every crunched title will flop. What the research does show is that increased stress turned up across every type of crunch it studied, and that studios where feature prioritization was routine reported less crunch.

The 2017 study drew on game postmortems and employee interviews, and it identified four distinct types of crunch. Increased employee stress showed up across all four. That’s the detail to remember. No version of overtime gets a pass just because it looks organized on a project plan. A team working a “planned” sprint is still working longer hours under pressure.

The same study found something studios should find uncomfortable. Teams at studios where feature prioritization was routine reported less crunch. When a studio decides early which features matter, cuts the rest, and sticks to that list, the late-stage panic shrinks. Crunch often isn’t a sign of dedication. It’s frequently what happens when a team never made the hard decisions until the release date made them for it.

Those costs rarely show up in review scores, but they show up in the people doing the work. The game may still ship, and it may even be fun. It’s just a riskier way to build it, and the people paying that risk are the ones working the weekends.

The modern production model is different from the old one. Crunch used to end when a boxed game went gold and the team got a few weeks off. Live-service games and microtransaction-driven release calendars don’t really finish. They roll from one season into the next, with a battle pass that needs new cosmetics every few weeks, events that go live on fixed dates, and a store that needs fresh items to keep revenue moving.

That’s the trap. When the calendar is built around monetization, content pressure never fully stops. A studio can plan a launch perfectly and still end up in crunch because the next seasonal update was already advertised, the event dates are locked, and the store has promised a new character by the weekend. Nobody has to write “crunch” in a memo for it to happen. The schedule does the talking.

The old crunch had an ending, even if it was a miserable one. The live-service version can run indefinitely, with each season’s deadline arriving before the last one has cooled off. Teams get a few days of recovery, then the next roadmap lands on the desk, and the cycle restarts before anyone has asked whether it should.

So ask a simple question of any live-service roadmap: who picked the date, and did the developers have a say in it? If the answer is a quarterly revenue target, the crunch isn’t a surprise. It’s a business model with a development team quietly absorbing the cost every season. Players see the new skins and the limited-time event. They rarely see the weekends that made them possible.

Can Unions and Management Fix Crunch?

Fixing crunch starts with management, because leadership decides how big the game is, how many people build it, and when it ships. Unions and reporting only help if studios accept limits on those decisions. Developers rarely get a vote on any of the three. A producer signs off on the feature list, a studio head agrees to the release window, and a publisher adds the marketing date to the calendar. When the scope is too big for the headcount and the deadline is too early, the overtime is scheduled before the first sprint starts.

The International Game Developers Association has published written standards that separate crunch from unsustainable work and from management abuse of workforce resources. That split matters. Crunch is a short, planned push toward a deadline. Unsustainable work is a schedule that keeps running past what people can absorb. Abuse of resources is when a team is simply expected to pay for someone else’s bad planning. A studio that can’t tell those three apart is either confused or hoping you are.

Grassroots groups have been pushing on the other side of that equation. Game Workers Unite and similar organizations have pushed for collective action and public accountability, which mostly means making labor visible: sharing working conditions, organizing across studios, and asking companies to answer for their schedules on the record. Their power comes from numbers and from refusing to let every crunch be treated as a private embarrassment.

Unionization is the sharper tool. QA testers at Raven Software, an Activision Blizzard studio, formed a union, which gave them a formal way to bargain over working conditions instead of hoping a manager would be reasonable at 11 p.m. Unions don’t make games ship faster, and they won’t stop a publisher from wanting the release date it already announced. What they do is turn overtime from a favor into a term of employment that can be negotiated.

Feature prioritization is the most practical lever a manager has. The 2017 study found that teams at studios where prioritizing features was routine reported less crunch. Prioritization that actually works is not glamorous. It means agreeing on a ranked feature list before production gets heavy, writing down what gets cut and why, and setting a content lock date that the publisher signs off on in advance. Studios that do this have decided what the game isn’t before the calendar decides it for them.

Then there’s the public relations problem. Some studios announce a wellness program, a mental health day, or a “no-meeting Friday” and leave the deadline exactly where it was. That’s a free lunch served during a fire drill. A perk doesn’t cancel a months-long sprint, and a studio proud of its wellness page while the Saturday build checks continue is grading its own homework. Real commitments look less cuddly. They say overtime needs approval and pay, scope changes after a set date require a schedule change, and crunch gets reported instead of quietly absorbed.

So the test for any union agreement or reporting pledge is simple. Does the studio give up something it wanted, such as a feature, a date, or a planned headcount cut, or does it only add something to the break room? A company that agrees to bargain but refuses to move the release date has handed the union nothing to win. A studio that publishes a crunch policy while the team chat keeps pinging at midnight has written a poster and called it a policy.

Players can help by asking the question studios hate most: what did you cut to make this date? If the answer is a list of features, a clear schedule, and a team that went home on time, you may be looking at a studio that took management seriously. If the answer is a thank-you post about the team’s passion, you already know who’s paying for the weekend.

What Players Can Do Before the Next Crunch

Start with the release calendar you can see. If a live-service game posts its season dates months ahead, with battle pass drops and events locked in, the roadmap may have been set before anyone knew how long the work would take. Hold off on pre-ordering until you’ve seen how the first few weeks go.

Watch the launch-day patch, too. If a game sold as finished needs a massive update in its first days, the team was probably fixing the last crashes while you were playing the first levels. That’s a planning problem, not a sign of bad luck.

Then ask the question studios dislike most. Post on the official forum or social channels and ask what got cut to hit the date. A straight answer tells you the team made hard choices early. A vague answer tells you something too.

Finally, reward the studios that put their labor practices on the record. If a developer publishes an overtime policy, has a union, or openly talks about scope cuts, say so in your reviews and recommendations. Players rarely get a seat at the planning table, but the way you spend your time and money is still a signal developers can read.

Scroll to Top