Subnautica 2 Co-op Guide: Shared Progress, Hosting and Playing When the Host Is Offline

Co-op is the headline feature of Subnautica 2, and it is also the source of the most common confusion new groups run into. The big questions are always the same. Whose progress counts? What do we share? And the one that comes up constantly: if my friend builds the world, am I locked out whenever they are not online?

The answers are clearer than the forums make them sound. Here is how it actually works in the current Early Access build.

The basics: four players, crossplay, no mods

Subnautica 2 supports up to four players in online co-op, and you do not need any mods to do it. Crossplay is in from day one between PC on Steam and Xbox Series X and S, so a Steam player and an Xbox player can dive together with no extra setup.

To start, you pick from the main menu. Host Multiplayer creates a world you control. Join Friends drops you into someone else’s world from your friends list. To connect people, you either add a friend with their unique in-game Friend Code or invite them from your friends list once they are added.

That is the easy part. The part that confuses people is what happens to progress.

What is shared and what is yours

Subnautica 2 uses a fully shared world. That does not mean everything is shared, though, and knowing the split saves a lot of “where did my stuff go” arguments.

Shared across everyone:

• The world itself. Bases, terrain changes, vehicles, the lot. It is one world that all four of you live in.
• Blueprints and data entries. If one player scans a creature or a fragment and unlocks a blueprint, every player in the session gets it automatically. You do not all have to scan the same thing.
• Base storage. Every storage locker built in the world is communal. Anyone can pull from any base locker. This is great for shared resource pools and occasionally annoying when someone grabs the titanium you were saving.

Kept private:

• Personal inventory. The items you are currently carrying on your character are yours alone. They do not get dumped into a shared pool. If you want to share something on your person, you put it in a base locker.

So the model is: one shared world and shared knowledge, but your own pockets stay your own. For tips on dividing roles around that shared setup, the co-op strategy guide goes deeper on who should do what.

Does my progress carry over?

Yes, and this is the reassuring part. When you join your friend’s game, you become part of their save file. Any progress you make in that world, every blueprint you unlock, every base piece you build, every resource you bank, is tracked in that save.

You are not building a separate ghost copy that vanishes when you leave. You are contributing to the one shared world, and it persists in the host’s save. The next time you all play that world, it is exactly where you left it.

If you want the step-by-step on getting a group session running for the first time, the co-op setup guide walks through friend codes and joining.

The host question, answered

Here is the one everybody asks. The world save belongs to the host. So by default, if the host is offline, the other players cannot get into that world. There is no always-on dedicated server sitting in the cloud keeping the world live. The world lives in the host’s save, and that save travels with the host.

That sounds like a dealbreaker for groups whose schedules do not line up. It is not, because of the cloud save system.

The cloud save trick

This is the workaround that fixes the host problem, and it is worth learning early.

From the main menu, you can take any save, single-player or multiplayer, and upload it to the cloud. The flow:

1. Select your save in the menu.
2. Click Upload to Cloud, then confirm the upload and wait for the files to finish.
3. When it is done, the game gives you a code.

To use a code someone shared with you, restart the game, click Import Save at the bottom of the screen, paste the code, and the save appears in your game.

Put those two halves together and you get the real answer to the host question. The last person playing uploads the world to the cloud and shares the code. The next person to play imports that code and continues from there. The world gets handed around the group like a baton, and nobody has to wait on one specific person being online.

The tradeoff to keep straight: whoever imported and played last has the newest version of the world. The group has to be a little disciplined about always grabbing the latest code, or you risk someone continuing from an older save and splitting the timeline. Treat the most recent uploaded code as the single source of truth for your world.

Quick practical rules for groups

• Pick a save owner per session, not forever. Whoever plays last uploads and shares the code. That person is the temporary keeper until the next session.
• Always import the newest code. Before anyone plays solo on the shared world, confirm you have the latest uploaded code so you are not building on a stale copy.
• Use base lockers as the shared bank. Personal inventory is private, so dump anything the group needs into communal storage before you log off.
• Let scanning spread out. Blueprints are shared, so split up and scan different things. The whole group benefits from each unlock.
• Back up the code. If the host’s PC dies or a save corrupts, the last good cloud code is your recovery point. Keep it somewhere outside the game.

That is co-op in Subnautica 2 as it stands. One shared world owned by the host, shared blueprints and base storage, private inventory, and a cloud save system that quietly solves the “host is offline” problem if you use it. Set those expectations with your group up front and you skip the usual week-one confusion entirely.

Worth noting for the future: the EA 1.2 update is the co-op-centric patch, with confirmed additions like player trading, player revive, and proximity voice chat on the way. The shared-world fundamentals above are what you are working with today.