Platform holders own floors, not ceilings
A studio's address — the building where the work actually happens — is a consequence of ownership, and ownership in the console industry has been redrawn so many times since the mid-1990s that many of the most recognisable names in the medium now sit inside one of three corporate structures. Nintendo, Sony Interactive Entertainment ↗, and Microsoft ↗ each operate networks of internal studios alongside the publisher-facing certification process that all external developers must pass. The distinction matters because an internal studio does not clear the same gates a third party does: it has earlier access to hardware, closer contact with the platform's engineering teams, and a different relationship to the submission calendar.
The geography is real and it shapes output. Nintendo's internal development groups are concentrated in Kyoto, where the company has been headquartered since its founding in 1889, and in Tokyo. The Kyoto campus houses teams responsible for mainline Mario and Zelda production; smaller satellite arrangements exist, but the cultural and logistical centre of Nintendo's first-party work has not moved. Sony Interactive Entertainment's studios are distributed across a wider set of countries: Naughty Dog and Insomniac Games operate out of California; Santa Monica Studio, also in California, is the home of the God of War franchise; Guerrilla Games is in Amsterdam; and Media Molecule is in Guildford, England. Most of these became internal through acquisition rather than being founded by Sony, which means each carries institutional memory and toolchain habits from its pre-acquisition life.
Microsoft's internal portfolio is the most geographically dispersed of the three, and the most recently enlarged. The company's Xbox Game Studios label grew substantially through the acquisition of Bethesda Softworks' parent company ZeniMax Media in 2021, adding studios in Maryland, Texas, and Sweden in a single transaction. The subsequent acquisition of Activision Blizzard, completed in 2023, added further locations across California, Wisconsin, and beyond. What had been independent publishers became internal studios almost overnight, which altered the platform access, certification relationships, and multiplatform obligations of every team inside those structures.
The consolidation decade and what it fixed in place
The period between roughly 2000 and 2012 is when the present map was drawn. Mid-sized independent publishers that had thrived through the fifth and sixth console generations — when disc manufacturing and retail distribution were the primary bottlenecks — found themselves squeezed between rising development costs and platform holders willing to pay acquisition premiums for proven teams. The studios that became first-party during those years brought with them audiences, franchises, and, crucially, engine expertise. Insomniac's acquisition by Sony in 2019 is actually a later example of the same logic: a long-term exclusive relationship formalised after decades of de-facto alignment, because the studio's Ratchet and Clank work had already been built on PlayStation hardware for nearly twenty years.
The consolidation also fixed the internal certification relationship. An internal studio and an independent developer face different submission processes: first-party teams work against the same Technical Requirements Checklist that external developers face, but the communication channel is direct rather than mediated, and schedules can be adjusted through internal negotiation in ways that third-party publishers cannot access. That is not a shortcut through certification — the checklist items are the same — but it is a different operational rhythm, and it compounds over a seven-year hardware generation in ways that show up in what those studios can attempt.
Third-party studios that remained independent — CD Projekt in Warsaw, Larian Studios originally from Ghent, FromSoftware in Tokyo — operate on a different logic. They negotiate platform access through the developer programmes each holder runs, clear external certification for every submission, and make their own engine decisions without the backstop of a platform holder's internal tools team. The costs of that independence are real: development kit access is later, toolchain support is thinner, and the submission calendar is less flexible. The benefits are also real: the studio is not bound to a single platform's release schedule, and its back catalogue does not become a negotiating chip in a corporate acquisition.
What the address tells you about the machine
A studio's physical location carries platform-economic meaning beyond the obvious. European studios that came into Sony's network during the PlayStation 2 and PlayStation 3 eras — Guerrilla in Amsterdam, Evolution Studios, which was later closed, in Runcorn, England — were building on hardware designed in Tokyo and certified against standards written in California and Japan. The distance was not only geographical: it was organisational, and studios in that position developed distinct internal processes for managing the compliance calendar across time zones. The same pattern applies to any large publisher with studios in multiple regions working toward a simultaneous global certification submission.
Nintendo's concentration in Kyoto has a different consequence: hardware design, software development, and the certification framework that governs external developers are all produced within a relatively tight organisational perimeter. That proximity is one reason Nintendo's internal software tends to be written unusually close to the hardware — teams are within reach of the engineers who built the specification, and the accumulated knowledge of a fixed machine compounds more efficiently under those conditions than it does across an international corporate structure.
The studios named across this site, then, are not just addresses: they are positions inside a platform-economic structure that was largely set during the consolidation years of the 2000s, and that the acquisitions of the early 2020s have extended rather than replaced. Where a studio works determines which hardware it touches first, which certification process it navigates, and how much of its engine and toolchain was chosen freely versus inherited from an acquisition. Those variables are upstream of everything a team produces, which is why the address is the right place to start before anything else about the work.
