7 Days to Die Crossplay on GameGrid
Steam, PlayStation 5, Xbox Series X/S and Epic players can share one GameGrid server. New servers start with crossplay on; it needs 8 or fewer player slots, EAC on, and no 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.
New servers start with Enable Crossplay on, so a server you order today is open to console and Epic players from its first start. A server created before crossplay became the default keeps the setting it had, which was off: check Enable Crossplay on the Settings tab if yours is older. Crossplay only works with Maximum Players at 8 or fewer, and neither the default nor turning it on lowers Maximum Players for you, so raising the player cap above 8 is the usual way a crossplay server stops working for console players.
To turn it on or off: Settings tab, Enable Crossplay, save. It is restart-required, so on a running server the panel restarts it for you. Turn it off if you want a Steam-only server. With it on, check the four rules below - crossplay being on does not change any of them for you.
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. Nothing stops your server starting over them: a server that breaks one still starts normally and Steam players can still join it, but PlayStation, Xbox and Epic players cannot find or join it. While Enable Crossplay is on, the Settings tab shows a warning at the top listing every one of the first four rules your server breaks right now - including a mod folder in Mods - and the warning goes away once they are fixed. Fix them, then restart.
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.
Before the first mod install on a server, the Mods tab can ask you to confirm that console players will not be able to join while a mod is installed. A mod uploaded through the Files tab or FTP is never asked about, and locks console players out just the same.
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 console players cannot find the server after you enable crossplay, check the four rules in Settings first: Easy Anti-Cheat on, Maximum Players 8 or fewer, World Generation Size 8192 or smaller on an RWG world, and no mods on the Mods tab or in the Mods/ folder. The usual one is Maximum Players above 8. The server starts either way, so a normal start does not mean crossplay is working.
Then 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.