Balatro browser mods guide

How modded sessions are separated

Modded play uses a separate mode. Normal saves, public leaderboards, Chips, achievements, and quests stay separate so testing a mod does not pollute normal progression.

What the browser can run

The uploader accepts ZIP, Lua, Lovely, and JSON packages up to 30 MB. Lua and Lovely style mods usually have the best chance. Packages can change cards, art, menus, scoring, and other runtime behavior when the APIs they use are browser-compatible.

What may not work

Native desktop code, operating-system integrations, direct desktop file paths, unsupported networking, or unusual UI patches may fail. Two mods that work separately can still conflict when combined.

Reading player checks

Most used reflects how many player libraries contain the package. Works and Breaks are player-submitted checks, not automatic certification. A tie is shown as working, while a package with no checks remains Needs testing.

Safe mod habits

Use mod files from sources you trust, keep a normal save separate, and report the exact mod name plus console text if a launch fails.

Related pages

Testing a new mod

Start with one mod and a modded save slot. Launch it by itself, confirm the main menu appears, then start a run and click around. A mod that only reaches the menu is not fully tested.

If it works alone, add a second mod. If the pair fails, report both names because menu hooks, file access, and card definitions can collide.

• Test a fresh modded save when a mod changes game data.
• Watch for missing art, missing names, frozen menus, and crashes after clicking.
• Keep normal progression separate from modded play.

Why some desktop mods need work

Many Balatro mods assume desktop file paths or APIs that do not exist in a browser. The web client can translate common patterns, but native files, unusual loaders, or heavy runtime hooks can still fail.