Developer checklist
Steam Deck Developer Checklist
Check controller flow, text entry, readable UI, sensible default performance, launcher behavior, device-local graphics settings, and the SteamOS details that are easy to miss.
Compatibility score
Not Verified-ready
0% of Verified gates passed. Fix red items first.
- Verified gates
- 0/75
- Best practices
- 0/55
- Bonus items
- 0/26
0 / 36 items
How to read this checklist
- Verified gates
- Checks based on Valve compatibility requirements. Missing one can keep a game out of Verified territory.
- Best practices
- Valve recommendations and Deck issues players notice quickly.
- Bonus items
- Extra checks that are good for players, but not required for Valve's compatibility review.
SteamOS / Linux Compatibility
Verified Gate: Core Requirements
Input & Controls
Performance
Display & UI
System Integration
General notes
Why this checklist exists
This checklist exists because games still ship with hidden graphics settings, or sync device-specific graphics settings through Steam Cloud, even in 2026. After talking to developers who cared about Steam Deck support, it became clear that some details are just easy to miss. Maybe the guidance was overlooked. Maybe some of it appeared in Steamworks later.
This does not replace Valve's review process. It is a quick pass over the things players and reviewers notice fast: controller prompts that do not match the device, tiny UI text, awkward defaults, missing on-screen keyboard support, launchers that need a mouse, and the other small Deck problems that add up.
The first version came out of a conversation with Steam Flow about where Steam Deck verification, developer assumptions, reviewers, and real players do not always line up.
