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

LEGO Batman: Legacy of the Dark Knight is the rare modern LEGO release where Steam Deck performance is a real question instead of a footnote. The published PC requirements assume FSR or XeSS Balanced plus Frame Generation just to hit 30 FPS at Low / 1080p, while the recommended Medium / 1440p / 60 FPS target allows DLSS, FSR, or XeSS Quality with Frame Generation. That is not a normal LEGO-game spec sheet. It is the reason setting the right Deck expectation matters before you buy.

The game is Verified, it is playable on Steam Deck, and it is not a locked-60 handheld experience. Contained story levels run comfortably above 30 FPS based on early hands-on coverage; open-world Gotham traversal sits closer to that target and can dip below it. The safest read: treat it as a 30 FPS game, tune around open-world Gotham, and do not assume that performance in lighter or more contained missions represents the whole game.

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. SteamDB additionally lists Denuvo Anti-Tamper as the game's DRM, which matters for troubleshooting because DRM-related launch failures can look similar to Proton failures from a user's point of view.

The official PC requirements are worth reading directly, because they tell you something the Verified badge alone does not. The minimum spec targets Low / 1080p / 30 FPS with FSR or XeSS Balanced plus Frame Generation enabled, meaning the publisher expects reconstruction and frame generation as part of the baseline PC experience. The recommended spec targets Medium / 1440p / 60 FPS with DLSS, FSR, or XeSS Quality plus Frame Generation. The Deck running this game at 30 FPS without frame generation is, in context, a real handheld result rather than a low bar.

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. That supports the idea that the Deck profile needs real settings discipline, even though it is not a benchmark source.

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

Community reports on r/SteamDeck and the game's Steam Community discussions roughly cluster around the 30 FPS handheld profile, with predictable spread on either side.

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.

One specific setting punches above its weight

The most useful technical detail in the current source set is a Steam Community discussion identifying Material Quality as an outsized performance cost. The poster reports that dropping Material Quality below Epic produced roughly a 20 FPS gain in the open world, from around 40 FPS to 60+ at native resolution on desktop hardware.

That is not a Steam Deck measurement, but it is relevant evidence. Material Quality shows up at Low in TwistedVoxel's Deck profile, in the Steam Community 30 FPS Deck profile, and across community settings discussion. If you build a custom preset for the Deck, Material Quality is the setting to keep conservative before you raise other sliders.

Four problems worth knowing about

Performance is not the only thing readers report. Four issues come up enough in current coverage to flag explicitly.

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.

Open-world regression versus contained levels. The pattern is consistent across published hands-on coverage and community reports: enclosed or lighter sections are easier to hold near the target, while open-world Gotham is where performance complaints concentrate. Driving, gliding, combat-heavy traversal, and co-op are the conditions most likely to expose dips. This is not a separate bug based on the current source set. It is the workload reality of the game on Deck hardware, and it is why a 30 FPS cap is the safer strategy.

Recommended settings

The configuration below is the most defensible Deck setup based on the current source set. Start here.

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
• Hands-on coverage: contained levels run well; open world generally 30 FPS or higher
• TwistedVoxel profile: mostly above 30 FPS, with occasional high-20s dips
• r/SteamDeck area reports: enclosed sections closer to target; open-world traversal more uneven
• Combat, driving, gliding, and co-op: most likely to show drops

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

Battery numbers specifically for this game are sparse in the current source set. Sources do not consistently identify whether testing was on OLED or LCD, and no source in this draft provides a hard battery figure worth publishing as a site claim. The honest read: this is a heavier-than-typical handheld LEGO game with active GPU and CPU load in Gotham, so expect shorter handheld sessions than older LEGO titles.

For a practical estimate, plan around shorter handheld sessions at the recommended settings, especially on LCD, where the battery is smaller. A manual TDP cap can help extend runtime, but lower it gradually and watch Gotham traversal for stutter instead of starting aggressively.

Consensus and outliers

Across the sources reviewed, the rough center of gravity is playable with caveats. Valve's compatibility metadata is Verified. Early hands-on coverage and TwistedVoxel's low-settings Deck test both report performance mostly at or above 30 FPS, with the open world running tighter than contained sections. Community owners largely agree that a 30 FPS target is realistic, while also reporting drops during heavier combat, co-op, driving, gliding, or open-world traversal.

Where sources disagree is mostly about the severity of the open-world penalty. The strongest negative outlier is the Steam Community thread reporting 20-30 FPS at Low settings with FSR and an image the poster considered too soft. On the other side, the strongest positive owner report says the game plays very well after a couple of hours. Both are useful, but neither should carry the article alone.

The cleanest explanation for the disagreement is test conditions. Reports from enclosed or lighter sections are more positive. Reports from open-world Gotham, combat, driving, gliding, or co-op are more likely to mention dips. Frame Generation also splits opinion: some users like the extra smoothness, while others notice latency and interpolation artifacts. Across both Deck and desktop reports, Material Quality remains the single setting most likely to surprise people by costing more performance than expected.

One useful note on hardware variants: the accessible community reports rarely specify OLED versus LCD. Treat the performance numbers in this article as Deck-general unless a source explicitly identifies a model.

Bottom line

LEGO Batman: Legacy of the Dark Knight is a real Steam Deck Verified release with real handheld value. The official PC requirements expect upscaling and frame generation even on stronger hardware, which means the Deck running this game around a 30 FPS target without Frame Generation is a meaningful result, not a fallback. Treat it as a 30 FPS handheld game with conservative settings and it is a good fit.

Watch for the black-screen relaunch issue after graphics changes. Avoid cycling Proton runtimes while troubleshooting because Denuvo-related errors can muddy the signal. Switch active controllers manually in the Quick Access Menu if you dock or use external pads. Keep Material Quality at Low if you customize the preset. Beyond those caveats, the Verified configuration and a conservative Low / FSR Balanced profile are the right starting point.