01 Can a PS5 player join a hosted Palworld server?
Yes, with a compatible current server configured for the correct connection path. Pocketpair’s server-type documentation ↗ lists crossplay platforms including PS5 and says PS5 and Xbox need a Community server. A server working through PC direct IP does not alone establish PS5 support.
When comparing Palworld server hosting that allows PS5, ask the host to confirm Community registration and the current build, then have a PS5 player actually find and join it. Also ask whether your chosen mods are compatible with the console members of the group. Do not rely on an old article saying all dedicated servers are Steam-only, or on a newer marketing label without a joining test.
02 Invite code versus a dedicated-server invitation
For a dedicated server, send connection instructions rather than assuming a co-op invite code will work. Pocketpair documents IP-and-port entry for direct connection and Community-list selection for Community servers. Official connection guide ↗.
| Send to a friend | Example or check |
|---|---|
| Connection method | Community search, or supported direct IP. |
| Exact visible name | Use a distinctive name you can recognize. |
| Address when direct IP is supported | 203.0.113.25:8211 is a documentation example, not a live server. |
| Player password | Share privately; never send the admin password. |
| Build and play window | Agree on updates and when the machine will be online. |
For a private group that needs Community discovery, use the documented player password and give access details only to your group. Being discoverable in a list need not mean letting strangers play.
03 Self-hosted Community setup: verify one layer at a time
For a native self-managed server, add the official -publiclobby option. A Linux launch example is ./PalServer.sh -publiclobby; on Windows, use the corresponding PalServer.exe. Pocketpair Community deployment ↗.
- Confirm the world starts normally before changing network rules.
- Test from a supported local client to establish application health.
- Map the actual UDP gameplay port through the router and allow it in the host firewall. Use your configured port, not an assumed number.
- Have an outside player search the name and connect. Local tests alone do not prove internet reachability.
- Check the PS5 client separately and verify the expected character and world load.
If your ISP does not provide a reachable public endpoint, port forwarding alone may not solve access. Ask the ISP about inbound connectivity, or choose hosting with an externally reachable allocation. Do not permanently disable the whole firewall.
04 Crossplay settings and a useful final acceptance test
The current configuration reference uses CrossplayPlatforms and marks the older AllowConnectPlatform unavailable. Confirm PS5 is included in the active configuration, using your current provider editor or version-matched file. Do not overwrite a full settings file with a fragment from a different release.
A meaningful acceptance test is: one PC player and one PS5 player join together, see the same known base, make a small saved change, disconnect, then reconnect after a clean server restart. If only PC can join, investigate the Community path and allowed platforms; if both fail, start with the shared server or network failure. For Pine-specific discovery steps use the Pine guide; for protecting that world use the save export checklist.