The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
There is no single best frame-rate setting for every Steam Deck game. As a starting point, use 40 FPS at 40 Hz on the LCD model or 45 FPS at 90 Hz on OLED when the game can hold that rate in demanding scenes. For a game that cannot sustain its target, a stable 30 FPS usually feels better than a higher, erratic frame rate.
Choose a target that fits the game
FPS here means frames per second, not a first-person-shooter preset. Your target is a trade-off between smoothness, responsiveness, image quality, battery use, heat, and fan noise. Higher frame rates can reduce input latency, but only if the game delivers frames consistently. A steady 40 FPS can feel better than a game that swings between 45 and 60.
Each frame at 30 FPS lasts about 33.3 ms; at 40 FPS, 25 ms; and at 60 FPS, 16.7 ms. Valve has described 40 Hz as a useful balance of responsiveness, consistency, and battery life, but that is a starting point rather than a promise that every game will run well at 40 FPS. Valve’s 40 Hz guidance explains the refresh-rate trade-off.
Recommended Free Tools
| Game or goal | LCD starting point | OLED starting point |
|---|---|---|
| General demanding games | 40 FPS / 40 Hz if stable | 45 FPS / 90 Hz if stable; otherwise 40 FPS / 40 Hz |
| Very demanding games | 30 FPS / 60 Hz | 30 FPS / 90 Hz |
| Older or well-optimized games | 60 FPS / 60 Hz | 60 or 90 FPS, matched to refresh rate when sustainable |
| Turn-based games, strategy, and visual novels | 30 or 40 FPS | 30, 40, or 45 FPS |
| Competitive first-person shooters | Highest stable rate, commonly 60 FPS | 60–90 FPS if sustainable |
| Emulation | Match the emulated system’s expected cadence | Match the emulated system’s expected cadence |
For emulation, a cap that conflicts with the original game’s expected timing can cause uneven pacing or alter game speed. Use the emulator’s guidance for that system rather than applying a general Deck target blindly.
#1 Best Overall
- 1TB NVMe SSD
- 1280 x 800 HDR OLED display with premium anti-glare etched glass, 7.4" Diagonal display size up to 90Hz refresh rate
- Wi-Fi 6E
- 50Whr battery; 3-12 hours of gameplay (content-dependent)
- Carrying case with removable liner
Account for LCD and OLED display limits
Both models have a 1280×800 built-in display, but their refresh-rate ceilings differ: LCD reaches 60 Hz and OLED reaches 90 Hz. Valve lists a 40 Wh battery for LCD and 50 Wh for OLED; the OLED’s higher refresh ceiling does not automatically make games render faster. Its newer 6 nm APU and power characteristics may affect results, but performance still depends on the game and its workload. See Valve’s LCD specifications and OLED specifications.
Useful pairings include 30 FPS at 60 or 90 Hz, 40 FPS at 40 Hz, 45 FPS at 90 Hz, and 60 FPS at 60 Hz. On OLED, 90 FPS at 90 Hz can suit a lightweight game that actually sustains it. These pairings help make frame delivery predictable; an arbitrary cap and refresh-rate combination may not look equally smooth.
Set a cap and test it in the game
- Launch the game, then press the Quick Access button (…).
- Open the Performance tab and temporarily enable the performance overlay. Use it to check actual FPS and frame-time behavior while tuning.
- Set the refresh rate and frame-rate limit for the target you want to test. Menu labels and available choices can vary between SteamOS revisions.
- Return to the game and test a demanding section: combat, a busy town, traversal into a new area, or another scene that stresses the game. A menu or quiet opening area is not a useful stability test.
- If the result works for this game, save the settings as its per-game profile so they do not become an accidental system-wide rule.
Start at the game’s native 1280×800 output where practical, then try a Medium preset and the relevant cap. If demanding scenes repeatedly fall below the target, reduce settings that affect the bottleneck or choose a lower cap. The Steam Deck APU has a 4–15 W power envelope, so results vary with the engine, resolution, shader compilation, Proton compatibility, and whether the game is CPU- or GPU-limited.
Judge frame pacing, not just the FPS counter
A displayed FPS number is an average or momentary reading, not a complete account of how smooth play feels. Watch the frame-time graph and test the same demanding areas more than once. Check whether the cap is respected, whether stutters occur on first visits or repeat visits, and whether performance changes as the scene becomes busier.
- Frame-time graph: Look for consistent delivery rather than repeated spikes.
- CPU and GPU activity: Low GPU use alongside poor FPS can point to a CPU or main-thread bottleneck, a cap, or an engine limitation.
- Power draw and battery drain: Compare settings during the same section of gameplay; do not infer battery life from a brief test.
- Stutter timing: A hitch when entering an area may come from asset streaming or shader work rather than an FPS target that is too high.
Uncapped rendering can help you check the Deck’s performance ceiling, but it is not a good default: the device may spend power rendering frames that the display cannot show. The Steam Deck performance-settings guide describes the overlay and available performance controls.
Rank #2
- International (UK) Version
- 7.4” diagonal, HDR OLED, 1280 x 800 x RGB, up to 90Hz Refresh rate, High performance touch, <0.1 ms Response time, 1,000 nits peak brightness (HDR), 600 nits (SDR)
- SteamOS 3.0 (Arch-based)
- 512GB NVMe SSD, 16GB LPDDR5 on-board RAM (5500 MT/s quad 32-bit channels), microSD UHS-I supports SD, SDXC and SDHC
- 6 nm AMD APU, CPU: Zen 2 4c/8t, 2.4-3.5GHz (up to 448 GFlops FP32
Use one frame limiter at a time
Try the game’s built-in limiter or the SteamOS per-game limiter first; do not stack several limiters and synchronization options before you know how each behaves. If the game’s limiter is smooth and accurate, it may be preferable. SteamOS is convenient when a game has no usable limiter or when you want a per-game cap tied to a display setting. Test both if pacing or latency feels wrong.
- In-game limiter: May give the engine more direct control or expose more cap values, but quality differs by game; some implementations pace frames unevenly.
- SteamOS limiter: Easy to configure per game, but some titles may show added latency, audio glitches, or unexpected behavior with refresh-rate limiting.
- V-Sync: Can reduce tearing, but may add latency depending on the game and implementation. Turning it off may reduce latency while making tearing visible.
- Allow Tearing: Can reduce synchronization-related latency in some situations, at the cost of visible tearing and less consistent presentation.
For a competitive shooter, test the highest rate the Deck can hold, then compare the in-game and SteamOS limiters. If the game’s presentation is acceptable, V-Sync off may be worth trying for responsiveness. None of those choices is best for every engine. Controller layout, Steam Input, and other input settings are separate from graphics and frame-rate tuning.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Lower the settings that cost the most
If the game misses its target, identify whether it is GPU- or CPU-limited before lowering everything. Resolution and render scale, ray tracing, shadows, volumetric lighting, reflections, ambient occlusion, view distance, foliage, particles, and crowd or simulation density can have substantial performance effects. Crowd density and simulation settings can matter particularly when the CPU is limiting performance.
Texture quality, anisotropic filtering, and interface quality are often less costly than those settings, provided the game’s memory behavior remains healthy. Do not lower textures automatically if sharper surfaces matter and the game is not constrained by memory. Motion blur, film grain, chromatic aberration, and depth of field are primarily visual-preference options; disabling them is not guaranteed to deliver a meaningful performance gain.
Choose between native resolution and upscaling
Output resolution is what the Deck displays; internal resolution is what the game renders before any reconstruction. In a less demanding title, begin with native 1280×800 rendering. If GPU load is the limit, try a built-in temporal upscaler or FSR at a higher-quality mode before sharply reducing output resolution. Upscaling can reduce GPU work, but may introduce softness, shimmering, ghosting, or other reconstruction artifacts—especially at very low internal resolutions. SteamOS FSR and an upscaler built into a game are not necessarily equivalent. Change one setting at a time and compare both GPU load and image quality; upscaling will not fix a CPU bottleneck.
Rank #3
- Operating System: SteamOS 3.0
Keep TDP and manual GPU controls optional
A TDP limit restricts power available to the APU. It can reduce power use or heat when a game does not need the full power envelope, but it can also cut performance. Do not apply a universal wattage to every game: CPU-heavy and GPU-heavy titles react differently.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minute- Test the game with the default TDP and note typical and low FPS, frame-time behavior, and power draw.
- Lower the limit gradually, using the same demanding section for comparison.
- Stop when frame-time spikes or FPS drops become unacceptable; restore the default if the trade-off is not worthwhile.
- Save a successful adjustment only to that game’s profile.
Manual GPU clock control should generally remain off unless a repeatable test shows a benefit. Forcing a clock can leave less headroom for other parts of the APU’s workload. Establish a stable frame-rate target and graphics setup before experimenting with either control.
Separate a performance limit from stutter or compatibility trouble
Steady low FPS suggests the game may be beyond the chosen target. A brief hitch on a first visit to a scene, or on repeated asset loads, can instead involve shader compilation, cache behavior, or streaming. Proton compatibility can also affect a particular title. Change one suspected cause at a time rather than lowering graphics settings to fix every hitch.
- Update SteamOS before diagnosing a broken performance control; Valve’s SteamOS update notes include fixes affecting frame pacing and per-application performance settings.
- Allow applicable shader data to build or download, then replay the same area to see whether the hitch recurs.
- Start with the game’s default Proton version. Try another version only when the game has a documented compatibility issue or a reproducible problem that points to Proton.
- Avoid treating legacy launch options such as
DXVK_ASYNC=1 %command%as a general fix; older advice may apply only to specific historical Proton workflows. Community reports are title-specific, as illustrated by reports for one game.
Do not install third-party compatibility tools just to apply generic FPS settings. The game’s own compatibility behavior should be investigated separately from the basic frame cap.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot a cap or performance that feels wrong
The game shows 40–45 FPS but still feels uneven
Check the frame-time graph rather than relying on the counter. Possible causes include a poor in-game limiter, shader work, CPU spikes, asset streaming, mismatched refresh and frame rates, background activity, or latency from V-Sync or stacked limiters. Test a single limiter and replay the same section.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallRank #4
- Valve is entering the gaming console marketplace with the new Steam Deck, a console geared towards PC gamers. The Steam Deck can be docked to a monitor, and used as a PC, or docked to a TV.
- Players can play a huge variety of games at any time with the comfort of a console and the freedom of a PC. Not anti-glare screen.
- Like the name suggests, the Steam Deck will include upgraded 1TB storage, and will include a carrying case. A micro SD slot will also enable expanded storage.
- Valve partnered with AMD to create a specialized APU optimized for handheld gaming, and Valve says the chip will deliver performance to run AAA gaming titles.
- The Steam Deck is outfitted with a 7-inch touchscreen, and two trackpads under the control sticks that allow gamers to operate games never designed outside of mouse and keyboard capabilities.
The FPS cap does not take effect
- Confirm that the intended per-game profile is active.
- Check whether the game’s own limiter or a launch option is overriding the SteamOS setting.
- Verify that the frame-rate overlay changes when you adjust the cap; do not assume the chosen value is being enforced.
- Update SteamOS and retest. Valve has noted fixes for cases where per-app performance settings and FPS limits did not apply correctly.
GPU use is low but performance is poor
Consider a CPU or main-thread bottleneck, shader compilation, engine limitations, a frame cap or V-Sync, asset streaming, or compatibility behavior. Lowering textures or other GPU-heavy settings will not resolve a CPU limit; crowd density, simulation detail, or view distance may be more relevant.
FPS is high but battery drain is not
Try a lower stable target such as 40 FPS/40 Hz or, on OLED, 45 FPS/90 Hz. You can also test a modest per-game TDP limit, reduce brightness, lower GPU-heavy settings, or disable unnecessary background overlays. Valve estimates 2–8 hours for LCD and 3–12 hours for OLED, but actual runtime depends on the game and settings and can fall outside those broad ranges; see the model LCD and OLED specifications.
Performance changes on an external monitor
The built-in-screen recommendations do not transfer automatically to a docked display. A 1080p or higher output requires rendering substantially more pixels than 1280×800. Make a separate profile for the monitor and reduce output resolution or render scale if needed. A dock enables external-display use; it does not improve handheld FPS. See Valve’s Docking Station page for hardware details.
Practical starting profiles by model
Steam Deck LCD
Start a demanding but reasonably optimized game at 40 FPS/40 Hz. If it cannot sustain 40 in its heavy scenes, try 30 FPS rather than accepting repeated drops. Use 60 FPS/60 Hz for a lightweight or older game only when the Deck can maintain it and the extra responsiveness is worth the power use.
Free tools Windows power users keep installed
One-click scans. No signup required.
Steam Deck OLED
Try 45 FPS/90 Hz for a game that remains stable at 45 in demanding scenes. If it does not, use 40 FPS/40 Hz or 30 FPS/90 Hz according to the game’s performance and your preference. Reserve 60 or 90 FPS for titles that can sustain those rates; the 90 Hz panel is an option, not a guarantee of higher rendering performance.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
