The Game Developers Conference began with a scale problem that now sounds almost comic. In April 1988, game designer Chris Crawford gathered other developers at his home in the San Jose area for a peer-to-peer meeting about making computer games. The modern GDC describes its origin simply: a small developer meetup, literally in a living room.
Even the head count is a useful reminder that early industry history is not always perfectly tidy. Game Developer's 35th-edition retrospective says Crawford gathered 25 developers. A separate Game Developer reprint of reporting from the second conference says 27 people were present at the first. Later histories often repeat the 27 figure. The safe conclusion is the important one: the first meeting involved only a few dozen people, not the thousands associated with GDC decades later.
What happened next explains why that small disagreement survives at all. The gathering did not remain small for long.
The living room was immediately too small
Crawford had already been publishing the Journal of Computer Game Design, giving developers a place to exchange ideas in print. The 1988 gathering turned that exchange into a room full of peers talking directly about design and development. The event was initially known as the Computer Game Developers Conference.
A contemporary account later republished by Game Developer records that the first conference had 27 people present and that Crawford hoped the next one might attract 60. The estimate was conservative. The second conference, held later in 1988, drew about 120 attendees according to that account. Other histories round the figure to roughly 125.
The venue changed with the audience. Instead of returning to Crawford's home, the second meeting was held at a Holiday Inn in Milpitas. That jump — from a domestic gathering to a hotel conference in the same year — captured the demand for a professional space where game makers could compare techniques and argue about the shape of their young industry.
The arguments were not merely technical. The second-conference report discussed concerns about how publishers should participate and whether their greater resources might overwhelm the independent developers the event was meant to serve. That tension feels surprisingly modern: who gets access, who gets heard and whether a professional conference remains useful to the people doing the work.
A conference grows with an industry
GDC's own history describes the event expanding through the 1990s and 2000s into a global destination for technical learning, postmortems, platform changes and wider industry discussion. As game development broadened, so did the subjects on the program. What began around computer games became a meeting place for people working across consoles, mobile, online games and newer technologies.
The conference also accumulated institutions of its own. The Independent Games Festival and the Game Developers Choice Awards became recurring parts of the GDC calendar. The GDC Vault created a long-lived archive of talks and postmortems, making parts of the conference useful even to developers who were nowhere near the room when a session happened.
That growth did not erase the original idea. The current GDC describes the 1988 meetings in terms of curiosity, candour and shared problem-solving. Strip away the expo halls, awards and corporate announcements and the basic proposition is recognisable: people who make games learn faster when they can show one another how they solved difficult problems.
The useful part of the origin story
It is tempting to tell the history as a straight line from 25 — or 27 — people in a living room to an enormous international event. Real institutional history is messier. Venues change, owners and organisers change, the industry's priorities shift, and even simple details such as an early attendance count can survive in conflicting versions.
But the first year gives the story a clear turning point. One gathering in April produced enough energy for another, much larger meeting before 1988 was over. Crawford expected roughly 60; around twice that number came. The living-room model had already outgrown the living room.
For game developers, that origin matters because it makes GDC look less like a conference that appeared fully formed and more like a tool the profession built for itself. A few dozen people wanted a better way to exchange hard-won knowledge. The format scaled because the need scaled with it.
Nearly four decades later, the furniture is different. The core idea is not.
Reporting notes