Balatro has a compact but multi-file profile. Back up save.jkr together with profile.jkr and the rest of the profile directory so run state and long-term unlock state are not separated.
Identify the exact save you intend to edit
The researched Balatro PC save location is Windows: %APPDATA%Balatro<profile>. Known file/folder pattern: save.jkr, profile.jkr, settings.jkr, and related profile files. Storefront context: Steam, GOG. The active Steam, GOG installation determines which local profile and cloud copy can overwrite the save. Identify the storefront and account before restoring files. Do not edit a similarly named file from a different profile, edition, or cloud cache.
Make an untouched backup first
Close Balatro, let the launcher finish any synchronization, then copy the complete documented save directory to a dated folder outside the live path. Preserve companion files rather than selecting only the newest-looking record. Keep that copy outside the live save directory and do not overwrite it with later experiments. Cloud context: Steam Cloud can synchronize Balatro profile files; allow sync to complete before manual restore. If a launcher can synchronize the save, prevent it from silently replacing either the original or edited copy while testing.
Understand the format boundary
Balatro keeps save, profile progression, and settings in a small profile directory. These files have distinct roles, so preserve the entire profile folder rather than only save.jkr. File-extension context: .jkr Compatibility note: Treat saves as version-, storefront-, account-, and mod-sensitive unless the game or a separately verified migration workflow proves otherwise. A similar filename or extension is not evidence that two releases are interchangeable. These facts help identify the save but do not automatically reveal every field, checksum, encryption rule, or version-specific structure inside it.
Use only a Tool whose claim matches the file
Generic viewers and diff tools can inspect bytes without claiming game-specific semantics. A game-specific editor should be used only when its Tool page explicitly lists Balatro, a matching supported version/container, and a Verified operational runtime. A planned URL or Game Hub is not evidence that an editor exists.
Test the edited copy safely
Write to a new output file when the Tool supports it, keep the original backup, restore the edited copy into the correct profile/storefront location, and launch the game only after the file operation finishes. If the game rejects it, If progress is missing after a restore, confirm the active Windows account, storefront/profile, cloud state, and exact directory first. Restore the untouched backup before experimenting with individual files or older autosaves. Return to the untouched backup before trying another change.
Verification context: Windows save location, file-boundary, launcher/cloud, and backup notes were reviewed against the linked game-specific references for Balatro. This Game Hub is documentation only and does not claim a new game-specific Save Editor.
Recorded Phase 40 evidence boundary
This Phase 40 entry is grounded in the researched PC save boundary for Balatro: Windows: %APPDATA%Balatro<profile> The recorded file or folder pattern is save.jkr, profile.jkr, settings.jkr, and related profile files. These concrete identifiers are retained so backup, transfer, recovery, and editing preparation remain tied to the documented game/storefront context instead of a generic extension guess.