About the data

Palworld ships its game data as Unreal Engine DataTables inside a single packed archive. We run a Palworld dedicated server install, unpack that archive, and export all 914 DataTables to JSON — including DT_PalMonsterParameter, which holds every Pal’s stats, work suitabilities, ride speeds and breed rank.

That extraction runs automatically. When Pocketpair ships a patch, the server files update, the tables are re-exported, and the changes flow through to these pages — so the site tracks the game rather than someone’s memory of it.

Localised names come from the same place: the game carries its own translations in 16 languages, so the Japanese, Chinese and Korean names shown on each Pal page are Pocketpair’s, not a machine translation of ours.

If the game does not state a number, this site does not print one. Where a field is missing it is left out and the page says so, rather than filling the gap with a plausible-looking estimate. Partner skills are absent for exactly this reason: linking them up correctly needs a table join we have not finished, and a blank field would read as “this Pal has no partner skill”, which is false.

Before any data refresh is published it has to clear a validation gate that compares entry counts and core stats against the previous version. A stale extraction that silently produced 40 Pals instead of 286 would fail that check rather than quietly go live.

Elemental damage multipliers are the single thing here that is not datamined. Palworld resolves elemental damage in compiled code rather than a data table, so there is nothing in the files to extract. The type chart uses the community-documented matchups, cross-checked across independent sources and verified internally consistent. Every page that relies on it carries that caveat.