7 Days to Die supports crossplay between PC (Steam), PlayStation 5, and Xbox Series X|S, with continued support through V2.6 Stable. This guide covers what's actually required to set up a crossplay-capable server, the in-client crossplay toggle, and the snags that catch console players. Where specific values aren't documented in the public reference, this page errs on the side of "check your version and host" rather than fabricating numbers.
| Platform | Crossplay Support | Notes |
|---|---|---|
| PC (Steam) | Yes | Full support with EAC enabled |
| PlayStation 5 | Yes | Server browser only |
| Xbox Series X|S | Yes | Server browser only |
| PlayStation 4 | No | Legacy version, no updates |
| Xbox One | No | Legacy version, no updates |
The crossplay-relevant serverconfig.xml properties (verified against our XML reference):
| Property | Recommendation | Why |
|---|---|---|
EACEnabled | true | Cross-platform sessions require EAC. Console players cannot join an EAC-disabled server. |
ServerDisabledNetworkProtocols | Default (SteamNetworking disabled, LiteNetLib enabled) | Console players reach the server via the LiteNetLib path — don't disable it. The default config is correct for crossplay. |
ServerVisibility | 2 (Public) | Console clients use the in-game server browser; "Friends-only" (1) and "not listed" (0) hide the server from the browser. |
| Mods | None for crossplay | Console clients can't load PC-side modlets. A modded server may still accept PC connections but won't accept console connections cleanly. |
There is no CrossplayEnabled property in serverconfig.xml — crossplay is enabled by the combination of EAC + LiteNetLib + Public visibility, not by a single switch. If you've seen "set CrossplayEnabled=true" in older guides, that's an older or fabricated naming.
Player-count and world-size caps for crossplay aren't publicly documented as hard limits — what's listed elsewhere as "max 8 players, max 8192 world size" appears to come from in-UI guidance that varies by version. Check the live in-game crossplay toggle for whatever your current build enforces.
Edit your serverconfig.xml to the following crossplay-friendly defaults — these are real properties:
<property name="EACEnabled" value="true"/>
<property name="ServerVisibility" value="2"/>
<!-- Default ServerDisabledNetworkProtocols ("SteamNetworking") is correct for crossplay; do not add LiteNetLib to the disabled list -->
Set ServerMaxPlayerCount and WorldGenSize to whatever your audience and hardware support — see Player Capacity Optimization for the trade-offs. Crossplay-specific upper bounds, if any, will be enforced by the in-game crossplay toggle and rejected at join time with an explicit error.
EACEnabled=true.ServerVisibility=2 (Public).LiteNetLib to ServerDisabledNetworkProtocols — console clients use it.ServerPort (default 26900, UDP) and adjacent ports.Note: Console players cannot connect via direct IP - server browser only.
Cause: Server has settings outside the crossplay-eligible ranges enforced at join time.
Solution:
Cause: EAC mismatch between client and server.
Solution:
Cause: Different game versions between client and server.
Solution:
Cause: Server configuration issue.
Checklist:
Solution for console:
Most reliable for crossplay:
| Aspect | PC | Console |
|---|---|---|
| Max View Distance | 12 chunks | 10 chunks |
| Load Times | Varies by hardware | Generally longer |
| Frame Rate | Uncapped | 60 FPS target |
| Graphics Options | Full customization | Preset options |
Yes, with crossplay enabled and EAC on.
No. Any mod on the server disables crossplay.
Server must be Public (not Friends-only), crossplay enabled, EAC on, and vanilla (no mods).
No. Save data is platform-specific.
No. Only PS5 and Xbox Series X|S support crossplay.
Console split-screen works, but both local players connect as one to crossplay servers.