Unofficial PoE2 Build Planner helper

Check your PoE2 .build file before the game tries to load it.

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.

Paste your .build file

Checks JSON structure, common missing fields, and import issues.

Local only
No file selected

Your pasted file is checked in your browser. V1 does not upload or store the file content.

Put the file in the right BuildPlanner folder

Path of Exile 2 reads .build files from a BuildPlanner folder in your local game documents path.

Windows

Most players

Use this when PoE2 runs from a regular Windows documents folder.

C:/Users/<Name>/Documents/My Games/Path of Exile 2/BuildPlanner

Steam Deck / SteamOS

Proton

Use this as a starting point for the Proton Windows documents folder.

/home/deck/.local/share/Steam/steamapps/compatdata/2315204395/pfx/drive_c/users/steamuser/Documents/My Games/Path of Exile 2/BuildPlanner

The compatdata id may vary by install. Confirm your local Steam app folder if this path does not exist.

Generate a minimal starter .build file

This creates a minimal starter file, not a complete character build.

Starter file ready when the preview has a build name.

JSON preview

Starter file ready
 

Troubleshoot the two common PoE2 .build failures

Use these focused guides when the game does not detect a file or a patch breaks an existing Build Planner import.

PoE2 build file location on Linux & Steam Deck

Find the Proton prefix, confirm the Documents/My Games/Path of Exile 2/BuildPlanner folder, and avoid placing the file one folder too high.

Check Linux build file location

PoE2 Build Planner not working or broken

Work through extension, JSON, folder, unsupported support gem, charm slot, and patch-specific experimental format issues.

Fix Build Planner not working

PoE2 Build Planner broken after a patch

Use a minimal starter file to separate folder detection problems from patch-specific format failures before editing the original build.

Debug a broken build file

PoE2 Build Planner not showing in game

Added a file but the planner is empty or greyed out? Work through the file watcher, folder, extension, and JSON checks.

Fix it not showing

Learn how PoE2 build files work

New to .build files? These guides explain the format, where the game looks for the file, and how to share one without breaking it.

How to use a PoE2 build file (step by step)

New to the in-game Build Planner? The full flow: get a file, validate it, place it, and load it in game.

Read the how-to guide

What is a PoE2 .build file?

A plain-language look at the JSON format, the fields it uses, and why it is still experimental.

Read the format guide

PoE2 build file location by platform

The exact BuildPlanner folder on Windows, Steam, Epic, and Steam Deck.

Find the folder path

How to share a build file

Send a build to a friend or post it online without corrupting the JSON in transit.

See sharing methods

日本語ガイド

PoE2 ビルドファイル(.build)の場所と読み込み方法を日本語で解説しています。

日本語ガイドを読む

Build files on Xbox & console

Why the in-game Build Planner only reads files on PC and Steam Deck — and what console players can do instead.

Console & Xbox support

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.