Cross-play, cross-progression, and cross-buy sound like three names for the same feature, but they are separate promises. Cross-play lets you join the same match as someone on a different platform. Cross-progression carries your save file, unlocks, and achievements when you move between devices. Cross-buy means one purchase unlocks a game on several platforms. A title can offer any one of these without the others, and most games deliver only some combination of them.
This guide explains how each mechanism works under the hood, using the official developer documentation from Valve, Epic Games, and Microsoft. The goal is to give you a way to read a store page and know what you are actually getting, and what you are not. The three ideas are easy to conflate in marketing copy, but they are built from different pieces, and each one can fail on its own.
Cross-play starts with identity, not netcode
The hardest part of cross-play is not moving game packets between devices. It is making sure two people on different storefronts can find each other and prove they are the same person across accounts. Every platform runs its own account system and its own friends list, and none of them talks to the others by default. Your Xbox friends list, your Steam friends list, and your PlayStation friends list are three disconnected address books.
Epic states the problem directly in its Online Services documentation: the point of its crossplay feature is to “enable players accessing your game from different storefronts to play together using a combined friends list.” That combined list is the core of cross-play. A developer integrates the Epic Accounts system, and players who sign in with Epic credentials can be matched across whatever storefronts the game supports. The technical overview says developers use Epic Accounts to enable crossplay for titles on the Epic Games Store, Steam, and consoles.
This is the piece most players never see. When a game asks you to link a platform account to an Epic account, a Microsoft account, or a publisher account, that is the cross-play machinery being wired up. The game is building one shared identity space on top of the separate platform account systems, so that a player on a PlayStation and a player on Steam resolve to the same kind of record and can be invited into the same lobby.
The takeaway is that cross-play is a product of a shared account layer, not of the game’s network code. When a game supports cross-play, it is almost always because the developer adopted a middleman identity system, Epic’s or Microsoft’s or one they built themselves, that sits above the platform accounts. Two games can have identical networking and one will be cross-play and the other will not, depending entirely on that identity layer.
The matchmaking and networking underneath
Once players share an identity layer, the game still has to put them in the same session. Valve’s Steamworks Multiplayer documentation lays out the building blocks most online games use, whether or not they are on Steam: matchmaking and lobbies, peer-to-peer networking, dedicated game servers, and the Steam Datagram Relay.
The documentation draws a distinction that is easy to miss: matchmaking and lobbies do not provide networking features. A lobby is where players gather before a session starts; it is not the thing that moves packets during the game. For actual data transfer, a developer pairs the lobby system with peer-to-peer networking for small groups or with game servers for larger, persistent, or competitive games. Valve recommends dedicated servers for esports-style titles and names Dota 2 as the example, while smaller parties suit matchmaking plus peer-to-peer networking.
The same page walks through the decision a developer faces before writing any of it: does the game already have networking, and does it need peer-to-peer or server-based play. A peer-to-peer game that only wants friends to find each other can add matchmaking and lobbies on top of what it has. A competitive game that needs a persistent world has to run dedicated servers. Voice chat is yet another layer: Valve’s voice APIs handle the audio capture but do not network the audio by themselves, so the developer still has to send that data through peer-to-peer networking or game servers.
This matters for cross-play because it means the network layer and the identity layer are separate decisions. A game can use platform-specific servers and still enable cross-play if its account layer is shared, or it can use fully cross-platform networking and still lock matchmaking to one platform. Cross-play does not mean the servers are shared; it means the players can be routed into the same session, however that session is hosted.
The Steam Datagram Relay is the piece most relevant to cross-platform play in the wild. It is a relay service a game can route traffic through when two players cannot reach each other directly, which is common when they sit on different home networks or different storefronts. A developer can lean on that relay instead of exposing raw peer-to-peer connections, and the decision is independent of whether the players happen to be on the same platform. The relay solves a reachability problem, not an identity problem, which is another way of saying the plumbing and the account system are two separate concerns.
Cross-progression: the save file has to live somewhere neutral
Cross-progression is a data problem. Your save, achievements, and unlocks are normally stored by the platform you play on. To move them, the developer has to keep that state on its own servers and tie it to your shared account, then push it down to whichever device you launch next. The platform’s own save storage is not designed to be read by a competitor’s storefront, so the developer has to become the middleman for its own data.
Microsoft’s Xbox Play Anywhere program packages this in the cleanest form. The program page states that a Play Anywhere game plays on Xbox console, PC, and supported gaming handhelds at no additional cost, and that progress goes with you, listing saves, game add-ons, and achievements as the things that carry over. The page reports more than a thousand games in the program and describes a store badge that marks participating titles.
Note the scope. Play Anywhere ties Xbox, Windows PC, and handhelds together because all of those run through the Microsoft account. It does not reach a PlayStation or a Nintendo account, and it does not move your Steam saves into a console version. Cross-progression is always bounded by which accounts the developer has chosen to connect, and the marketing line rarely spells out that boundary.
Cross-buy is a pricing decision, not a technology
Cross-buy is the simplest of the three and the least standardized. It means a single purchase grants the game on more than one platform. Xbox Play Anywhere is the clearest example because it is an explicit buy once, play anywhere promise attached to a store badge. Many other cross-buy arrangements are ad hoc: a developer may offer a free Steam key to console owners, or bundle versions, without any formal program behind them.
Cross-buy and cross-play are independent. A game you bought twice can still let you play with friends on the other platform, and a game you bought once may not. When a store listing says cross-play, that says nothing about whether you also get the other version for free. The two features are frequently confused because the same program, Play Anywhere, happens to deliver both, but they are wired to different parts of the system: cross-buy to the entitlement record on your account, and cross-play to the identity and matchmaking layers.
The limits you will actually hit
The documentation also surfaces concrete constraints that store pages rarely mention.
Platform authorization is a gate. Epic’s crossplay documentation describes a multi-step process to bring each console into the fold: developers work through the PlayStation Partners Portal and the PS5 DevNet, a Microsoft account representative, and the Nintendo Developer Portal plus a middleware authorization form for Switch and Switch 2. Cross-play is not something a developer flips on once; it is negotiated per platform, which is one reason support arrives unevenly and sometimes ships later on one console than another.
Even the overlay that makes cross-play invites convenient has gaps. Epic notes that its Social Overlay is not available on macOS, Linux, Linux ARM64, Android, and iOS, and that developers can fall back to the EOS SDK’s multiplayer features, like Sessions, with their own interface on those platforms. In practice this means the polished friend-invite flow a player gets on a console may not exist on a Linux or mobile build of the same game, even though the underlying cross-play is there.
Cross-progression has its own footguns. Save state tied to a shared account only follows you if the developer built and maintains that sync. DLC and add-ons are often excluded, and purchases made inside a game, a season pass or a cosmetic, frequently stay on the platform where you bought them. A cross-progression promise about your character level says nothing about whether the expansion you bought on one store will unlock on another. The safest assumption is that only what a store listing explicitly promises, like Play Anywhere’s saves, add-ons, and achievements, will carry over.
Why the same game behaves differently on different stores
Understanding the three layers explains a lot of otherwise confusing behavior. A game that is fully cross-play may still run its own platform-specific servers, which is why performance or cheat enforcement can feel different depending on where you bought it. A game with cross-progression may still sell its DLC per platform, which is why your content library can differ between your console and your PC. And a game with cross-buy may still ask you to link accounts, because the free second copy is delivered through an entitlement tied to a shared account, not magically.
None of this is accidental. Each layer is a separate business and engineering decision, and each storefront has its own policies about how accounts link, how entitlements are granted, and how player data can move. The developer is threading a path through those policies, and the result is a specific, limited set of promises rather than a single universal switch.
What to check before you buy
When you are weighing a cross-play purchase, read for the three promises separately. Look for a stated cross-play or cross-platform multiplayer line, a stated cross-progression or cross-save line, and a Play Anywhere or equivalent cross-buy badge. Then check the fine print on add-ons and in-game purchases, because those are the most common exclusions.
If cross-progression matters to you, confirm which platforms are named, not just that the feature exists. If cross-buy matters, confirm the second copy is actually delivered on the store you care about, not just advertised. And if you are buying specifically to play with a friend, confirm their platform is in the supported list, because cross-play is almost always scoped to a defined set of platforms, not to everyone at once.
Cross-play is a shared identity layer plus networking. Cross-progression is server-side save state. Cross-buy is a pricing promise. Understanding which of the three a game actually makes will save you from buying the wrong version of a game and expecting it to behave like the right one.
