Named copies documented at launch
| Name | What the list means | Evidence |
|---|---|---|
| Nathan Calloway | A doppelganger version has been documented; verify the current visitor from scratch. | community-tested |
| Julietta Granger | A doppelganger version has been documented; verify the current visitor from scratch. | community-tested |
| Brandon Keller | A doppelganger version has been documented; verify the current visitor from scratch. | community-tested |
| Judith Calhoun | A doppelganger version has been documented; verify the current visitor from scratch. | community-tested |
| Jade Sinclair | A doppelganger version has been documented; verify the current visitor from scratch. | community-tested |
| Tommy Delgado | A doppelganger version has been documented; verify the current visitor from scratch. | community-tested |
| Clyde Dawson | A doppelganger version has been documented; verify the current visitor from scratch. | community-tested |
Creature-form sightings
Documented form
Car Doppelganger
Treat the vehicle encounter as its own verification problem; do not assume a normal counter workflow applies.
Documented form
Elongated Doppelganger
An overtly abnormal silhouette is high-confidence evidence, but exact encounters may move with patches.
Documented form
Forest Doppelganger
Keep the outside route and return path clear before investigating a suspicious forest event.
Why there is no fixed Night 1–13 face list
The official store describes Story Mode as 13 randomly generated shifts. A deterministic list that says a person is always safe would conflict with that design. The useful database records possible copies, observable conflicts and patch context instead.
Last checked against launch-week sources: . patch-sensitive
What to record for each sighting
| Field | Useful detail | Avoid |
|---|---|---|
| Customer identity | Exact displayed name and current shift. | Marking the person permanently unsafe. |
| ID evidence | Barcode, photo, date or printed-detail conflict. | Vague statements such as “looked wrong.” |
| NET evidence | Exact field that disagreed or deceased status. | Relying on memory from a prior run. |
| Question evidence | The question and the conflicting stored answer. | Treating voice delivery as a database fact. |
| Patch context | Date and platform when the sighting was reproduced. | Assuming launch data never changes. |
How to use the names safely
Use the documented names to slow down and perform a full check, not to pre-judge the visitor. The official design randomizes each shift, while the named list comes from launch-week community documentation. That difference is why every row is labeled community-tested rather than verified as a permanent spawn rule.
Quick answers
Frequently asked questions
Is there a fixed human and doppelganger list?
No fixed roster is safe to use across every run. The game randomizes shifts, and a documented copied identity may appear differently later.
Why list names at all?
Names help players recognize documented cases and search the right record, but the current evidence still decides the customer.
Will patches change this list?
They may. The developer has already announced more customers, so the list is explicitly patch-sensitive.
Source register
Evidence used on this page
- Official Shift At Midnight Steam pageOfficial game features, modes, platforms, system requirements and roadmap. Retrieved 2026-08-01.
- AllThings.How doppelganger identification guideSecondary documentation of launch-version checks and named copies; re-check after patches. Retrieved 2026-08-01.