Balatro browser mods guide
Browser mods are experimental because many Balatro mods were built with desktop assumptions. The site tries to translate common mod APIs, but unstable packages can still break a session.
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 works best
Lua and Lovely style mods usually have the best chance. Heavy desktop-only behavior, missing browser-safe file access, or unusual UI patches may fail. Start with one mod before combining several.
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.