Palworld 1.0 New Pal Breeding Combinations

How to use the new Pal combinations browser

The table above starts with breeding rows whose offspring belongs to the 72-record Palworld 1.0 addition set. Search any parent name, offspring name, internal name, or Paldeck number to narrow the rows. Use the filter to show all additions, only base Pals, or only variant forms. The counter reports the full number of matching combinations and renders the first 100 so the page remains responsive.

When you find a practical pair, choose “Open in calculator.” The link transfers both parents and any gender requirement into the main breeding tool. Confirm the displayed offspring there, then use Swap parents or the gender badges if you need the layout to match your in-game farm. Keeping the exact forms and genders with the link prevents a visually similar record from replacing the one you intended.

If you start with a target, search its full name first. If you start with a Pal you own, search that parent and compare the available 1.0 offspring. Add a second term only when the result set is still too broad. The browser searches every matching row in the current PalCalc dataset rather than showing only a hand-picked list.

What the 72-record filter actually means

Pocketpair’s official 1.0 changelog says the release adds 72 Pals in total: 47 new Pals and 25 variant Pals. Separately, the community-maintained PalCalc data grew from 227 searchable Pal records and forms in its last pre-1.0 release to 299 searchable Pal records and forms in its current 1.0-compatible release. The difference is also 72 records, and the filter below uses that reproducible data comparison.

The filter compares PalCalc v1.16.5, the last pre-1.0 baseline used here, with the 1.0-compatible v1.17.6 release. It includes the exact Pal and form records added between those versions. That gives the list a repeatable definition instead of relying on names remembered from trailers or screenshots.

Pocketpair confirms the official total of 47 new Pals and 25 variants. PalCalc supplies the community breeding rows. The matching total is a useful cross-check, but Pocketpair does not provide or certify the pair-by-pair combinations shown here.

A record count also differs from a count of broad species families. PalCalc keeps forms separate when they have separate breeding behavior. That is why the filter offers base and variant views and why a familiar Paldeck number can appear on more than one named form.

Find a target among thousands of rows

Many new offspring can be produced by a large number of ordinary pairs, so a complete table may contain far more rows than you expect. Begin with the target’s exact name. If several forms share part of that name, switch the filter to Base Pals or Variants. Paldeck numbers are useful when spelling varies, but the name and form label are still necessary to distinguish records that share a number.

Once the target is isolated, do not assume the first pair is the best pair. The table is ordered for browsing, not for your Palbox, base capacity, or passive-skill plan. Scan for parents you already own, parents that are easy to reproduce, and pairs whose gender requirements you can meet. A combination that saves one capture or preserves a good breeding parent may be more valuable than the first alphabetical row.

If no row appears, clear the form filter and shorten the query. The search includes both parents and the child, so a very specific phrase can exclude a valid row when the displayed form name differs from the term you used. Also check whether the Pal is breedable in the current community data. The page only lists actual rows from the pinned dataset; it does not invent a route for every 1.0 roster addition.

For a general target outside the 72 additions, use all breeding combinations or switch the home calculator to Find parent pairs. The filter narrows the child side of the table so you do not have to sift through every older offspring first.

Choose a parent pair you can actually use

A mathematically valid pair is only the beginning. Check whether both parents are available, whether one is needed elsewhere, whether their forms match the row, and whether the required genders exist in your Palbox. If several rows remain, prefer the one that reduces the largest practical cost. That might be capturing a rare parent, rebuilding passives, or waiting for another correct-gender offspring.

Think one generation ahead. A convenient pair that produces the target can be useful even when the first child is not final quality. You can keep a correct species or form as the next breeding parent, then improve passives or stats in a later generation. Conversely, a pair with excellent traits may be worth extra setup if it preserves progress you already made.

Use the main calculator link to verify one row before assigning the farm. It shows the child clearly and preserves the selection in the URL. Share that URL with another player or keep it beside your breeding notes. A static copied name pair can lose form and gender details; a complete result link is easier to audit.

After confirming the pair, choose a Cake based on the quality goal rather than the novelty of the offspring. Vegetable Cake supports egg volume, Deluxe Vegetable Cake supports Mutation, Mushroom Cake favors higher-stat likelihood, and Special Cake favors multiple passive inheritance. The Cake guide explains those choices without attaching unsupported percentages.

Forms, Paldeck numbers, and repeated names

Variant forms are first-class records in the community data when their breeding behavior needs to be represented separately. The browser marks them through the child name and the Variants filter. Do not remove the form suffix when copying a result. Two records can share a Paldeck number or family name while pointing to different breeding outcomes.

The Paldeck number is a confirmation aid, not a complete identity by itself. Read the displayed name, form label, and number together. If a guide says only “use #041,” compare its publication date and screenshot with the exact current record before spending Cake. The 1.0 addition of many variants makes shorthand more error-prone than it was in a smaller roster.

Base and variant filters apply to the offspring, not to both parents. A Base Pals view can still include a variant parent when that parent is part of a valid row. Search the parent name if you want to include or exclude a particular parent form. This keeps the filter honest about its job: identifying what kind of new child the row produces.

When an in-game result disagrees, check the form before assuming that the whole pair is outdated. A missing suffix, a similarly translated name, or a parent selected from the wrong card can all point the calculator at a different record. Report a reproducible mismatch through Contact with both exact parent names, genders, expected child, displayed child, and the result URL.

Gender-specific and special combinations

Most breeding rows work with either gender on either named parent as long as the farm contains one male and one female. Some special combinations are directional: the same two names can produce different children when their genders are reversed. The table displays “Any gender,” “Male,” or “Female” beside each parent so the requirement remains part of the row.

Katress and Wixen demonstrate why this matters in the current data. Katress female with Wixen male produces Katress Ignis, while Katress male with Wixen female produces Wixen Noct. A list that stores only the two names loses the rule that separates those results. The Open in calculator action includes gender parameters for precisely this reason.

Parent order on the screen is mostly a presentation choice, but gender is not. Use Swap parents if you want Parent 1 and Parent 2 to resemble your farm placement; verify that the badges still match the intended male and female. For a special row, copy the full setup rather than relying on memory.

Do not infer that an unmarked row has a hidden special rule. The page renders the gender value in the current PalCalc data. At the same time, remember that this is community-maintained data and can be corrected. If a row behaves differently in Palworld 1.0, preserve the exact evidence so the source can be checked rather than replacing one unsupported assertion with another.

Why an older breeding guide may disagree

The official changelog says breeding combinations were reviewed overall and adjusted to match game progression, but Pocketpair does not publish a complete changed-pair table. That makes version context essential. A pre-1.0 chart may be accurate for its game build and still be wrong for a current farm. It may also omit new forms simply because those records did not exist yet.

Check the guide’s date, named data version, exact forms, and gender handling. A page updated after July 10, 2026 is not automatically current if it copied an older table without a data refresh. Conversely, a disagreement does not prove that the community file is perfect. Reproduce the row in game and keep enough detail to identify which source needs correction.

Here, “new in 1.0” always means the difference from the fixed pre-1.0 PalCalc baseline. Later game additions should not be mixed into this set simply because the dataset receives another update.

If you only need a summary of confirmed features rather than a table, read Palworld 1.0 Breeding Changes. It covers the official roster count, Mutation, new Cakes, and the difference between Pocketpair’s roster number and community breeding-record counts.

How to verify a result

Open the row in the main calculator and confirm that both exact parent forms, genders, and the child match the table. Then compare that setup with your current game build before spending a rare Cake. Every row shown comes from the fixed 72-record 1.0 addition set and the PalCalc v1.17.6 data v26 dataset.

The table does not rank parents by capture difficulty, passive quality, ingredients, or incubation time. It also cannot promise that a later Palworld patch will preserve every pair. Treat it as a complete searchable starting point, then choose the row that best matches your Palbox.

A reliable 1.0 combination workflow

1. Search the exact new offspring name and select Base Pals or Variants if needed.
2. Compare several rows for parents already available in your Palbox.
3. Read both form names, Paldeck numbers, and gender labels.
4. Open the chosen row in the main calculator and confirm the child.
5. Save or share the result URL so the complete setup stays together.
6. Choose a Cake based on egg volume, stats, Mutation, or passive inheritance.
7. Recheck any guide written before the July 2026 release.
8. Report a reproducible mismatch with the data version and result URL.

Following the same sequence for every project makes a large table manageable. It moves from broad search to one auditable setup, then separates species selection from offspring-quality decisions. That is the fastest way to benefit from thousands of rows without letting forms, genders, and version changes turn into avoidable mistakes.