Ben Drowned is an internet horror legend that spread through creepypasta and video game rumor forums. This verified explainer summarizes what the story actually says, how it originated, and what is known about any in-game events or real-world references. It does not treat unverified speculation as fact and distinguishes between fictional storytelling, fan fiction, and the behavior of the underlying game code.
What Ben Drowned refers to and how the story spread
Ben Drowned is a creepypasta character that emerged around 2010 on imageboards and forums, claiming to be a haunted Majora’s Mask save file. The story describes a player encountering a corrupted version of the child character Link, named Ben, whose town and friends were supposedly destroyed. The story gained traction through forum posts, YouTube videos, and livestreams that framed odd game behavior as evidence of a haunted cartridge. It is important to note that these accounts are user-generated narratives and not part of the official game script or developer statements.
Origin and documented references
There is no canonical event in The Legend of Zelda: Majora’s Mask that describes a character named Ben dying or being deleted from the game. The tale likely originated from edited save files, altered NPC names, and glitch encounters that players shared online. No official source—such as developer interviews, patch notes, or product documentation—mentions a character named Ben or a death event matching the creepypasta. This classification indicates the story is modern folklore rather than a part of the official narrative or design.
Key elements of the Ben Drowned creepypasta
- A supposedly haunted Majora’s Mask cartridge
- A renamed NPC called Ben with a tragic backstory
- Glitches, distorted audio, and corrupted text presented as in-game proof
- Alleged consequences such as missing data or crashes
Official sources and developer position
Nintendo and the original development team have not commented on the Ben Drowned story as an in-game event. The series’ official strategy documents, credits, and support channels do not reference haunted cartridges or NPC deaths of this nature. Independent analyses, disassembly discussions, and emulator tests show that NPC naming and quest triggers are modifiable but do not support the supernatural elements claimed by the story. The absence of corroboration from primary sources is a strong indicator that the narrative is fictional.
Comparison of claims versus verified details
| Claim | Verified Detail | Source Type |
|---|---|---|
| Ben Drowned is a canon character who died in Majora’s Mask | No character named Ben exists in the game’s script; no death event matches the story | Game script analysis, developer statements |
| A haunted cartridge can corrupt other saves | Save corruption can happen due to hardware or software errors, not due to a narrative curse | Technical documentation, emulator tests |
| Glitches prove the story is real | Glitches are common in older hardware and do not confirm supernatural elements | Hardware analysis, player reports |
Evaluating evidence and critical approach
When assessing stories like Ben Drowned, prioritize primary sources such as developer interviews, official patch notes, and hardware documentation. User testimonials and edited footage are not reliable evidence of in-game events. Checksum verification, cartridge inspections, and emulator logs can clarify whether reported behaviors are technical rather than narrative. Applying these methods helps separate fan creativity from factual game history and prevents misattribution of ordinary glitches to fictional causes.
Status and legacy of the story
Ben Drowned remains a well-known example of early internet creepypasta that influenced later urban legends and indie games inspired by haunted media stories. Its persistence reflects how compelling storytelling interacts with gaming culture, but it should not be read as historical fact about The Legend of Zelda. The story’s cultural impact is documented in fan works and retrospectives, while its canonical status is consistently absent from authoritative sources.