Windows
Most playersUse this when PoE2 runs from a regular Windows documents folder.
Unofficial PoE2 Build Planner helper
Paste a .build file, find the right BuildPlanner folder, and generate a minimal starter file. Everything runs locally in your browser.
This fan-made tool is not affiliated with, endorsed by, or sponsored by Grinding Gear Games.
Checks JSON structure, common missing fields, and import issues.
Your pasted file is checked in your browser. V1 does not upload or store the file content.
Path of Exile 2 reads .build files from a BuildPlanner folder in your local game documents path.
Use this when PoE2 runs from a regular Windows documents folder.
Use this as a starting point for the Proton Windows documents folder.
The compatdata id may vary by install. Confirm your local Steam app folder if this path does not exist.
This creates a minimal starter file, not a complete character build.
Build name is required before downloading.
Starter file ready when the preview has a build name.
Use these focused guides when the game does not detect a file or a patch breaks an existing Build Planner import.
Find the Proton prefix, confirm the Documents/My Games/Path of Exile 2/BuildPlanner folder, and avoid placing the file one folder too high.
Work through extension, JSON, folder, unsupported support gem, charm slot, and patch-specific experimental format issues.
Use a minimal starter file to separate folder detection problems from patch-specific format failures before editing the original build.
Added a file but the planner is empty or greyed out? Work through the file watcher, folder, extension, and JSON checks.
New to .build files? These guides explain the format, where the game looks for the file, and how to share one without breaking it.
New to the in-game Build Planner? The full flow: get a file, validate it, place it, and load it in game.
A plain-language look at the JSON format, the fields it uses, and why it is still experimental.
The exact BuildPlanner folder on Windows, Steam, Epic, and Steam Deck.
Send a build to a friend or post it online without corrupting the JSON in transit.
PoE2 ビルドファイル(.build)の場所と読み込み方法を日本語で解説しています。
Why the in-game Build Planner only reads files on PC and Steam Deck — and what console players can do instead.
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.