The four ratings
| Badge | Meaning |
|---|---|
| Verified | Passes every check. Everything works with no setup from the player. |
| Playable | Works, but the player has to do something: pick a community controller config, open the keyboard manually, or use the touchscreen for a launcher. |
| Unsupported | Doesn't run on that device, usually because of a Proton or hardware incompatibility. |
| Unknown | Not reviewed yet. |
Deck and Machine ratings are separate, but the checks overlap heavily, and a game Verified on Steam Deck is automatically Verified on Steam Machine. None of this affects whether players can buy or play your game, only how it's presented.
The Verified checklist (Deck and Machine)
The default controller configuration must reach all content: Deck's built-in controls, or the Steam Controller's (nearly identical) inputs on Machine. Players must not have to change a setting to turn controller support on.
On-screen button prompts must match the controller in use. Don't show keyboard or mouse prompts to a controller player. The Steam Input API handles this for you.
If players ever type (naming a save, a character), open Steam's on-screen keyboard through the Steamworks API (ISteamUtils::ShowGamepadTextInput or ShowFloatingGamepadTextInput) or provide your own controller-friendly entry.
The default settings must hit 30fps: at 800p on Steam Deck and 1080p on Steam Machine.
Don't tell the player their OS or GPU is unsupported.
Any launcher must meet all of the above, including full controller navigation. Better still, don't have one.
Steam Deck display checks
These are tested on Deck only. Steam Machine connects to screens of every size, so display checks don't apply there.
| Check | Requirement |
|---|---|
| Resolution | Must run at a supported resolution. Native 1280×800 is preferred, 1280×720 is fine. |
| Text size | No UI character smaller than 9px tall at 1280×800. Aim for 12px. A text-size option is strongly recommended. |
Getting reviewed
Games reach the review queue in three ways: automatically, when a back-catalog title matches Valve's heuristics; when Valve decides a game matters to Steam hardware owners; or by requesting it yourself through the Steam Hardware Compatibility Review link in the Technical Tools section of your app landing page. That link isn't available to every partner yet, and Valve is widening access over time.
You can request a compatibility review before launch, but only after your game has passed its standard build review.
You get an email and a point-by-point breakdown for Deck, Machine and other SteamOS devices, plus a preview of the badges players will see.
Publish the results, push a fixed build and request a re-review, or dispute a result you think is wrong. Do nothing and the results publish automatically after roughly a week.
Quick wins
| Common Playable cause | Fix |
|---|---|
| Keyboard prompts shown to controller players | Use Steam Input, or swap glyphs based on the last input device. |
| Name entry needs a physical keyboard | Call the on-screen keyboard API when a text field is focused. |
| UI text too small on Deck | Scale UI with resolution and add a text-size option. |
| Launcher needs a mouse | Remove it, or make it fully controller-navigable. |
| Default settings too heavy | Detect the device and pick a lighter preset on first launch. |