Reopen the planner first
If you added the file while the planner was open, it may not have re-scanned. Close and reopen the in-game Build Planner, or relaunch the game, to force a fresh scan of the folder.
Troubleshooting
You dropped a .build file in the folder but the Build Planner is still empty or greyed out. The good news: the planner only activates once it detects a valid file, so "not showing" almost always points to one of a few fixable causes.
Unofficial fan-made guide. Not affiliated with, endorsed by, or sponsored by Grinding Gear Games.
The Build Planner uses an automated file watcher that scans the BuildPlanner folder. Its features only turn on once it detects at least one valid .build file. So an empty or greyed-out planner means the watcher hasn't accepted your file yet — not that the feature is broken.
If you added the file while the planner was open, it may not have re-scanned. Close and reopen the in-game Build Planner, or relaunch the game, to force a fresh scan of the folder.
If the planner shows the build but it behaves oddly, that's a different problem — usually a patch or format issue.
Why: The watcher re-scans on open.
Do: Close and reopen the in-game Build Planner.
Why: A file one level too high is ignored.
Do: Make sure it's inside BuildPlanner, not Path of Exile 2.
Why: Hidden extensions create .build.txt.
Do: Enable file extensions; confirm it ends in .build.
Why: The watcher rejects invalid files.
Do: Run the validator and fix any errors.
Why: A file without a name can look blank.
Do: Add a top-level "name" string.
Why: Isolates folder vs file problems.
Do: Generate a starter file and see if it shows.
Then the problem is the folder or platform, not your build. Re-check the exact path, and remember the planner only reads files on PC and Steam Deck — not console.
The folder is fine and your file is the issue. Validate it, confirm the extension, and re-export it if it came from before a recent patch.
Use this checklist before assuming the build itself is broken.
Symptom: The build never appears in game.
Quick check: Confirm the file is inside the local BuildPlanner folder.
Fix: Copy the platform path above and move the file there.
Symptom: The file looks correct but is ignored.
Quick check: Look for .json, .txt, or hidden extensions.
Fix: Rename the file so it ends with .build.
Symptom: The file was edited by hand or copied from a comment.
Quick check: Run the validator and look for INVALID_JSON.
Fix: Repair the comma, quote, or brace shown in the error.
Symptom: A minimal file has no obvious build label.
Quick check: Confirm a top-level string name field exists.
Fix: Add "name": "My Build" and validate again.
Symptom: A file worked before a patch but now behaves differently.
Quick check: Re-export from the source build tool if possible.
Fix: Treat this validator as best-effort after PoE2 updates.
Symptom: Steam Deck instructions do not match your install.
Quick check: Confirm your Steam compatdata folder.
Fix: Use the SteamOS path as a starting point, not a universal Linux path.
No. This is an unofficial fan-made helper and is not affiliated with, endorsed by, sponsored by, or approved by Grinding Gear Games.
No. V1 checks pasted or selected files locally in your browser. It does not upload the file content or save generated JSON.
No. The checks are best-effort because the PoE2 Build Planner file format is experimental and can change after patches.
The most common causes are wrong folder, wrong extension, invalid JSON, or a Steam/Proton path mismatch. Start with the validator, then confirm the path.
Re-export the file from the source tool if possible. This helper may need rule updates when the experimental Build Planner format changes.
No. This site focuses on validating, placing, and generating starter .build files, not full passive tree planning.