Balatro Steam Deck Settings: The 40Hz Battery Trick Most Guides Skip

Every Balatro Steam Deck guide says the same thing: it’s Verified, it runs at a locked 90 FPS, don’t touch anything. That’s true, and it’s also the wrong advice if you actually care about battery life. Balatro isn’t GPU-bound — it’s a 2D card table with light sprite animation, and 90 FPS of that costs the Steam Deck almost nothing compared to a real 3D game. That means the default settings leave real battery life on the table for a frame rate you’ll never consciously notice. Here’s what actually matters, what doesn’t, and why the frame-rate cap is the one setting that moves the needle. For the general Steam Deck battery playbook that applies across every game — brightness, charge limits, TDP by game type — see our Steam Deck battery life guide. This one stays focused on what’s specifically different about a game like Balatro.

Quick Start: The Settings That Actually Matter

1. Steam Deck refresh rate: 40Hz (Quick Access → Display), not the 60Hz default.
2. In-game frame limiter: match it — cap Balatro to 40 FPS via the Quick Access performance overlay.
3. In-game VSync: leave it On. Turning it off lets Balatro try to render up to 500 FPS internally [1], which fights every other cap you’ve set.
4. TDP limit: enable it and start around 4–6W.
5. GPU clock: leave on Auto. Don’t force a fixed clock.
6. Window Mode: Borderless (default) — no change needed, no letterboxing at the Deck’s native 16:10.
7. Cosmetic filters (CRT, CRT Bloom, Pixel Art Smoothing, Shadows): optional, marginal battery impact — last on the list, see below.

Why the Frame-Rate Cap Is the One Setting That Moves the Needle

Community wattage testing puts Balatro at roughly 7.5W drawn at an uncapped 90 FPS, dropping to about 6.5W at 60 FPS — good for around 8 hours versus 9 hours on OLED (7 on LCD) [2]. That’s real, but it’s a small gain for a big frame-rate cut, because Balatro was already cheap to render at 90 FPS. The bigger opportunity is going lower still, and Valve’s own numbers explain why. Pierre-Loup Griffais, one of the Deck’s lead engineers, has said Valve treats 30 FPS as the practical floor for playable performance on the Deck, and gave Portal 2 as the concrete example: capped at 30 FPS, it ran for 6 hours; uncapped, 4 hours — a 50% jump from a single setting [4]. Valve’s own caveat matters here too: the frame limiter’s battery savings shrink for demanding games already running close to that 30 FPS floor, because there’s no headroom left to cut [4]. Balatro is the opposite case — it has enormous headroom (90 FPS on a card table with a handful of animated sprites), which is exactly the profile where a hard cap pays off the most. No Balatro-specific test has published wattage below 60 FPS, so treat the exact number as an estimate rather than a measured fact — but going by the mechanism Valve describes, a 40 FPS cap on a game this light should land closer to Portal 2’s 50% gain than to the 13% difference between 90 and 60.

Refresh Rate and Frame Limiter: Why 40Hz Beats the 90Hz Default

The Steam Deck’s default panel refresh is 60Hz (90Hz on OLED models); most Balatro guides just leave it there and cap the frame limiter to match [3]. Do it differently: drop the display refresh to 40Hz in Quick Access → Display, then set the per-game frame limiter to 40 FPS for Balatro specifically — Steam’s per-game settings mean this won’t touch your refresh rate in anything else you play. 40Hz isn’t a compromise pick. It evenly divides a 40 FPS frame delivery, which is why SteamOS added it as a dedicated option instead of leaving you to cap 40 FPS on a 60Hz screen and eat the resulting stutter [5]. Frame time at 40 FPS is 25ms, sitting almost exactly between 30 FPS (33ms) and 60 FPS (16ms) — noticeably smoother than 30 FPS without asking for anywhere near 60 FPS worth of compute [5]. For a turn-based card game where you’re reading a hand, not tracking a moving target, you will not feel the difference between 40 and 90 FPS. You will feel the difference in how long the battery lasts.

One setting most guides skip entirely: Balatro’s own in-game VSync toggle. Leave it On. The Balatro Wiki’s settings reference notes that with VSync off, the game tries to render up to 500 FPS on its own [1] — regardless of what you’ve set the Deck’s OS-level limiter to. The Deck’s frame limiter should still cap what actually gets displayed, but there’s no reason to make the engine work that hard internally when you’ve already told the hardware to slow down. Keep all three layers capped together: 40Hz refresh, 40 FPS limiter, VSync On in-game. Leaving just one of the three uncapped undercuts the other two.

TDP Limit and GPU Clock: Cap What Balatro Doesn’t Need

Community-tested Steam Deck settings for Balatro list the TDP limit as ‘not required’ and the GPU clock override as ‘disabled’ [3] — meaning nobody found stutter or crashes without touching either. That advice was written for stability, not battery, and those are different goals. If your target is battery life rather than guaranteeing smoothness on an already-light game, enable the TDP limit and cap it low — starting around 4–6W is a reasonable place to begin, since even the game’s uncapped, no-limit power draw only reaches about 7.5W of total system power at 90 FPS [2], and a chunk of that total is the display and radios, not compute. There’s room to cut. Leave the GPU clock on Auto rather than forcing a fixed value: Balatro’s workload is inconsistent — a card-reveal animation costs more than sitting still on the shop screen — and a fixed clock either wastes power holding a ceiling you rarely need, or under-serves the brief animation spikes. Auto lets the chip scale down further at idle than a manual floor would allow, which matters more on a game that spends most of its time nearly idle than one under constant load. The same capped-clock, capped-TDP logic is the backbone of our PC game settings optimization hub — cutting rendering work you don’t need is the single highest-leverage change on any platform, handheld or desktop, it just shows up as battery life here instead of FPS.

In-Game Display and Graphics Settings

Balatro’s options menu splits into Game, Video, and Graphics tabs, and only a few entries in any of them touch rendering load [1]:

• Window Mode: Borderless is the default and correct choice on Steam Deck — no letterboxing at the Deck’s native 16:10 aspect ratio [2].
• Shadows, CRT, CRT Bloom, Pixel Art Smoothing: cosmetic shader passes layered on top of the card table. Turning them off trims a small amount of per-frame GPU work, but no source has isolated the wattage on just these filters, and on a workload already under 10W total, expect the saving to be marginal next to the frame-cap changes above — worth doing if you’re chasing the last percentage, not worth doing first.
• Screenshake and Reduced Motion: comfort and accessibility settings, not performance ones. They don’t move battery numbers in any meaningful way — see the FAQ below.
• Game Speed: controls animation playback speed (0.5x–4x), not frame rate. Bumping it to 2x or 4x shortens each hand’s animations, which very marginally reduces total render time per run, but it’s a pacing setting first and a power setting a distant second.

Which of These Settings Matter for You?

Not everyone optimizing Balatro on Steam Deck wants the same thing. Match your priority to the table below.

Settings dialed in, the real skill ceiling in Balatro is in your joker choices, not your frame rate — see our Balatro best joker combos guide for how to build a deck around them.

FAQ

Do I need to lower the TDP limit if Balatro already holds a locked 90 FPS?

Not for stability — but stability isn’t the goal here. ‘Doesn’t need it’ and ‘isn’t wasting it’ are different claims. Balatro’s own community wattage tests show it drawing about 7.5W uncapped, most of which nobody needs on a card game with no reflex requirement. Capping TDP costs nothing in smoothness and gets real battery back.

Will turning off CRT effects or pixel art smoothing meaningfully extend my battery?

Probably a little, not meaningfully. These are per-frame shader passes, so they do cost some GPU work, but no source has isolated their wattage on Balatro specifically, and the whole game only draws single-digit watts to begin with. Do the frame-rate and TDP changes first; treat the cosmetic filters as a last 1–2% squeeze, not the main event.

Should I turn off VSync for lower input lag?

No. Balatro isn’t a game where input lag is a real constraint — you’re clicking cards, not tracking a moving target — and turning VSync off lets the game render up to 500 FPS internally, which fights against every other cap you’ve set. There’s no upside here that offsets the battery cost.

Does turning down screenshake or enabling Reduced Motion save battery?

No, and this is a common mix-up. Screenshake and Reduced Motion are comfort and accessibility toggles — they change what gets displayed, not how much gets rendered underneath it. If battery is the goal, the frame-rate cap and TDP limit are doing all the real work; these settings are for your eyes and inner ear, not your battery gauge.

Settings verified against Balatro’s live Steam options menu and SteamOS’s Quick Access refresh-rate/frame-limiter controls, current as of August 2026. Both the refresh rate and frame limiter are OS-level Steam Deck features, not Balatro-specific ones, so they’ll keep working the same way across future Balatro updates unless Valve changes the Quick Access menu itself.

Sources

1. Balatro Wiki. Settings — full in-game options menu reference. Balatro Wiki
2. Steam Deck HQ. Balatro — Steam Deck Performance and Settings Review. SteamDeckHQ
3. Clawsome Gamer. Best Balatro Settings for Steam Deck. Clawsome Gamer
4. Engadget. Steam Deck Can Limit Frame Rates to Give You Longer Battery Life. Engadget
5. Game Rant. Steam Deck Gets 40Hz Refresh Rate, Improving Framerate Stability and Battery Life. Game Rant

Michael R.

I've been playing video games for over 20 years, spanning everything from early PC titles to modern open-world games. I started Switchblade Gaming to publish the kind of accurate, well-researched guides I always wanted to find — built on primary sources, tested in-game, and kept up to date after patches. I currently focus on Minecraft and Pokémon GO.