Independent archive How stories are researched and sourced

1986 · Famicom · Game story

Metroid (1986): A Labyrinth Built from What Was Left

Samus begins with a short beam and a very large problem. The original Metroid makes every upgrade feel like a new way to read the same hostile planet.

Official overview image for メトロイド
Official overview image for メトロイド Image source: Nintendo official game page ↗
In this story
  1. 01 A small gun, a large planet
  2. 02 “Why should I avoid them?”
  3. 03 The map is mostly in your head
  4. 04 When color does the navigating
  5. 05 A finish assembled under pressure
  6. 06 Samus is the reward—and the surprise
  7. 07 Even the name keeps changing shape
  8. 08 Go back with a better question

A small gun, a large planet

Metroid sends Samus Aran into Zebes with a Short Beam, a suit of armor and a truly unreasonable amount of planet to inspect. Nintendo’s original description gives the mission a clean shape: Space Pirates have taken the lifeforms called Metroids, fortified their base on Zebes, and Samus must reach and destroy Mother Brain. The actual experience is messier in the best way. The route begins as a handful of corridors that look less like an invitation than a technical fault in a very angry spaceship. 2 3

The Japanese Disk System version arrived on August 6, 1986. Nintendo’s Famicom page describes Zebes as a natural fortress with a complicated interior and traps, while the manual says upgrades hidden throughout it grant abilities and open places that had previously been inaccessible. That is the useful contract: the planet is not withholding progress arbitrarily; it is waiting for Samus to become the person who can read the next obstacle. 2 3 8

This is why the opening feels so good even when it feels unfriendly. You are not given a sightseeing tour of Zebes. You are given evidence: a high ledge, a small passage, a colored door, a room that looks impossible. Each piece quietly asks whether it is decoration, danger or unfinished business. Metroid turns the answer into a reason to keep moving rather than a paragraph of explanation. 3 4

Samus begins with little certainty and a great deal of Zebes, which is exactly the point of the first expedition. Image source: Nintendo · Metroid — Nintendo Classics ↗

See it in action

Watch メトロイド Loads a privacy-enhanced YouTube embed only after you choose to play.
Video referenced by Nintendo’s game page. Video source: Nintendo official game page ↗

“Why should I avoid them?”

Trivia Nintendo’s later interview gives Metroid one of the better origin stories in the Famicom library. Hiroji Kiyotake and another new designer began it despite having no television-game development experience; Gunpei Yokoi’s working belief, according to Yoshio Sakamoto, was that someone who could draw could make games. Kiyotake had made Game & Watch titles, not a full screen-spanning adventure. The assignment was less a polished production plan than a leap into deep water. 5

Trivia Kiyotake remembers watching Super Mario Bros. become huge and wanting to make something it did not have. His first example is wonderfully fussy: Mario slides a little before stopping, so Metroid should stop dead. Sakamoto then supplies the missing punchline. Mario asks players to avoid enemies; Kiyotake apparently complained, “Why do we have to avoid them?” The answer became the Screw Attack, a spinning jump that lets Samus destroy enemies by going through them. 5 3

That complaint is more revealing than a grand manifesto. Metroid’s movement is not merely transport between shooting galleries. Once the player earns the right upgrades, motion itself becomes an attack, a key and a form of confidence. A tricky gap can become a route; a clustered enemy can become something to cut through; a low tunnel can become an argument for folding into the Morph Ball. The game gives verbs to a body before it gives a map to a place. 3 2

Metroid’s upgrades do more than increase damage: they make movement itself feel newly argumentative. Image source: Nintendo · Metroid — Nintendo Classics ↗

The map is mostly in your head

There is no comforting in-game atlas for the player to consult in the original. Nintendo’s manual instead gives tangible rules: blue gates yield to a beam, red gates take five missiles, and some require ten. It lists the equipment that changes Samus’s possibilities—Morph Ball, bombs, High Jump, Varia, Ice Beam, Wave Beam, Energy Tanks and more. The Famicom page describes ten upgrade types and says a starting Short Beam can grow into an arsenal. 3 2

The first time a high ledge blocks you, it may be annoying. The second time, after finding High Jump, it becomes a joke Zebes was telling earlier. Metroid is full of those delayed punchlines. A small opening stops being background once Morph Ball exists; a suspicious wall becomes an experiment once bombs arrive. Progress feels less like receiving a permission slip than revising an opinion about a room you thought you understood. 3 4

A pencil map is not retro theatre; it is a very sensible second controller. Mark closed gates, strange shafts and the rooms where an item looked tantalizingly out of reach. The goal is not to draw Zebes perfectly. It is to leave yourself a breadcrumb that says, “I did not forget this; I merely lack the correct version of Samus.” The manual gives the vocabulary. Your paper gives it a past tense. 3 4

Nintendo’s own later summary calls the original mix of action and exploration the series trademark. That phrase is accurate but slightly tidy. The remarkable part is the tension between the two. Combat gives each room immediate pressure; exploration lets that pressure become unfinished knowledge. You flee an enemy today, discover a missile expansion tomorrow, then return remembering exactly why that corridor had felt rude. 9 8

A gate, a ledge or a narrow passage is not merely a barrier; it is a note for the better-equipped Samus who will return later. Image source: Nintendo · Metroid — Nintendo Classics ↗

When color does the navigating

Trivia The development interview is candid about how unfinished Metroid was when the wider R&D1 group joined near the end. Sakamoto says the early version had the same backgrounds everywhere and the same actions everywhere: a moving character, a dark mood, but hardly a game design. One of the late fixes was to change background colors so players could tell that they had progressed. It is a small visual adjustment carrying a surprising amount of orientation. 5

That explains a great deal about the finished planet. Zebes is not a model of architectural realism, and it does not need to be. Color, enemy pressure, door rules and the player’s own memory do the job that a modern map overlay might do. The world has a slightly dreamlike quality because it is built from repeated pieces, but the repetition becomes useful once you learn what differences actually matter. 5 3

Trivia Kiyotake says he originally animated Samus with many fine movements, only to find that the animation consumed too much memory once backgrounds and sound also needed room. Those movements were drastically reduced. It is tempting to imagine a lost, smoother Metroid in the abstract. The more interesting truth is the one the developers give us: the Samus players know is partly the silhouette that survived a crowded disk. 5

The result is austere in a way that helps. Samus is not asking to be admired from every angle; she is asking to get over that ledge before something bites her. The rooms do not need many flourishes when their job is to make a new power-up feel like an act of interpretation. Metroid’s restraint can be severe, but it also makes each newly possible movement land with unusual force. 3 2

A finish assembled under pressure

Kiyotake estimates that the two new designers worked for less than ten months before the finishing push. Sakamoto says he joined only in roughly the last three months, followed by the rest of R&D1. They did not have time to invent large new systems; they used what was already available and worked out how to make it fun. That is not romantic speculation about hardship. It is the participants’ own, fairly blunt account of the schedule. 5

Trivia The sound arrived late enough to feel momentous. Kiyotake recalls that when he and one colleague were alone on the project, they could make only simple “pew, pew” noises. Proper audio made the partly formed aesthetic feel real. It is a modest anecdote, but it catches the texture of early game production better than a myth of instant mastery: a strange planet becomes convincing one layer at a time, often after somebody discovers there is still room for a sound effect. 5

The Disk System made that scale of persistence practical in Japan. Nintendo’s history notes the peripheral’s larger-capacity disks, built-in saving and Disk Writer stations; the Classic Mini interview likewise describes saving as part of the hardware proposition. Metroid’s repeated expeditions make more sense in that setting. A maze with hidden improvements does not have to be conquered in one heroic sitting if the machine is allowed to remember your progress. 6 5

None of this means players should romanticize every rough edge. A password screen in the NES version can be inconvenient, and getting lost can become tiring. But the constraints gave Metroid a useful friction. It asks you to take the planet seriously enough to remember it. The answer to a blocked route is rarely a message from the game; more often it is a changed tool, a changed eye, or a note you made before switching the power off. 3 6

Samus is the reward—and the surprise

Trivia Hiroji Kiyotake named Samus Aran after a football misunderstanding. He tells Nintendo that he was a Pelé fan and believed the player’s name was something like “Samus Arantes Nascimentos.” The interviewer gently corrects him: Pelé’s name is Edson Arantes do Nascimento. Kiyotake laughs, admits he was off, and notes that “Arantes” at least survived. The hero of Zebes carries a name born from an almost-right bit of sports trivia. 5

Trivia The helmet reveal was also a late reward decision, not a carefully advertised premise. The developers were discussing different endings based on completion time and wanted players to replay faster. Someone suggested that it would surprise people if the armored character turned out to be a woman; they decided quickly, then prepared four ending variations with different degrees of armor removed. Nintendo’s later Dread report confirms that completion time changes the end screen. 5 8

The design works because it does not need to carry the entire game. Samus is already compelling as a moving set of possibilities: beam, ball, bomb, jump, missile, survival. The reveal adds a final bit of misdirection to a game full of it, but it does not replace the pleasure of tracing a route through Zebes. The player earns a different ending because they learned the world well enough to make speed feel possible. 5 3

Samus’s armor makes a promise the player gradually learns to fulfill: every new ability changes the shape of a return trip. Image source: Nintendo · Metroid — Nintendo Classics ↗

Even the name keeps changing shape

Trivia A later Nintendo Dread report offers a delightful bit of lore housekeeping. It warns that someone encountering the floating creature might assume Samus is named Metroid, then says the word means “ultimate warrior” in the Chozo language. Another Nintendo Dread report gives a different historical explanation: Metroid was formed from “metro,” in the sense of an underground transit system, and “android.” Rather than forcing the two statements into one tidy answer, it is more honest to notice the franchise adding language and story around an older name. 7 8

Both explanations point back toward the same thing the 1986 game makes tangible: a machine-like explorer moving through an underground network. Nintendo’s current series materials describe the original as establishing the universe and tone, while the old Famicom page names the hostile floating organisms and the fortress that exploits them. A name can gather new meanings over decades without changing the immediate thrill of finding one more way through a wall. 8 2

That changing shape suits Metroid. The game is always making an earlier screen mean something different later. At first a passage is too small. Later it is a route. At first a creature is just a thing to avoid. Later it is something a Screw Attack turns into momentum. The series has accumulated lore; the original’s lasting pleasure is more immediate: it keeps teaching you that the place you were in was not finished looking at you. 3 7

Go back with a better question

Play Metroid with a notebook and a little patience for the places that initially make no sense. Mark obstacles rather than hunting for a perfect route. When an upgrade arrives, ask what it changes about your oldest notes. The best returns to Zebes feel like arguments with your earlier self: you were right that the wall mattered, wrong about why, and now just equipped enough to settle the matter. 3 4

Nintendo continues to list Metroid in its Japanese Nintendo Classics catalog, with official images and a referenced video on the game page. Access conditions can change, so the first-party listing—not a frozen article—is the appropriate place to verify current availability. 1

Metroid is not interesting because it proves that every constraint was secretly a masterstroke. Its makers describe false starts, discarded movement, limited memory and an anxious last stretch. It is interesting because the finished game makes those limits playable. Zebes feels hostile, then readable, then almost familiar—until the next small tunnel or locked gate proves you have only been visiting one version of it. That is a very good reason to go back. 5 3 2

Sources & image credits

Facts were checked against the links below. Official media remains the property of Nintendo and the relevant rights holders.

  1. Metroid — Nintendo Classics Nintendo ↗
  2. Metroid — Famicom official game page Nintendo ↗
  3. Metroid — NES Classic Edition electronic manual Nintendo ↗
  4. Metroid — instruction booklet Nintendo of America ↗
  5. Nintendo Classic Mini: NES special interview — Metroid Nintendo of Europe ↗
  6. Famicom history — 1986 and the Disk System Nintendo ↗
  7. Metroid Dread Report Vol. 3: Seven points that define the 2D saga Nintendo ↗
  8. Metroid Dread Report Vol. 4: Unraveling a saga 35 years in the making Nintendo ↗
  9. Metroid — NES game page Nintendo of Europe ↗
How Classic Explorer checks facts and credits media →

Continue reading

Related reading

Explore the full database →
Design history · Where to start Seven Nintendo Consoles, Seven Different Ideas of Play From the Famicom living room to Virtual Boy’s red depths, seven Nintendo systems changed where games lived, how they moved, and how players met. Series history · Maps, abilities and atmosphere Metroid Across Four Nintendo Generations: How Exploration Learned to Speak From the Famicom’s suspicious walls to Fusion’s urgent station, Metroid kept changing how a player reads a room, remembers a route and earns a way forward.
1986 株式会社バンダイナムコエンターテインメント

バベルの塔

Originally released in 1986 for Famicom, with 株式会社バンダイナムコエンターテインメント credited on Nintendo’s listing. This entry organizes verified release facts, official imagery, and direct primary-source links in one place.

Open catalog record
1986 株式会社バンダイナムコエンターテインメント

マッピーランド

Originally released in 1986 for Famicom, with 株式会社バンダイナムコエンターテインメント credited on Nintendo’s listing. This entry organizes verified release facts, official imagery, and direct primary-source links in one place.

Open catalog record

Official image · Source: Nintendo ↗