Windrose Co-op & Multiplayer Guide: Hosting, Crew Setup, and What Actually Carries Over
Up to 4 players is the real sweet spot, not the official cap of 8. How to host, what carries over between worlds, why Shared Quest Progress matters more than anything else, and the crossplay claim that doesn't hold up to scrutiny.

TL;DR
- Official server cap is 8, but the developers themselves flag performance issues above 4: treat 4 as the real practical maximum, not 8.
- Any solo world can become a co-op session at any time with zero progress loss. No separate multiplayer save required.
- Enable Shared Quest Progress in World Properties: it's the single setting that determines whether co-op actually saves you time or not.
- Loot from chests is per-player, but world resources (wood, stone) are shared. Understand the difference before you're arguing about it mid-session.
Windrose is genuinely better with a crew: naval combat with real roles, splitting questing duties across islands, someone holding boss aggro while someone else reloads. But the game barely explains its own multiplayer rules, and getting them wrong costs real time. Part of the full Windrose cluster. See the XP & Leveling Guide for how Shared Quest Progress actually affects your levelling speed.
The Basics
| Multiplayer type | Online co-op only, no local split-screen |
| PvP | None. You cannot attack other players |
| Official server cap | 8 players |
| Practical recommended max | 4 players; developers flag real performance issues above this, especially late-game |
| Public server browser | None, invite-only via code or Steam friends list |
| Console | None, PC only at launch |
How to Actually Start a Co-op Session
- From the main menu, select Host a Game instead of Solo/Offline
- Choose an existing solo save or create a new one. Any solo world can become co-op at any time with zero progress loss, there's no separate multiplayer save required
- Set your Server Name, Password (optional), and Max Players in World Properties
- Confirm. The game generates a unique invite code
- Share the code (or, if you're already Steam friends, right-click their name and send a direct invite)
- After a player's first successful join, the server saves automatically. They won't need to re-enter the code next time
Hosted Sessions vs. Dedicated Servers
| World stays online when host logs off | No, session ends | Yes, persists independently |
| Setup complexity | Trivial, invite code | Requires a hosting provider (Nitrado is the common option) |
| Approximate cost | Free | ~$10-15/month |
| Recommended RAM (4+ players) | N/A | 32 GB |
| Best for | Crews playing the same schedule | Crews playing at different times |
What Actually Carries Over, and What Doesn't
This is the most commonly misunderstood part of Windrose co-op:
- Character progress (gear, stats, items) carries over between different worlds and servers you join. Your captain is persistent, not tied to one save
- Loot from chests is separate for each player: nobody's "stealing" your rewards, everyone gets their own
- World resources (wood, stone, and similar gathering materials) are shared: your crew genuinely impacts the same world state together
- Quest progress depends entirely on the Shared Quest Progress setting: with it enabled in World Properties, completing a co-op quest marks it done for every player who had it active simultaneously, which is the actual mechanism behind co-op's XP advantage over solo play
The Crossplay Claim, Examined
Most coverage states flatly that there's no crossplay: Steam and Epic Games Store players are on separate networks. At least one detailed technical account disputes this directly, arguing the actual connection routes through Windrose's own gateway rather than platform-specific matchmaking (Steam or Epic Online Services), meaning the storefront a player bought from doesn't functionally matter for the connection itself. The one place storefront genuinely does matter either way: friends-list invites are platform-specific, so a Steam friends list only shows Steam friends and vice versa. If your crew is mixed across storefronts, skip friends-list invites entirely and just share the invite code directly, through Discord or any other channel, rather than assuming it won't work.
We can't fully settle this discrepancy with confidence, and Kraken Express hasn't made an official statement either direction as of this writing. If you're planning a mixed-platform crew, the safe assumption is to test with a direct invite code rather than relying on a platform friends list either way.
Communication Without Built-In Voice Chat
Windrose doesn't include built-in voice chat as of this writing, which is a genuine gap compared to some other Early Access co-op titles that ship with proximity voice built in. What it does offer: text chat for written messages, and a G-radial ping system (hold G to open a radial menu) for quick callouts and marking objectives or waypoints on the map. For most organised crews playing with people they already know, this combination handles planning and in-the-moment coordination reasonably well, with Discord or another external voice tool covering the gap. The absence is felt most acutely in two specific situations: coordinating with strangers who aren't already in a shared Discord, and large eight-player sessions where text and pings alone struggle to keep pace with what's happening. Voice chat is listed by the studio as a planned feature, though with no confirmed date. Check the Windrose Roadmap for the current status on this specifically.
Crew Etiquette and Session Planning
A few practical habits that make co-op sessions run smoother, beyond the pure mechanics:
- Decide on Shared Quest Progress before you start, not mid-session. Toggling it after a session is already underway can create confusion about what's actually been credited to whom.
- Establish rough roles early, even informally. Someone handling navigation, someone on resource gathering, someone leading combat encounters. Windrose doesn't force role assignment, but crews that settle into loose specialisation tend to progress faster than crews where everyone does everything simultaneously and duplicates effort.
- Agree on session length expectations up front. Since hosted sessions end when the host logs off, a crew without a dedicated server needs some shared understanding of how long a given session is likely to run, especially mid-voyage or mid-boss-fight.
- Use the G-radial ping liberally. It's a low-friction way to flag loot, hazards, or objectives without needing full voice coordination, and crews that use it consistently report smoother navigation than crews relying purely on verbal description over an external voice call.
Troubleshooting Common Connection Issues
If a friend can't join your session, the most common culprits, in rough order of likelihood: they haven't cleared the initial tutorial objective yet (join errors are common until this is done), the invite code was mistyped or has expired, or, if your crew spans Steam and Epic, they tried a friends-list invite rather than a direct code, which only works within the same storefront's network. Server routing was also a genuine issue at launch specifically, when some ISPs blacklisted IP ranges the game's servers were routed through; that particular problem was addressed in a server update shortly after release and shouldn't affect current sessions, but it's worth knowing about if you're troubleshooting against very old advice.
Naval Combat as a Crew
Co-op ship combat is genuinely one of the strongest parts of Windrose, and it's worth dedicating a specific section to since it's where crew coordination matters most visibly. With a full crew, one or two players can handle cannon duty while another steers and a fourth watches hull integrity and manages repairs mid-fight. See the Best Ships Guide for more on how ship choice interacts with crew size. Boarding actions specifically reward a crew that's rehearsed the transition from ship-to-ship combat to melee: someone needs to hold the wheel steady during the approach, and the rest of the crew needs to be ready to shift immediately once boarding begins, rather than everyone abandoning their post the moment the fight moves onto the enemy deck. A disorganised crew can genuinely lose fights a well-coordinated smaller crew would win, simply through wasted motion during the transition.
Should You Play Solo or Co-op?
Windrose is genuinely playable and complete solo: every system works without a crew, and the game doesn't gate meaningful content behind multiplayer specifically. That said, the numbers are honest about where the game is strongest: co-op crews reach the current level cap in 4-6 hours against 8-15 solo, naval combat benefits enormously from role division, and several reviewers independently noted the game feels meaningfully more polished in co-op than solo, where rougher combat encounters show more clearly. If you're deciding whether to wait for friends before starting, that's a reasonable instinct backed by real evidence rather than just a general "games are better with friends" platitude. Windrose specifically seems to have been built with a crew as the primary intended experience, even though solo play works fine on its own terms.
Where to Go Next
- Windrose Roadmap: the full hub
- XP & Leveling Guide: exact XP values and Shared Quest Progress detail
- Talent Tree & Builds Guide: branches, the level 10 commitment
- Beginner Guide: first-hour priorities
- Best Ships Guide: every ship compared
- Crafting Guide: every station, build order, material gating