Balatro browser guide
Browser play is convenient, but it works differently from a normal desktop install. These guides explain what to check before you start and what to do when something looks wrong.
Guide topics
How to use these guides
Start with the browser launch guide if you are new. Use the requirements page when the client will not start, then use the save sync and fullscreen pages for issues that happen after the game appears.
The pages are written for normal players, not developers. They explain what to try, what to avoid, and what details are useful when you send a report.
Common paths
If the loader never finishes, read the loading help page. If the game appears but the screen is wrong, read the fullscreen and mobile page. If progress looks wrong, read the save sync page before clearing browser data.
- Browser launch issues usually involve cache, storage, network, or device memory.
- Display issues usually involve fullscreen, rotation, canvas sizing, or graphics acceleration.
- Save issues usually involve account state, browser storage, or closing the page too soon.
Recommended reading order
Use the guide like a checklist. Read the launch page first, then requirements, then save sync. Mobile and desktop comparison pages are there for the cases where the game opens but the experience does not feel right.
- New player: launch guide, requirements, save sync.
- Mobile player: fullscreen and mobile guide, then mobile controls help.
- Returning player with a broken run: save sync guide, then save not syncing help.
Common guide mistakes
The biggest mistake is treating the browser client like a normal static page. It is closer to a game runtime inside a page, so storage, cache, user clicks, fullscreen permission, and device memory all matter.
Another common mistake is clearing data too early. A simple refresh is safer than wiping local files before you know whether the problem is cache, account state, or a temporary network failure.
Honest limits
The site can improve launch flow and recovery, but it cannot make every managed school device, old phone, strict browser extension, or unusual embedded browser behave like a desktop install. When a problem only happens on one device, test a normal desktop browser before assuming the account is broken.
Quick decision table
If the game has never opened on your device, start with requirements. If it opened before and suddenly stopped, start with loading help. If it opens but looks wrong, start with fullscreen or black screen help. If your run state looks wrong, stop launching new sessions and read save sync first.
This order matters because the safest fix depends on the failure point. A display issue should not be treated like a save issue, and a first-time download issue should not be treated like a broken account.