The useful Palworld breeding sites already own the obvious search queries. I did not build Palbreed to outrank them.
I built it because I wanted a local-first 1.0 calculator: a pinned pair table, three tools that read the same snapshot, and no live breeding API in the critical path.
The site is Palbreed. Unofficial. Not affiliated with Pocketpair. Palworld and related assets belong to their rights holders.
What "local-first" means here
Palbreed is a Next.js app. After the page loads, the solver reads a bundled snapshot from /data/palworld-1.0.json (cache: "force-cache"). The client refuses to boot the graph unless all three checks pass:
meta.palcalcRelease === "v1.17.6"pals.length === 299breeding.length === 44851
The snapshot is labeled PalCalc database v26 on Palworld 1.0. The loading copy on the site is blunt: the local graph and portraits are prepared in the browser, and no network data source is required for that graph.
That is the product claim I am making. The pair table is not fetched from a wiki, a scrape, or a third-party breeding endpoint at query time. If a later patch moves a recipe, the badges have to move with the file. Until then, the calculator, reverse search, and path solver all read the same pin.
Roster, settings, and saved plans stay in localStorage. There is no account and no application database for that state.
If you want a specific child, parent pair, or route, open the tool. I am not going to paste a combo table into this post. Hand-filled lists go stale the moment the snapshot changes.
Tool 1: two parents, one child
Page: https://palbreeding.org/calculator
The homepage 308s to /calculator. The screen is a direct pair tool:
Choose two parents. Reveal their child.
It uses the verified 1.0 snapshot, including fixed combinations and gender-specific results. "Why this result?" on the child card says the answer is read from the bundled PalCalc 1.0 breeding table, which already applies fixed recipes, gender rules, exclusions, power ranking, and tie-breaking.
I am not listing example pairs here. If you care about a specific outcome, go check the calculator.
Tool 2: start from the child
Page: https://palbreeding.org/reverse
Reverse Search flips the question. Pick a target Pal, then read every direct parent pair in the bundled snapshot.
The page copy is: it shows direct Palworld 1.0 parent pairs from that snapshot. Filters on the live screen include owned pairs first, gender-specific recipes only, and both parents owned.
Again: no handwritten list in this post. The ranking belongs on /reverse, next to the same version badges.
Tool 3: a route from what you already have
Page: https://palbreeding.org/paths
Path Solver is the multigeneration view. It expands only from Pals marked owned in My Pals, and falls back to the smallest direct capture set when needed.
The route graph comes from the bundled 1.0 pair table. Egg counts on that screen are planning estimates, not simulated probabilities. The disclaimer page says the same thing: generation counts come from the graph; egg and time labels are estimates; later patches, mods, or extraction errors can disagree with the snapshot.
Save a route as a plan if you want. Plans stay on the device.
What I refused to ship in this post
A combo dump. A "best Anubis line" list. A promise that Palbreed will rank for Palworld breeding calculator.
Those SERP slots are already held by large databases. This post is a build note and a link to a pinned tool, not a content-site play.
The Data Status screen on the site also records a boundary I kept: 299 PalCalc breeding entities drive the solver. One extra Paldeck-only boss entry is bundled for roster completeness and never enters breeding results.
If a number in this post disagrees with the live badges, trust the badges and the calculator.
Try it
- Calculator: https://palbreeding.org/calculator
- Reverse Search: https://palbreeding.org/reverse
- Path Solver: https://palbreeding.org/paths
Unofficial fan tool. Check the result in-game before you spend Cake.
Top comments (0)