GameGrid
7 Days to Die Crossplay on GameGrid - visual guide

7 Days to Die Crossplay on GameGrid

Steam, PlayStation 5, Xbox Series X/S and Epic players can share one GameGrid server. Crossplay is opt-in, and it caps the server at 8 players, needs EAC on, and rules out mods.

Read This First

Crossplay works on GameGrid 7 Days to Die servers. Steam PC, PlayStation 5, Xbox Series X/S and Epic Games Store players can all join the same world.

It is off by default, and that is deliberate rather than an oversight. Turning crossplay on caps your server at 8 players, so enabling it automatically on a 20-slot server would quietly take 12 slots away from you.

To turn it on: Settings tab, Enable Crossplay, save, restart. That is the whole process.

Correction, 2026-09-08: this article previously said GameGrid servers were Steam-only and that console players could not join. That was true, and it was our fault rather than the game's - the platform was writing a per-server platform.cfg that switched off Epic Online Services, the layer crossplay runs on. It was a workaround for a bug in 7 Days to Die V1.0 that the game fixed in V2.0, and it kept being applied long after it stopped being necessary. It has been removed. If you were told crossplay was impossible here, that answer is no longer correct - open a ticket and we will make it right.

The Four Rules

These are the game's requirements, not ours, and 7 Days to Die enforces them itself: your server refuses to start if crossplay is on and any of them is broken. That is loud rather than silent, which is what you want - a server that starts and quietly excludes your friends is worse.

Easy Anti-Cheat must be enabled. It is on by default.

Maximum Players must be 8 or fewer. This is the one that surprises people on a larger plan.

If your world is RWG, World Size must be 8192 or smaller. Navezgane and the Pregen worlds are fine.

No mods. Not "mods that misbehave" - any mod at all. See the trade-off below.

One more, less obvious: Ignore EOS Sanctions must stay off. Crossplay servers are only found in searches and joinable when sanctions are respected.

Mods or Crossplay - Pick One

This is a real fork in the road and it is worth deciding before you generate a world, not after your group has 40 hours in it.

Mods need EAC turned off, because anything shipping a DLL trips it. Crossplay needs EAC turned on. There is no configuration where both are true.

So: a modded server (Darkness Falls, Undead Legacy, War3zuk, Sorcery) is Steam PC only. A crossplay server is vanilla. If your group is split across PC and console, run vanilla; if the overhaul is the point, everyone needs to be on Steam.

See Installing Mods and EAC Settings and When to Disable It.

How Your Players Connect

Steam PC players use the Server Address on the Overview tab, through Direct Connect or the in-game server browser. See How to Connect.

Console and Epic players find the server through the in-game browser once crossplay is on and Server Visibility is set to public (2). They cannot type an IP - the console clients have no direct-connect field - so visibility has to be public for them, and it can take a few minutes after a restart for the server to appear in the EOS listing.

The platform also clears Disabled Network Protocols on every start, so both SteamNetworking and LiteNetLib are available. A server with SteamNetworking disabled answers "could not retrieve server id" to Steam-authenticated players, and that is the failure this prevents.

If It Is Not Working

If the server will not start after you enable crossplay, one of the four rules is broken and the start result names which. The usual one is Maximum Players above 8.

If the server starts but console players cannot find it: check Server Visibility is 2 (public), check Ignore EOS Sanctions is off, and give it a few minutes - EOS registration happens late in the boot.

If Steam players can join and console players cannot, and everything above checks out, open a ticket. Include your service number and we will read the EOS registration lines out of your server log.

platform.cfg sits in your server's folder and you will see it in the file manager. Leave it alone - the platform writes the correct crossplay-enabled version on every start, so an edit will be overwritten, and an edit is not the fix for anything described here.