Palworld Breeding Chart: Read the Rule, Then Record the Result
Use a breeding chart as a decision record, not as a promise that two names always produce the row you expect. First test whether the exact pair is listed as a special combination. If it is not, use the ordinary breeding-power rule and its tie priority. Then record the actual hatch separately. This keeps a source lookup, a prediction, and an observation from becoming one uncheckable claim.
Checked 23 October 2026. Palpedia describes ordinary breeding as choosing the score nearest the parents’ average unless a pair has a unique combo. OP.GG publishes the midpoint formula and tie-priority rule. PalDB exposes pair, target-child, owned-Pal, and multi-Pal views. This page turns those published inputs into a reusable chart-reading workflow; it does not claim an in-game test, a complete calculator, or a guarantee across every game build.
The chart: one question per column
How to read the ordinary score row
OP.GG states the ordinary rule as: choose the breedable Pal whose breeding power is closest to floor((parent1 + parent2 + 1) / 2); where candidates are tied, the larger tie-priority number wins. That gives a chart reader three inputs to preserve: parent A’s power, parent B’s power, and the version of the table consulted. A copied child name without those inputs cannot be audited later.
| Chart field | What to enter | Why it stays separate |
|---|---|---|
| Exact parent pair | Names, including suffixes such as Cryst, Ignis, or Terra | A similar-looking species is not evidence that the same pair rule applies. |
| Rule branch | “Listed special pair” or “ordinary score lookup” | Special combinations are an exception to averaging, so the branch must be decided first. |
| Score work | Two source scores, midpoint, candidate, and tie priority if needed | This is a prediction trail, not a claimed hatch result. |
| Observation | Hatched Pal, game build, date, and a short note | Keeping it apart makes a disagreement visible instead of overwriting the evidence. |
A small worked chart without inventing a result
Start with the branch, not the arithmetic. Say your target pair appears in a unique-combo source. The chart ends its ordinary-score column there: write “special listing checked” and note the reference date. Do not calculate an average merely to make the chart look complete. The score formula describes ordinary selection; it is not an alternate proof that a listed exception is wrong.
For an ordinary candidate, retain the ingredients. If parent A is recorded as A and parent B as B, the worksheet midpoint is floor((A+B+1)/2). Next to it, write the candidate table’s date and, if two candidates are equally close, the tie-priority value used. This compact record can be rechecked when a data source changes without pretending that a remembered species name is enough.
Use “unverified” as a valid chart result. A source conflict, an unknown game build, or a missing candidate is a reason to stop at an unverified row. It is not a reason to fill the row from an old screenshot or a different parent pair. An honest blank protects the next breeding step better than a confident-looking but mixed-source chart.
Only the last column comes from your save. After hatching, compare the observed Pal with the prediction trail. If it differs, preserve both values and re-check the exact pair, spelling, source date, and build before changing the chart. This makes the sheet useful for troubleshooting and avoids turning one observation into a rule for every player.
Use this chart with the tools you already have
PalDB’s pair view starts from two parents; its parent calculator starts from a desired child; its owned-Pal and multi-Pal options make the available roster explicit. Those are different questions. Label which question you asked before copying any output into a breeding plan. A target-child result does not prove you currently own the required parents, and an owned-Pal result does not by itself show that the final child has been observed.
For special combinations, first read the exact pair listing. For normal planning, record the powers and tie handling. For base setup and cake collection, use the existing Breeding Farm plan. For examples of why a special pair must not be averaged first, see the combos audit.
Download a clean chart for one project
Download the printable breeding-chart card. It is a blank record for one project: source date, parents, rule branch, score inputs, tie note, and hatch observation. Save or print the filled copy as a record; use a fresh card for a new project. It is not a calculator and does not promise to restore form fields after reopening.
Before sharing a chart, write what it is: source lookup, calculated ordinary candidate, or observed hatch. That one label prevents most chart confusion, because the three kinds of information have different evidence behind them. Return to the main breeding guide for the broader setup.