Deepwell Codes and Locations

Find all four Deepwell access codes in HUSH: They can hear. with a clean search plan, co-op roles, and a no-guess tracking sheet.

If you are stuck at the Deepwell access point in HUSH: They can hear., the missing HUSH: They can hear. deepwell code is probably the only thing between you and a clean run. This HUSH: They can hear. deepwell code guide focuses on a repeatable search method, not random guesses. It explains what the four-code hunt involves, how to organize a clean sweep, and what to do when the digits are not obvious.

What the HUSH: They can hear. deepwell code Hunt Requires

The HUSH: They can hear. deepwell code hunt is built around four access codes, not one master password. The useful question is not just “what is the code?” It is “which of the four Deepwell locations have we confirmed, and where is the missing one?” That shift matters because a partial list creates false confidence. You can know three strings and still be locked out if the fourth has not been read.

The exact four code strings are not printed in this guide because an unconfirmed code is worse than no code: it sends a team into a false loop. Confirm each string at its Deepwell location and keep a written record. Treat the puzzle like a four-item checklist, not a memory test.

Tracker slot	What to record	Why it matters	Status to use
Code 1	Exact string from the location	Prevents a full route repeat	Confirmed / recheck
Code 2	Where the string was found	Helps a teammate return if needed	Located / unread
Code 3	Who holds the screenshot	Avoids duplicate searches	Verified / pending
Code 4	Last known readback	Confirms all four before entry	Ready / missing

A code is only “done” when every player who needs it can see the same string. Use one recorder instead of letting three people write three versions. Small differences in a code string can turn a clean solution into a wasted run.

Write the digits as one continuous string; do not reformat them from memory.
Screenshot the code before leaving the location.
Read the string back once before the group moves on.
Mark the slot as confirmed only after the readback matches the screenshot.

Where to Focus During a Deepwell Code Search

The hunt spans four Deepwell access-code locations, so treat it as a route problem rather than one central terminal. Do not clear the same wing twice because someone forgot to mark it. Move in a loop, confirm the code, then leave the area before the next alert.

A clean sweep has a beginning, a confirmation point, and an exit. If your group splits without a shared order, you will collect fragments but lose the location tied to each one. The tracker matters as much as the digits because it tells you where to return when one slot is still missing.

Search phase	Main action	What to record	Stop condition
Start	Agree on a first location and a recorder	Starting point and team order	Everyone knows the first stop
Perimeter pass	Check outer rooms before deep rooms	Location name and access status	Outer route is marked
Interior pass	Move room by room, not by memory	Exact code string and screenshot owner	All visible slots are logged
Confirmation	Read back each string with the group	Confirmed or recheck status	No conflicting versions remain
Exit	Leave together and name the next target	Missing slot and next location	The group has one clear objective

Do not rush the confirmation phase. A group that reads the code aloud once, checks the screenshot, and then moves on will save more time than a group that sprints between locations and argues at the entrance. If a location is unclear, mark it “recheck” rather than guessing. A recheck is useful information; a guessed digit is noise.

HUSH: They can hear. deepwell code and Sound Discipline

Sound is the pressure system in this game. The title is literal: they can hear. A HUSH: They can hear. deepwell code run fails when the group treats the puzzle like a race and forgets that every loud action adds attention. Before you read the code objective, stop sprinting, let the last noise fade, and confirm that the area is calm enough to record the string.

You do not need to turn the run into a silent movie, but you do need a noise plan. Use short callouts, keep the recorder’s voice clear, and save jokes for after the run. If a threat reacts, move away and reset instead of talking over the problem. The goal is not zero sound; it is controlled sound.

Noise risk	Better habit	Why it helps
Sprinting into a code room	Walk the final approach	Keeps the readback calm
Fighting beside a code location	Disengage before reading	Fewer interruptions
Re-entering immediately after an alert	Pause, reset, then return	Avoids compounding noise
Several people talking during readback	One recorder speaks	Cleaner confirmation

The best code hunters are not always the fastest players. They are the ones who know when to stop, crouch, wait, and listen. That discipline protects the whole group’s work.

How to Organize a Group Code Run

Four codes do not require four separate solo searches. If you play with friends, assign jobs so nobody duplicates work. The group needs a navigator, a recorder, a lookout, and a reader. These are not game classes; they are simple roles that keep the team from stepping on each other.

Role	Main job	Information to pass	Avoid
Navigator	Choose the next Deepwell location	Missing slot and route order	Leading from memory
Recorder	Hold the screenshot and readback	Exact string and owner name	Editing digits while reading
Lookout	Warn about attention and pacing	Threat direction and quiet window	Chasing every sound
Reader	Read the code slowly	Clear digits, one at a time	Rushing the final line

Use a fixed callout order: location, code, status. “Location two, code confirmed, screenshot with Recorder” is more useful than “I think I got it.” If someone separates from the group, they should return to the last confirmed point instead of searching alone. A missing teammate is a bigger delay than a missing code.

Say “confirmed” only after the screenshot and readback match.
Keep one shared tracker; do not let each player keep a private list.
Name the next location before anyone moves.
If the group disagrees, stop and recheck instead of voting on a digit.

HUSH: They can hear. deepwell code Mistakes That Waste Runs

Most failed code runs are bookkeeping failures, not puzzle failures. A HUSH: They can hear. deepwell code hunt breaks when the team trusts a random comment, mixes partial lists, or reads the code while a threat is active. The entrance is not the place to discover that two players have different versions of the same string.

Before you enter the code, do a ten-second audit. Count the confirmed slots. Check that every screenshot is visible to the recorder. Read each string once without commentary. If anything feels off, return to the unconfirmed location instead of spamming guesses.

Mistake	Symptom	Fix
Trusting an unverified code	The string fails and the group loops	Confirm it at the Deepwell location
Mixing partial lists	Three slots look right, one is missing	Use one shared tracker
Reading during an alert	The code is cut off or misheard	Clear the area first
No screenshot	Two players remember different digits	Screenshot before leaving
Searching the same rooms	Time lost with no new code	Mark each location’s status

A wrong code does not mean the puzzle is broken. It usually means the group skipped a confirmation step. Slow down at the readback, protect the screenshot, and keep the tracker honest. That routine is boring, but boring is how you get out with all four codes.

FAQ

What is the HUSH: They can hear. deepwell code?

The HUSH: They can hear. deepwell code is not one master password. It refers to the four-part access-code hunt tied to the Deepwell. The exact strings must be confirmed at their locations; guessed digits are not a reliable substitute.

Where are the Deepwell codes found?

They are tied to four Deepwell access-code locations. Clear each location, record the string, and confirm all four before entry. A partial list can send the group back through rooms they already cleared.

How many Deepwell access codes are there?

There are four. Track them as separate slots so you can see which one is still missing. The number is small, but the locations and the readback details are easy to lose without a written record.

How should a team track the codes?

Use one recorder, one screenshot per code, and a shared status for each slot. Mark a code “confirmed” only after the group reads it back and matches it to the screenshot. If there is any disagreement, mark it “recheck” and return to the location instead of guessing.