Palworld Crossplay (2026): PC + Xbox + PS5 Setup Guide

Palworld Crossplay (2026): PC + Xbox + PS5 Setup Guide

Last updated: May 24, 2026. Verified against Palworld 1.x current as of late May 2026.

Crossplay Compatibility Chart (2026)

The Crossplay Timeline (How We Got Here)

• January 19, 2024: Palworld launches in Early Access on Steam and Xbox Series X/S + Game Pass. Crossplay between Xbox ecosystem clients only; Steam clients on a separate pool.
• v0.5.0 (March 19, 2025): The "Crossplay Update". Steam clients can now connect to Xbox/Game Pass servers and vice versa. Global Palbox feature for cross-platform pal transfer.
• 1.0 Release (May 2025): Palworld leaves Early Access. PlayStation 5 launches alongside, with full crossplay across all three platforms. Sakurajima endgame zone added.
• Mid-to-late 2026: Pocketpair has confirmed continued development with a next major patch in the queue (raids expansion + Sakurajima refinements).

Step-by-Step: Crossplay Dedicated Server Setup

You want a single Palworld dedicated server that PC (Steam), PS5, and Xbox (Game Pass / console) players can all connect to. The community keeps asking "best dedicated server for crossplay?" - the answer is less about the host and more about getting these eight things right. Run through this list before launching.

1. Use the EOS (Epic Online Services) build, not Steam-only

Palworld dedicated server has two distribution channels: the Steam-only build (PC clients only) and the EOS build (cross-platform). For crossplay you must use the EOS-enabled build. All managed hosts default to EOS; if you self-host via SteamCMD, your launch command must include the EOS authentication parameters. Without EOS, console clients silently fail to discover your server.

2. Set the right ports in PalWorldSettings.ini

PublicPort=8211
PublicIP=<your-public-ip>
RCONPort=25575
RCONEnabled=True

The default Palworld port is 8211/UDP. Forward this port through your router; on a managed host it is open by default. Console clients connect to the same port as PC clients - there is no separate "console port."

3. Enable all crossplay platforms in config

CrossplayPlatforms=("Steam","Xbox","PS5","Mac")
bIsRESTAPIEnabled=False

The CrossplayPlatforms list controls which client platforms the server accepts. Setting all four enables full crossplay. To restrict (e.g., a Steam-PC-only event server), remove platforms from the list. Most communities run the full list.

4. Verify the server is publicly listed (or make it password-only)

bShowPlayerList=True
ServerPassword=""
ServerDescription="Crossplay PvE - All platforms welcome"

Empty password = public server (appears in the in-game server browser). Set a password for direct-IP joins only. The description shows in the browser and signals to mixed-platform players that they are welcome.

5. Player direct-connect addresses

Public listing is nice but direct connect is what everyone actually uses, because each platform handles the server browser slightly differently. Tell your players:

• Steam (PC): Join Multiplayer Game → Connect by IP → your.public.ip:8211
• Xbox / Game Pass: Multiplayer → Join via IP → your.public.ip:8211
• PS5: Multiplayer → Direct Connect → your.public.ip:8211
• Managed host with domain: replace IP with your-server.host.com:8211

6. Test from each platform before opening to your community

Before announcing, connect from each platform you have available:

• A Steam PC client
• A PS5 (if you have one)
• An Xbox Series X|S (if you have one)
• A Game Pass for PC client (if you have one - Game Pass for PC is the same build as Xbox, but the discovery path is different)

Each platform handles authentication slightly differently. If one fails to connect, fix it before going public. Your future support load drops dramatically.

7. Communicate the per-platform character split

Characters are bound to the platform account (Steam ID, Microsoft/Xbox account, PSN ID). If a player joins your server from Steam and again from Xbox Game Pass, they have two completely separate characters on the same world. This catches new crossplay servers out constantly.

Document this in your Discord pin:

• Each platform login = one character on this server
• If you want to swap from Steam to Xbox, your Steam character stays behind
• Pals stored in shared chests are world-state, accessible to any character on the server (so chest-based handoff still works)

See the friends-forced-to-make-new-character article for the recovery flow when a player accidentally orphans a character.

8. Crossplay-specific known issues to communicate up front

• Console clients can time out during world load on large worlds. Workaround: have them connect during low-traffic hours when the server has spare CPU. Increasing the Connection Timeout in client settings also helps.
• Voice chat is platform-specific. No cross-platform voice. Use Discord for unified comms.
• Console mod support is limited. A heavily-modded server will reject console clients. If crossplay matters, run vanilla or only the lightest QoL .pak mods (cosmetic, UI). Pure-server-side mods are fine.
• EOS lobby ID can drift after a server restart. If a Steam player can suddenly not see your server, ask them to refresh the browser; the EOS lobby re-registers on restart.

The Steam vs Game Pass Character Question (Most-Asked Issue)

The single most common confusion on a crossplay Palworld server is "I bought Palworld on Steam, my friend got it on Game Pass, can we play together?" The answer is yes, and the trap is that they think it means "shared character." It does not.

How it actually works:

1. Both players join the same dedicated server using the same direct-IP address.
2. Each player creates a character on their first login. The character belongs to that platform account.
3. Steam-bought player owns "Character A" on the server. Game-Pass player owns "Character B" on the server.
4. Both characters exist in the same world, walk the same map, can trade pals via chests, and progress independently.

If a player tries to switch platforms mid-campaign (e.g., started on Steam, now wants to play on PS5), the new platform creates a new character. The old character stays orphaned in the world. There is no merge tool.

Common Crossplay Troubleshooting

"I cannot see the server in my browser"

Check, in order:

1. Is the server actually running EOS build? Open the panel's Logs tab and grep for EOS; you should see lobby registration messages on startup. If not, the server is on the Steam-only build.
2. Is the firewall open on UDP/8211? Test with a port checker.
3. Has the EOS lobby drifted? Restart the server; if a Steam player still cannot see it, ask them to use direct-IP connect.
4. Did the player select the right region filter in the in-game browser? "All regions" should be set.

"My friend on Xbox cannot join my Steam server"

The most common cause is the server is on the Steam-only build. See section above. If the build is correct, have the Xbox player use direct-IP connect rather than the server browser; this bypasses any EOS discovery delay.

"PS5 player times out during world load"

Large worlds (lots of bases, lots of pals) take longer to stream to PS5 clients than to PC. Increase the client's connection timeout, or restart the server during low player count so the streaming is faster.

"PC and Xbox players see different game versions"

Palworld updates roll to platforms slightly asynchronously (Xbox via Microsoft Store, Steam via Steam, PSN via Sony certification). For 12-48 hours after a major patch, mismatched versions can appear. The server runs whichever version was installed when it started; clients on older versions cannot join until they update.

For deeper troubleshooting see the crossplay troubleshooting article.

What's NOT Crossplay (Still)

A few things to set expectations:

• Voice chat: platform-native (Discord is your friend)
• Mods: .pak mods work on PC; console clients ignore or reject mods. Server-side balance and rate mods are fine.
• Friend lists: Steam friends list shows only Steam friends; Xbox friends list shows Xbox; you cannot send a cross-platform invite. Use direct IP or in-game invites once they are on the server.
• Save transfer: Characters stay on the platform they were created on. No cross-progression save transfer between Steam, Xbox, and PS5 single-player worlds.

Related Palworld Server Guides

• Crossplay troubleshooting
• Dedicated server setup in 10 simple steps
• Connection fixes
• Dedicated server requirements
• Friends forced to make a new character (fix)
• Server settings reference
• Xbox-specific notes
• How to join on Xbox

Want a Palworld host that ships the EOS build by default with all three platforms enabled from day one? See Palworld plans. Daily backups, instant setup, and 5 region options. PS5 + Xbox + Steam-PC all welcome on the same server.