Video walkthrough
Watch the route, then match the frames
Video chapters
5 stepsVideo references
Watch or inspect the route before you dive
Click YouTube cards to load the player. Open frame cards to compare local screenshot notes. Use the evidence to confirm landmarks, movement, and encounter pacing, then follow the written checklist below.
Vehicle upgrade route context
Watch for: MK1 and MK2 module evidence, installation checks, and safe first-depth testing.
Module route frame review
Watch for: Start with Tadpole depth module guide at 00:20. Compare the screenshot cue, route note, and player action before following the guide in-game.
MK2 plan frame review
Watch for: Start with Tadpole depth module guide at 02:28. Compare the screenshot cue, route note, and player action before following the guide in-game.
Video watch notes
What to pause, compare, and write down
Do not watch the video like entertainment only. Use these notes as a second-screen checklist: pause on landmarks, confirm the player action, then return to the written route.
Watchlist
Watch the route to the module source before the menu appears.
Pause on MK1 or MK2 confirmation and connect it to the depth band it opens.
Look for whether the creator tests the module on a known route before diving deeper.

Module route
The route frame tells players whether they are ready to chase the module at all.
Action: Bring only the tools needed for the module route and leave side pickups alone.

MK1 check
The MK1 frame proves the upgrade state and should change only the next planned route.
Action: Install, test near a known area, then update the route plan.

MK2 plan
The MK2 frame belongs to deeper progression and needs stronger support.
Action: Check storage, power, threat response, and exit plan before using the new limit.
Video route timeline
Turn the video into playable checkpoints
Use this section like a second-screen route sheet. Open each checkpoint, compare the frame, do the action, then stop if your route no longer matches the video evidence. It keeps the guide useful even when Early Access shifts small placements or creature behavior.
00:20Checkpoint 1: Check whether depth is the real blocker before chasing optional modules.The route frame tells players whether they are ready to chase the module at all.Expand

Module route
Depth module runs should begin only after depth is the real route blocker.
Player action
Check whether depth is the real blocker before chasing optional modules.
Proof before moving on
The route frame tells players whether they are ready to chase the module at all.
Watch this timestampIf this fails
Delay the module and solve storage, scanning, or base workflow first.
01:14Checkpoint 2: Follow the fragment route and scan only confirmed module targets.The MK1 frame proves the upgrade state and should change only the next planned route.Expand

MK1 check
Use the module menu as proof that the vehicle can safely attempt the next band.
Player action
Follow the fragment route and scan only confirmed module targets.
Proof before moving on
The MK1 frame proves the upgrade state and should change only the next planned route.
Watch this timestampIf this fails
Run a short known route before opening a new deep objective.
02:28Checkpoint 3: Open the upgrade menu and confirm whether MK1 or MK2 is unlocked.The MK2 frame belongs to deeper progression and needs stronger support.Expand

MK2 plan
MK2 planning should include power, storage, and a known test route before deep exploration.
Player action
Open the upgrade menu and confirm whether MK1 or MK2 is unlocked.
Proof before moving on
The MK2 frame belongs to deeper progression and needs stronger support.
Watch this timestampIf this fails
Treat depth access as permission to scout, not permission to loot everything.
00:20Checkpoint 4: Install the module and return to a familiar route for a first test.The route frame tells players whether they are ready to chase the module at all.Expand

Module route
Depth module runs should begin only after depth is the real route blocker.
Player action
Install the module and return to a familiar route for a first test.
Proof before moving on
The route frame tells players whether they are ready to chase the module at all.
Watch this timestampIf this fails
Delay the module and solve storage, scanning, or base workflow first.
01:14Checkpoint 5: Push into the new depth band only after the vehicle and exit plan feel stable.The MK1 frame proves the upgrade state and should change only the next planned route.Expand

MK1 check
Use the module menu as proof that the vehicle can safely attempt the next band.
Player action
Push into the new depth band only after the vehicle and exit plan feel stable.
Proof before moving on
The MK1 frame proves the upgrade state and should change only the next planned route.
Watch this timestampIf this fails
Run a short known route before opening a new deep objective.
Gameplay evidence
Screenshots to match before you keep swimming
Use these frames as visual checkpoints. If the terrain, lighting, or landmark does not match, slow down and re-check the route instead of forcing the next step.

Module route
Depth module runs should begin only after depth is the real route blocker.

MK1 check
Use the module menu as proof that the vehicle can safely attempt the next band.

MK2 plan
MK2 planning should include power, storage, and a known test route before deep exploration.
Route decision lab
Decide if this route is worth running now
This section turns the video into a practical in-game decision. Use it before leaving base, after the first landmark, and again before entering a deeper or darker area.
Route purpose
Prioritize Tadpole Depth Modules when the next objective sits below your current safe band. Find the module fragments, confirm MK1 or MK2 in the upgrade menu, install it, then test on a known route before diving deeper.
Visual checkpoint
Depth module runs should begin only after depth is the real route blocker.
Map anchor
Tadpole Depth Module Chain in Depth module fragment route. Use it for use this when depth is the blocker, not when a flashy optional module would merely be nice.
Abort rule
Treating depth modules as optional comfort upgrades when objectives are gated.
Field manual translation
Depth modules should be evaluated as route gates. The useful evidence is the module route, the MK1 or MK2 confirmation, and a safe test before deeper exploration. This keeps the guide from encouraging players to dive straight into a new threat band after installing an upgrade.
Primary job
Open the next depth band - Depth is critical when the next objective is physically below the current safe limit.
Best entry habit
Module proof first - Use the upgrade menu to prove the module state before changing route plans.
Stop condition
No test route - Do not use a new depth limit on an unknown route until the module is tested safely.
Patch-safe reading
Exact item positions can shift during Early Access. The useful part of this page is the route logic: what to prepare, what visual cue to confirm, what objective to finish, and when to turn back.
Updated
2026-06-12 / tracking / Early Access
What this guide covers
Requirements
- Tadpole unlocked
- Module route
- Known test route
Use this if
You want a route you can follow from video evidence without needing exact official coordinates. The screenshots and steps are written to help you recognize areas, landmarks, and decisions while playing.
Early Access can move details. Treat this as a video-based walkthrough and verify landmarks in your own build.
Step-by-step walkthrough
Follow the video route without guessing
Check whether depth is the real blocker before chasing optional modules.
Use this step as a route checkpoint, not as a promise that every object spawns in one exact coordinate. Match the landmark, compare the screenshot, then continue only if the return path is still clear.
If your game build looks different, stay with the same decision: keep oxygen safe, scan or collect the current blocker, and return before pushing into the next unknown area.

Depth module runs should begin only after depth is the real route blocker.
Follow the fragment route and scan only confirmed module targets.
Use this step as a route checkpoint, not as a promise that every object spawns in one exact coordinate. Match the landmark, compare the screenshot, then continue only if the return path is still clear.
If your game build looks different, stay with the same decision: keep oxygen safe, scan or collect the current blocker, and return before pushing into the next unknown area.

Use the module menu as proof that the vehicle can safely attempt the next band.
Open the upgrade menu and confirm whether MK1 or MK2 is unlocked.
Use this step as a route checkpoint, not as a promise that every object spawns in one exact coordinate. Match the landmark, compare the screenshot, then continue only if the return path is still clear.
If your game build looks different, stay with the same decision: keep oxygen safe, scan or collect the current blocker, and return before pushing into the next unknown area.

MK2 planning should include power, storage, and a known test route before deep exploration.
Install the module and return to a familiar route for a first test.
Use this step as a route checkpoint, not as a promise that every object spawns in one exact coordinate. Match the landmark, compare the screenshot, then continue only if the return path is still clear.
If your game build looks different, stay with the same decision: keep oxygen safe, scan or collect the current blocker, and return before pushing into the next unknown area.

Depth module runs should begin only after depth is the real route blocker.
Push into the new depth band only after the vehicle and exit plan feel stable.
Use this step as a route checkpoint, not as a promise that every object spawns in one exact coordinate. Match the landmark, compare the screenshot, then continue only if the return path is still clear.
If your game build looks different, stay with the same decision: keep oxygen safe, scan or collect the current blocker, and return before pushing into the next unknown area.

Use the module menu as proof that the vehicle can safely attempt the next band.
After-action plan
What to do after the guide works
Bank the result
Push into the new depth band only after the vehicle and exit plan feel stable.
Clean the inventory
Move route-critical materials into labeled storage so the next dive starts with empty space and a clear job.
Pick the next guide
A Tadpole upgrade checklist for depth modules, route expansion, module priorities, and safer vehicle planning.
Next route queue
Use these as the next blockers to solve after this route. Each queue card keeps the same evidence style: source video, gameplay frames, and a written checklist.
Best immediate follow-upTadpole Upgrades Guide
A Tadpole upgrade checklist for depth modules, route expansion, module priorities, and safer vehicle planning.
Use if the route branchesTadpole Fragments Location Guide
A route-first Tadpole fragments guide for finding, scanning, and turning the vehicle unlock into safer deeper exploration.
Save for the next diveTadpole Submersible Guide
How to use the Tadpole as a route-planning anchor for biome pushes, co-op hauling, vehicle safety, and threat retreats.
Detailed notes
Depth modules are route gates
A depth module is valuable because it changes where the Tadpole can safely operate. The guide should connect each module to the objective band it opens.
How to use this in-game
Turn this note into one action before leaving base: decide the objective, keep only the materials or tools that support it, then stop the route once the scan, pickup, or landmark is confirmed. This keeps the guide useful even when Early Access patches move small details.
Safe test rule
After installing MK1 or MK2, test the new limit on a known route before using it for a dangerous objective. This separates upgrade confidence from exploration risk.
Install
Known route
Depth check
Return
How to use this in-game
Turn this note into one action before leaving base: decide the objective, keep only the materials or tools that support it, then stop the route once the scan, pickup, or landmark is confirmed. This keeps the guide useful even when Early Access patches move small details.
When to delay MK2
Delay the next depth module if the deeper route still lacks power, storage, or threat response. Depth access without route support can make the next trip worse, not better.
How to use this in-game
Turn this note into one action before leaving base: decide the objective, keep only the materials or tools that support it, then stop the route once the scan, pickup, or landmark is confirmed. This keeps the guide useful even when Early Access patches move small details.
Video route notes
Tadpole Depth Module Guide should be followed as a resource route, not as a memory test. Start by watching the first route movement and naming the entry condition before copying the path in-game. Check whether depth is the real blocker before chasing optional modules. Then pause again when the video reaches the first visible proof point, because that is where the guide changes from general advice into an action you can repeat. Follow the fragment route and scan only confirmed module targets. If the route starts to feel different in your build, keep the same player goal: repeat the route without relying on a perfect coordinate.
Entry check: Tadpole unlocked
Route action: Check whether depth is the real blocker before chasing optional modules.
Proof to look for: material or fragment proof
Version note: Early Access / tracking
How to use this in-game
Turn this note into one action before leaving base: decide the objective, keep only the materials or tools that support it, then stop the route once the scan, pickup, or landmark is confirmed. This keeps the guide useful even when Early Access patches move small details.
Screenshot checkpoints
Use screenshots as checkpoints instead of decoration. The first image should answer where the route begins, the second should show what confirms progress, and the third should explain what to do after the scan, pickup, puzzle state, or threat read is visible. Open the upgrade menu and confirm whether MK1 or MK2 is unlocked. This is especially important in Early Access because exact positions can drift while landmarks, depth bands, room states, and player decisions stay useful. A good screenshot lets you say, "I am at the right kind of place," before you risk oxygen, storage space, or vehicle safety.
Entry frame: match the landmark before moving deeper
Proof frame: confirm material or fragment proof
Exit frame: know the return direction before adding side goals
Loadout frame: check Module route
How to use this in-game
Turn this note into one action before leaving base: decide the objective, keep only the materials or tools that support it, then stop the route once the scan, pickup, or landmark is confirmed. This keeps the guide useful even when Early Access patches move small details.
Stop rule and next dive
The most useful part of this page is the stop rule. Treating depth modules as optional comfort upgrades when objectives are gated. Testing a new module in an unknown threat band. When the objective is confirmed, return and convert it into progress: craft the upgrade, sort the material, save the route note, or mark the blocker as solved. If the route fails, do not repeat the same swim blindly. Change one variable at a time: enter from a clearer landmark, reduce inventory clutter, bring the missing tool, or wait until oxygen and vehicle support match the route. That turns a failed resource route into better field knowledge instead of another full-inventory wander.
How to use this in-game
Turn this note into one action before leaving base: decide the objective, keep only the materials or tools that support it, then stop the route once the scan, pickup, or landmark is confirmed. This keeps the guide useful even when Early Access patches move small details.
Common mistakes
Treating depth modules as optional comfort upgrades when objectives are gated.
Testing a new module in an unknown threat band.
Forgetting storage, power, and return route after reaching a deeper zone.
FAQ
Is this guide for the current Subnautica 2 build?
This page is written for Early Access and includes a visible update date. Treat exact values as tracking notes until the current build is field-tested.
Does this page use official screenshots?
Pages combine attributed official Steam / Unknown Worlds media, local gameplay frame captures, and source-video evidence cards. New player-submitted captures should keep the route, timestamp, and build context attached.
Community notes
Add a field report
Player reports enter a moderation queue. Approved notes can load from Supabase; pending drafts stay visible in this browser for follow-up.
Near starter shallows
Approx. 70-120m from pod
Confirm oxygen before leaving the first landmark. The route is much safer when you mark the return path before collecting side materials.
Guide-wide
N/A
Creature patrol ranges and fragment placement can shift between builds, so treat exact distances as field estimates until multiple players confirm them.