PoE2 build importer

Import PoE2 .build files without guessing the folder.

This guide explains the practical import workflow: create or normalize a `.build` file, place it in the planner folder for your operating system, then open the planner and select the file.

Import checklist

Download a `.build` starter file from the converter.
Check that the file parses as JSON before importing.
Place it under your Path of Exile 2 BuildPlanner folder.
If the folder does not exist, export one build first or create the folder manually.

Common import paths

Windows usually starts from `%USERPROFILE%\Documents\My Games\Path of Exile 2\BuildPlanner`. macOS and Linux paths vary by launcher, Steam compatibility data, and local install choices, so the in-page import helper gives copyable starting points.

Why imports fail

Most failed imports come from malformed JSON, wrong folder placement, unsupported fields, or files copied from a source that was never designed for your planner version. Run the checker before moving the file.

Step-by-step import workflow

Start by keeping the original build source next to the file you want to import. If the source came from a guide, stream, Discord message, or pobb.in link, paste it into BuildFileConverter first and download the starter manifest. The manifest is not a finished game file, but it preserves the source, detected domain, timestamp, and conversion status so you do not lose where the build came from.

Next, create or paste the actual `.build` JSON you want to test. Use the checker to confirm that it parses, inspect top-level keys, and look for warnings about missing game, class, or skill fields. A parseable file is not automatically a valid PoE2 planner file, but invalid JSON is always a bad starting point. Fix obvious syntax issues before you move anything into your game or planner directory.

Finally, copy the file into the BuildPlanner folder for your operating system. If the folder is missing, create one manually or export a build from the planner once so the application creates its own directory. After import, compare the class, skills, notes, and expected source link against the original guide. Treat this as a handoff workflow, not a DPS simulator.

Patch and version compatibility

PoE2 builds can become stale when a patch changes skill behavior, item modifiers, passive tree nodes, or planner schema fields. A file that imported last league may still parse while pointing to outdated assumptions. For that reason, BuildFileConverter separates structure checks from game validation. It can tell you whether the file is readable and self-descriptive; it cannot confirm that every skill, item, or passive still works in the latest patch.

FAQ

Can I import a pobb.in link directly?

Not as a finished file in v1. The tool captures the link as source metadata and marks the output as not import-ready until a real parser can map the source into planner fields.

Should I put starter manifests in the game folder?

Only if your planner expects this custom starter format. For normal use, treat the starter as a record of the source and build notes, then create a real planner-compatible `.build` file from it.