Local Multiplayer Is Back on Browsers (Yes, Really)

For the first decade of the console era, multiplayer meant local multiplayer. Two players on a couch, sharing one screen, with two controllers plugged into the same machine. This is the form that produced most of the shared-gaming memories I hear about from people my age and older. The GoldenEye 007 deathmatches. Mario Kart blue-shell betrayals. Street Fighter II versus matches with someone you knew well enough to be obnoxious about it. Bomberman bracket nights. Then online multiplayer became the default and the local form started a slow decline that's been going on for twenty years.

In 2026 local multiplayer on consoles is basically extinct outside of party-game compilations. The major franchises that built their identity on local multiplayer have either gone fully online or kept local modes as marketing bullet points that almost nobody actually uses. The form is absent enough from contemporary consoles that an entire generation of players has reached adulthood without playing a game with someone next to them on a couch.

Where it survived

Browser games are one of the few categories where local multiplayer is actually doing well right now. Partly technical, partly cultural.

Technically: a browser with a keyboard, mouse, and one or two gamepads is functionally a local-multiplayer machine. Input events route to different in-game players based on which keys or which gamepad triggered them. No networking code required. Development overhead is low.

Culturally: the browser-game audience overlaps with a specific kind of social-play scenario. Friends at a kitchen table sharing one laptop. Family members passing a tablet around. Classroom situations where kids share devices. Coffee-shop tables where the laptop owner reluctantly lets a friend press one of the keys. These contexts work for same-device multiplayer in ways that console living rooms don't anymore.

The design constraints are real

Local multiplayer in a browser imposes specific constraints, and the games that succeed in the form are the ones that respond to those constraints rather than pretending they don't exist. Screen has to be visible to all players. Input bandwidth is limited to keyboard regions plus optionally a gamepad or two. Audio is shared, which kills positional cues that work for a single player with headphones. Pause-state is a shared event because there's only one game running.

These constraints suit certain genres way better than others. Top-down arena games translate naturally: twin-stick shooters, kart racers, fighting games viewed from above, plus the occasional 2D brawler. Side-scrollers with bounded play areas can fit both players in a shared view. Turn-based games with pass-and-play conventions sidestep the screen-sharing problem entirely. Genres that need widescreen first-person cameras don't translate.

What the resurgence has actually produced

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, basically a love letter to the GameCube era. Co-op platformers with one player on WASD and the other on arrow keys, producing weirdly intimate puzzle-solving where you have to actually communicate. Versus fighting games with both players on the same keyboard. Party games designed for in-person play with several mini-games rotating through.

I'll give you the specific example I keep coming back to. There's a two-player puzzle game on this site that I played with my partner three Sunday afternoons in a row. We solved maybe two-thirds of the levels. The other third we gave up on because we kept arguing about whose fault the failure was. I count that as a positive review. Online co-op doesn't generate that kind of disagreement because nobody can see your face when you mess up.

The economics are strange

Local multiplayer is not a high-revenue feature. The players sharing a device are also sharing ad impressions, which cuts the per-player monetisation in half. But the engagement metrics, session length, return rate, recommendation rate, and time before the players close the tab, are typically the strongest in any browser-game category by a wide margin. A two-player local match that runs 45 minutes generates ten times the engagement of a solo session that ends in 5 minutes. The math is funny but it works out, mostly because retention compounds.

Why this matters beyond the format

Resurgence of local multiplayer in browser games carries design lessons that the broader industry has mostly forgotten. Designing for local-multiplayer means thinking about player attention as a shared resource. About input as a contested resource. About pacing as a social negotiation. And about the social fabric of play, because sitting next to someone matters in ways that a discord chat doesn't replicate.

These constraints produce different design choices than online multiplayer does. Games tend to be more forgiving, because no public leaderboard is being tracked. More conversational, because the players can talk to each other directly without typing. More inventive in their input schemes, because the constraints force creativity. And more interested in what happens at the table afterward than what shows up on a leaderboard. This adds up to 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 haven't.

For players: bring a friend over, open a couple of the local-multiplayer games on this site, and remember what shared-screen gaming was like before everyone retreated into their own rooms. For developers: think about whether your next browser game could support a local mode, and how the constraints might open creative possibilities the solo-player frame closes off. The form has more headroom than most people realise.