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.
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.