Run the Steamworks Steam Deck compatibility review workflow and interpret the resulting badge report
domain: partner.steamgames.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Build and test your Linux-native build first if you have one; Valve tests the Linux build before falling back to testing the Windows build under Proton.
Self-test against the Deck compatibility checklist categories — input (full controller support with correct glyphs), display (native 1280x800 rendering, legible text), seamlessness (no mouse/keyboard-required first-run setup), and system support (suspend/resume, no incompatible anti-cheat/DRM).
Submit the build for Valve's Deck Compatibility review from the Steamworks partner site and wait for the point-by-point results.
Review the detailed pass/fail breakdown during the review window before results are published, and fix any failing checklist items you can address quickly.
Track Proton version changes over time and periodically re-test after major Proton updates, since your compatibility rating can be affected by engine-level changes outside your control.
Known gotchas
A regression in a newer Proton version can affect a previously Verified title; Valve pins games to the last known-good stable Proton version until the issue is resolved, so don't assume Verified status is permanent without monitoring.
Anti-cheat or DRM that isn't Linux/Proton-compatible will fail the system-support category outright, regardless of how well the rest of the game runs.
Passing every checklist item yourself is necessary but Valve's own review is still required for the official badge — self-testing doesn't grant Verified/Playable status automatically.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?