Supermassive Games begins third round of layoffs in three years
Supermassive Games is preparing to eliminate up to 75 roles at its UK studio, adding another painful round of restructuring to a team already hit by multiple layoffs in recent years. For developers, the headline is less about one studio’s headcount and more about how quickly a production slate can turn into a staffing problem when budgets, schedules, and publisher expectations get out of sync.
This is the studio’s third layoff round in three years, which suggests the pressure is not a one-off correction. Supermassive has built its reputation on cinematic, choice-driven horror, a format that can be expensive to produce because it leans heavily on performance capture, animation, narrative content, and long content pipelines. When those costs rise faster than revenue or deal flow, the impact tends to land on staffing.
The exact roles affected haven’t been disclosed, but cuts of this size usually ripple across production, art, design, and support functions before they reach the public. For teams elsewhere in the industry, it’s another reminder that even established studios can face abrupt workforce changes if they’re carrying too many projects or relying on uncertain release timing.
The broader takeaway is that stability in game development still depends on disciplined scope, realistic forecasting, and a pipeline that can absorb delays without forcing layoffs. For developers watching the market, this is another sign that hiring decisions are increasingly tied to short-term project visibility rather than long-term studio growth.
- what
- Supermassive Games is eliminating up to 75 roles in a new layoff round.
- who
- UK studio Supermassive Games is affected.
- when
- This is the studio’s third layoff round in three years.
- impact
- The cuts may affect production, art, design, and support staff, adding uncertainty for developers.
Another layoff round signals continued industry instability.
Follow layoffs updates
See relevant stories in your personalized news feed.
Discussion