Balatro Cheats & Debug Menu: Complete Activation Guide

To enable Balatro’s debug menu, open Balatro.exe as an archive with 7-Zip, find conf.lua inside, and change _RELEASE_MODE = true to _RELEASE_MODE = false. Save the file, launch the game, and hold Tab to open the cheat menu mid-run. Unlike mods, this method keeps achievements fully active — you won’t see a single achievement lock for using it.

The debug menu is built directly into the game by developer LocalThunk. It lets you spawn any Joker, toggle editions, add currency, skip Antes, and even instantly win or reset a run. Below is everything you need: the exact setup steps and a full table of every available cheat.

Debug Menu vs. Mods — Why the Distinction Matters

Balatro’s modding scene is strong, and tools like Steamodded give you enormous flexibility. But mods come with a real cost: most disable achievements the moment they load. For players still grinding unlocks — Legendary Jokers, Challenge completions, collection items — that’s a dealbreaker.

The debug menu sidesteps this entirely. Because it’s part of the base game binary, Balatro doesn’t flag it as external interference. Your achievement progress stays intact regardless of what you do in the debug session. That makes it the right tool for a specific use case: testing. You want to know if Fibonacci plus Bloodstone plus Hologram actually scales the way you think it does before committing an entire run to the theory. The debug menu lets you set that up in two minutes.

There’s a trade-off to be honest about. The debug menu doesn’t offer the breadth of mod tools — no custom Joker creation, no run-state editing outside what the menu exposes. If you want deep sandbox control, mods remain the better option (just accept the achievement tradeoff). For quick combination testing or collection completion while keeping your profile intact, debug mode wins.

Before You Start: The One Tool You Need

You need 7-Zip (free, open source, available at 7-zip.org). That’s genuinely the only prerequisite. Balatro stores its game files — including conf.lua — packed inside the executable itself, so you can’t just open a folder and find them. 7-Zip reads Balatro.exe as a compressed archive and lets you access the files inside directly.

Any basic text editor works for the actual edit. Notepad on Windows is fine. On Mac or Linux, TextEdit or gedit will do. You don’t need anything fancier — the change is a single word in a single line.

One thing to confirm before starting: make sure Balatro is fully closed. Editing conf.lua while the game is running won’t cause damage, but the changes won’t register until the next launch anyway.

Step 1 — Find Your Balatro Installation Folder

For most Steam users on Windows, Balatro lives at:

C:Program Files (x86)SteamsteamappscommonBalatro

If it’s not there — maybe you have Steam installed on a different drive or moved the library — the fastest way to find it is through Steam itself. Open your library, right-click Balatro, select Manage, then Browse Local Files. Steam opens the exact folder in Explorer.

You should see Balatro.exe sitting in that folder. That’s the file you’re working with. On Mac, the path will differ (look inside the .app package), but the process is the same once you have 7-Zip or an equivalent archive tool open.

Step 2 — Open Balatro.exe with 7-Zip

Right-click Balatro.exe and look for the 7-Zip option in the context menu. On Windows 11, it may be hidden under Show More Options — that’s normal, just click through to it. Select Open archive.

7-Zip opens the executable like a zip file. You’ll see a list of internal files and folders. This is the actual game data packed into the binary — don’t delete or move anything here. You’re only reading one specific file.

Scroll through until you find conf.lua. It should be near the top level of the archive, not buried deep in subfolders. Double-click it and 7-Zip will ask you which application to use — select Notepad (or your text editor of choice).

Step 3 — Edit conf.lua and Activate Debug Mode

The file is short. You’re looking for one specific line:

_RELEASE_MODE = true

Change true to false. The line should now read _RELEASE_MODE = false. That’s the entire edit.

Save the file. Here’s where some users hit a snag: 7-Zip may prompt you asking whether to update the archive with the modified file. Say yes. If the save fails — sometimes this happens due to permissions — extract conf.lua to your desktop first, make the edit there, then drag the modified version back into the 7-Zip archive window to replace the original.

Launch Balatro. Start or load a run, then hold Tab. The debug menu appears as an overlay with buttons and interactive elements. If nothing appears, double-check that you saved after the edit and that you’re actually holding Tab (not tapping it — the menu requires a sustained hold).

To disable debug mode later, just reverse the change: open conf.lua again through 7-Zip and set _RELEASE_MODE back to true.

Every Balatro Cheat — Full Debug Menu Reference

With the menu open (Tab held), here’s what everything does. The keyboard shortcuts apply to items you’re currently hovering over in your collection or hand:

Getting the Most Out of Debug Testing

The Negative edition trick (pressing Q four times on a Joker) is the single most powerful thing in the debug menu. Standard runs cap you at five Joker slots. Negative Jokers don’t consume a slot — so with debug, you can stack eight, ten, twelve Jokers simultaneously and see exactly how synergies interact at scale. That’s genuinely hard to test otherwise without fishing for very specific seeds.

For scaling tests, use +1 Ante repeatedly to push into Ante 7 and 8 territory without grinding there legitimately. Then use X10 Mult or X2 Chips to simulate what your combination would actually output at those score thresholds. Real talk: the gap between Ante 6 and Ante 8 requirements is steep enough that a build that feels unbeatable in early Antes can completely fall apart at the end. Debug lets you verify before you commit.

The Boss Reroll button is underrated for testing. If you’re working out how a specific Joker setup handles different Boss mechanics — The Eye, The Needle, Cerulean Bell — you can just keep rerolling until one appears and test against it directly. No more hoping a specific boss shows up on a legitimate run.

One thing to keep in mind: the $10 button adds money in $10 increments. Click it repeatedly if you need a larger amount for shop testing. There’s no “add $1000” shortcut, so budget a few extra clicks for complex shop simulation.

Finally — the debug menu resets to inactive state each session if something goes wrong with the conf.lua edit. If the Tab overlay stops appearing after a game update, check whether the update overwrote your conf.lua changes. Balatro patches occasionally touch the executable, which can reset _RELEASE_MODE back to true. Just repeat Step 3 and you’re back in business.