Pal SaveEditor
Runs locallyOpen a save

Evidence-based compatibility

Palworld 1.0 save compatibility by platform, format, and task.

Palworld 1.0 save compatibility cannot be reduced to a single supported badge. A tool may recognize PlM, decode an outer container, parse part of GVAS, and still fail to rebuild current RawData or load the export in game. Pal Save Editor reports recognition, reading, writing, round-trip, and game-load confirmation as separate stages so a read-only answer never appears as safe editing support.

Scan local files Try the safe sample
PlZRecognizeZlib-era container; safe writes still require RawData round-trip proof
PlMRecognize + blockOodle container; no permissive proven browser write path
CNKRecognizeGame Pass outer container; migration requires identity mapping

Quick answer

Palworld 1.0 save compatibility: what to know first

  • Post-1.0 issue reports show failures in specific RawData paths, proving some parsers need updates without establishing that every 1.0 save is affected.
  • PlZ identifies a zlib container; it does not prove that the inner 1.0 world can be edited safely.
  • PlM uses Oodle and remains read-only here because licensing and broad current-version round trips are unresolved.
  • Compatibility must name the platform, file type, task, parser version, validation result, and actual game-load evidence.

Local safety workbench

Run the same safety workflow on your local files.

Scan locally and export a receipt. Editing, diff, and validation are limited to the sample and Pal Save Editor JSON fixtures; every real binary input stays read-only.

0 B of save data uploadedLocal hashing and ZIP inspectionBlocked export on failed validation
What needs to happen?
Find my save
Files never leave this tab Original input stays immutable Real binary writing is locked in this release

Local return loop

Save Chronicle

Receipt metadata lives only in this browser. Raw saves are never stored.

Your next local scan will appear here.

ReadyLocal workbench loaded.
01

Read the Palworld 1.0 save compatibility matrix correctly

Recognition finds a file role and outer format signal. Reading turns the required bytes into a structured model. Writing rebuilds the file. An unchanged round-trip proves the parser can decode and re-encode its model. A changed round-trip verifies selected edits. Actual game loading confirms the current Palworld build accepts the result.

Each stage can fail independently. For example, a PlM marker is easy to recognize, but decoding needs Oodle. Post-1.0 reports also show failures in specific Palworld RawData paths. That evidence means affected parsers need updates; it does not define a complete 1.0 schema change list or prove every 1.0 save is affected.

Pal Save Editor compatibility as of July 27, 2026
Format or inputRecognizeStructured readBinary write
Pal Save Editor JSON fixtureYesYesYes, fixture safe pack
PlZ Steam / server saveYesHeader evidence onlyLocked pending RawData proof
PlM Steam / server saveYesRead-only diagnosisLocked: Oodle and round-trip gate
CNK Game Pass containerYesFile-set diagnosisLocked: conversion and identity gate
Unknown or truncated saveFingerprint onlyNoBlocked
02

Why PlM and Oodle change browser support

Palworld moved many saves from PlZ/zlib to PlM/Oodle starting around version 0.6. Browser tools distribute a WebAssembly decoder to visitors, so each component's license and provenance become part of the product. GPL implementations can be used commercially only while meeting their source and copyleft obligations; other code or binaries have unclear or education-only terms.

That licensing problem is separate from correctness. Decompression only exposes GVAS and Palworld RawData. The writer still needs bounded parsing, full input consumption, stable serialization, and current-game testing. Pal Save Editor therefore recognizes PlM and explains the block instead of presenting a guessed export button.

Palworld 1.0 save compatibility diagnosis showing PlM Oodle compression recognized and binary editing blocked
PlM recognition is useful evidence, but it is not equivalent to a safe Palworld 1.0 write path.
03

What Palworld 1.0 changed for save tools

Current GitHub reports show `EOF not reached` failures inside specific Palworld RawData paths after 1.0, including work assignment structures. This proves outer-format support alone is insufficient and that some parsers need updates. It does not establish a complete schema change list or prove every 1.0 save is affected.

A draft Palworld integration for the MIT `uesave` project reports unchanged round-trip testing across 261 real saves. The pull request is still a draft, its current WebAssembly wrapper is not a finished Palworld browser product, and enabling its optional Oodle dependency changes the resulting binary to GPL. Those caveats matter as much as the reported test count.

04

How Palworld save compatibility should be tested

Compatibility testing needs representative real saves for each platform, outer format, file role, world size, multiplayer shape, and task. The test record should include game version, parser commit, fixture hash, expected objects, unchanged round-trip result, changed reparse result, non-target comparison, and actual load confirmation.

Failures should remain visible in the changelog. Hiding unsupported versions encourages users to replace files based on a green badge that no longer matches the current game.

  1. 01

    Identify the exact input

    Record platform, file role, PlZ, PlM, CNK or GVAS, declared size, and game version.

  2. 02

    Consume the full structure

    Reject trailing bytes, unknown required fields, excessive allocation, and broken references.

  3. 03

    Prove unchanged round-trip

    Rebuild an untouched model and compare decompressed bytes or a documented semantic equivalent.

  4. 04

    Prove scoped edits

    Reparse the changed export and verify only approved paths or regions changed.

  5. 05

    Confirm in the current game

    Load the export and verify affected and unaffected players, Pals, bases, guilds, and options.

SAFE

Task checklist

  1. 01Check outer format and inner GVAS separately.
  2. 02Require current-version fixtures for edit claims.
  3. 03Treat decode-only support as read-only.
  4. 04Record actual game-load confirmation separately.
  5. 05Keep unsupported versions visible instead of silently guessing.
FAQ

Questions people ask before touching the save

Does PlZ mean my save is safe to edit?

No. PlZ identifies the outer compression path. The inner Palworld data still needs current-version parse and round-trip support.

Why is PlM blocked?

No reviewed browser path currently meets this product's licensing, bounded parsing, round-trip, and current-game evidence gates together.

Is Palworld 1.0 automatically compatible?

No. Post-1.0 issue reports show failures in specific RawData paths, but each task and format still needs direct evidence against representative real saves.