Help

Balatro browser help

Use these pages when the browser client, save sync, audio, fullscreen, or mobile controls are not behaving correctly.

Unofficial community site. Balatro belongs to its original creators. This site is built for players who already own Balatro and want browser access, account tools, and community features.

Troubleshooting topics

Not loadingRefresh, storage, extensions, and network checks.Black screenGraphics acceleration, cache, and low memory checks.Audio not workingAutoplay, mute switch, tab sound, and permissions.Mobile controlsTouch input, fullscreen, and orientation.Save not syncingAccount state, storage, and refresh timing.

Before sending a report

Try one normal refresh, check the last visible message, and write down where the issue happened. A report with the exact screen is much easier to act on than a report that only says the game broke.

If the issue is tied to a duel, modded session, or mobile controls, mention that mode. The fix path can be different for each one.

What not to do first

Avoid clearing browser data as the first step. That can remove local files that may help recovery. Also avoid opening several game sessions at once while testing the same problem.

Do not spam refresh during a download.
Do not start a new run to test a broken save.
Do not switch devices until the current session state is clear.

Fast triage guide

If the page never reaches the game, use the loading page. If the game appears but the picture is wrong, use the black screen or mobile controls page. If the run data looks wrong after a crash or power loss, use the save sync page.

Step by step triage

Use the help pages in order instead of guessing. Start with what you can see on screen, then move to the matching page.

Loader never reaches the game: use Not Loading.
Game area appears black or empty: use Black Screen.
Picture works but sound does not: use Audio Not Working.
Touch or fullscreen is wrong: use Mobile Controls.
Progress looks wrong after a crash or tab close: use Save Not Syncing.

Common support mistakes

Do not send only a one-line report if you can see an error message. The exact status text, route, device, browser, and mode matter. A duel launch failure, modded launch failure, and normal solo launch failure can look similar while needing different fixes.

Do not wipe browser data before writing down what happened. Clearing data can remove the local evidence that would help explain the issue.

Limitations of browser troubleshooting

Some failures are caused by device policy, browser bugs, extensions, power loss, or unsupported embedded browsers. The help pages give the safest first steps, but they cannot guarantee that every device can run a game runtime smoothly.

What a useful report looks like

A useful report says what you were doing, what screen you were on, what the last visible message said, and what device and browser you used. If the issue happened after a power loss, update, duel queue, mod launch, or fullscreen change, include that too.

Short reports can still help when they include the exact visible error. Long reports are less useful if they leave out the page, mode, or timing.

Last check before reporting

Try to reproduce the issue once after a normal refresh. If it happens again, stop there and send the report. Reproducing once is useful. Repeating the same failing launch many times can hide the original failure and make recovery harder.

Last updated: July 6, 2026.