PoE2 build planner
PoE2 build planner importer for shared build sources.
BuildFileConverter helps you turn shared Path of Exile 2 build sources into a cleaner planner workflow: capture the source, generate a `.build` starter file, check the structure, and follow OS-specific import paths.
What this planner importer does
The tool is built for players who receive a pobb.in link, poe.ninja build URL, PoB-style code, or raw `.build` JSON and need a practical next step. It does not pretend to simulate every skill or calculate DPS. It focuses on source capture, file hygiene, and import readiness.
- Detects common PoE2 build source types.
- Creates a `.build` starter manifest for external links.
- Normalizes valid JSON build files in the browser.
- Shows Windows, macOS, and Linux import path starting points.
When to use it
Use this page when you want a lightweight bridge between build sharing and a local planner. It is especially useful for testing import folder setup, preserving source metadata, and turning messy notes into a consistent starter file.
What the planner importer can validate today
BuildFileConverter can validate file-level basics: whether pasted content is valid JSON, whether it has a top-level object, which major keys appear, whether the extension looks unusual, and whether a generated source manifest is clearly marked as not import-ready. These checks are intentionally boring, but they catch the kinds of problems that break a build handoff before the planner even gets a chance to read it.
It cannot validate the full game meaning of a build yet. It does not know whether a passive tree node still exists, whether a skill was changed in the latest patch, or whether an item roll is legal. Those checks require game data and planner-specific schemas. The current importer gives you a safer staging workflow while those deeper integrations are still evolving.
Planner-ready versus source-captured
A planner-ready file should contain real structured build fields that your target planner understands. A source-captured file is different: it records where the build came from, what type of source was detected, and what still needs to happen before import. The site now labels these states separately so you do not mistake a saved source for a finished build.
Practical planner notes
When you are testing a new build workflow, use one small file first instead of importing a large build copied from a guide. Confirm that your planner can see the folder, that the file name is easy to recognize, and that the build notes still point back to the original source. After that, move on to richer data. This slower workflow saves time because it separates folder problems, JSON syntax problems, and real build compatibility problems.
If you share the result with another player, include the source URL and the current status. A note like “source captured, not import-ready” is much clearer than sending a file that looks official but still needs manual reconstruction.
FAQ
Does this create a finished PoE2 planner build?
Only when the input is already valid build JSON that can be normalized. External links are captured as starter manifests and marked not import-ready.
Why use it before a real planner?
It gives you a quick way to preserve sources, check file syntax, and confirm import paths before spending time inside a heavier planner.