A compact toolkit for PoE2 build files and import workflows.

Tools included

• Build link converter for shared source URLs.
• Browser-side .build checker for parse and structure warnings.
• Importer guide for local file placement.
• Starter template for quick workflow testing.

Who it is for

This hub is for players who are collecting builds from guides, streams, Discord, Reddit, or build planning tools and want a practical way to organize source links and local files.

What it does not do

It does not replace a full planner, simulate DPS, or promise exact passive tree compatibility. It focuses on the file and import layer where small mistakes often break a build handoff.

Recommended tool workflow

If you are collecting builds from YouTube, Discord, Reddit, poe.ninja, pobb.in, or a written guide, begin by saving the original source. Paste the URL or source text into the converter and download the starter manifest. This gives you a record of where the build came from and whether the site treated it as a link, PoB-style code, or raw build note.

After that, use the checker for any actual `.build` JSON you plan to import. A good build handoff should be parseable, self-descriptive, and tied back to a source. The checker cannot verify every passive or item, but it can catch basic file problems before you waste time debugging folder placement.

Finally, use the import path helper. File location is a boring detail, but it is one of the most common reasons an otherwise usable build never appears in a planner.

How this hub should grow

• Source capture today, deeper parsing later.
• More realistic `.build` examples as community schemas stabilize.
• Discord and Reddit summary output for easier build sharing.
• Patch compatibility notes so old builds are not mistaken for current recommendations.

The goal is not to become a full simulator. The goal is to make the build file handoff less fragile.

Why small build tools still matter

Large planners are excellent once you are already inside the build. Smaller utilities help before and after that moment: saving a link, checking a file, copying a folder path, or explaining why an import is not ready. Those steps are easy to ignore, but they are exactly where shared community builds often break. A clear handoff tool can reduce confusion even without calculating damage or simulating encounters.

For SEO and real users, this page is the index for that workflow. It points each intent to the right page instead of forcing every visitor through one overloaded converter screen.

FAQ