The Quiet Return of Local Multiplayer in Browser Games

For the first decade of the console era, multiplayer meant local multiplayer. Two players on a couch, sharing a screen, with two controllers plugged into the same machine. This was the form that produced the iconic shared-game memories of the 1980s and 1990s — the GoldenEye 007 deathmatches, the Mario Kart blue-shell betrayals, the Street Fighter II versus matches. Then online multiplayer became technically feasible, and the local form began a quiet decline that has continued for twenty years.

In 2026, local multiplayer on consoles is essentially extinct outside of party-game compilations. The major franchises that built their identity on local multiplayer have either pivoted entirely to online matchmaking or maintain local modes as marketing features that almost nobody actually uses. The form is so absent from the contemporary console landscape that an entire generation of players has reached adulthood without ever experiencing it.

Where local multiplayer survives

Browser games are one of the few categories where local multiplayer is having a quiet renaissance. The reasons are partly technical and partly cultural. Technically, a browser with a keyboard, mouse, and one or two gamepads is functionally a local-multiplayer-capable machine: input events can be routed to different in-game players based on which keys or which gamepad triggered them. The development overhead is low; no networking code is required.

Culturally, the browser-game audience overlaps with a particular kind of social play scenario: friends at a kitchen table with one laptop, family members sharing a tablet, classroom situations where multiple students play together. These contexts privilege same-device multiplayer in ways that the contemporary console audience does not.

The design constraints

Local multiplayer in browsers imposes specific design constraints that produce specific design responses. The screen must be visible to all players, which often means split-screen or shared-arena layouts. The input bandwidth is limited to keyboard regions (the left side for player 1, the right side for player 2) plus optionally connected gamepads. The audio is shared; positional audio cues that work for a single headset-wearing player become noise when two people share a speaker.

These constraints suit certain genres better than others. Top-down arena games (twin-stick shooters, fighting games, racing games viewed from above) handle split-screen naturally. Side-scrolling games with bounded play areas can fit both players in a single shared view. Turn-based games with pass-and-play conventions sidestep the screen-sharing problem entirely. Genres that require widescreen first-person camera work do not translate well.

What the resurgence has produced

The current generation of local-multiplayer browser games is small in number but interestingly varied in design. Kart racers with two-player split-screen on desktop preserve the genre's social character. Co-op platformers with one player on WASD and the other on arrow keys produce shared puzzle-solving experiences. Versus fighting games with two-player local matches handle the input separation cleanly. Party games designed explicitly for in-person play distribute mini-games across multiple inputs in ways the format suits.

The financial outcomes are modest. Local multiplayer is not a high-revenue feature; the players sharing a device are also sharing the ad impressions, which reduces per-player monetisation. But the engagement metrics — session length, return rate, word-of-mouth recommendation rate — are typically the strongest in any browser-game category. A two-player local match that goes for 45 minutes produces ten times the engagement of a solo session that ends in 5 minutes.

Why this matters

The resurgence of local multiplayer in browser games is interesting partly for its own sake and partly because it carries design lessons that the broader industry has mostly forgotten. The form requires designers to think about player attention as a shared resource (both players are looking at the same screen), about input as a contested resource (one keyboard, two hands), and about pacing as a social negotiation (you cannot pause an online match the way you can a local one).

These constraints produce different design choices than online multiplayer does. The games tend to be more forgiving (because no public leaderboard is being tracked), more conversational (because the players can talk to each other directly), and more inventive in their input schemes (because the input constraints force creativity). The result is a small body of work that occupies a different design space than either solo or online-multiplayer browser games, and that space is worth visiting if you have not.

For players: bring a friend over, open one of the recommended local-multiplayer games on this site, and remember what it was like before the multiplayer-in-different-rooms paradigm came to dominate. For developers: consider whether your next browser game could support a local-multiplayer mode, and how the design constraints might open creative possibilities that the solo-player frame closes off.