Metroid Dread walkthrough: planning a route through ZDR
A metroid dread walkthrough is more useful when you read it like a level designer than like a checklist. Metroid Dread hands you ability-gated regions on the planet ZDR, and the order in which you pick up those abilities shapes which doors open, which bosses you face early, and how much backtracking you accept. IGN’s official Metroid Dread walkthrough presents the game by region and by immediate objective, which mirrors the way most players actually explore once they leave the opening tutorial behind. This guide re-frames that structure for readers who want to understand the underlying routing logic, the resource economy of Energy Tanks, Missiles, and Power Bombs, and the design decisions that make the game feel like a single connected map rather than a string of levels.
The aim is to keep one clear player task in view: complete a first or repeat run, decide whether to chase a 100% collectible sweep, and understand which mechanics the game rewards so you can plan a save file you actually want to keep. Everything below is built around the verified content of the official walkthrough and the design notes that have been discussed publicly by the development team. No hidden exploits, no fabricated sequence tricks, and no details that the source material does not actually support.
Why Metroid Dread rewards route planning over reaction
2D Metroid games from Metroid through Metroid Fusion share a common design contract with the player. The world is one connected map, progression is gated by abilities, and the player’s reward for exploring is the next ability that opens more of the same map. Metroid Dread continues that contract, so the most reliable runs come from players who can read the map as a routing problem rather than a sequence of isolated rooms.
Three design choices drive that reading:
- Abilities double as traversal tools, combat tools, and puzzle tools, so picking up the Varia Suit, Morph Ball, or Grapple Beam always opens more than one type of content.
- Energy Tanks, Missile Tanks, and Power Bomb Tanks are finite, and their total counts are documented in the official walkthrough. That turns resource management into a planning exercise instead of a scramble.
- The save network in the game is dense enough that you can reload a section without losing meaningful progress, which makes careful route planning cheaper than in older entries.
These mechanics mean a walkthrough should be evaluated against the routing it implies, not just the rooms it lists. A route that walks the player linearly through each region in order is rarely the fastest or the most resilient to mistakes.
Region-by-region structure: how the official walkthrough is organised
The IGN walkthrough that anchors this page divides ZDR by region name and by the next immediate objective, usually the next ability or upgrade. That is the same partitioning a level designer uses when planning milestone builds, and it is the most useful structure for a player who wants to keep their own notes.
| Region | Primary ability gates | What the region introduces |
|---|---|---|
| Artaria | None, then Morph Ball and Basic Missile | Movement, basic combat, and the E.M.M.I. threat |
| Cataris | Varia Suit, Diffusion Beam, Morph Ball Bombs | Heat rooms, vertical map, first major ability chain |
| Dairon | Grapple Beam, Space Jump | Long corridors, timing puzzles, and a checkpoint-rich structure |
| Burenia | Gravity Suit | Underwater navigation, fluid combat pacing |
| Ghavoran | Flash Shift, Pulse Radar | Optional expansion, save room density, and collectible density |
| Elun | Spin Boost | Late-game routing, prerequisite setup for the final approach |
| Ferenia | Storm Missile, Aeion abilities | Sequence breaks and faster routing options for repeat runs |
| Hanubia | None new | Final descent and ending branch |
| Itorash | None new | Final boss arena and ending condition triggers |
Two things are worth noticing in that table. First, the early regions teach movement and basic combat, the mid regions gate the most-used abilities, and the late regions consolidate them. Second, the ability that opens the most doors in a region is almost always the one that an experienced player will seek first, even if the walkthrough presents the region in a different order.
Resource targets a 100% run has to track
Resource planning is one of the few areas where a walkthrough can give you a hard, verifiable target. The official source documents the totals that the game tracks, and those totals change the way you explore. They are worth recording at the start of a run, not at the end.
| Resource | Base total | Total with amiibo scans | Planning note |
|---|---|---|---|
| Missile Tanks | 275 | 285 | Distribution favours mid and late regions; running out early is the most common 100% run failure |
| Energy Tanks (E tanks) | 12 | 13 | Front-load exploration if you want survivability for E.M.M.I. chases |
| Power Bomb Tanks | 15 | 15 | Pickup locations are dense; backtracking pays off more than rushing |
The walkthrough’s checklist mode is built around these totals. When you record a pickup, you reduce a number, not a vague sense of progress. That is the simplest way to make sure a 100% run does not silently miss a tank in a region you will not return to.
Reading the ability tree as a routing tool
Each ability in the game has a primary combat role, a primary traversal role, and a secondary puzzle role. That three-way use is what gives the game its routing depth. A walkthrough that only lists the room where you pick up an ability is hiding the part that matters.
- Morph Ball: opens tunnels, blocks, and bomb puzzles. It is the first major traversal ability and the first major time investment.
- Varia Suit: removes heat damage, which means the entire heat-themed region stops being a survival problem and becomes a routing problem.
- Grapple Beam: opens swing points and breaks specific blocks. It also enables the first speedrun-relevant movement tech in the casual route.
- Space Jump: converts vertical rooms into simple climbs. Once you have it, several earlier puzzles become trivial.
- Gravity Suit: unlocks full-speed movement in water, which removes the worst time loss in Burenia.
- Flash Shift and Pulse Radar: give combat and detection options that are useful in both directions, and Pulse Radar in particular changes how you approach E.M.M.I. encounters.
When a walkthrough recommends an order, ask which of those roles it is optimising for. A route that picks up Space Jump early is a route that is optimising for traversal time. A route that picks up Gravity Suit early is a route that is optimising for safety in a specific region. Both are valid; they are simply not the same route.
E.M.M.I. zones: where the walkthrough’s advice gets sharpest
Each E.M.M.I. zone is a contained evasion puzzle with its own terrain. The official walkthrough treats them as section breaks because that is how the game structures the world. A practical walkthrough has to say more than “run from the E.M.M.I.”
| E.M.M.I. zone | Counter ability | Common failure mode | Planning note |
|---|---|---|---|
| Artaria | Basic counter window | Waiting too long and losing the opening to counter | Practice the counter timing before exploring side rooms |
| Cataris | Counter with heat awareness | Heat damage during chase | Carry the Varia Suit before the first full chase |
| Dairon | Counter in long corridors | Trapping yourself against a wall | Map the save room locations before committing to a chase |
| Burenia | Counter under water | Missing counter window during a vertical chase | Use Gravity Suit movement to control vertical spacing |
| Ferenia | Counter with Aeion abilities | Running out of Aeion energy mid-fight | Plan an Aeion restock before the zone, not during |
| Ghavoran | Counter with Flash Shift | Using Flash Shift as a crutch instead of a planning tool | Use Flash Shift to set up a counter, not to delay one |
The counter ability is the same in every zone, but the terrain is not. Walkthroughs that treat E.M.M.I. zones as one repeated task will not help you in the zones where terrain is the actual challenge.
Bosses: what a walkthrough should and should not promise
The game has a defined boss list, and the walkthrough organises encounters by region. A useful walkthrough is honest about what it can and cannot tell you. Boss patterns are deterministic enough to learn, but the specific openings a player has access to depend on the abilities they have already collected. Two players at the same boss with different ability sets do not have the same fight.
For that reason, the boss advice here is structural rather than step-by-step. The same approach that the walkthrough uses for the rest of the game applies here: know the gating ability, know the resource target, and know which ending condition your progress already satisfies.
| Boss category | Player’s planning goal | Common mistake |
|---|---|---|
| Early mini-bosses | Learn the counter timing and basic dodge windows | Healing too early and missing the next opening |
| Ability-locked bosses | Make sure the gating ability is fully upgraded before the attempt | Fighting with the base version of an ability that the upgrade trivialises |
| E.M.M.I. defeats | Treat the counter as a scripted interaction, not a combat check | Trying to damage the E.M.M.I. instead of counter-attacking |
| Late-area bosses | Stack Aeion abilities and reserve healing for second-phase openings | Spending Aeion energy on traversal during the boss attempt |
| Final boss | Plan resource reserves that match the run’s ending target | Ignoring which ending unlockables are tied to completion rate |
Ending conditions are a useful reminder here. The walkthrough documents that completion rate and time affect unlockables, which means the choice of route has consequences after the credits roll. A first run that chases every pickup is not a mistake; it is a different product than a speedrun or a clean minimum-completion run.
Collectible tracking that does not slow you down
Collectible tracking is the part of any walkthrough that gets the most screen time and delivers the least insight on its own. The mechanism is simple: there is a finite list, the list is documented in the source, and the only real question is how to track it without slowing the run. The game itself helps by placing save rooms densely, and the walkthrough helps by giving region totals.
A practical approach for a 100% run:
- Start each region with a quick check of how many Missile Tanks and Energy Tanks the walkthrough lists for that region.
- Mark pickups on a map or checklist at the moment of collection, not at the end of the region.
- Use the save room closest to a major pickup as the boundary between exploration sessions.
- After each save, compare your current totals against the regional totals and decide whether to backtrack before moving on.
- Reserve the last hour of the run for a sweep of the densest collectible regions, where missed tanks cost the most time to recover.
This is a small workflow, but it is the difference between a 100% run that finishes cleanly and one that loses an hour to a missed tank in a region you have already left.
Save rooms and the rhythm of exploration
Save rooms in Metroid Dread are dense enough to be a design feature rather than a convenience. The walkthrough relies on them implicitly, because each section break is essentially a save-to-save journey. If a section takes more than two save rooms, the walkthrough’s framing is starting to break down.
Two habits make that less of a problem:
- Treat each save room as a checkpoint for resource decisions, not just a checkpoint for progress.
- Plan the next two save rooms before you leave the current one, especially in regions where the E.M.M.I. chases can end a run.
For a 100% run, that habit also doubles as a collectible sweep: the saves you have planned are the same saves you can revisit cheaply to backtrack for missed pickups.
Ending conditions: what your route is actually buying you
The official walkthrough notes that completion rate and time affect the unlockables you receive after the credits. That is the game’s way of telling the player that the route itself is part of the save file. A walkthrough is most useful when it makes that visible.
For a first run, the practical targets are:
- Reach the final boss with a full set of upgrades.
- Hit the documented resource totals for Missiles, Energy Tanks, and Power Bombs.
- Visit every region, even briefly, so that the completion counter is at its maximum.
For a repeat run, the same walkthrough changes shape. The collectibles you already know become optional, the speed you can sustain in Dairon and Burenia becomes the variable, and the resource totals become the proxy for completion rate. Both runs use the same walkthrough, but they do not read the same.
Common walkthrough traps and how to avoid them
Walkthroughs that read like checklists make the same handful of mistakes. They are worth listing because the official source is structured to avoid them, and a careful player will spot them in derivative guides.
- Implying a fixed order that is actually a region-locked option. The walkthrough is organised by region and by immediate objective, not by a single linear sequence.
- Hiding sequence breaks that are real. The game has documented routing options that change the order of ability acquisition. A walkthrough that pretends they do not exist is harder, not better.
- Treating E.M.M.I. zones as interchangeable. Each zone is its own puzzle with its own terrain, and the counter ability does not erase the terrain.
- Promising boss tips that depend on upgrades the player may not have. Boss advice is most useful when it is paired with the gating ability the player is expected to have.
- Ignoring the resource totals. Without the totals, a 100% run becomes a feeling instead of a plan.
Recognising these traps is the easiest way to use a walkthrough as a tool rather than a crutch.
Putting the walkthrough into a development mindset
For readers who care about game development as well as play, a walkthrough is a small case study in level design. The game’s region structure, ability gating, and resource economy are the same tools that a 2D Metroidvania project uses in production. Reading the official walkthrough with that lens turns a player guide into a design reference. The region table above is the same kind of document a producer would build for milestone scoping: a list of regions, their gating mechanics, and the new content each region introduces.
That is also the reason a walkthrough benefits from being explicit about its routing choices. A level design document is only useful when it explains why one order is preferred over another. The same is true for a player guide. The official walkthrough’s regional structure, and the resource totals it documents, are the pieces that survive contact with the actual game.
Building a personal walkthrough from the official one
The strongest way to use the official walkthrough is to treat it as a starting point, not a script. That means building a small personal layer on top of the source rather than rewriting it. The minimum useful personal layer has three parts:
- A region checklist for Missile Tanks, Energy Tanks, and Power Bomb Tanks, kept against the totals from the source.
- A note on which ability the player wants to prioritise in each region, chosen from the structural list above.
- A note on which E.M.M.I. zone the player is willing to attempt without preparation, based on the table in the E.M.M.I. section.
That is enough to make any future run cheaper. A 100% run becomes a verification of the same checklist, a speedrun becomes a reduction of the same checklist, and a casual run becomes a subset of the same checklist. The walkthrough stops being a script and starts being a tool.
Validation: how to know your run is on track
A walkthrough is only useful if it gives the player a way to know their run is on track. The official source gives you three independent checks that any player can use:
- You have visited every named region at least once, even if you have not fully explored it.
- Your running pickup totals match the regional targets in the source’s checklist mode.
- You have the documented ability set that the final approach assumes, or you know exactly which ability you are missing and where to find it.
If all three are true, the run is on track. If any one of them is false, the walkthrough is telling you that the run has drifted, and that is the right time to backtrack. That is also the moment a walkthrough earns its keep.
Where a walkthrough ends and a guide begins
The walkthrough is the regional structure and the resource totals. Everything above this point is that document, organised for a reader who is doing the planning. Anything that is more about style, preference, or personal taste belongs in a guide, not in a walkthrough, and it is worth keeping the two separate. A walkthrough that drifts into “what feels right” loses the property that makes it useful: the property that any two players following it will end up in the same place at the same time.
The official source keeps that separation clean, and the best way to use it is to do the same. Keep the walkthrough for the route and the totals. Keep the guide for the choices that the walkthrough deliberately leaves open.
Frequently asked questions
How long does a first run of Metroid Dread take with a walkthrough?
A first run that follows a walkthrough typically finishes in the documented single-digit hours range, depending on how much optional exploration the player takes on. The exact time varies because the game’s region structure lets players choose how much they detour for collectibles. The walkthrough is more useful for route decisions than for time estimates, since time depends on how the player uses the route.
Does the walkthrough change for a 100% collectible run?
Yes. The same walkthrough covers a 100% run, but the player is expected to use the checklist mode, hit the documented totals for Missile Tanks, Energy Tanks, and Power Bomb Tanks, and revisit the densest collectible regions for any missed pickups. A 100% run is the same route with the verification layer active.
Can a walkthrough help with the E.M.M.I. zones specifically?
Yes. The official walkthrough treats each E.M.M.I. zone as its own section because the zones are designed as distinct evasion puzzles. A walkthrough is most useful for the zones when it explains which counter window the player should expect, where the save rooms are, and which Aeion abilities the player should reserve before the chase.
Do amiibo scans change the walkthrough?
They change the totals, not the route. The official source documents that Missile Tanks and Energy Tanks have higher totals when amiibo scans are used, which is a planning note for a 100% run rather than a route change. Players without amiibo access can still follow the same walkthrough with the base totals.
What is the most important ability to prioritise in a first run?
The single most important priority is whichever ability unlocks the next region the player wants to explore. The walkthrough is structured to make that decision explicit by listing the immediate objective at the start of each region. The table of abilities here is a more general version of the same decision.
Is the walkthrough different for a repeat or speedrun run?
The structure is the same, but the order changes. Repeat runs lean on documented sequence breaks, faster routing through Dairon and Burenia, and a willingness to leave collectibles behind. The walkthrough’s regional organisation is robust enough to support both styles without modification.
Where do most players lose time on a 100% run?
Time loss on a 100% run usually comes from missed pickups in the densest collectible regions, where backtracking is expensive. The walkthrough’s checklist mode and the regional totals are designed to prevent that, but only if the player records pickups at the moment of collection rather than at the end of the run.
Does the walkthrough explain ending unlockables?
Yes. The official source documents that completion rate and end-game time affect the unlockables the player receives after the credits, and the walkthrough’s checklist mode is the cleanest way to control those variables. The route itself is part of the save file, and a walkthrough that ignores that is harder to use for a 100% run.
Should a casual player use a walkthrough at all?
It depends on what the casual player wants from the run. A walkthrough is most useful when the player has a concrete goal, like reaching the credits, finishing a 100% run, or learning a specific boss. For freeform exploration, the walkthrough is a reference, not a script, and players can ignore sections that do not match their current goal.
What should I do if my run drifts from the walkthrough?
Stop, save, and check the three validation points listed here. If you have visited every region, your pickup totals match the regional targets, and you have the ability set the next section assumes, the run is still on track. If any of those is false, the walkthrough is telling you to backtrack, and that is the right call.
