Couch co-op on cloud almost works and the gap is worth understanding

A single screen running one game. Two controllers paired to that game. Both players seeing the same view (or split-screen views of the same game world). Latency low enough that both players can react in time to in-game events.

Classic couch co-op titles: It Takes Two, Cuphead, Overcooked, Streets of Rage, Borderlands, Halo (split-screen), Mario Kart, Smash. These titles were designed around the same-screen-two-controllers paradigm.

Two controllers paired to a single cloud session: supported on all major cloud services. The cloud client pairs both controllers locally and forwards inputs to the cloud game. Player 1 and Player 2 work as expected.

Same-screen split-screen view: supported because the cloud session renders the game with split-screen the same way the local console would. The cloud stream just transmits the rendered output.

Local network latency: not a factor because both players are using the same cloud session over the same network connection. The shared session has identical latency for both players.

Controller pairing UX. Pairing two controllers to a cloud client is more cumbersome than pairing to a console. Game Pass Cloud requires both controllers to be paired before launching the session; GeForce Now is more flexible but still has rough edges.

Player-2 onboarding. Some games show 'press a button on controller 2 to join' prompts that work on console but don't always work cleanly in cloud sessions. The cloud client doesn't always pass the button-press through with the right metadata.

DualSense for both players. If both players want DualSense controllers, the cloud client's Bluetooth stack often only fully supports one DualSense feature set at a time. Player 2's haptics may not work even though Player 1's do.

It Takes Two on Game Pass Cloud with two Xbox controllers on a TV: works beautifully. The split-screen renders correctly, both controllers respond correctly, the experience is comparable to local console play.

Overcooked 2 on GeForce Now with multiple controllers: works. Steam Input handles the multi-controller setup cleanly. The Steam Big Picture launching path is the simplest setup we've found.

Cuphead, Streets of Rage 4, similar 2D co-ops: works on every major service. The latency requirements are forgiving and the input setup is simple.

4-player local co-op (Smash, Mario Kart). Sometimes you need 4 controllers paired to the cloud session. Most cloud clients support 2 controllers cleanly, 3 awkwardly, 4 unreliably. The 4-player couch session on cloud is borderline broken.

Asymmetric local multiplayer (Spaceteam, Keep Talking and Nobody Explodes, certain Jackbox games where one device is the screen and others are phones): hard to set up because the cloud session can't pair phones-as-controllers in the same way a local game can.

Cloud gaming marketing focuses on individual play. The implicit assumption is that cloud is a single-user product. The 'cloud replaces your console' narrative ignores the couch co-op use case.

Conversely, dismissive takes on cloud assume couch co-op is impossible. That's wrong. The 2-player couch co-op on cloud works well for many titles. The 4-player variant is harder but not impossible.

The honest framing: cloud is a credible 2-player couch co-op platform for non-marquee multi-player titles. It's not a great 4-player party game platform. It's not a great asymmetric-multiplayer platform. Decide based on your specific use.

If your couch co-op pattern is 2-player It Takes Two, Overcooked, Stardew Valley couch co-op, Cuphead: cloud is a workable solution. Worth trying.

If your pattern is 4-player Smash/Mario Kart/party games: cloud is the wrong tool. Keep a local console or Switch in the rotation for those nights.

If your pattern is asymmetric or phone-as-controller games: cloud is poorly fit. Mostly stick to local hardware for these.