PoE2 In-Game Build Planner Guide
How to use the native Build Planner added in patch 0.5 - import .build files, overlay your passive tree, gems, and gear hints directly in the client without alt-tabbing.
Most players follow builds by alt-tabbing between PoE2 and external sites, PoB spreadsheets, or videos mid-session. The native Build Planner (added in patch 0.5 / Return of the Ancients) lets you overlay the passive tree, skill gems, gear slots, and level-progression notes directly inside the game client - no third-party tools needed at runtime.
Step-by-Step Setup
Look for builds on Reddit or X that explicitly mention in-game Build Planner support or provide a downloadable .build file. Popular creators and web planners export these directly.
If you want to create your own, use a community web planner to map your passive tree, gems, and gear - then export the .build file.
After any major patch, passive tree and gem changes can break old .build files. Always grab fresh ones for the current patch version.
Drop the .build file into the BuildPlanner folder for your platform. Create the folder if it doesn't exist.
Restart the game client after placing the file. It will not appear otherwise.
Console players face filesystem access limitations. PC or Steam Deck is the straightforward path for this feature.
Open your Passive Skill Tree screen. In the top-left corner you'll see a small blue Build Planner icon. Click it, then select your build from the dropdown list.
The overlay now highlights:
- Recommended passive nodes with level-range brackets
- Ascendancy choices in order
- Skill gems and supports (with notes per slot)
- Gear slot hints at each progression stage
Allocate passive points as highlighted. Swap gems and supports when the planner shows level-appropriate ones. Read the notes on notables and gear slots - many builds rely on them to explain why a specific support gem matters at a given stage.
For multi-stage builds (e.g. Act 1-3 vs. endgame), check for level-range tags on each node group. These auto-switch recommendations as you progress.
If a build has no level-range tags, create separate .build files per stage and swap them in the dropdown as you hit each milestone.
Use any community PoE2 web planner to allocate your tree, gems, and gear. Add notes and level-range tags, then export the .build file and follow Steps 2-4 above.
If you use Path of Building, check recent Reddit threads for PoB-to-.build converters - the format is JSON and community tools exist to bridge both planners.
Key Decision Points
Import ready .build files from trusted creators for proven meta power. Build your own via a web planner if you're experimenting or want a save-and-compare workflow.
Prefer builds with level-tagged gem and gear entries for smooth auto-switching. Otherwise maintain one .build per campaign stage and swap via the dropdown at milestones.
If your current build lives in Path of Building, look for community converters on Reddit. The .build format is JSON - converters exist to translate PoB exports into planner-compatible files.
PC is the most reliable path. Steam Deck works via the Proton path above. Console file access is currently limited - most players workaround with a second device for reference.
Common Mistakes
.build files. Post-patch passive tree and gem changes silently break them. Always grab a fresh export for the current patch.