LEGO Batman: Legacy of the Dark Knight on Steam Deck: Verified, but Target 30 FPS

Quick verdict

Recommended on Steam Deck with a 30 FPS target. Use the default Verified runtime, Low preset, FSR Balanced, Frame Generation off, and a 30 FPS cap. Use Gotham traversal as your tuning test, because driving, gliding, co-op, and combat-heavy moments are where reports most often describe drops.

Not recommended if you require a locked 60 FPS or are unwilling to use a frame cap. The available reports point to a playable handheld experience, but not one with enough headroom to chase high frame rates consistently across the open world.

What Valve and official sources confirm

Steam's compatibility metadata, mirrored through SteamDB, marks the game as Verified with a test timestamp of May 12, 2026. The checklist confirms the default controller configuration works, Steam Deck button icons display correctly, interface text is legible, and the default graphics configuration performs well on Steam Deck. SteamDB's compatibility metadata points to Proton 10.0-4 for the Deck runtime path, and SteamDB detects support for AMD FSR upscaling, FSR Frame Generation, Intel XeSS, DLSS, DLSS Frame Generation, and NVIDIA Reflex.

Valve's notes flag one specific caveat worth knowing: the game does not default to external Bluetooth or USB controllers on Deck or SteamOS. If you dock the Deck or use a third-party pad, you may need to switch the active controller manually through the Quick Access Menu.

The minimum PC spec targets Low / 1080p / 30 FPS with FSR or XeSS Balanced and Frame Generation. The recommended spec targets Medium / 1440p / 60 FPS with DLSS, FSR, or XeSS Quality and Frame Generation. Against those requirements, Deck reaching 30 FPS without Frame Generation is meaningful.

What hands-on testing shows

SteamDeckHQ's launch-week hands-on describes the game's performance as splitting into two zones on Steam Deck. Contained story levels run well, while open-world Gotham generally sits at 30 FPS or higher. The default settings land at mostly low quality with upscaling but look surprisingly good on the Deck's small screen. The site notes 16:10 support without black bars and reports that HDR did not appear to hurt performance in early testing. The coverage was based on the opening hours of the game, not a full playthrough, so later areas may behave differently.

TwistedVoxel's settings guide, published May 21, gives the clearest published Deck settings recipe currently in the source set. The outlet's tested configuration uses 1280x800, V-Sync off, the in-game FPS limit set to unlimited, AMD FSR Balanced, and Low settings across lighting, shadows, textures, reflections, post-processing, and population. Material Quality is set to Low and Distance Field Ambient Occlusion is off. TwistedVoxel reports that performance stays above 30 FPS for the most part, with occasional dips into the high 20s.

TechRadar's review does not provide Deck FPS numbers, but the outlet confirms the game was played on PC via Steam and on handheld. The review says a fair number of settings had to be lowered to get the best performance, especially on Steam Deck, and describes the game as surprisingly demanding performance-wise. It also flags wall glitches and overworld bugs in the review build. It supports using lower settings but provides no benchmark data.

PC Gamer's review lists "Steam Deck: Verified" in its review header but does not include first-hand Deck benchmark testing. Its desktop performance detail is still useful context: PC Gamer reports dropping multiple settings from Epic to High to get a decent frame rate, and notes that some boss QTE takedowns dropped into slideshow territory even after those cuts. Use that as general evidence that the game can be heavier than its LEGO branding suggests, not as Deck-specific FPS data.

What community reports add

The most detailed r/SteamDeck performance thread includes one user reporting 30 FPS with FSR Balanced and Frame Generation enabled, describing the experience as running very well about an hour in. Another user in the same thread says Frame Generation introduces visible delay and a clip-show quality to motion. A third reports mid settings running roughly 40-50 FPS outside combat, with dips during combat sequences. The thread also notes that co-op reduces performance and that the first area appears not well optimized.

A separate r/SteamDeck help thread gives the clearest area-by-area breakdown in community coverage: enclosed levels around 30 FPS on Low settings, with the open world struggling, especially during driving or gliding. The commenter calls the game playable but not ideal at Low settings. That is why open-world traversal should be treated as the tuning test, not lighter missions.

On the game's Steam Community discussions, one Deck owner reports that it plays very well after a couple of hours, with quick loading, no stuttering, and no bugs encountered. Another user in the same thread posts a 30 FPS Deck profile using 1280x800, upscaling off, Frame Generation off, Textures and LEGO Mesh on Epic, Material Quality at Low, and view / streaming distance set to Near.

The strongest negative outlier comes from a Steam Community thread titled "Steam Deck performance is abysmal", where the poster reports 20-30 FPS with FSR and Low settings, describes the image as a pixelated mess, and says Lossless Scaling did not help. The accessible reply in that thread directly disagrees and says the game is fine for them. The disagreement is worth preserving because it shows the spread in user experience, but the broader source set does not support treating that thread as the baseline.

Material Quality has the largest reported cost

A Steam Community post reports that lowering Material Quality below Epic produced roughly a 20 FPS desktop gain, from around 40 FPS to 60+ at native resolution. This is not a Deck measurement, but Material Quality is also Low in TwistedVoxel's Deck profile and the Steam Community 30 FPS profile. Keep it Low before raising other sliders.

Three problems worth knowing about

Black-screen relaunch after changing graphics settings. The clearest report describes the game launching once successfully, then black-screening on later launches after the user changed FSR mode and enabled FSR Frame Generation. Multiple commenters in the same thread report the same pattern. One commenter says the game works for them on Proton Experimental. The fix is not universally confirmed, but if you hit a relaunch black screen, Proton Experimental is the documented workaround to try once. Status: situational, not yet cleanly solved.

Denuvo and troubleshooting discipline. SteamDB confirms the game uses Denuvo Anti-Tamper, and one r/SteamDeck launch-error post shows a CodeFusion anti-tamper error on Deck startup, though no fix is confirmed in the accessible discussion. Because Denuvo-related launch failures are hard to distinguish from Proton issues on Deck, avoid changing multiple variables at once while troubleshooting. If you test a fallback runtime, try one change, then stop and document the result.

Controller routing for external pads. Valve's compatibility notes flag that the game may not default to external Bluetooth or USB controllers on Deck or SteamOS. Switching the active controller through the Quick Access Menu is the documented workaround. This is noted as a known behavior in SteamDB's Deck checklist, not a bug to troubleshoot.

Recommended settings

Start with this source-supported Deck profile.

Compatibility

• Runtime: Default Verified runtime; SteamDB's compatibility metadata points to Proton 10.0-4
• Fallback if you hit a relaunch black screen: try Proton Experimental once
• Do not cycle through multiple Proton versions while troubleshooting

SteamOS

• Frame cap: 30 FPS
• Refresh rate: 60 Hz
• TDP: Auto to start
• CPU/GPU clocks: Auto
• HDR: Optional (early hands-on tested without major performance hit)

In-game

• Display mode: Fullscreen or Borderless, whichever behaves better
• Resolution: 1280x800
• Graphics preset: Low
• Upscaling: FSR Balanced
• Frame Generation: Off
• Motion blur: Off or Low
• Material Quality: Low
• Distance Field Ambient Occlusion: Off

Expected performance based on aggregated sources

• General target: 30 FPS
• Published profiles: mostly at or above 30 FPS, with occasional high-20s dips
• Open-world combat, driving, gliding, and co-op: more uneven than contained levels

If traversal feels uneven at the Balanced profile, FSR Performance is the smoother but softer fallback to test. If you mostly play story missions and want a sharper image, FSR Quality with the same 30 FPS cap is worth testing, but expect less headroom outdoors.

Frame Generation should stay off for the default profile. Community reports split on it: some users report smooth play with it enabled, while others describe visible delay and motion artifacts. A 30 FPS cap without Frame Generation is the cleaner baseline to recommend until broader reports settle.

Battery, briefly

No source in the current set provides a reliable battery figure, and community reports rarely identify OLED versus LCD hardware. If you try a manual TDP cap, lower it gradually and use Gotham traversal to check for stutter.