The little green tick says Verified. You install fourteen gigabytes with real optimism. The game launches, runs at what feels like a slideshow, and the fan makes a noise usually associated with departing aircraft.
The Deck was not lying, exactly. It was answering a different question from the one you asked.
What "Verified" actually promises
Verified means the game works: it launches, the controls are mapped, the text is legible at 800p, and it does not require a login box you cannot type into. Those are compatibility guarantees.
What it does not promise is a frame rate. A Verified game can run at 22fps with the fan at maximum and still be Verified, because it technically works. Fine print doing an enormous amount of load-bearing.
The order matters more than the settings
Most people open the graphics menu and start flipping things at random. There is a correct sequence, because two of these changes are worth more than all the others combined.
1. Cap the frame rate first. Not last — first. Use the Deck's own frame limiter (the QAM, the little cog) rather than the game's. Pick 40 if the game can hold it, 30 if it cannot.
A locked 30 feels dramatically better than a floating 35-to-50, because your eyes object to variance far more than to a low number. Consistency reads as smooth. Fluctuation reads as broken, even when the average is higher.
2. Match the refresh rate to the cap. This is the step everyone skips and it is nearly free. Set the display to 40Hz alongside a 40fps cap, or 30Hz with 30fps. Each frame is then shown for exactly one refresh, which removes the uneven pacing that makes a capped frame rate still feel wrong.
40fps at 40Hz is one of the genuinely great tricks of this device. It sits perceptually much closer to 60 than the numbers suggest, and it costs a fraction of the power.
3. Now open the game's settings, and only now.
What actually costs frames on this hardware
The Deck's weak point is not raw shader power. It is memory bandwidth, shared between CPU and GPU. So the expensive settings are the ones that move a lot of data, not the ones that sound impressive.
Turn these down first — they cost the most and show the least:
- Shadows — from Ultra to Medium is frequently 10–15% of your frame time back for a difference you will not notice on a seven-inch screen
- Volumetric fog / clouds — brutally expensive, almost invisible at this size
- Screen-space reflections — expensive, and mostly visible in puddles you are not looking at
- Ambient occlusion — Medium is plenty; Ultra is money set on fire
- Ray tracing — if the option exists, it is not for this machine
Keep these up — they are cheap and they are what you actually see:
- Texture quality — nearly free if it fits in memory, and the single biggest factor in whether a game looks good
- Anisotropic filtering — effectively free, keeps floors from turning to mush
- Level of detail / draw distance — medium is fine, but do not gut it; pop-in is more distracting than soft shadows
Resolution and the thing to do instead
The native panel is 1280×800. Dropping below that is a real performance lever, but doing it crudely makes everything mushy.
Use the upscalers instead. FSR at Quality, or the game's own implementation if it has one, renders at a lower resolution and reconstructs — which looks substantially better than simply running at 960×600 for a similar cost. On a screen this size the reconstruction artefacts are close to invisible.
Order of preference: the game's built-in FSR/XeSS > the Deck's system-level FSR > lowering resolution directly.
Battery, and being honest about it
Every one of these choices is also a battery decision, and the frame cap is the dominant one. An uncapped game will consume everything available to produce frames you cannot see, then die in ninety minutes.
Rough guide: uncapped and demanding is 1.5–2 hours. Capped at 30–40 with sensible settings is 3–5. A 2D indie game with a 30 cap will outlast your attention span.
The TDP limit in the QAM is the other blunt instrument — capping at 8–10W often costs almost nothing visible in a game already limited to 40fps, and buys a large amount of runtime.
When the answer is "not on this device"
Some games simply do not belong here, and it is kinder to say so than to spend an evening chasing settings. Heavy simulation, dense strategy with thousands of units, anything with a hard CPU bottleneck — the Deck's CPU is the constraint, and no graphics setting rescues a CPU-bound game.
The tell: if dropping every visual setting to Low changes nothing, you are CPU-bound. Stop adjusting. That is the hardware talking.
The five-minute version
- Cap at 40 (or 30) in the QAM
- Set the refresh rate to match
- Shadows, fog and reflections to Medium or off
- Textures high, anisotropic filtering on
- FSR Quality rather than lowering resolution
- TDP to 10W and check whether you notice
Six changes, most of them once per game, and the difference between "why did I buy this" and the reason people are so fond of the thing.