pobb.in to .build file
Capture a pobb.in build link before turning it into a PoE2 .build file.
If you searched for a pobb.in to `.build` file converter, the important detail is that a hosted build link and a finished local planner file are not the same object. BuildFileConverter v1 captures the pobb.in source, creates a starter manifest, and helps you check the final `.build` JSON before import.
What happens when you paste a pobb.in link
The converter detects the pobb.in domain, records the original URL, marks the result as `source-captured`, and generates a `.build` starter manifest with `importReady: false`. That status is intentional. It tells you the source has been saved, but the file has not yet been decoded into real class, skill, item, passive, and planner fields.
This is useful when you are collecting builds from guides, Discord, Reddit, YouTube descriptions, or ladder discussions. Instead of losing the source link in a chat thread, you get a structured record that can travel with your notes and later be expanded into a real build file when parsing support is available.
Why v1 does not claim full conversion
A full pobb.in conversion needs a maintained decoder for the hosted source format and a target schema for the planner you want to import into. It must preserve build-critical data such as class, ascendancy, skill setup, support gems, passive tree choices, items, notes, and patch assumptions. If a tool guesses these fields, the output may look importable while silently changing the build.
BuildFileConverter avoids that trap. It gives you source capture, a conversion status badge, a starter manifest, and a checker for final JSON. When the input is already valid `.build` JSON, it can normalize the file immediately. When the input is an external pobb.in URL, it clearly labels the result as not game-import-ready.
Recommended workflow
- Paste the pobb.in URL into the source capture tool.
- Download the starter manifest and keep it with your build notes.
- Use the original pobb.in page to recreate or export real build fields in your target planner.
- Paste the final `.build` JSON into the checker before moving it into the BuildPlanner folder.
- Keep a patch or league note if the build depends on current balance.
What a finished .build file may need
A finished PoE2 planner file may include game version, build format, class, ascendancy, main skills, support setup, item data, passive allocations, configuration notes, and tool-specific metadata. Different planners may use different field names. That is why the checker focuses on parseability and obvious structure rather than pretending there is one universal official schema.
FAQ
Can I convert pobb.in to a real import-ready .build file today?
Not fully in v1. You can capture the pobb.in source and create a starter manifest. A true import-ready conversion needs source decoding and target planner schema support.
Why is the output called a starter manifest?
Because it stores source metadata and next steps. It is a starting point for a build handoff, not a guarantee that the game or planner can import it directly.
What should I do after source capture?
Use the original build source to create real planner fields, then run the final JSON through the `.build` checker and follow the import path guide.