Quick answer: yes, online co-op is supported
Yes. Waterpark Simulator supports online co-op. The official Steam listing includes multiplayer cooperation in the 1.0 release, and the Xbox store lists online multiplayer/co-op for two to four players on Xbox Series X|S. That confirms the feature, but it does not confirm crossplay, local split-screen, or identical invite menus on every platform.
The game entered Steam Early Access on 22 August 2025 and reached 1.0 on 31 July 2026. An older guide may describe an earlier build and still be wrong about the current one, so match every multiplayer instruction to a date, platform, and game version. This page was checked again on 21 August 2026.
Multiplayer lets friends build and run a park together, but the current sources do not define every permission. Host ownership, guest progression, save behavior, join-in-progress, and exact PS5 capacity are Pending verification. Do not fill those gaps with assumptions copied from another platform.
Verified player and platform facts
Steam lists online co-op and describes playing with friends. Xbox provides the most specific platform record: solo play and two-to-four-player online multiplayer/co-op for Series X|S, with an online subscription requirement. PlayStation identifies PS5 and online play as optional.
These fields should stay attached to their platforms. The Xbox two-to-four number cannot silently become a universal PS5 limit, while the PlayStation “1 player” field cannot erase official multiplayer information. Current PS5 group size and the meaning of that store classification remain Pending verification.
The current sources do not confirm local co-op, split-screen, LAN-only play, family guest support, or a browser/mobile multiplayer edition. They also do not confirm Xbox One, PS4, Mac, or Switch releases. Search suggestions are not platform announcements, so organize sessions around verified editions only.
Is there split-screen or couch co-op?
The current official sources confirm online co-op, but this evidence pass found no equal-quality official statement confirming local split-screen or couch co-op. That is an evidence gap, not permission to claim a permanent “no.” If local players are the purchase requirement, treat split-screen as Pending verification and check the current platform store and game menu before buying.
Online co-op also does not imply that two controllers can share one console. Keep this separate from cross-platform multiplayer, which has a dated developer reply: PC on Steam, PS5, and Xbox cannot join the same lobby.
Multiplayer is not crossplay
Multiplayer means more than one player can participate under supported conditions; crossplay means different platform ecosystems can share the same session. Waterpark Simulator supports the first and not the second on the current evidence. A CayPlay developer said in a 5 August 2026 community reply that cross-platform support had not been planned from the beginning.
Therefore, do not expect Steam PC, PS5, and Xbox players to enter one lobby. Keep a friend group on one platform family unless a later official announcement explicitly changes the status. Buying on different stores because all three mention online play will not create crossplay.
Cross-save and cross-buy are separate questions and also remain Pending verification. Xbox cloud saves confirm an Xbox feature, not a transfer to Steam or PlayStation. The cross-platform guide maintains the dated developer answer and should be checked again after major updates.
Host and invite details that remain pending
The current sources do not document the exact create-session button, invite path, privacy setting, password behavior, mid-session join, host migration, or reconnection flow for the latest build. Those details are Pending verification on Steam, PS5, and Xbox. Follow the current in-game interface and the platform's own invitation tools rather than an undated video.
Save ownership also needs field testing. It is not confirmed whether a guest can later load the same park, which progress belongs to the host, or how achievements behave for every participant. Protect the host's known-good save and avoid promising shared progression until a current same-platform test records it.
Community reports around the console launch described some non-host interaction problems. That is a useful role-specific signal, not proof that guests always lack permission or that every current build is defective. Record what works for the host and what fails for the guest before attempting a workaround.
Before you invite friends
First, confirm that everyone is using the same platform edition and has installed the latest offered game update. Check each account's online-play requirement; Xbox ties console online multiplayer to an appropriate Game Pass subscription, while current regional PlayStation conditions should be read on PSN. Fix an access or version mismatch before diagnosing the game.
Choose one host and protect that player's working park. Start with one guest and test a basic interaction in a small area before loading a complex objective or inviting the maximum listed Xbox group. This small test makes host/guest differences visible and keeps an old park issue from looking like a connection problem.
Keep mods out of the first PC multiplayer test. PC mods are unofficial and version-sensitive, and a different loader or file set adds another variable that the official multiplayer evidence does not cover. Establish a clean same-version baseline before testing a modified session.
If something fails, record the platform, version, host, group size, objective, and exact error text. Those details make a report useful. “It does not work” cannot distinguish a subscription problem, version mismatch, crossplay attempt, guest-permission issue, or patch defect.
Troubleshooting without deleting saves
Begin with reversible checks: verify service status, confirm the offered update, close the game normally, restart the platform, and recreate the lobby with the same host and one guest. Test one basic action, then reverse host roles only if both saves are protected and the comparison is useful. Do not delete progress because a launch thread proposed it.
If only a guest cannot interact, preserve the exact object and action while noting that the host succeeds. If everyone fails the same objective, preserve its wording and counter because it may be a quest or version issue rather than the lobby. Console launch reports mentioned both categories, so role evidence matters.
For PC, disable unofficial modifications before blaming the base game and compare loader logs only when a mod page requires them. For consoles, do not install unofficial packages or assume a PC file repair applies. Current status for individual launch issues is Pending verification.
When the failure continues, send official support or the developer community a compact reproduction: platform, game version, host/guest role, account access, action, expected result, actual result, and whether a clean session changes it. Preserve saves and screenshots. This creates a versioned answer without promising a fix that the sources do not verify.
Retest that same small action after each offered patch and keep the observation date.