We Were Here Tomorrow Crossplay: All Platforms

Every pairing works, and the official announcement puts crossplay in its title rather than in a footnote. The pairings:

What does not exist is a Switch, macOS or Linux version, so those platforms are outside the matrix entirely. The crossplay support does not extend to a platform that has no build.

Two players is also a hard limit rather than a matchmaking preference. One outlet puts it plainly: there is no room for a third player in the lobby.

Everyone needs their own copy, a working microphone and an internet connection. There is no friend pass on any platform, so a mixed-platform pair is two purchases rather than one plus a guest.

Console players need their subscription tier: the PS Store states PS Plus is required for online play and supports up to two online players with it. Xbox online play works the same way through its subscription.

PC players need a machine that meets the minimum, which includes Windows 11, a GTX 1660 Ti class card and 25 GB of storage. The microphone is listed in the requirements rather than in a footnote, which tells you how central it is.

You create a public lobby in game and wait for someone to join. The official FAQ offers exactly that, plus the Steam forums and the official Discord, as the way to find a partner — there is no described friend-list invite flow.

That is the awkward part of crossplay here: the platforms can talk to each other, but the social layer is a lobby browser rather than an invite from your friends list. Plan the session in Discord and then find each other in the lobby.

One competitor write-up mentions a room-code system, but we could not verify it in the source we read, so we do not describe a code flow. If your build shows a code, use it; if not, you are not missing a step.

If the lobby stays empty, do not wait in it. Post the time and the platform in the Discord, then create the lobby at that time, because a public lobby with nobody waiting is invisible to anyone who is not already looking.

The series is built on asymmetric information: one player sees the instructions, the other sees the machine, and the puzzle is the conversation between them. A shared screen would display both halves at once, which is the opposite of the design.

That is also why there is no local co-op on consoles or PC, and why two people in the same room still need two machines and two copies. The closest you get is playing in the same room with separate setups.

If you are weighing "couch co-op night" against this game, the honest answer is that it is a voice-call game. Two controllers on one sofa cannot start a session on any platform.

The nearest thing to a shared evening is two setups in one room, with both players on headphones so the two voice channels do not bleed into each other. That works, and it is also the only way to play the proximity-chat moments without echo.

The game uses proximity voice in addition to the walkie-talkie. The official known-issues page lists it as a feature rather than a bug: you can hear each other directly when you are close, and the walkie-talkies appear on screen automatically once you are out of hearing range.

That explains a class of "voice is broken" reports. If you can hear your partner faintly but the radio interface is missing, you are simply standing near each other.

It also gives you a small tactic: when a puzzle needs a quiet moment to read a panel, walking away switches the audio channel rather than muting your partner.

Cross-platform saves are not documented anywhere we could find. We have not seen an official statement about carrying progress between platforms, so treat saves as platform-bound rather than assume they follow the account.

Room codes are in the same category. One page describes them, the source we checked does not, and we would rather leave a gap than publish a flow that does not exist in your build.

Console-specific bug lists are also unverified here. The official support site keeps separate known-issue pages per platform and we have only read the PC one in detail, so a console problem may be documented somewhere we have not opened. If you hit one, the platform page on this site is the place to check what we do know.

Before the session, confirm four things on each side: the game is installed and updated, the microphone works in the platform's own party chat, the console subscription is active, and both builds are on the same patch. A version mismatch after an update is the most common reason a lobby will not fill.

Agree who hosts before anyone launches. The host owns the checkpoint, which is why a host who leaves ends the run rather than handing it over, and why swapping partners mid-run resets progress.

Test voice before the first puzzle rather than during it. Say a sentence, confirm it arrived, then walk apart and confirm the walkie-talkie appears. Five minutes here saves an hour of blaming the lobby.