A practical checklist for validating Palworld 1.0 breeding data

When a breeding result stops matching an older guide, the fastest fix is usually not trying more random parent pairs. First verify which game version and dataset the calculator is using.

What I check

1. Supported game version. A calculator should say whether it targets Palworld 1.0 or an earlier dataset.
2. Pinned source data. Look for a source release, commit, dataset date, or checksum instead of a vague “updated” badge.
3. Both lookup directions. Parents → Child helps when you already own two Pals. Target → Parents is better when you know the offspring you want.
4. Special rules. Fixed pairs, same-species results, and gender-direction exceptions should not be flattened into one average-rank formula.
5. Explicit limits. Species outcomes are different from passive inheritance, IV inheritance, mutation, cake timing, or shortest-route planning.

A small tool built around that workflow

I built PalBreed as a free, no-sign-in Palworld 1.0 breeding calculator. It supports both lookup directions and currently indexes 44,851 parent relationships.

The more useful part for debugging is its data status page: it publishes the supported game version, dataset date, upstream release and commit, SHA-256 checksums, regression cases, and known limits.

For players who want to inspect the whole relationship index rather than run one calculation, there is also a searchable breeding combinations list.

PalBreed is an independent community tool and is not affiliated with Pocketpair. It currently calculates species outcomes only; it does not simulate passives, IVs, mutation, cake timing, shortest paths, or personal inventory.