Fast triage order
- Confirm the file ends in .build.
- Validate the JSON before moving it again.
- Confirm the platform folder path.
- Reopen the in-game Build Planner after moving the file.
Troubleshooting
PoE2 Build Planner not working?
Start with the common fixes: check the folder, confirm the file ends in .build, then validate the JSON.
Fast triage order
Do not skip the local checks
Most failures are local file issues, not a broken build. The validator does not upload your file and only checks it in your browser.
When a patch changed the experimental format
The Build Planner file format is still experimental, so a file that worked before a game update can fail after a patch.
Unsupported support gem
If a build stopped loading after a patch, check whether it references an unsupported support gem, renamed gem, or a gem that no longer matches the current skill setup. Re-exporting from the source planner is usually safer than hand-editing unknown fields.
Charm slot or item slot mismatch
A charm slot, weapon set, or inventory slot value can become stale when the source planner and the game disagree. If the JSON is valid but the game ignores the build, compare the generated slots with a fresh minimal export.
Use a minimal test file
Generate a minimal test file and put it in the same folder. If the minimal file appears, the folder is correct and the original build likely contains a field-level compatibility issue.
Keep the fix conservative
Do not delete large sections at random. First validate JSON, then test the file path, then compare against a fresh export after the patch changed the experimental format.
Common reasons PoE2 does not detect a build file
Use this checklist before assuming the build itself is broken.
Wrong folder
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.
Wrong extension
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.
Invalid JSON
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.
Missing name
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.
Experimental format
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.
Linux path mismatch
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.
FAQ
Is this an official Path of Exile 2 tool?
No. This is an unofficial fan-made helper and is not affiliated with, endorsed by, sponsored by, or approved by Grinding Gear Games.
Does this upload or store my file?
No. V1 checks pasted or selected files locally in your browser. It does not upload the file content or save generated JSON.
Can this guarantee the game will detect my build?
No. The checks are best-effort because the PoE2 Build Planner file format is experimental and can change after patches.
Why does my file still not show in game?
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.
What if the format changed after a patch?
Re-export the file from the source tool if possible. This helper may need rule updates when the experimental Build Planner format changes.
Can I make a complete character build here?
No. This site focuses on validating, placing, and generating starter .build files, not full passive tree planning.