Beginner Guide
Learn how to turn your first dives into repeatable safe loops: gather, scan, craft, return, and push farther next time.
Sub2Wiki is a player-first Subnautica 2 wiki for maps, resources, fragments, beginner routes, Tadpole progression, co-op planning, platform questions, console commands, patch notes, and Early Access changes. It is built to answer what players actually ask while playing: where should I go, what should I bring, what should I scan, and when should I turn back?
A good game wiki should not force you to browse a giant database when you only need one decision. Choose the module that matches your current situation and follow the route notes.
These are static published guide cards, not an automated CMS feed. Each card points to a real page included in this deployment package.
Learn how to turn your first dives into repeatable safe loops: gather, scan, craft, return, and push farther next time.
Prepare for the vehicle unlock path by treating fragment hunting as a planned expedition, not a random swim.
Use version notes to avoid old routes, outdated platform assumptions, or fragment information from an earlier build.
For now, the homepage embeds only the verified official Early Access gameplay trailer. Additional video guide slots should be replaced with your own videos when your channel is ready.
Use this as a visual overview of the new world, co-op direction, survival loop, vehicles, creatures, bases, and Early Access tone.
Subnautica 2 rewards curiosity, but it also punishes bad preparation. Sub2Wiki focuses on practical decisions instead of filler: where to go, what to bring, what to scan, what to craft, what to avoid, and what changed after updates.
Each content page starts with a quick answer, then explains the route, risks, required preparation, and related pages.
The site does not declare a search schema until a real search page exists. This avoids misleading crawlers and users.
Every core guide includes a Last Updated line and Early Access note so players can judge freshness before following advice.
Subnautica 2 is an Early Access survival game, so the smartest way to use any guide is to treat it as a route planner rather than a script. A route planner tells you what to bring, what danger to expect, what to check before you leave, and how to recover if something is different in your save. That matters because a resource point, fragment spawn, or creature path can be adjusted between updates. When you are reading Sub2Wiki, look for the quick answer first, then read the route notes and the build note before you commit to a long dive. If a page says a detail is unverified, do not build an entire expedition around it. Use it as a clue, compare it with your in-game map, and return to safety before you run out of oxygen or storage space.
Solo players should plan for safety and return paths. Co-op players can take more ambitious routes, but they should still organize roles before leaving the base. A simple four-player plan works well: one player scouts, one gathers common materials, one scans fragments and creatures, and one stays responsible for storage, crafting, and route calls. That division prevents the common co-op mistake where everyone swims to the same glowing object, nobody watches oxygen, and the team returns with four copies of the same material but none of the item they actually needed. If you play with friends, use guide pages as shared checklists. Read the quick answer together, agree on the target, and decide who carries what.
Because the game is in Early Access, this page should be reread after major updates. If a route no longer works, the best response is not to assume the guide is useless; it may simply need a version note. Check whether the page has a newer Last Updated line, whether the official patch notes mention changed resources, and whether your current save was created before or after a large update. For a wiki about a living game, freshness is part of accuracy. Sub2Wiki pages are structured so that changed locations, changed recipes, changed platform notes, and changed progression steps can be updated without rewriting the entire guide.
Subnautica 2 is an Early Access survival game, so the smartest way to use any guide is to treat it as a route planner rather than a script. A route planner tells you what to bring, what danger to expect, what to check before you leave, and how to recover if something is different in your save. That matters because a resource point, fragment spawn, or creature path can be adjusted between updates. When you are reading Sub2Wiki, look for the quick answer first, then read the route notes and the build note before you commit to a long dive. If a page says a detail is unverified, do not build an entire expedition around it. Use it as a clue, compare it with your in-game map, and return to safety before you run out of oxygen or storage space.
Solo players should plan for safety and return paths. Co-op players can take more ambitious routes, but they should still organize roles before leaving the base. A simple four-player plan works well: one player scouts, one gathers common materials, one scans fragments and creatures, and one stays responsible for storage, crafting, and route calls. That division prevents the common co-op mistake where everyone swims to the same glowing object, nobody watches oxygen, and the team returns with four copies of the same material but none of the item they actually needed. If you play with friends, use guide pages as shared checklists. Read the quick answer together, agree on the target, and decide who carries what.
Because the game is in Early Access, this page should be reread after major updates. If a route no longer works, the best response is not to assume the guide is useless; it may simply need a version note. Check whether the page has a newer Last Updated line, whether the official patch notes mention changed resources, and whether your current save was created before or after a large update. For a wiki about a living game, freshness is part of accuracy. Sub2Wiki pages are structured so that changed locations, changed recipes, changed platform notes, and changed progression steps can be updated without rewriting the entire guide.
Subnautica 2 is an Early Access survival game, so the smartest way to use any guide is to treat it as a route planner rather than a script. A route planner tells you what to bring, what danger to expect, what to check before you leave, and how to recover if something is different in your save. That matters because a resource point, fragment spawn, or creature path can be adjusted between updates. When you are reading Sub2Wiki, look for the quick answer first, then read the route notes and the build note before you commit to a long dive. If a page says a detail is unverified, do not build an entire expedition around it. Use it as a clue, compare it with your in-game map, and return to safety before you run out of oxygen or storage space.
Solo players should plan for safety and return paths. Co-op players can take more ambitious routes, but they should still organize roles before leaving the base. A simple four-player plan works well: one player scouts, one gathers common materials, one scans fragments and creatures, and one stays responsible for storage, crafting, and route calls. That division prevents the common co-op mistake where everyone swims to the same glowing object, nobody watches oxygen, and the team returns with four copies of the same material but none of the item they actually needed. If you play with friends, use guide pages as shared checklists. Read the quick answer together, agree on the target, and decide who carries what.
Because the game is in Early Access, this page should be reread after major updates. If a route no longer works, the best response is not to assume the guide is useless; it may simply need a version note. Check whether the page has a newer Last Updated line, whether the official patch notes mention changed resources, and whether your current save was created before or after a large update. For a wiki about a living game, freshness is part of accuracy. Sub2Wiki pages are structured so that changed locations, changed recipes, changed platform notes, and changed progression steps can be updated without rewriting the entire guide.