14 Free Steam Store Metadata Export and Diff Tools for Indie Teams - 2026 Fest Prep

You run the Wednesday metadata diff ritual. You still need tools to export live Steam copy, compare it to approved git baselines, and log RED rows without buying enterprise DAM suites.

May 2026 is when fest teams promote demo branches faster than they update FAQs. October 2026 Next Fest multiplies the damage. This Listicle curates fourteen free tools that map to field groups G1–G6 from the Wednesday workflow—capture, diff, log, block promotion.

What you will walk away with

A release-evidence/05-operations/store-metadata/ folder containing weekly live-*.txt exports, approved-*.txt baselines, diff artifacts, and ISO-week logs—proof you did not wing store copy during fest prep.

Why this matters now

1. Branch ≠ page update — Promotion is automated; store text is manual—tools close the gap.
2. FAQ LLM drift — Human diff gates need repeatable exports.
3. Partner dimension 7 — Mock audit compares FAQ to demo.
4. Fest marketing cap — Spend worksheet assumes honest pages.
5. Evidence culture — BUILD_RECEIPT discipline extends to marketing surfaces.

Direct answer: Adopt git diff (Tool 1) + Meld (Tool 2) + spreadsheet log (Tool 6) + Steamworks screenshot discipline (Tool 8) first; add Playwright (Tool 7) when manual copy-paste fails. Re-evaluate the stack after four consecutive GREEN Wednesdays in Tool 6—habit proof matters more than owning all fourteen apps.

Selection criteria

Each tool passed:

1. Free at indie budget for the workflow described
2. Under 45 minutes to first useful output
3. Maps to G1–G6 from Wednesday ritual
4. Evidence-friendly filenames partners understand

How this listicle relates to May 2026 fest cluster

You may already run BUILD_RECEIPT, validate-packet, and Wednesday metadata diff. This article names apps for the Wednesday ritual's export/compare steps—binary integrity without copy integrity still fails mock audit dimension 7.

Who should skip this listicle

• Teams with zero Steam page live yet—publish baseline first.
• Teams with agency-owned store pages—agency must adopt same log format.
• Teams without fest branch plans—tools still help Q3 partner windows.

Everyone else: pick five tools minimum.

The 14 tools

Tool 1 — Git diff (free, built-in)

Version-control approved store copy as plain text. Weekly git diff approved-baseline.txt store-metadata/live-2026-W21.txt surfaces G1–G3 changes in seconds.

Workflow:

1. Commit store-metadata/approved/ when producer signs copy.
2. Each Wednesday export live fields to store-metadata/live/2026-W21-g1.txt (split by group or one combined file).
3. Run git diff --no-index if live folder is not yet tracked—still valid evidence.
4. Paste diff summary into wednesday-metadata-diff-2026-W21.md.

Use for: G1 short, G2 about, G3 FAQ text files.
Pair with: FAQ pipeline faq-approved/ paths.
Beginner mistake: Committing only live exports without approved baseline—diff has nothing to compare.
Pro tip: Tag baselines store-metadata-approved-2026-05-18 when demo scope changes.

Tool 2 — Meld (free, Win/Linux)

Visual side-by-side diff when git line noise overwhelms non-technical reviewers. Producer approves RED fixes in Meld without reading unified diff syntax.

Workflow: Open approved/faq-q03.txt vs live/2026-W21-faq-q03.txt. Red highlights tell marketing what changed on live page without engineer translation. Export Meld comparison PDF only for major partner recoveries—file size matters in ZIPs.

Use for: G3 FAQ paragraph compares.
Limit: macOS teams use Tool 3 instead.
When not to use: Tiny one-line G1 changes—git diff faster.
Pro tip: Screenshot Meld window for partner packets when FAQ recovery mattered.

Tool 3 — VS Code Compare (free)

Select for Compare on two exported .txt files—fast on all platforms. Built-in for teams already living in VS Code for game code.

Workflow: Right-click live-2026-W21-g3-faq.txt → Select for Compare → Compare with approved/faq-bundle.txt. Use Problems panel separately—compare view is for copy truth, not compile errors.

Use for: Quick Wednesday ritual before stand-up.
Pair with: Markdown preview for approved FAQ formatting.
macOS / Windows / Linux: All supported natively.
Pro tip: Add store-metadata/ to workspace multi-root for visibility.

Tool 4 — WinMerge or KDiff3 (free)

Windows/Linux merge tools when Meld unavailable. Three-way merge helps when two people edited Steam copy differently—pick approved lane, reject drift.

Use for: Conflict resolution after emergency fest hotfix copy.
Pro tip: Never merge without producer sign-off row in log.

Tool 5 — curl + html2text or pandoc (free)

Export public store page text for read-only comparison—not authoritative for hidden Steamworks fields. Useful when verifying what players see vs partner view.

Use for: Sanity check G1 live vs your export.
Caution: Respect Steam terms; do not hammer URLs; manual export (Tool 8) stays primary.
Pro tip: Save curl output as live-public-YYYY-MM-DD.txt separate from Steamworks paste.

Tool 6 — Google Sheets or LibreOffice Calc (free)

Track ISO-week RED/YELLOW/GREEN per field group. Columns: week, build_id, G1–G6 status, promotion blocked Y/N, owner.

Use for: Month-view fest prep; operating review slides.
Pro tip: Link sheet row to wednesday-metadata-diff-YYYY-WW.md path.

Tool 7 — Playwright or Puppeteer (free, OSS)

Script repeatable text extraction from store URL for teams with many weekly diffs. Human still judges G3 truth—automation only exports.

Minimal pattern: navigate to public store URL, page.textContent('.game_description') or selectors you validate once manually, write live-public-W21.txt. Selectors break when Valve updates HTML—budget maintenance.

Use for: Scaling Wednesday ritual past manual copy-paste.
Pair with: Wednesday ritual export sketch.
Not for: Replacing Tool 8 Steamworks authoritative fields.
Pro tip: Version script in repo; log version in diff header.

Tool 8 — Steamworks partner manual export discipline (free)

The authoritative source: copy each field into grouped .txt files every Wednesday. No vendor—just procedure. Screenshot depot page for G6.

Field checklist (copy order):

1. Short description (G1)
2. About the game / detailed description (G2)
3. FAQ entries one file per question id (G3)
4. Note trailer URL and screenshot filenames (G4)
5. Confirm base price visible settings (G5)—numbers live in regional worksheet
6. Depots + branches panel screenshot + ids in g6-depots.txt (G6)

Use for: All groups; especially fields public curl cannot see.
Pair with: Demo depot audit.
Time: 12–18 minutes once practiced.
Pro tip: Same person exports weekly to reduce paste variance.

Tool 9 — pre-commit (free)

Block commits that change faq-approved/ without updating faq-promotion-log.md. Hooks echo validate-packet spirit.

Use for: Preventing silent approved-copy edits.
Pro tip: Keep hooks fast—metadata only, not full game compile.

Tool 10 — jq (free)

Query BUILD_RECEIPT.json for build_id when naming live-*.txt exports. Append receipt hash row to Wednesday log automatically in CI.

Use for: G6 linkage; upload_log.csv joins.
Pro tip: jq -r .build_id in export script filename.

Tool 11 — Python difflib (stdlib, free)

Ten-line script metadata_diff.py live.txt approved.txt for unified diff in CI logs. No Meld on headless runners.

Use for: Nightly drift alert when live export automated.
Pro tip: Exit code 1 on non-empty diff—wire to Slack without auto-fixing copy.

Tool 12 — ShareX or Flameshot (free)

Screenshot live Steam store page and Steamworks edit screens for G4 media group and incident response. Visual proof when FAQ text matched but screenshot lied.

Use for: G4; fest incident retro.
Pair with: Screenshot capture listicle.
Pro tip: Filename store-live-W21.png beside text exports.

Tool 13 — markdownlint CLI (free)

Lint approved FAQ markdown before paste to Steam—catch broken lists, heading drift, and [NEEDS_HUMAN] placeholders that should never ship.

Use for: G3 after FAQ Gate D.
Pro tip: Run in CI on faq-approved/ only.

Tool 14 — release-evidence folder template (free, yours)

Not a download—a store-metadata/README.md describing G1–G6 files, Wednesday log naming, and promotion gate checklist. Copy structure from release-evidence taxonomy.

README sections to include:

• Who exports (name role)
• ISO-week filename rules
• RED promotion block policy
• Links to FAQ pipeline and Wednesday ritual
• Sample wednesday-metadata-diff template embedded

Use for: Onboarding contractor writers mid-fest.
Pair with: Partner ZIP map 05_ops/.
Pro tip: Ship last four Wednesday logs in diligence ZIP.

Week in the life (solo dev, fest prep)

Repeat until October; boring logs win.

Tool expansion notes (3–6, 9–13)

Tool 3 — VS Code: Install "Partial Diff" extension only if built-in compare insufficient; avoid extension sprawl.

Tool 4 — WinMerge: Excellent for three-way merges when marketing edited live Steam while engineer updated git—common fest panic pattern.

Tool 5 — curl: Example discipline: one request per weekly export, user-agent string identifying studio, backoff on errors.

Tool 6 — Sheets: Add conditional formatting—RED cells turn red. Executives understand color faster than markdown tables.

Tool 9 — pre-commit: Sample hook message: faq-approved changed without promotion log—commit rejected.

Tool 10 — jq: Combine with upload_log.csv join in Sheets for "which build was live when FAQ lied" timelines.

Tool 11 — difflib: Ship metadata_diff.py in release-evidence/scripts/ beside validate-packet.

Tool 12 — screenshots: Store next to palette swatch exports for visual continuity audits.

Tool 13 — markdownlint: Rule MD041 and friends catch headings; customize .markdownlint.json once per studio.

Tool-to-field-group matrix

Use matrix when onboarding—do not buy tools outside empty cells you actually need.

Deep dive — G3 FAQ toolchain chain

FAQ is highest lie risk. Recommended chain:

1. FAQ pipeline Gate D produces faq-approved/Q*.md
2. Tool 13 markdownlint on approved folder
3. Tool 8 paste to Steamworks
4. Tool 1 diff faq-approved aggregate vs Tool 8 export same week
5. Tool 6 log RED if co-op, AI, or demo scope wrong

Never skip step 4 because "we pasted carefully."

Deep dive — G6 demo depot linkage

G6 is not public store text—it is internal truth:

• Tool 8 screenshot of Steamworks depots + branches page
• Tool 10 jq reads BUILD_RECEIPT build_id
• Tool 12 archives screenshot beside demo depot audit
• Tool 14 README lists depot id strings engineers must copy exactly

Promotion gate blocks when G6 RED even if G1–G3 GREEN.

CI pipeline sketch (Tools 9–11)

Wednesday 09:00 UTC
  → export-live.sh (Tool 7 or 8)
  → metadata_diff.py (Tool 11)
  → if diff: notify Slack, exit 1
  → human marks log GREEN/RED (Tool 6)
  → promote branch only if log allows

Automation notifies; humans promote.

Partner and diligence packet rows

When assembling diligence ZIP:

Shows process maturity without claiming false metrics.

Fest month escalation

Align with fest marketing cap—no ad spend bump when Tool 6 shows G3 RED.

Comparison to screenshot tooling listicle

Run both before October; neither replaces 32px icon gates.

Recommended stack by team size

Budget reality check

None of these tools require subscription. Hidden costs are time:

Compare to one fest-week support meltdown (10+ hours). Tools pay back in May, not October.

Handoff between writer and engineer

Breakdowns happen at handoff boundaries—tools name owners.

Truth audit week tool mapping

During 7-day truth audit:

• Day 1–2: Tool 8 baseline refresh
• Day 3: Tool 1 diff all groups
• Day 4: Tool 12 screenshot gallery vs demo
• Day 5–7: Tool 6 track fixes

Listicle tools operationalize the challenge—not replace it.

Ninety-minute setup sprint

Pairing with adjacent workflows

Common mistakes (seven)

1. Diffing without approved baseline — Everything looks RED.
2. Only Tool 5 public curl — Misses Steamworks-only fields.
3. Automating judgment (Tool 7) — Script says GREEN; FAQ still lies.
4. Skipping Tool 12 screenshots — G4 drift invisible.
5. No Tool 6 history — Cannot prove discipline to publishers.
6. Tool 9 hooks too aggressive — Team bypasses git; fix hooks.
7. Buying tools before Tool 8 habit exists — Process before stack.

Pro tips (six)

1. ISO-week filenames everywhere.
2. Same exporter weekly — reduces paste variance.
3. Block promotion on RED — Tools support gate, not replace it.
4. Attach diffs to Friday Block 5 when interesting.
5. Fest month: add Tool 7 only if manual export slips.
6. Do not diff trailers with text tools — Use screenshot listicle for visual G4.

Key takeaways

• Fourteen free tools support export, diff, log, and gate—not replace human judgment.
• Git + visual diff + spreadsheet + Steamworks paste is the core stack.
• Map tools to G1–G6 from Wednesday metadata ritual.
• Automate export (Playwright, difflib) only after manual discipline works.
• Evidence folder (Tool 14) makes partner questions answerable.
• Pair with FAQ pipeline, demo depot audit, and BUILD_RECEIPT ids.
• October 2026 fest rewards teams who can prove store copy matched build_id.
• Start with ninety-minute setup; fifteen minutes weekly after.
• Tool 8 manual export remains authoritative—automation assists, never overrides.
• Handoff table prevents writer/engineer blame loops during RED weeks.
• Budget time honestly—free tools still cost calendar hours.
• Pair with screenshot and icon listicles for full G1–G6 coverage.
• Contractors should inherit Tool 14 README on day one, not discover exports during a RED week.

FAQ

Are these tools Steam-approved?
They operate on your exports and repos—follow Steamworks terms for any scraping.

Mac team without Meld?
Use Tool 3 or free KDiff3 builds.

Do I need all fourteen?
No—solo teams thrive on five-tool core.

How does this relate to regional pricing worksheet?
G5 commercial group; pricing sheet owns numbers, diff tools catch live drift.

Incident toolkit (when RED hits mid-fest)

Tools do not replace apology discipline— they prove timeline.

Outbound references

• Steamworks documentation — field definitions
• Git diff documentation — baseline compares

Extended FAQ

Can we use only Notion instead of git?
Export Notion to markdown weekly and diff with Tool 1 --no-index—slower but valid for tiny teams.

Does Tool 5 violate Steam ToS?
Use lightly for sanity checks; Tool 8 remains source of truth for partner-facing discipline.

How does this connect to cold-hash challenge?
Different week focus—hash week still run Wednesday mini-diff on G3+G6 before Friday hash.

What about AI disclosure challenge?
Disclosure sprint produces approved G2/G3 source text; these tools prevent post-sprint drift.

Can agencies use our Tool 14 README?
Yes—require agency deliverables as live-*.txt plus diff against your approved baseline, not PDF-only handoffs.

We already use prompt registry freeze—enough?
Registry governs runtime prompts; store FAQ is separate—Tools 1–8 still apply to G3 marketing copy.

Conclusion

Fest branch promotion without metadata diff is a lie accelerator. These fourteen tools make the Wednesday ritual fast enough to keep.

Pick five tools this week. Export once. Diff once. Log once. When October traffic arrives, you will promote branches—not surprises.

Store metadata tooling is boring on purpose—the excitement should be your game, not your FAQ apologizing for co-op that never shipped.

When a partner asks what tools you use, answer with process: Wednesday export, git diff, signed log, promotion gate. The fourteen names are implementation details—the habit is the product.

Bookmark this list beside the Wednesday ritual doc in your evidence folder so new contractors pick tools on day one instead of reinventing exports mid-fest. The goal is not maximum tooling—the goal is never promoting a branch while the FAQ still lies.