Balatro web save sync guide
Save sync combines browser storage and account backed session state. It is useful, but players still need to avoid closing the browser at the wrong time or mixing multiple sessions carelessly.
What sync is meant to do
The site stores session data so your account can continue from the expected state. Browser local storage helps the client start faster and preserve local files between visits.
What sync cannot promise
No browser sync system can protect against every crash, power loss, private mode wipe, blocked storage setting, or forced reload. If a tab closes while the game is writing data, the next launch may need recovery.
How to protect progress
Use one active tab, wait for save or end session messages, avoid private browsing, and do not clear site data unless you are intentionally resetting local files. If something looks wrong, report it before repeatedly launching new sessions.
Related pages
How to avoid save confusion
The safest pattern is simple: finish one session, wait for the site to return to the session screen, then start the next one. Opening multiple game tabs can make it harder to tell which state is newest.
If your device dies or the browser crashes, launch from the same account and same browser first. That gives the site the best chance to recover the local state it last saw.
- Do not clear site data unless you mean to reset local files.
- Do not start a second session to test a broken first session.
- Report the run state before trying risky recovery steps.
What reports should include
Useful save reports include your username, the device, the browser, the time it happened, and whether the issue started after a crash, power loss, refresh, or normal End Game button. Screenshots of the last visible message help more than a general description.
Step by step safe session flow
The safest save flow is boring on purpose. One account, one game tab, one session ending cleanly gives the site the clearest state to preserve.
- Start from the signed-in app.
- Play in one active tab.
- Use the site End Game control when finished.
- Wait for the session screen or result message.
- Only then close the tab or start another session.
Common save mistakes
The most common mistake is opening a second session to check whether the first one saved. That can make the recovery story harder to read. Another mistake is clearing browser data after a crash, which can remove local files that might have helped restore the session.
Power loss, browser crashes, and forced tab closes can interrupt writes. The site can recover some cases, but it needs the original account and browser state whenever possible.
Practical recovery notes
If a run looks wrong after a crash, stay on the same browser and report the time, account, and what happened before trying resets. If you changed devices, mention that too. A save issue after switching devices is different from a save issue after the same tab crashed.