Convert shared PoE2 build links into a structured starter file.

Supported source types

• pobb.in links and short build URLs.
• poe.ninja character or build pages.
• Path of Exile profile and build-related URLs.
• PoB-style pasted text and raw `.build` JSON.

What conversion means in v1

External links are captured as source manifests because full game-ready conversion depends on live tool schemas. Valid JSON can be normalized immediately. The result is honest: a safer starter file, not a fake full simulation.

Next step after link capture

Download the starter file, keep the original source URL in the manifest, then use the `.build` checker to confirm that your final file is parseable before importing.

pobb.in, poe.ninja, and PoB-style sources are different

A shared PoE2 build link is not the same thing as a local `.build` file. A pobb.in URL may represent a compressed or hosted build source. A poe.ninja page may be a public character snapshot or ladder view. A PoB-style paste may contain encoded data that needs a dedicated parser before it can become structured class, item, skill, and tree fields. BuildFileConverter detects these source families and records what it sees instead of pretending every link has the same format.

This distinction matters for trust. If a converter silently turns every URL into a file that claims to be import-ready, users may import a broken build and blame the planner. The safer v1 behavior is explicit: the starter manifest says `source-captured`, `importReady: false`, and includes the original URL. That gives you a clean handoff artifact while preserving the evidence needed for future parsing.

What a real conversion would need

A full build link converter needs to decode the source format, map passive tree identifiers, normalize skill gems or support gems, preserve item data, understand ascendancy choices, and write fields that the target planner actually accepts. Those mappings can change with patches and community tool updates. Until that schema is stable, this page is best used as a build source capture and pre-import checklist.

• Capture the original source URL and domain.
• Record the source type and timestamp.
• Warn that the output is not game-import-ready.
• Use the checker for final JSON before import.

How to judge a captured link

A good captured link record should answer four questions: where did the build come from, when was it captured, what source type was detected, and what still needs to happen before import. If any of those answers are missing, the next person who opens the file has to guess. BuildFileConverter writes those details into the starter manifest so the handoff stays understandable even before full parsing exists.

FAQ