Beta client AreaTable row 16685 names this sub-area within Riverglades. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16723 names this sub-area within Riverglades. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16724 names this sub-area within Riverglades. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16725 names this sub-area within Riverglades. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16726 names this sub-area within Riverglades. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16727 names this sub-area within Riverglades. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16728 names this sub-area within Riverglades. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16729 names this sub-area within Riverglades. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16731 names this sub-area within Riverglades. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16734 names this sub-area within Riverglades. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16735 names this sub-area within Riverglades. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16736 names this sub-area within Riverglades. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16737 names this sub-area within Riverglades. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16743 names this sub-area within Riverglades. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16744 names this sub-area within Riverglades. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16820 names this sub-area within Riverglades. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 17780 names this sub-area within Riverglades. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 17808 names this sub-area within Riverglades. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 17809 names this sub-area within Riverglades. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Blizzard lists Zephras Isle in beta Week 1 and says all zone content up to level 20 is available. This root is beta-active; individual sub-area names below remain client-reported.
Beta client AreaTable row 16622 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16623 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16624 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16625 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16626 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16628 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16629 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16630 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16631 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16635 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16636 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16638 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16663 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16672 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16673 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16674 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16679 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16720 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16833 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16988 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 17221 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 17674 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 17675 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 17676 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 17677 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 17678 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 17684 names this sub-area within Zephras Isle. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 2657 names this sub-area within Shen'dralas. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16675 names this sub-area within Shen'dralas. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16676 names this sub-area within Shen'dralas. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16677 names this sub-area within Shen'dralas. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16678 names this sub-area within Shen'dralas. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Beta client AreaTable row 16742 names this sub-area within Shen'dralas. Its exact point and individual beta access are not confirmed; this is an area result, not a pin.
Blizzard announced Mount Hyjal as a recovering land to explore. No map is shown because the retained beta art records do not establish which candidate map art is player-visible; no location pin is asserted.
This first map subset covers Zephras Isle, Riverglades, Shen'dralas, and Darkspear Islands. The artwork comes from the Forever beta client, build 1.60.1.70058. Named areas come from AreaTable; plotted points require a position record and a matching UiMapAssignment. Mount Hyjal stays in the directory without a map view because the retained extraction leaves its in-game artwork selection unverified.
A client point is a position recorded in the client tables, projected onto its matching map. It is not an independently tested route, an NPC spawn guarantee, or a dungeon entrance. A parent-area result opens the relevant map without placing a pin. A not-mapped result gives the supported location detail without moving the map.
Search matches place names, parent areas, and location details. Zone, place-layer, and availability filters narrow the directory and the visible points together. The separate Map View selector changes the artwork. Zoom enlarges that artwork inside a scrollable frame; Reset All clears every filter, selection, map choice, and zoom.
Beta Access and Planned Places
Blizzard named Zephras Isle in the beta's first-week content. That supports the beta-active label for its zone and parent-area directory; it does not establish every individual marker's behavior. The October 1 update raised the cap to 30 and opened more dungeons. Client records for other places do not, by themselves, establish that players can reach them now.Source: Blizzard beta announcement, What's Available in Beta; October 1 development notes, checked Oct 3, 2026.
Riverglades, Shen'dralas, and Mount Hyjal have announced Forever roles. Blizzard places Riverglades beside Burning Steppes, Redridge Mountains, Swamp of Sorrows, and Badlands, and connects Powderfuse Port to the Steamwheedle route. It places Shen'dralas south of Desolace through the Valley of Bones. These are useful regional descriptions; the tool does not turn them into exact entrances or a drawn ship route.Planned, first-party, in the future tenseSource: Blizzard Found Photos recap, Riverglades and the Roads Between; Mount Hyjal, checked Oct 3, 2026.
Beta-active identifies coverage supported by current beta sources. Planned identifies announced content without verified current access in this subset. Access unresolved identifies a client record whose availability the checked sources do not settle. Artwork and coordinates carry their own evidence separately from those access labels.
Continue With a Leveling Route
Use the zone guide for announced zone context and leveling zones for level bands and route planning. This map does not calculate a safe leveling path or claim complete Azeroth coverage.
For an in-game route addon, start with RestedXP, then review Zygor. The Zygor versus RestedXP comparison explains the choice. These guides retain their own editorial detail; the map helps you find the place before choosing a route.
A named parent area, not an exact coordinate. Availability is labeled separately.
Roll on analytics? Need = Clicky, GA4 & Microsoft Clarity with cookies and session replays, to see which guides help. Pass = no analytics at all.Privacy