Steam October 2026 Next Fest Demo Depot and Branch Rules - May 2026 Trend Playbook

Your main build is stable. Your fest demo depot still points at last month's playtest branch, carries a missing Steam Input default config, and your producer just learned October 2026 Next Fest locks six weeks out—not six days.

This Trend-Jacking / News Commentary playbook is not a release-notes repost. It is the May 2026 operations read on what micro-studios are actually failing in partner-facing threads and autumn Deck Verified refresh prep: demo depot parity, branch naming discipline, and promotion rehearsal before October traffic—not after the upload button greys out.

Read alongside the six-week timeline lock, vertical slice seven-day drill, and playtest branch evening tutorial.

Who this is for and what you get

Time: ~90-minute first audit; 15-minute weekly refresh May–September 2026.
Prerequisites: Steamworks partner access, demo scope frozen or dated, release-evidence/ habit optional but recommended.

Why this matters now (May 2026)

1. Six-week lock culture — The October timeline treats demo metadata as frozen infrastructure; May is when branches get created wrong.
2. Autumn Deck Verified pressure — Demo-specific Steam Input rejections show up on demo depots, not only main game depots.
3. Evidence stack maturity — Teams running validate-packet scripts expect depot ids in receipts and README maps—not vibes.
4. Fest spend caps — Marketing worksheet assumes demo traffic converts; broken depots burn runway without wishlists.
5. Store art passes — 32px icon gates drive clicks; depots deliver the handshake.

Direct answer: Create fest-demo-depot-audit-2026.md listing depot ids, branch names, Steam Input VDF paths, and last successful promotion + install test date.

What teams are getting wrong (pattern read, not invented metrics)

Public partner discussions and post-mortems in Q1–Q2 2026 clusters repeat five failures—none require AAA budgets:

This playbook turns patterns into checks you can run in May while schedules still bend.

How this differs from the six-week timeline article

The timeline lock post answers when to freeze marketing, scope, and trailer beats. This playbook answers what to verify inside Steamworks so the frozen build is installable:

Use both—neither replaces store art gates or palette lock.

Q2 2026 community signals (why the trend hook is real)

Without citing invented percentages, partner-facing discourse in Q2 2026 keeps returning to:

• Demo depots missing default Steam Input after main-game fixes landed
• Fest uploads blocked while playtest branch passwords still circulate for an old rc
• Creators streaming builds that do not match store "demo" button
• Publishers asking which depot id was in the diligence ZIP

The playbook converts recurring chatter into audit rows you control.

Check 1 — Branch naming and password discipline

Goal: One canonical fest branch string everyone repeats.

Steps:

1. Pick format: nextfest-oct-2026-rc3 (date + rc counter)—avoid demo_final_FINAL.
2. Mirror string in: Steamworks branch, BUILD_RECEIPT build_id, internal Slack topic, and upload_log.csv.
3. Document password rotation owner; stale passwords look like "game broken" in fest chat.
4. If using playtest branch tutorial layout, extend it—do not fork a second naming scheme.

Pass: New teammate can install fest build from written steps without asking engineer.

Red / yellow / green scoring (audit header)

Add at top of fest-demo-depot-audit-2026.md:

Ship rule: No fest marketing increase while any row is RED (spend cap).

Check 2 — Demo depot exists and is in CI

Goal: Demo depot promotion is as automated as main—minus scope.

Pair with partner ZIP naming when partners ask for offline packets—demo slice may omit annex files but must list depot id.

Beginner quick start (30 minutes)

If Steamworks feels overwhelming, do only this:

1. Screenshot your depots page—circle demo vs main.
2. Write the fest branch name in a shared doc.
3. Ask engineer: "When did we last promote demo?"
4. Install demo on a laptop that never had your game.
5. Mark pass/fail in one sentence.

That is enough for May; expand to full audit in June.

CI wiring patterns (micro-studio realistic)

Attach CI run URL to audit rehearsal log—partners increasingly ask which automation produced the fest binary, echoing diligence packet trends.

Security and access control

• Limit Steamworks users who can promote to fest branch.
• Rotate playtest passwords when contractors roll off.
• Never commit passwords to public repos—vault ids in audit only.

A leaked fest password during October is recoverable only if rollback rc is documented today.

Check 3 — Steam Input default config parity (demo depot)

Goal: Demo depot includes the same default controller config story as main, adapted for demo scope.

Steps:

1. Copy controller_config/ structure to demo depot content root per Deck tools listicle checklist.
2. Extend VDF action manifest for autumn archetypes (xbox_elite_*, ps_dualsense_edge, etc.) if main game already did—demo cannot lag.
3. Run Unity Input preflight on demo scene if applicable.
4. Promote with SteamPipe flags your team already documents—no hand-wavy "includes configs."

Pass: Fresh Steam account install launches demo with correct glyphs on Deck and Xbox pad without manual config browse.

Glyph migration reminder (autumn refresh)

If main game already migrated GetGlyphForActionOrigin_Legacy to GetGlyphPNGForActionOrigin, demo must follow in the same promotion cycle—not "after fest." See Deck autumn refresh Change 1 and 48-hour recovery case study for failure shapes.

Check 4 — Cold promotion rehearsal

Goal: Prove install path, not compile path.

Rehearsal script (60 minutes):

If rehearsal fails, freeze marketing spend increases—fix depot before ads.

Check 5 — Store page and demo truth line

Goal: Fest page promises match demo binary.

Cross-check wishlist truth audit:

• Features listed in bullets exist in demo first hour
• "Full game" systems not implied when demo ends at chapter 1
• AI disclosure matches demo build if AI-assisted content ships
• Price and regional rows frozen per fest calendar

May–September rehearsal calendar

Align with fest marketing cap—July is last comfortable month for structural depot fixes.

Template — fest-demo-depot-audit-2026.md

# October 2026 Next Fest — demo depot audit
Updated: YYYY-MM-DD

## Branch
- canonical_branch_name:
- last_promoted_build_id:
- password_owner:

## Depots
| depot | id | last_ci_publish | last_cold_install |
|-------|----|-----------------|-------------------|
| main | | | |
| demo | | | |

## Steam Input
- vdf_path_main:
- vdf_path_demo:
- default_config_present_demo: yes/no
- last_glyph_test_date:

## Store truth
- truth_audit_pass_date:
- known_demo_limits (bullets):

## Rehearsal log
| date | tester | platform | pass/fail | notes |
|------|--------|----------|-----------|-------|

Store under release-evidence/05-operations/fest/ beside finance and pricing worksheets.

Main depot vs demo depot — decision matrix

When uncertain, default to separate demo depot for October traffic—rollback is cleaner.

SteamPipe promotion hygiene (operations, not tutorial)

Document commands your team already uses; the audit file stores last successful invocation, not every flag.

Rollback rule: Keep previous rc tag promotable within 30 minutes during October first 48 hours—pair with 72-hour intake thinking for internal response, not Valve SLA claims.

Never promote from a developer laptop without the same log discipline you expect for SHA256 cold drills.

Engine-specific depot notes

Unity 6.6 / URP

• Demo scene list explicit in build profile—no "all scenes" accidents.
• Input System assets included in demo build profile; verify rebinding preflight on demo scene, not menu-only.main.
• If using Addressables, demo catalog hash must appear in receipt or annex when partners ask.

Godot 4.5+

• Export preset named demo-nextfest-2026 with frozen feature tags.
• Web demo teams: browser SKU rules differ—see itch HTML5 opinion before duplicating Steam demo story on itch.

Unreal

• Chunking can balloon demo size—watch fest download complaints.
• Default input mapping context must ship inside demo pak, not editor-only paths.

Influencer and press key hygiene

Fest keys often map to branches. If branch renames, keys lie.

Add key_batch_id row to audit markdown.

Store surfaces beyond Steam (coordination)

If you maintain two storefronts, fest demo truth on Steam must not contradict secondary demo builds. Weekly hash note in audit is enough for micro-teams—full dual-publish is optional.

Weekend drill — "Depot Saturday" (3 hours)

Success: fest-demo-depot-audit-2026.md has one green cold-install row dated this month.

Producer tabletop (45 minutes)

1. Read branch name aloud—everyone writes same string.
2. Demo depot id from Steamworks—photo screenshot.
3. Assign rehearsal owner for June calendar invite.
4. Agree: no fest marketing spend bump until Check 4 passes (cap worksheet).
5. File audit in release-evidence/05-operations/fest/.

When to escalate to full vertical slice week

If Checks 1–3 pass but demo crashes in first 15 minutes for two testers, switch priority to 7-day vertical slice challenge—depot metadata cannot fix scope creep.

Pairing with evidence and cert lanes

Fest demo depots are not partner cert packets—but diligence readers notice when demo ids disagree with receipts.

Common mistakes (seven)

1. Treating demo as "just a smaller exe" — Metadata parity still required.
2. Promoting only on lead dev machine — Password cache hides auth bugs.
3. Skipping demo in BUILD_RECEIPT — Cannot prove what players got.
4. Last-minute branch rename — Breaks influencer keys and UTMs.
5. Main game Input fixed, demo forgotten — Autumn refresh failure mode.
6. Fest week price edits — Conflicts with pricing freeze guidance.
7. Upload without cold install log — No evidence when Twitter reports crashes.

Pro tips (six)

1. Suffix demo receipts — build_id includes -demo token.
2. Automate depot id in README — Partner ZIP map bullet 3.
3. Schedule promotion after stand-up — Human witness for rollback.
4. Keep one rollback build — Previous rc tag documented.
5. Pair with crash-log challenge — repro folders named by branch.
6. Screenshot Steamworks depot page — Attach to audit monthly.

Snippet-friendly answers

What is a Steam Next Fest demo depot?
A separate SteamPipe depot (or depots) carrying the time-limited fest build, with its own metadata, Steam Input files, and promotion branch—must stay in sync with your lock plan.

When should micro-studios lock demo depots for October 2026?
Structural locks align with the six-week timeline; May–June 2026 is for creating audits and CI, not October panic.

Does Deck Verified apply to fest demos?
Players install demos on Deck; treat glyph and default config parity as fest-blocking if you market Deck compatibility.

Key takeaways

• May 2026 is depot-and-branch month—not trailer month—for October Next Fest.
• Failures cluster on metadata parity, not secret engine tricks.
• Five checks: branch naming, demo depot in CI, Steam Input defaults, cold install rehearsal, store truth.
• Use fest-demo-depot-audit-2026.md as living evidence.
• Demo depots need the same Input manifest discipline as main after autumn refresh pressure.
• Tie build_id to BUILD_RECEIPT and upload logs.
• Cold install beats green CI alone.
• Fix depots before raising fest marketing cap.
• Pair with vertical slice challenge for final-week quality.
• Outbound: verify current requirements in Steamworks documentation before submit.
• May audits prevent October branch rename emergencies that break influencer keys, press keys, and UTMs alike.

Observability during fest week

Minimal analytics still required:

Align with vertical slice Day 7 instrumentation—do not ship fest blind. Evidence cycles beat hourly patch theater during spike.

Post-fest retrospective prompts

Within seven days after October event:

1. Which depot id was live at hour zero?
2. Did cold install rehearsal date slip?
3. Did Steam Input rejections happen on demo, main, or both?
4. Did UTMs prove which traffic source owned installs?
5. Update audit for next fest cycle—filename fest-demo-depot-audit-2027.md if needed.

Outbound references (verify before submit)

• Steamworks festival documentation
• Steam Input documentation
• SteamPipe documentation

Valve can revise requirements; your audit header should note last doc review date.

FAQ

We only ship main depot—do we need a separate demo depot?
Many fest setups use a dedicated demo depot or clearly scoped demo app id—document what Steamworks shows for your app; ambiguity becomes upload-week risk.

Can demo share main depot with a beta branch only?
Possible for some teams; audit must show which branch players receive during fest and that promotion path was rehearsed cold.

What if fest rules change after May 2026?
Re-read official festival pages monthly; update audit header with doc revision date—this playbook is operations discipline, not legal advice.

How does this relate to two-storefront rule?
Secondary storefront demos still need Steam depot truth if Steam is primary fest surface.

We failed cold install—delay fest?
Fix or narrow scope; do not compensate with paid traffic on broken installs. Cold install green is the real fest readiness signal.

Conclusion

October 2026 Next Fest rewards teams whose demo depot story is boring: named branch, promoted build, Input defaults present, cold install logged, store copy honest.

Run the May audit before June CI work lands on the wrong depot. Fest week is too late to discover your demo never had a default controller config.

Save the audit beside your timeline and marketing cap. When production is loud, the markdown file is the calm source of truth.

Micro-studios win October 2026 Next Fest when players press Install and the build that downloads matches the story on the store page—that is depot discipline, and May is when it is cheapest to enforce. Book the next cold install before you book the next trailer shoot. Treat depot audit green rows as a launch gate equal to demo fun—players forgive rough art long before they forgive broken installs.