Common locations are listed above for Windows, Linux / Steam Deck, and macOS. If you use Proton, make sure you are editing the file inside the Balatro compatdata AppData path rather than a different Steam prefix.
Browser-based tool
Balatro Save Editor
Open a Balatro .jkr file in the browser, inspect the data, make targeted edits, and download the
updated file without installing a separate desktop editor.
Common save locations
- Windows:
%APPDATA%/Balatro - Linux / Steam Deck:
[steam path]/compatdata/2379780/pfx/drive_c/users/steamuser/AppData/Roaming/Balatro/ - macOS:
/Users/[user]/Library/Application Support/Balatro/
Supports
- Settings files
- Meta files
- Profile files
- Full save files
Best workflow: duplicate the original file first, then edit the copy so rollback is trivial.
How to use this Balatro save editor safely
1
Copy the original file first
Never edit your only copy. Duplicate the file in the Balatro save folder so you can instantly roll back if something breaks.
2
Open the cleanest mode you need
Normal is safest. JSON is good for structured edits. Raw is only for advanced users.
3
Download and replace carefully
Write the edited file back only after saving your backup. On Steam Deck or Linux, double-check the correct compatdata folder before replacing anything.
What this page is good for
This tool is strongest when you know exactly what you are trying to inspect or fix.
Profile and unlock checks
Inspect profile-level values and understand whether a change is being stored in settings, meta, or the profile file.
Settings repairs
Useful when you want to verify a settings file or move between Normal, JSON, and Raw views for troubleshooting.
Backup-friendly edits
The browser-first workflow is fast for single-file edits and avoids spinning up a heavier external editor just to inspect a few fields.
Modded save caution
When mods are involved, use this as a careful inspection tool, not as a promise that every custom structure will round-trip perfectly.
A controlled edit: backup, change one value, verify
1. Identify the active copy
Close Balatro before copying a save. Locate the profile you were actually using, and copy the entire relevant save folder to a separate backup directory. Give the backup a descriptive name containing the date and profile. Keep this copy outside the active folder so an accidental overwrite is easier to spot. If several installations or Steam accounts exist, use the recent modification time as a clue and verify the profile in game before making changes.
2. Inspect before changing anything
Open a duplicate file in this editor and inspect the visible structure. A successful parse means the editor can read that representation; it does not prove every value is valid for your game version. Start with a setting whose meaning you understand and whose original value you can write down. Do not change identifiers, nested tables, or unfamiliar mod fields simply because they appear editable.
3. Preserve the value type
Keep numbers as numbers and booleans as true or false when using JSON. A quoted number is a string and may not be accepted where the game expects a numeric value. JSON syntax also requires quoted keys and valid commas. Normal mode is preferable for a small targeted change; JSON and Raw modes expose more structure and make broad accidental edits easier. Save a note containing the original value, the replacement, and the reason.
4. Download, reopen, and test
Download to a separate location, then reopen that downloaded file in the editor. Check that the intended change survived and that nearby fields still look correct. Reopening is a format check, not a game compatibility guarantee. With the game still closed, copy the edited file to the intended location. Launch the matching game version and profile, test the specific change, then exit normally. Keep the backup until you have confirmed normal play.
Recovery when a file fails or an edit disappears
If the editor cannot parse a file, preserve it unchanged. Confirm that it is a Balatro .jkr file rather than an archive, renamed download, or another game's save. A mod may add structures this editor cannot round-trip. Avoid trying random text replacements in a compressed file. Restore the known working copy and repeat with the same game and mod versions that created it.
If the edit disappears, check whether you edited another profile or whether the game was still running when the file was replaced. Cloud synchronization can also introduce another version. Compare timestamps and retain both copies before resolving a sync conflict. Do not choose a cloud or local version solely because its timestamp is newer; identify which one contains your expected progress.
To report a problem, send the browser, operating system, game version, mod list, file category, and exact error message through Contact. Describe the smallest action that reproduces it. Do not send passwords, payment details, or your whole save archive by default. The editor reads the selected file in your browser; support correspondence is a separate action that you choose to take.
FAQ
Sometimes, but modded saves are riskier. Back them up first and treat successful parsing as a convenience, not a guarantee.
Normal mode is the safest default. JSON mode is easier to bulk-edit if you understand the structure. Raw mode is best reserved for users who already know the Lua-style layout.
Yes. It runs in the browser. You choose a local .jkr file, edit it locally, and then download the updated file.