Steam Cloud Saves and Progression Claims vs Fest Demo Hour-One Parity - Next Fest 2026 Checklist for Micro-Studios

Your FAQ says local saves only. Your About bullets still mention cross-device continuity. Steamworks still has Steam Cloud enabled for the app. Players quit on laptop, open the Next Fest demo on Deck, see a cloud sync icon flicker, and assume progress follows them into a full game that does not exist yet.

Save lies are subtle store-demo mismatches—partners screenshot FAQ against Settings UI. This Process & Workflow checklist maps cloud saves, cross-progression, carry-over, and meta unlocks to fest demo hour-one proof. Pair with achievements stats parity when saves gate trophies. Anchor ops to Steamworks Steam Cloud documentation. No invented studios or metrics.

Time to read: ~35 minutes. Time to run first save audit: ~2.5 hours with two-device cold install.

Support tickets that cite "lost progress" or "cloud lied" are expensive to close because players attach Steam client screenshots—not gameplay bugs. A thirty-minute Steamworks toggle check in May prevents a fest-week argument about whether your team ships honest infrastructure or marketing fiction.

Why this matters now (May–October 2026)

1. Cloud icon implies product maturity — Players read sync UI as full-game infrastructure.
2. Fest demos reuse main-game Steam app id — Cloud config often left on by default.
3. Cross-save marketing is trendy — 2026 stack narratives tempt vague bullets.
4. Deck + PC testing doubles save risk — Two installs expose sync lies fast.
5. May is config trim month — Disable cloud for demo period before October lock.

Direct answer: Build save-claim-proof.md, test save behavior on two non-dev accounts and two machines, align Steamworks Cloud toggle with FAQ, document in BUILD_RECEIPT, and triangle-diff against About, tags, and hub posts.

Who this is for

Prerequisites

Save claim proof table (core artifact)

release-evidence/02-builds/saves/save-claim-proof.md:

Pass rule: Every progression claim matches what a player sees in Settings and save slots within hour one on fest build.

Two-machine hour-one test (engineer script)

Log in two-machine-save-test.md.

Steamworks Cloud toggle discipline

Document choice in docs/save-policy-fest-2026.md.

BUILD_RECEIPT fields

"save_policy": "local_only_demo",
"steam_cloud_enabled_live": false,
"save_proof_path": "release-evidence/02-builds/saves/save-claim-proof.md",
"two_machine_test_date": "2026-05-20"

Triangle diff (saves leg)

Common mistakes (twelve)

1. Cloud left on from main game config.
2. FAQ says local; UI shows sync.
3. Cross-progression in trailer VO.
4. No two-machine test.
5. Assuming demo namespace isolates—verify.
6. Deck test skipped.
7. Press kit promises carry-over.
8. Save migration code from main branch active.
9. PlayerPrefs + files drift.
10. Ignoring uninstall/reinstall path.
11. October enable cloud without FAQ update.
12. Support macros say cloud.

Worked example (anonymous)

Before: Cloud on; FAQ local only.
Fix: Disabled Steam Cloud for fest; About bullet rewritten; two-machine test archived.
Result: Refund tickets on saves dropped.

Evidence folder layout

release-evidence/02-builds/saves/
  README.md
  save-claim-proof.md
  two-machine-save-test.md
  settings-screenshots-machine-A.png
  settings-screenshots-machine-B.png
  steamworks-cloud-toggle-YYYY-MM-DD.png
  engineer-signoff.txt

Link from release-evidence taxonomy.

Progression claim types (audit all)

Engine implementation notes

Use DEMO_BUILD define to skip cloud init—document in demo build identity pass. Cross-read save migration if versioning exists—demo must not read v2 full-game headers.

Wednesday ritual row

Add Saves to Wednesday ritual: screenshot Steamworks Cloud page + FAQ save row diff—five minutes after gameplay promotions.

validate-packet guards

• save_policy in receipt matches steam_cloud_enabled_live
• save-claim-proof.md zero Fail
• Two-machine test file dated within 14 days of build_id
• Exit non-zero if FAQ claims local and Steamworks shows Cloud enabled

Meta-progression and demo length

If FAQ claims 90-minute demo, saves that unlock week-two progression mislead—map unlock timers in progression-proof-annex.md.

Uninstall / reinstall path

Hour-one test annex:

1. Play 15 minutes, save, exit
2. Uninstall demo
3. Reinstall same branch
4. Confirm only local slot behavior documented in FAQ occurs

Players do this during fest—support tickets follow.

Deck and PC parity

Deck tools: repeat two-machine test with Deck as machine B—cloud UI differs; capture both.

Press, hub, and events

Review key email must state save policy. Hub posts must not say "take your save to launch." Event posts cannot promise cross-save rewards.

Red-team questions

1. "Will my demo save carry to full game?"
2. "Why does cloud icon appear?"
3. "Can I continue on Deck?"
4. "Is progression shared with EA build?"
5. "Support said cloud—why offline?"

Team RACI

Comparison to reactive recovery

Save mismatch screenshots appear in partner ZIPs—May toggle cheaper than October FAQ emergency.

Localization

Translated FAQ must not imply cloud if English disables—localization QA.

Integration with metadata sprint

Day 6d optional: save claims after spec honesty day.

Publisher diligence

Save policy audit <date> — <policy>; two-machine test attached; Steamworks toggle screenshot included.

Mock audit

Engineer demonstrates save behavior live—Settings + slot load on call.

Snippet-friendly answers

Does the Next Fest demo use Steam Cloud?
Only if your FAQ and Steamworks both say so and two-machine tests prove it—default recommendation is local-only for fest demos.

Will demo progress carry to the full game?
State FULL GAME plan explicitly or say no—never imply carry-over without implemented entitlement.

Beginner path

1. Read Steamworks Cloud page.
2. Play demo 20 minutes on PC.
3. Install on second device.
4. Fill proof table.
5. Fix fails same day.
6. Update FAQ row 8 pattern.

October freeze

Lock save_policy September. October: no Steamworks Cloud toggles without full re-test.

Post-patch re-audit

Demo patch notes touching save format trigger two-machine test—tag drift sprint parallel if platform tags involved.

Ads and UTM

No landing copy "sync anywhere" unless proven—UTM experiment discipline.

Asia–EU handoff

Do not toggle Cloud overnight without EU morning proof update—Asia–EU handoff.

Operating review

Friday Block 5: save row when promoting gameplay builds.

5-day metadata freeze

Assign saves to day five in 5-day freeze.

Additional mistakes (eight)

13. Demo reads %USERPROFILE% main-game path.
14. Steam Deck suspend/resume desync blamed on players.
15. Cloud quota errors without FAQ mention.
16. Family sharing + save confusion unaddressed.
17. Families shared libraries test skipped.
18. Save corruption not in crash-log challenge.
19. Property-based fuzzing deferred—see save corruption test article for full game, demo still needs smoke.
20. Assuming Steam Auto-Cloud filename collision impossible.

Schedule save audit the week BUILD_RECEIPT first documents fest build_id.

Carry-over FAQ templates (copy-paste)

Local only (recommended fest default):

DEMO: Saves are stored locally on this device for the Next Fest build. Steam Cloud and cross-device sync are not active in the demo. Progress does not carry into the full game at launch unless we announce otherwise later.

Isolated demo cloud (if you truly ship it):

DEMO: Steam Cloud sync works only between installs of this fest demo on the same Steam account. Progress does not transfer to the full game release.

Full game later (FULL GAME section):

FULL GAME: We plan Steam Cloud support at 1.0—not available in the fest demo.

Pick one block; delete the others from FAQ to avoid contradiction.

Steam Families and borrowed libraries

Steam Families shared libraries can make saves appear "wrong" when borrowers install—FAQ annex: "Saves are tied to the Steam account that installed the demo."

Content descriptors and online features

Content descriptors online interaction flags do not cover cloud—but players conflate them. Keep FAQ explicit.

Short description and save verbs

300-character short description cannot fit save policy—do not use "sync" verbs in G1 if demo is local-only.

Trailer and VO

Trailer frame audit: ban VO lines "continue your journey anywhere" unless proven.

Intake compression partner script

Q: "What is the save model for the fest build?"
A: Open save-claim-proof.md + save_policy in receipt + Settings screenshot—under two minutes.

Correction post if cloud left on by mistake

Subject: Correction — <Game> demo save policy (build_id <id>)

Our store copy previously implied cloud sync. The Next Fest demo uses local saves only.
Steam Cloud has been disabled for this demo period. FAQ updated: <url>

Log in hub if public post referenced cloud.

Producer pre-promotion checklist

• [ ] Steamworks Cloud screenshot matches receipt
• [ ] Two-machine test dated
• [ ] FAQ save row matches Settings
• [ ] About bullets scanned for "anywhere" language
• [ ] Tags lack misleading platform/cloud tags
• [ ] Press email includes save policy sentence
• [ ] validate-packet save dimension exit 0

Cross-surface save policy table

Wishlist truth audit annex

Wishlist truth audit add Day 7c save policy after community hub—closes silent Settings lies.

Metadata sprint eleventh surface

7-day metadata sprint completion should include saves when cloud icon risk exists—most teams skip until refunds arrive.

Cold-hash coupling

After cold-hash week, re-run two-machine test—save path code may ride with binary changes.

Fest marketing cap

Fest marketing cap: no ads emphasizing cross-device play without save proof.

Two-storefront

Itch browser demo saves in localStorage—do not claim Steam Cloud parity on itch page.

Glossary

FAQ expansion

What if Steam Auto-Cloud still uploads files?
Disable in Steamworks or change remote path for demo—verify with network logging if unsure.

Do we mention saves in system requirements?
Only if disk space relevant—save policy belongs in FAQ not GPU rows per spec honesty.

Can we test cloud only internally?
Internal builds may differ—fest public branch must match published policy.

Run uninstall/reinstall test on the same account you use for review key redemption—press installs follow player paths.

Ninety-minute save audit (first pass)

Save file forensics (engineer annex)

Document in save-path-forensics.md:

• Absolute path on disk for demo slot
• Whether main-game folder name appears in path
• File size after 20-minute session
• Whether cloud remote file exists in Steam userdata when policy is local-only

If userdata contains cloud files while FAQ says local, toggle is lying.

Partner ZIP README bullet

Add under builds section in partner ZIP map:

Fest demo save policy: <policy>; evidence: save-claim-proof.md; two-machine test date: <date>.

Vertical slice and save expectations

Vertical slice opinion: slices can still be local-only—do not imply persistent MMO-style accounts.

Regional and legal copy

EU players ask about data residency when cloud mentioned—if cloud off, FAQ can say local device storage only; if cloud on, link privacy policy per privacy templates.

Operating review metric

Four Friday five-block review: track save-related refund tags weekly—spike means proof table stale.

Evidence cycles

Evidence cycles opinion: typo fixes to FAQ save row batch weekly; policy changes same-day with two-machine test.

Hash mismatch parallel

Hash case study culture applies—save policy is another receipt field partners expect to match live behavior.

Sample proof rows (expanded)

Row — About bullet:

Row — Steam Deck suspend:

Gameplay resume issues belong in crash-log challenge—save policy still must not promise cross-device sync when broken.

Canonical save-policy.md in git

One file lists:

• save_policy enum: local_only | demo_cloud | full_game_cloud_later
• FAQ paragraph id to paste
• Steamworks toggle target state
• Whether carry-over to 1.0 is promised (yes/no/date)

All surfaces copy from this file—never improvise per channel.

Key takeaways

• Save claims are Settings-visible promises.
• save-claim-proof.md + two-machine test.
• Steamworks Cloud toggle must match FAQ.
• Triangle-diff saves across store surfaces.
• BUILD_RECEIPT save policy fields.
• May config trim before October.
• Pair with achievements when saves gate unlocks.
• Use FAQ templates for local-only vs isolated demo cloud.
• Producer checklist before promotion.
• Uninstall/reinstall path in hour-one annex.
• Metadata sprint eleventh surface when Cloud UI visible.
• Canonical save-policy.md in git for all surfaces.
• Save file forensics when userdata disagrees with FAQ.
• Screenshot Steamworks and Settings on promotion day.
• Mock audit should demo Settings live when partners ask.

FAQ

Can demo use Steam Cloud for small slice?
Yes with isolated namespace and explicit DEMO FAQ—prove with two-machine test.

What about cross-save to console later?
FULL GAME labeled; not fest demo scope.

What if players expect Early Access cloud from main game news?
Fest demo is separate scope—FAQ must state demo policy and deny carry-over unless implemented.

Does mock audit cover saves?
Add live Settings demonstration—fail if cloud enabled while FAQ says local.

Can we ship with cloud on but sync disabled in code?
No—players still see cloud UI; disable in Steamworks or explain honestly in FAQ.

Conclusion

Players notice cloud icons before they read bullet lists. A fest demo that flickers Steam Cloud while FAQ swears local-only teaches the same distrust as a co-op lie.

Turn off cloud unless you prove sync. Test two machines. Write the policy once in FAQ and copy it everywhere.

Run the two-machine test before you send the next review key batch.

When metadata sprint marks store surfaces green, add saves as the eleventh surface if Steam Cloud can appear in Settings—silent UI beats silent FAQ every time.

Players forgive short demos; they do not forgive a cloud icon that promises continuity your fest zip never implemented. Archive Steamworks and Settings screenshots on the same day you promote—partners date-match evidence to build_id promotions. If your team cannot run two machines this week, run two Windows user accounts on one PC as a minimum bar before sending review keys. Open save-policy.md before you open the Steamworks Cloud page—policy first, toggles second, screenshots third, always, before any keys go out.