Supported Balatro web mods
Compatibility depends on the current browser build, the mod package, and how closely the mod follows APIs the web client can support. This page avoids inventing a fixed support list.
How to judge compatibility
A mod is more likely to work when it includes clear Lua entry files, normal metadata, browser-readable assets, and avoids native desktop-only code.
What the site can show
The mod library can display package names, versions, file names, and icons when the uploaded package includes that metadata. Missing metadata may fall back to the file name.
When a mod fails
Try the mod by itself first. If it still fails, report the mod name, version, and the first error line. That helps improve shared compatibility instead of only patching one package.
Related pages
What support means here
Supported does not mean every feature of every package is guaranteed forever. It means the current browser client can read the package, load its main files, and run it without breaking normal site systems.
A mod can still have partial issues, such as missing optional art, a broken config panel, or a conflict with another mod.
Package details that help
Good packages include clear manifest data, version information, normal folder structure, image assets with expected dimensions, and Lua files that do not depend on a desktop-only path. Thunderstore, GitHub, and other sources can work when the package layout is readable.