Steam Back Catalog Monetization After Record H1 2026 - Indie Keep Hold

If you ship on Steam in August 2026 and your Discord still argues “discount everything because the platform is huge,” you are solving the wrong problem. Alinea Analytics estimates that Steam’s first half of 2026 was another record year for the storefront—about $11.1B in estimated consumer spend, up roughly 14.5% year over year versus H1 2025—with roughly 79% of that spend landing on the steam back catalog and only about 21% on new releases. The mix has been sliding for years: new-release share of H1 spend moved from about 29% (H1 2024) to 27% (H1 2025) to 21% (H1 2026). That is not a pep talk. It is a keep/hold brief: protect launches that still need full-price discovery, and deepen discounts only on SKUs that already behave like catalog.

This article is for micro-studios that own one live SKU, or a small slate of older packages plus a launch candidate. It is not a seasonal opt-in checklist. For Autumn Sale dates, Discount Management rows, and join/sit-out rituals, use the dedicated Steam Autumn Sale 2026 discount playbook. For list price, regional floors, and bundle math, use how to price and bundle indie games in 2026. For tooling that supports wishlist hygiene and store audits without inventing policy, see 15 free Steam marketing and store optimization tools. The Steamworks rules that gate every keep/hold decision live in Valve’s Discounting and Seasonal Sales docs—cite those pages, not a screenshot of someone else’s Discord.

Time estimate: 60–90 minutes for a single-SKU studio with a clean price history; 2–3 hours if you have multiple packages, a launch inside 30 days of a planned sale, or a price increase still cooling down.
Honest limits: Alinea’s H1 figures are third-party estimates, not Valve revenue. Steamworks discount rules can change—re-read Discounting before you enter a cut. Seasonals do not waive release or price-increase cooldowns. A custom discount on the same calendar dates as a seasonal is not the seasonal path. This piece does not replace the Autumn Sale playbook or the pricing/bundle guide.

Non-repetition note: Do not treat this URL as a second Autumn Sale checklist. The Autumn article owns Oct 1–8, 2026 join/sit-out, seasonal Discount Management screenshots, and October forward sheets for Cooking / Next Fest / Scream. The pricing guide owns list price, regional strategy, and bundles. This page owns the H1 mix shift decision: which SKUs stay KEEP (launch protection / full-price discovery) versus HOLD-for-depth (catalog stair-step discounts) before those seasonal nights. If your only output tonight is “join Autumn at 40%,” you opened the wrong article.

Why this matters now (August 13, 2026)

Steam’s H1 2026 story is not “indies should panic-discount.” It is that catalog depth already wins most of the spend, while new releases still fight for a shrinking slice. Alinea’s write-up of another record half—about $11.1B, roughly 79% back catalogue / 21% new releases, up about 14.5% versus H1 2025—sits next to a multi-year trend: new-release share of H1 spend falling from about 29% → 27% → 21% across H1 2024 → 2025 → 2026 (Alinea). For a micro-studio, that mix means two different jobs on the same partner account:

1. Launch protection — keep a young SKU readable at full price long enough for wishlists, reviews, and algorithm-adjacent visibility to form. Burning a deep cut too early can collide with Steamworks cooldowns and teach buyers to wait.
2. Catalog depth — treat older packages as the engines that fund the slate. Stair-step discounts, seasonal participation, and wishlist-email floors (≥20% on the lowest-priced package when you want emails) live here—not on every new AppID the week after launch.

August is the right week to write that split down. Autumn Sale (October 1–8, 2026) and October Next Fest pressure arrive fast; demo signup and seasonal Discount Management are different products (Next Fest press preview decide). If you wait until September “% FOMO,” you will collapse KEEP and HOLD into one panicked cut and then discover a cooldown or a wishlist-email miss after the fact.

Three clocks drive this evening:

Beginner Monday path - one evening KEEP / HOLD / MIX

Use this when someone says “H1 was record, so we should discount” and nobody can name which AppID is launch-protected.

Prerequisites

• Partner account access to Discount Management and package pricing history
• Release date and last price-increase date for each live package
• A one-line product goal for the next 90 days (reviews, wishlist conversion, cash for payroll, visibility for DLC)
• The Autumn Sale playbook open in another tab for seasonal dates—not for tonight’s SKU labels

Evening steps (about 60–90 minutes)

KEEP / HOLD / MIX decision table

Common beginner mistake: labeling the whole account HOLD because “Steam is 79% catalog.” Catalog share is a platform mix estimate, not a permission slip to cut your only launch SKU.

First-path example (single SKU)

You released six weeks ago. Reviews are thin. Autumn is seven weeks out. KEEP until release cooldown and a written discovery goal clear. Do not invent a “soft 25% custom now so we learn discounts.” Learning that creates a discount cooldown that can block later custom events—and seasonals still care about release and price-increase cooldowns.

First-path example (two SKUs)

Base game from 2024, DLC from last month. HOLD the base with a stair-step toward Autumn. KEEP the DLC until its own cooldown and discovery goals clear. That is MIX by SKU—not “one studio policy.”

What the H1 mix actually means for single-SKU vs multi-SKU micro-studios

Alinea’s H1 2026 sketch—record spend around $11.1B, about 14.5% up versus H1 2025, roughly 79% back catalogue versus 21% new releases, with new-release share drifting 29% → 27% → 21% across three H1s—describes the storefront’s wallet split (Alinea). It does not mean every indie should behave like a publisher with a deep franchise ladder.

Pattern language (no fake case studies)

Use patterns, not invented studio war stories:

Single-SKU micro-studios feel the mix as pressure, not as permission. Buyers already trained on deep catalog discounts will wait—especially after record H1 headlines. Your job is to decide whether waiting is acceptable for this SKU this quarter. If you need reviews and wishlists more than an immediate conversion spike, KEEP. If the SKU is already past its discovery window and payroll needs cash, HOLD with a written ladder.

Multi-SKU micro-studios feel the mix as allocation. Put discount energy on packages that already convert on sale. Keep launch SKUs readable. Do not “synchronize” every AppID to the same % because a competitor screenshot looked tidy.

Companies evaluating a partner or acquisition should treat Alinea’s numbers as market context, not as diligence proof that a target’s catalog is healthy. Ask for the studio’s KEEP/HOLD sheet, cooldown dates, and whether Autumn participation is seasonal Discount Management or a custom overlap myth.

Steam discount rules that matter for keep/hold

Policy lives in Steamworks. Summarize for decisions; re-read the primary docs before you click submit.

Cooldown family (plain language)

Keep/hold mapping

• KEEP often means “release or price-increase cooldown still active” or “we choose not to burn a custom discount cooldown before a better seasonal.”
• HOLD means “eligible and intentionally deepening.” Clear the 20% floor on the lowest package if wishlist emails are part of the plan.
• Never assume a themed fest discount “uses up” Autumn. Themed events usually obey the discount cooldown; seasonals are the documented exception path—still blocked by release/price-increase rules.

Eligibility and specials visibility (high level)

Steam’s specials and sale surfaces expect released, eligible packages entered correctly. Coming Soon pages and demos are not “join the Autumn Sale as if it were a release.” Demo visibility belongs on the Next Fest track. Store optimization tools help you audit capsules and tags—they do not override cooldown math (tool list).

Catalog ladder worksheet - Harbor Loop (illustrative only)

The following studio and numbers are a worksheet, not real sales data, not Alinea figures, and not a claim about Valve. Use the structure; replace with your packages.

Fictional studio: Harbor Loop Games
Packages: Harbor Loop (base, released 2024), Harbor Loop: Night Shift (DLC, released March 2026), Harbor Loop 2 (upcoming—Coming Soon, not discountable as a seasonal product yet)

Starting labels (August 13 evening)

Illustrative stair-step % (HOLD base only)

Worksheet fields to copy into your sheet

1. Package name / AppID
2. Release date / last price increase
3. KEEP / HOLD / MIX
4. Next eligible discount date (by rule)
5. Next planned % and whether ≥20%
6. Seasonal vs custom path
7. Owner + review date

How to read the ladder: depth increases on HOLD packages over months so buyers see a story, not a random 70% the week after a 25% custom. KEEP packages stay off the ladder until a written graduation criteria fires (for example: release cooldown clear and review count goal and no conflicting launch week).

Graduation criteria example (write your own)

Harbor Loop’s fictional rule for Night Shift: move from KEEP to HOLD only when (a) release cooldown clear, (b) ≥N reviews or a written “enough signal” note, (c) base game Autumn plan already filed so DLC % does not collide with a confused Discord paste. Until then, DLC stays KEEP even if H1 headlines scream catalog.

Wishlist and visibility gates

Discounts without visibility planning waste cooldown budget.

Beginner path: if you only remember one number from this section, remember 20% for wishlist emails—and that it applies to the lowest-priced package, not “whatever package we feel like featuring.”

Developer path: log the package ID you used for the 20% floor in the receipt. Finance decks that say “we did 20%” without naming the package fail diligence.

H2 calendar keep/hold - before Autumn Oct 1–8 2026 and October Next Fest

This calendar is a SKU-label calendar, not a replacement for the Autumn join/sit-out ritual. Pair it with the Autumn Sale 2026 playbook when you enter Discount Management.

Forward sheet template (plain text)

H2 keep/hold forward — date: 2026-08-13
SKU: ________  Label: KEEP / HOLD / MIX
Release cooldown clear by: ________
Price-increase cooldown clear by: ________
Sep custom: yes / no / % ____  (cooldown impact noted: ____)
Autumn Oct 1–8: join / sit-out / N/A  via seasonal DM: yes/no
% planned: ____  lowest package for 20% emails: ________
Next Fest / demo: N/A / separate track owner: ________
Winter hold thought (one line): ________
Owner: ________

Discord-ready paste block

Steam back catalog keep/hold — Aug 13 2026 (NOT Autumn join ritual alone)
H1 context (Alinea estimate): ~$11.1B H1’26; ~79% catalog / ~21% new; new-release share ~29→27→21% H1’24→’25→’26
SKU: ________
Label: KEEP / HOLD / MIX
Why (one line): ________
Next discount path: none / custom / Autumn seasonal
% if any: ____  (≥20% on lowest package if emails: yes/no)
Release cooldown clear: yes / no until ____
Price-increase cooldown clear: yes / no until ____
Discount cooldown note: ________
Autumn Oct 1–8 plan: join / sit-out / hold for Winter
Next Fest / demo track: N/A / separate
Owner: ________  Receipt date: 2026-08-13

Creator checklist (shareable)

• [ ] Primary keyword spoken aloud: steam back catalog keep/hold—not “we’ll figure Autumn later”
• [ ] Every live package labeled KEEP / HOLD / MIX
• [ ] Alinea cited as estimate; Steamworks links bookmarked
• [ ] 20% wishlist-email floor assigned to a named lowest package when emails matter
• [ ] Autumn seasonal path separated from custom-on-same-dates
• [ ] Discord paste pinned; pricing owner named
• [ ] Link Autumn playbook + pricing guide in the pin for teammates who need the other rituals
• [ ] No fake “we recovered $X like Capcom” stories in the announcement

CapEx / diligence four-liner for companies

When finance, a publisher partner, or an acquirer asks “H1 was record and ~79% catalog—why aren’t you at 50% off everything?”:

1. Scope — KEEP/HOLD/MIX is by SKU, not by platform mix headline; Alinea’s ~$11.1B / ~79% catalog split is market context (Alinea), not a mandate to burn launch protection.
2. Cost — Discount cost is cooldown + trained wait behavior + wishlist-email miss if under 20% on the lowest package; seasonal participation must use the official path (Discounting, Seasonal Sales).
3. Evidence — C1–C6 receipt below + Discord paste + Discount Management screenshot when a cut is entered; no Slack “we’ll match competitor %.”
4. Owner — Named pricing lead who can explain why a young SKU stays KEEP while catalog SKUs HOLD into Autumn.

Common mistakes / failure modes

Verification / receipt-style checklist (C1–C6)

Plain-language gates. Fail closed if any required gate is blank.

Optional JSON-shaped receipt for teams that already use build receipts:

{
  "receipt": "steam_back_catalog_keep_hold_v1",
  "date": "2026-08-13",
  "evidence_id": "2026-08-steam-back-catalog-h1-record-indie-keep-hold",
  "sku_labels": [{"package": "", "label": "KEEP|HOLD|MIX", "why": ""}],
  "cooldowns": {"release_clear": "", "price_increase_clear": "", "discount_note": ""},
  "wishlist_email_floor": {"lowest_package": "", "percent": null, "applies": true},
  "autumn_path": "join_seasonal|sit_out|hold_winter|na",
  "owner": "",
  "gates": {"C1": false, "C2": false, "C3": false, "C4": false, "C5": false, "C6": false}
}

Pipeline depth - working developer evening

After labels exist, deepen the pipeline without turning this into the Autumn article.

1. Price history export habit

Pull package price/discount history from partner tools you already use. Mark every custom discount in the last 90 days. Ask: does another custom before Autumn create a discount-cooldown problem for a non-seasonal plan? Seasonals remain the exemption path for that cooldown family—release/price-increase still win arguments.

2. Lowest-package matrix

Bundles complicate “lowest.” If you are redesigning bundles, stop and use the pricing and bundle guide; then return to KEEP/HOLD.

3. Launch-protection scorecard (KEEP candidates)

Score 0–2 each; keep KEEP if total is low:

This scorecard is a decision aid, not a Steam algorithm claim.

4. Catalog-depth scorecard (HOLD candidates)

5. Conflict table vs October density

Beginner mistakes to avoid on Monday

1. Reading Alinea once and rewriting your entire price sheet at midnight.
2. Using “record H1” as a synonym for “our game is catalog.”
3. Skipping the pricing guide when list price itself is wrong—discounts cannot fix a broken regional floor.
4. Treating SteamDB consumer countdowns as partner policy.
5. Forgetting that 10–95% bounds still require a strategic choice inside the band.
6. Pasting competitor % without C3 cooldown dates.

Key takeaways

• Steam’s H1 2026 story (Alinea estimate: ~$11.1B, ~79% back catalog / ~21% new, ~14.5% YoY, new-release share ~29% → 27% → 21%) is a mix signal, not a mandate to discount your launch SKU.
• steam back catalog monetization for micro-studios starts with KEEP / HOLD / MIX by package, not one studio-wide %.
• Launch protection and catalog depth are different jobs on the same partner account.
• Steamworks release and price-increase cooldowns still block discounts—including seasonals; discount cooldown treats seasonals as the exempt path.
• Official seasonal Discount Management ≠ custom discount on the same dates.
• Wishlist emails generally need ≥20% on the lowest-priced package—name the package in the receipt.
• Use a stair-step ladder on HOLD SKUs; graduate KEEP→HOLD with written criteria.
• Pair this page with the Autumn Sale playbook and the pricing/bundle guide—do not merge them into one panicked evening.
• Companies should demand CapEx four-liners and C1–C6 evidence, not H1 headline slides alone.
• Cite Alinea and Steamworks Discounting beside claims; re-read docs before submit.

FAQ

What does steam back catalog mean after Steam H1 2026?

In this article it means older, already-released packages that behave like catalog for discount planning—contrasted with young launch SKUs that still need KEEP protection. Alinea’s H1 2026 estimate that roughly 79% of spend landed on back catalogue (vs ~21% new releases) describes the platform mix, not automatic labeling for your AppID.

Is Steam’s $11.1B H1 2026 figure official Valve revenue?

No. Treat it as an Alinea Analytics estimate from their public write-up of another record half, including the ~14.5% YoY note versus H1 2025. Always link the source when you cite it.

Why did new-release share fall from about 29% to 21% across recent H1s?

Alinea’s series shows new-release share of H1 spend moving roughly 29% (H1 2024) → 27% (H1 2025) → 21% (H1 2026). For indies, interpret that as stronger catalog competition for wallet share—not as proof your unreleased or young title should deep-discount immediately.

Should a single-SKU indie discount because Steam is mostly back catalog?

Not automatically. If your SKU is young, KEEP. Catalog-heavy platform mix often means other games already occupy buyer expectations for discounts. Your job is cooldown-aware timing and discovery goals.

What Steam discount cooldowns matter most?

Know three families: release, price-increase, and discount cooldowns. Seasonals are specially handled for the discount-cooldown family but still respect release and price-increase rules. Read Discounting and Seasonal Sales.

Do I get wishlist emails at 15% off?

Plan on at least 20% off the lowest-priced package when wishlist emails matter, and confirm current duration/eligibility in Steamworks. Under-floors are a common silent failure.

Is a custom discount during Autumn Sale the same as joining the Autumn Sale?

No. Use the official seasonal entry in Discount Management. Custom-on-same-dates is a different path with different cooldown behavior.

How is this different from the Steam Autumn Sale 2026 playbook?

That playbook owns join/sit-out, seasonal UI, and October forward rituals for the sale week. This article owns H1 mix → KEEP/HOLD/MIX and catalog ladders before you open that ritual.

How is this different from the pricing and bundling guide?

Pricing/bundling owns list price, regions, and bundles. This page assumes list price exists and decides whether and how catalog discounts should deepen after the H1 mix shift.

What should we do before October Next Fest?

Keep demo registration and press-preview decisions on the Next Fest track (press preview decide). Do not pretend fest participation assigns Autumn discount %.

Can we invent a Capcom-style case study to convince finance?

No. Use pattern language, your receipts, and third-party estimates with attribution. Fabricated recoveries fail diligence and editorial standards.

What % bounds does Steam allow?

Steamworks documents discount percentages in a broad 10–95% band for applicable discounts—your strategy still has to pick a point on the ladder that matches KEEP/HOLD goals.

Closing - what to do Monday

1. Open a sheet. List every live package with release and last price-increase dates.
2. Label each KEEP, HOLD, or MIX using the decision table—cite H1 mix as context, not as a blunt weapon.
3. Run C3 cooldowns against Discounting.
4. For HOLD packages, draft a stair-step toward Autumn; enter seasonals only via the official path (Seasonal Sales) when that week comes.
5. If emails matter, lock a ≥20% plan on the named lowest package.
6. Pin the Discord paste; fill the CapEx four-liner if anyone outside the team will ask.
7. When you need sale-week mechanics, switch to the Autumn Sale keep/hold playbook. When list price or bundles are wrong, switch to the pricing guide. Keep this URL for the steam back catalog label decision after record H1 headlines.

Record receipt date 2026-08-13. Re-read Steamworks before you click submit. Cite Alinea when you quote the H1 mix—and remember ~79% catalog is the store’s wallet, not a permission slip to burn your launch.