Your First Proton 11 Steam Deck Verify Pass - One Evening 2026

Proton 11 goes stable. Your Discord fills with "should we retest the demo?" Nobody wants to say yes, because retesting means two hours on a Deck with a sticky note. Nobody wants to say no, because last time Experimental ate audio and support tickets blamed the trailer.

This is a beginner evening tutorial for proton 11 steam deck: install Proton 11.0-1, pin it, run a bounded smoke on your indie build, choose native Linux vs Proton, and file a receipt - not a full Deck Verified autumn refresh week, and not a Proton Experimental silent-demo recovery. Official release: Proton 11.0-1 on GitHub. Partner criteria: Steam Deck compatibility. Log tooling cousin: 16 ProtonDB / Deck log export tools. Battery cousin: Deck OLED idle drain help.

Evidence note: Primary keyword proton 11 steam deck. Demand signals include Semrush-tracked steam deck parent volume and strong GitHub release engagement on proton-11.0-1. SERP gap: changelogs and player install tips; this URL adds a studio one-evening verify ritual with gates and a receipt.

Non-repetition: This is not the Deck Verified autumn refresh (full cert-lane prep). It is not the ProtonDB log listicle (incident zip tooling). It is not the silent Proton Experimental case study (audio recovery narrative). Same Deck stack, different job: first verify after Proton 11 stable.

Why this matters now (July 2026)

Proton 11.0-1 moved from beta to stable around July 7, 2026, rebased on Wine 11.0, with component updates (DXVK, vkd3d, Wine Mono, FEX) and a long list of newly playable / fixed titles plus Deck-relevant input fixes - including Hollow Knight wrongly registering the Deck Steam button as a left trigger (release notes, GamingOnLinux).

What changed for micro-studios:

1. Stable pin target moved - "works on Experimental" is not a July receipt anymore.
2. Wine 11 rebase can fix strangers and break your edge case - you only know by smoking your build_label.
3. Deck input quirks in the changelog prove Valve is still landing handheld-specific fixes - retest glyphs and Steam button behavior.
4. Compatibility ratings still need criteria - Verified / Playable / Unsupported / Unknown per Steamworks compat docs.

Direct answer: Tonight, install Proton 11 on a Deck (or SteamOS machine), force your demo/app to that pin, run the smoke table below, decide native Linux depot vs Windows+Proton, and latch P1–P6 with proton_11_verify_ok: true only if the receipt matches.

Who this evening is for

Time: about 90–120 minutes for a first pass on one build_label.
Prerequisites: Steam Deck or SteamOS device; partner build or local Windows build installable on Deck; written golden path (5–10 minutes of play); willingness to not promote during the smoke.

Who should skip tonight

• Teams mid-full Deck Verified resubmit - use the autumn refresh playbook instead.
• Teams hunting log zip tooling only - use the 16-tool listicle.
• Teams with a known silent audio regression - start with the Experimental Vulkan/audio case study, then return here to pin 11 stable.

What Proton 11.0-1 is (studio-relevant bits)

From Valve's release (GitHub):

Beginner mnemonic: Proton = Windows game on Linux Deck. Proton 11 = new translation layer. Your job = prove your game still speaks.

Native Linux vs Proton (decide before you smoke)

Steamworks is explicit: games without native Linux builds run through Proton on Deck; native Linux builds are preferred when present (compat docs).

Developer rule: Record runtime_path: native_linux | proton_11_0_1 in the receipt. "Works on Deck" without the path is marketing fog.

Evening script - minute by minute

If you stall: At 0:30 with wrong Proton version, fix pin before play. At 1:00 with broken glyphs, stop and file fail - do not "finish the evening" on keyboard mode. At 1:40 with silence, jump to the silent demo case study before blaming art.

Compatibility checklist mapping (Verified intent)

Use Valve's public criteria as your smoke spine (compat docs):

Honest scope: One evening does not equal a Valve review. It equals "we are not surprised by Proton 11 on Monday."

Install and pin - beginner path

1. On Deck Desktop or Steam Big Picture, open Steam.
2. Search Proton 11 in the store / tools and install.
3. Library → your game → gear → Properties → Compatibility.
4. Enable "Force the use of a specific Steam Play compatibility tool."
5. Select Proton 11.0-1 (exact string may show as Proton 11).
6. Screenshot the dropdown → n0_proton_pin.png.

Creator tip: If the game has a native Linux build and you intended native, do not force Proton - confirm the launch path in the receipt.

Pin troubleshooting (first 20 minutes)

Developer note: First boot after a Proton major can compile shaders for several minutes. Do not fail P3 during that window unless the game never reaches an interactive frame.

Input and overlay smoke - what "pass" looks like

Valve's Verified bar wants default controller config to reach all content, matching glyphs, and workable text entry (compat docs). Translate that into five timed checks:

1. Move + confirm through your first combat or puzzle beat.
2. Pause menu - every leaf reachable without touch.
3. Glyph audit - pause, confirm, and cancel show Deck (or correct Steam Input) icons, not mouse/keyboard.
4. Text entry - if you name a save or character, Steam keyboard or in-game controller entry works.
5. Overlay - Steam button opens overlay; resume returns to a live game (no soft-lock).

Proton 11's changelog called out Deck Steam-button / trigger mis-registration in another title. Treat that as a reminder: retest the Steam button path even if Proton 9/10 "was fine."

Performance glance (not a full TDP study)

Verified intent cites a playable default around 30fps at 800p on Deck. Tonight you only need a glance, not a week of MangoHud:

Write one line in the receipt: fps_note: "menu_stable_play_approx_40". Numbers can be approximate tonight; honesty beats fake precision.

Smoke artifacts to keep

Zip pattern can follow the Deck log listicle when players report failures later - tonight is developer-attested smoke.

Gates P1–P6

Latch: proton_11_verify_ok = P1 ∧ P2 ∧ P3 ∧ P4 ∧ P5 ∧ P6.

Receipt schema - proton_11_verify_receipt_v1.json

{
  "schema": "proton_11_verify_receipt_v1",
  "project": "your-game-slug",
  "build_label": "demo-2026-07-19a",
  "deck_model": "oled",
  "steamos_version": "noted",
  "runtime_path": "proton_11_0_1",
  "proton_version": "11.0-1",
  "wine_rebase": "11.0",
  "native_linux_depot": false,
  "controller_golden_path": true,
  "glyphs_match": true,
  "text_entry_ok": true,
  "overlay_ok": true,
  "unsupported_warning": false,
  "fps_note": "stable_menu_and_play_approx_40",
  "release_notes_url": "https://github.com/ValveSoftware/Proton/releases/tag/proton-11.0-1",
  "gates": {
    "P1": true,
    "P2": true,
    "P3": true,
    "P4": true,
    "P5": true,
    "P6": true
  },
  "proton_11_verify_ok": true,
  "owner": "engineering-lead",
  "notes": "Forced Proton 11.0-1; native Linux depot not shipping this SKU."
}

Worked examples

A - Windows-only Unity demo

Force Proton 11.0-1. Smoke glyphs and overlay. If Steam button misbehaves in menus, note it - Proton 11 specifically fixed a Steam-button-as-trigger class bug in another title; your UI may still need Steam Input tuning.

B - Godot with Linux export

Prefer native. Confirm Deck launches the Linux depot. Still run glyph/text checks - native does not skip Verified criteria.

C - Previously pinned Experimental

Re-pin to 11.0-1 stable. Do not leave Experimental as "the Deck default" after a silent week (case study).

D - Approaching Deck Verified submit

Tonight's pass is preflight. Schedule the full autumn refresh before partner submission.

Company diligence paragraph (copy)

On we retested build <build_label> on Steam Deck (<lcd|oled>) using Proton 11.0-1 (Wine 11 rebase per Valve's proton-11.0-1 release) or native Linux as recorded. Controller golden path, glyph match, text entry, and overlay checks passed per internal gates P1–P6. Receipt: proton_11_verify_receipt_v1.json. This evening pass does not replace Valve's compatibility review; it documents our pin and smoke after the Proton 11 stable move. Criteria reference: Steamworks Deck compatibility.

Facilitator Discord line (copy/paste)

“Proton 11.0-1 is our Deck pin for <build_label>. Please force that compatibility tool (or use the native Linux depot if your invite says so). If boot, glyphs, overlay, or audio fail, upload deck-logs-<build_label>-<date>.zip with pin screenshot + REPRO_STEPS.txt - do not ‘fix it’ by switching to Experimental mid-thread.”

Pin this when you promote after the evening pass. Pair later incidents with the 16-tool log export list.

Minimal verify sketch (optional CI cousin)

Studios that already gate BUILD_RECEIPT fields can add a boolean without inventing Valve's review:

#!/usr/bin/env bash
# verify_proton_11_smoke.sh — local honesty check against receipt JSON
set -euo pipefail
RECEIPT="${1:-proton_11_verify_receipt_v1.json}"
python - <<'PY' "$RECEIPT"
import json, sys
r = json.load(open(sys.argv[1], encoding="utf-8"))
assert r.get("schema") == "proton_11_verify_receipt_v1"
assert r.get("proton_version", "").startswith("11")
assert r.get("runtime_path") in ("native_linux", "proton_11_0_1")
gates = r.get("gates") or {}
ok = all(gates.get(k) is True for k in ("P1","P2","P3","P4","P5","P6"))
assert ok and r.get("proton_11_verify_ok") is True
print("proton_11_verify_ok")
PY

This does not prove you ran on Deck hardware - it only fails CI when someone marks green without filling gates. Hardware attestation still lives in screenshots + owner field.

Decision tree after the evening

Cold launch OK?
  No → file fail; check pin / native depot; do not promote
  Yes → glyphs + golden path OK?
        No → Steam Input / UI fix; re-run P4
        Yes → overlay + text OK?
              No → fix hang / entry; re-run P5
              Yes → submitting Verified soon?
                    Yes → schedule autumn refresh week
                    No → latch receipt; message facilitators; optional tool listicle later

Common mistakes

1. Smoking Experimental while calling it Proton 11.
2. No build_label - useless for support.
3. Keyboard mode to "finish" the checklist - fails glyph honesty.
4. Skipping overlay - fest players open it constantly.
5. Assuming native Linux without confirming Deck used it.
6. Confusing this evening with Verified submission.
7. Ignoring changelog Deck input fixes - retest Steam button / hotplug.
8. No screenshot of the pin dropdown.

How this pairs with other Deck URLs

Key takeaways

• Proton 11.0-1 stable (July 2026) is a Wine 11 rebase - retest your build, do not trust changelogs alone.
• One evening: install, pin, smoke, receipt - not a full Verified review.
• Record native Linux vs Proton 11 explicitly.
• Map smoke to Valve themes: controller, glyphs, text entry, performance, seamlessness.
• Capture pin screenshot + golden-path notes.
• Latch P1–P6 with proton_11_verify_receipt_v1.json / proton_11_verify_ok.
• Keep distinct from Verified refresh, log listicle, and Experimental recovery.

FAQ

How do I install Proton 11 on Steam Deck?

Search for Proton 11 in Steam and install the tool, then force it under the game's Compatibility properties (release).

Does Proton 11 replace Steam Deck Verified testing?

No. Verified is Valve's review against the compatibility checklist. This evening is your internal pin smoke after Proton 11 stable.

Should I use Proton Experimental instead?

Not for a "Proton 11 verify" receipt. Pin 11.0-1 stable unless you are deliberately chasing a fix that only exists on Experimental - and document that exception.

Do I need a native Linux build?

Not required to run on Deck - Windows builds use Proton - but native Linux can be smoother and avoids Proton-only bugs (compat docs).

What framerate should I target tonight?

Verified intent cites a playable default around 30fps at 800p on Deck. Tonight, note whether the golden path feels playable; deep profiling can wait.

What if glyphs show keyboard icons on Deck controls?

Fail P4. Fix Steam Input / UI glyph routing before claiming verify - see also Deck glyph tooling posts in related reads.

What does proton_11_verify_ok mean?

All gates P1–P6 passed and the JSON matches what you actually ran on that Deck and build_label.

LCD vs OLED - do I need both tonight?

One device is enough for a first Proton 11 pin smoke. Record the model. Before a Verified submit or major fest demo, smoke both if you own both - battery and brightness differ even when Proton path matches.

Can players "verify" for us via ProtonDB?

ProtonDB reports help triage, but they are not your studio receipt. Use them as signals; still run the evening pin smoke on your build_label (ProtonDB).

What if Wine 11 breaks our anti-cheat or overlay?

Fail P3/P5 honestly. Document the blocker; consider native Linux, a different Proton pin with an explicit exception note, or delaying Deck marketing until fixed. Do not ship a green receipt with a red overlay.

How does this pair with the verification tools listicle?

This tutorial is the ritual. The upcoming 14 Free Steam Deck Verification Tools After Proton 11 row is the toolkit. Link them; do not merge intents.

Conclusion

Proton 11 steam deck work is not a changelog vibe check - it is a pinned evening with screenshots and a receipt. Install 11.0-1, force or confirm the runtime path, smoke controller/glyphs/text/overlay, and latch proton_11_verify_ok only when honest. Then schedule full Verified prep if a partner review is next. Bookmark this beside the autumn refresh and the Deck log toolkit so each URL keeps its job.

Related reads

• Steam Deck Verified Autumn 2026 Refresh
• 16 Free ProtonDB and Steam Deck Log Export Tools
• We Recovered a Silent Fest Demo After Proton Experimental Vulkan Loader Regression
• Steam Deck OLED Idle Menu Battery Drain Help
• Wednesday Demo Build Smoke Ritual
• Your First Steam Crash Symbolicate Receipt
• Proton 11.0-1 Release (Official)
• Steam Deck Compatibility (Steamworks)