12 Free Steam Frame Verification Tools After Great on Frame - 2026

If you searched steam frame verification tools after Great on Frame started filling in August 2026, you do not need another headset rumor thread. You need a free toolkit that maps to Valve’s live standalone bar — 72 fps at 1728×1728 for VR, Unsupported below 1440, depth/motion-vector recommendations, controller glyphs, and honest “no kit yet” paper smokes — then a receipt before anyone pastes “Frame Verified” on a capsule.

This listicle is that toolkit. It is not the Steam Frame Verified 72fps keep/hold (decision playbook). It is not the 14 Deck verification tools listicle (handheld Proton 11). It is twelve free Frame-oriented utilities and docs for the Great on Frame era.

Why this matters now

Steamworks Frame compatibility defines Verified / Playable / Unsupported / Unknown for local standalone play. Press corrections reminded teams that GDC 90 fps folklore is not the live partner page (Road to VR). Meanwhile Great on Frame shelf growth means players browse Frame-friendly titles more often — competitive pressure without free measurement habits becomes marketing fiction.

Direct answer: Adopt four tools this week — Steamworks compat docs, Performance Assessment Overlay docs, Steam Frame debugging perf graph, and a Frame keep/hold receipt — then expand to the full twelve before any public Verified claim.

Who this list is for

Time: 30 minutes to pick the four-tool minimum; 90–120 minutes for a full kit smoke when you have hardware.
Honest limit: Several tools need a headset, SteamVR, or Windows OpenXR runtime. Without a kit, still run Tools 1–2, 11–12 as paper gates.

Non-repetition

Monday ritual (25 minutes)

1. Paste the Discord brief below.
2. Re-open Steamworks compat — confirm 72@1728 still quoted.
3. Assign verify owner for the active build_label.
4. Separate Frame toolkit from Deck Proton 11 toolkit.
5. File Tool 12 receipt before any “Frame ready” marketing.

Creator Discord paste

Steam Frame verify toolkit — Aug 2026 keep/hold:
• Live bar = Steamworks 72fps @ 1728x1728 (not GDC 90 folklore)
• Four-tool minimum: compat docs + perf overlay docs + Frame debug graph + receipt
• Local standalone only — stream comfort ≠ Verified
• OpenXR tools ≠ mirror-window FPS overlays
• Separate from Deck Proton 11 toolkit
Cite partner.steamgames.com Frame compat — ignore “Gold on Discord = Verified”

Plain-language glossary

Criteria → tool map

The twelve tools

1. Steamworks - Steam Frame Standalone Compatibility Review Process

What: Official criteria and badge definitions.
URL: https://partner.steamgames.com/doc/steamhardware/steamframe/compat
Cost: Free (partner account to act on reviews; docs readable for planning).
When to use: Before any tool night — paste VR 72@1728 and 1440 Unsupported sentences into the receipt.
How (5 min): Open page → copy performance + input + seamlessness bullets → date the paste.
Limits: Docs can update quietly; re-paste monthly.
Pair with: Tool 12 receipt; Frame Verified keep/hold.

2. Steamworks - Performance Assessment Overlay (VR criteria)

What: Partner documentation for SteamVR’s Performance Assessment overlay that measures resolution and frame rate against Frame checklist expectations, including depth/motion-vector warnings.
URL: https://partner.steamgames.com/doc/steamhardware/steamframe/compat/perf_criteria
Cost: Free with SteamVR.
When to use: Any VR title aiming Verified — this is Valve’s measurement language.
How: Follow partner steps to enable the overlay in SteamVR; run a normal-play loop; screenshot VERIFIED/PLAYABLE-style status, average frame time, target frame time; note depth/motion-vector warnings. Check perfcriteria.txt in SteamVR logs when thresholds trip.
Limits: Needs headset session; not for stream-only comfort tests.
Pair with: Tools 3–4.

3. Steamworks - Steam Frame Debugging (perf graph)

What: Official Frame debugging notes including in-headset performance graph (GPU work as FPS/ms, submitted resolution, compositor cost, power).
URL: https://partner.steamgames.com/doc/steamhardware/steamframe/debugging
Cost: Free with SteamVR / Frame tooling.
When to use: When Overlay status fails and you need color-coded compositor vs game GPU clues (green/yellow/red guidance in docs).
How: Enable Show Perf Overlay In VR per debugging doc; capture a turn/combat loop; save screenshots with build label.
Limits: Interpreting colors takes practice; still cite Tool 1 bar in CapEx.
Pair with: Tool 2; Frame developer tools link on the same page cluster.

4. Steam Frame developer tools (Deckard / partner tooling links)

What: Additional free developer performance utilities referenced from Steamworks Frame debugging (“frame-developer-tools” / partner tooling index).
URL: Follow links from https://partner.steamgames.com/doc/steamhardware/steamframe/debugging (GitLab SteamOS / Deckard frame-developer-tools as published).
Cost: Free as published by Valve.
When to use: After Overlay fails and you need Valve’s extra Frame-oriented helpers.
How: Open the linked repo/docs from the debugging page; install only what matches your OS/runtime; re-run the same play loop.
Limits: Tooling pages move — always enter via Steamworks, not a stale bookmark.
Pair with: Tools 2–3.

5. XRFrameTools (OpenXR performance)

What: Free OpenXR performance measurement for Windows — frame rate/interval, CPU segments, live display, binary logs → CSV.
URL: https://github.com/fredemmott/XRFrameTools
Cost: Free.
When to use: OpenXR titles where desktop FPS overlays lie (mirror window ≠ headset).
How: Install release → start XRFrameTools → launch OpenXR app → capture live data for a normal-play segment → export notes into receipt.
Limits: Windows-focused; not a deep engine profiler.
Pair with: Tool 6; engine profiler (11).

6. XR-Telemetry (OpenXR API layer HUD + CSV)

What: Free OpenXR API layer with in-headset FPS/frametime HUD and per-frame CSV timing logs; local-only.
URL: https://github.com/mledour/XR-Telemetry
Cost: Free.
When to use: Cross-runtime OpenXR smokes when you want HUD + logs without modifying game frames.
How: Install layer per repo README → enable HUD and/or CSV → run play loop → attach CSV snippet to receipt.
Limits: Verify against your runtime; report edge cases upstream.
Pair with: Tool 5.

7. RenderDoc

What: Free graphics debugger for frame captures (D3D/Vulkan paths commonly used in XR stacks).
URL: https://renderdoc.org/
Cost: Free.
When to use: When Overlay says you miss budget and you need a GPU capture of a bad frame.
How: Capture a failing moment → inspect draw costs / resolutions → file “suspect pass” notes — do not confuse with Verified badge automation.
Limits: Steep learning curve; capture alters timing.
Pair with: Tools 2–3, 11.

8. Steam Input (layouts + glyphs)

What: Steam’s free controller configuration and glyph system — Steamworks Frame checklist expects Frame controllers, default config covering content, and correct glyphs.
URL: Steamworks Steam Input docs + Steam client configurator (enter via partner Steam Input documentation hub).
Cost: Free.
When to use: Every Frame smoke — FPS PASS with keyboard glyphs FAIL is still a fail.
How: Build a default Frame-oriented layout → verify all content reachable without settings menus → screenshot glyphs during Frame control use.
Limits: Community layouts ≠ default config for Verified.
Pair with: Tool 1 input section.

9. Proton (Steam Play) — Windows builds on SteamOS Frame

What: Free compatibility layer for Windows games on Frame’s Linux OS when you lack a native Linux Arm64 build.
URL: Steam Play / Proton releases (e.g. GitHub ValveSoftware/Proton).
Cost: Free.
When to use: Windows-only titles targeting Frame standalone.
How: Pin a known Proton version for the smoke → retest after Proton upgrades → note Proton-specific Unsupported risks per Steamworks.
Limits: Proton blockers can force Unsupported until fixed — native Linux may be cleaner (Godot Frame playbook).
Pair with: Tool 10.

10. ProtonDB (early warning — not a badge)

What: Free community Proton reports.
URL: https://www.protondb.com/
Cost: Free.
When to use: Before kit night, scan for Deck/SteamOS class issues that may foreshadow Frame Proton pain.
How: Search your title or engine → note recent reports → still run hardware/Overlay smoke.
Limits: Never treat ProtonDB Gold as Frame Verified.
Pair with: Tool 9; Deck toolkit for handheld-only claims.

11. Engine profilers (Unity / Godot / Unreal — pick yours)

What: Free built-in profilers in your engine (Unity Profiler, Godot Debugger/Monitors, Unreal Insights).
Cost: Free with the engine.
When to use: After Overlay fails — find CPU/GPU culprits in your own systems.
How: Profile the same normal-play loop on device or closest XR target → attach top three costs to receipt.
Limits: Engine FPS ≠ SteamVR Assessment Overlay verdict.
Pair with: Tools 2, 5–7.

12. Frame verify toolkit receipt + keep/hold checklist

What: Process tool — dated receipt schema plus the decision playbook so marketing cannot outrun measurement.
URL: Use Steam Frame Verified keep/hold + JSON below.
Cost: Free.
When to use: End of every verify session.
How: Fill gates T1–T8; latch claims only when Valve badge + Overlay evidence align.
Limits: A receipt is not a Steamworks review result.
Pair with: All tools.

Quick-reference table

Four-tool minimum (no excuses)

1. Tool 1 — paste bar
2. Tool 2 — Overlay path when kit exists (else SKIP with reason)
3. Tool 8 — input/glyph paper or kit smoke
4. Tool 12 — receipt

Expand to OpenXR tools (5–6) when your stack is OpenXR-native.

Beginner path - first hour without a headset

1. Tool 1 paste into Notion.
2. Tool 10 skim for Proton landmines if Windows-only.
3. Tool 12 file KEEP_lab_HOLD_sku.
4. Schedule kit night for Tools 2–3.
5. Do not invent Verified from Steam Link comfort.

Developer path - kit evening (90–120 min)

1. Tools 1–3 with normal-play loop.
2. If OpenXR: Tool 5 or 6 for ten minutes.
3. Tool 8 glyph pass.
4. Tool 9 pin if Windows build.
5. Tool 11 if Overlay fails.
6. Tool 12 receipt before Slack announcement.

CapEx four-liner

1. Status: Frame verify toolkit adopted (Tools 1–3 + 12 minimum).
2. Evidence: Dated Overlay screenshot or honest SKIP + compat paste.
3. Ship default: HOLD public Verified claims until Valve badge + Toolkit 12 align.
4. Owner: named QA lead for Frame (separate from Deck owner if both exist).

Sample receipt schema

{
  "receipt": "steam_frame_verify_toolkit_v1",
  "as_of": "2026-08-17",
  "build_label": "frame-smoke-001",
  "cited_bar": "72fps@1728x1728",
  "tools": {
    "T1_compat_docs": "PASS",
    "T2_perf_assessment_overlay": "PASS",
    "T3_frame_debug_graph": "PASS",
    "T5_xrframetools": "SKIP_not_openxr",
    "T8_steam_input": "PASS",
    "T9_proton_pin": "n/a_native",
    "T12_keep_hold": "KEEP_lab_HOLD_sku"
  },
  "motion_vectors_depth": "submitted",
  "notes": "Local standalone only. Not stream test."
}

Failure modes

Worked example - OpenXR action game

Wrong: Capture desktop FPS at 90, cite Godot day-one support, ship “Frame Verified” tweet.
Right: Tool 1 paste → Tool 2 Overlay on combat loop → Tool 6 CSV for hitch → Tool 8 glyphs → Tool 12 HOLD until Valve review.

Relation to Great on Frame shelf growth

More Great on Frame titles raise player expectations. Your toolkit does not put you on the shelf — Valve review does. Tools make your submission and marketing honest while the shelf fills.

Format ladder

Week-two after four-tool minimum

1. Add Tool 5 or 6 if OpenXR.
2. Train one designer on Tool 8 glyph checks.
3. Re-paste Tool 1 after any Steamworks rumor week.
4. Keep Deck and Frame owners different people when possible.
5. Do not merge Machine Verified toolkit nights without a separate receipt.

Kit-access matrix (honest planning)

Lying about kit access in CapEx is worse than writing SKIP.

Shared vs dedicated hardware

If one headset serves Quest, PCVR, and Frame smokes:

1. Book calendar blocks labeled Frame-only.
2. Reset SteamVR settings between programs when overlays disagree.
3. Never paste a Quest FPS screenshot into a Frame receipt.

Tool ownership RACI (tiny studio)

Buying nothing vs buying a kit

This listicle is free-first. A kit still buys Assessment Overlay truth. Budget CapEx for device access separately from “we installed XRFrameTools.” Free software does not replace Steamworks paste night or a Verified keep/hold receipt when SKU copy is on the line. If finance asks what you bought this month, answer with “docs paste + overlay screenshots + KEEP/HOLD,” not a GitHub star count. Treat kit rental or DevKit CapEx as a separate line item when Assessment Overlay truth is required for SKU language.

Company diligence questions

1. Which Steamworks URL and date did we cite?
2. Did we use Assessment Overlay or a desktop FPS counter?
3. Stream test or local standalone?
4. Who owns Tool 12 before marketing ships copy?
5. Are Deck and Frame toolkits conflated?

Comparison - Frame toolkit vs Deck toolkit

Onboarding card

Title: Frame verify toolkit hour
Goal: Four-tool minimum + receipt
Do not: Claim Verified from stream FPS
Done when: Tool 12 filed

Key takeaways

• Great on Frame growth raises the cost of unverified marketing.
• Live bar lives on Steamworks Frame compat — start every night with Tool 1.
• Prefer SteamVR Performance Assessment Overlay and OpenXR-native profilers over mirror-window FPS.
• Steam Input and Proton honesty fail Verified even when FPS looks fine.
• File Tool 12 before any public Frame Verified language; pair with the keep/hold playbook.

FAQ

Can I verify Frame with only Deck tools?

No. Overlap exists (Proton, Steam Input), but Frame has its own Steamworks bar and overlays. Keep separate receipts.

Is XRFrameTools required?

No — required path is Tools 1–2 when you have VR kit. XRFrameTools helps OpenXR timing honesty.

Does submitting motion vectors make me Verified?

No. Recommended for reprojection; FPS/resolution floor still applies (perf criteria).

What if I have no headset?

Run Tools 1, 10, 12; schedule kit night; HOLD SKU claims.

Related to Godot day-one Frame support?

Engine export ≠ verification toolkit. Use both.

Related reading

• Stop Quoting Steam Frame 90 FPS Verified - Read Steamworks Instead 2026 — kill obsolete 90fps quotes before tool nights
• Steam Frame Verified 72fps - Indie Keep Hold Before Summer Window Closes 2026
• Godot Steam Frame Day-One Support - Indie XR Playbook 2026
• 14 Free Steam Deck Verification Tools After Proton 11 - 2026
• Steam Machine Verified - What Indies Should Lock After Great on Machine 2026
• Your First Proton 11 Steam Deck Verify Pass - One Evening 2026
• Steam guide hub