How to Monetize Your Indie Game on Steam in 2026

This article starts after the game is already for sale. The store page exists, the build installs, and you can open Steamworks reports. What follows is how wishlists, price changes, and discounts actually behave, and which numbers you should refuse to invent. It does not rebuild a store page, it does not explain depots, and it does not quote Steam’s revenue share. The cut Steam takes is in the partner agreement and the current Steamworks fee docs. Read those. A blog is the wrong place to copy a percentage from.

Valve edits these rules. Everything specific below is from the Steamworks Discounting page and the Wishlists page as they read when this piece was written. Open both before you schedule anything:

• https://partner.steamgames.com/doc/marketing/discounts
• https://partner.steamgames.com/doc/marketing/wishlist

If the live page disagrees with this article, the live page wins. The discount doc itself notes that a cooldown changed once already, from 28 days to 30 days at the start of 2023. That is a good reason not to trust memory.

Wishlists are a list, not a forecast

Players wishlist a game to keep track of it. Steamworks shows you how many have. That count is real. What it will turn into in sales is not something you can know until the dashboard shows sales. Do not multiply wishlists by a conversion rate from a conference talk. That rate is not your game, and this article will not supply a replacement.

The wishlist documentation describes notifications when you release and when you discount. It also says the triggers may change. As written, a discount at or above 20 percent can email or push players who wishlisted you, if it affects the lowest-priced package and runs long enough for the rule on that page. A deluxe-only discount does not qualify if a cheaper package exists and stays full price. There is also a frequency limit so the same person is not mailed about the same app constantly. Read the current wording before you plan a calendar around a notification.

You can watch wishlist adds and removes in Steamworks. Use that as a clue about whether a demo, an update, or a festival changed interest. It is not a budget. A spike after a festival still has to show up later as plays and purchases, or it was only a spike.

Discounts you can set, and the waits between them

Discounting requires the Manage Pricing & Discounts permission, and you need to be in the partner that gets paid for the product. The dashboard is under Apps & Packages, Discount Management. Launch discounts are the exception: the Discounting page says they are configured near the release date on the app landing page, and only before release. If the game is already out and you did not stage one, you cannot add a launch discount after the fact.

As that page states it, a launch discount can run 7 to 14 days and cannot exceed 40 percent. It is optional. Valve writes that they generally suggest something around 10 to 15 percent if you use one. That is their suggestion, not a measured result for your game. Standard discounts cannot be under 10 percent or over 95 percent, and they cannot run shorter than one day or longer than 14 days. A discount also cannot push any currency under Steam’s minimum price thresholds. Those thresholds are on the pricing docs, not in this article.

Three 30-day waits matter:

• After release, including an Early Access release, you cannot run another discount for 30 days, except the launch discount you set up beforehand.
• After you increase the base price in any currency, you cannot discount for 30 days. A price cut does not start that wait.
• After a discount ends, you generally cannot start another for 30 days.

Seasonal sales, the four Steam-wide events, are exempt from the discount-to-discount wait. They are not exempt from the release wait or the price-increase wait. A custom discount you happen to run during a seasonal sale does not inherit the exemption. The seasonal discount has to be the one entered for that event. You cannot change the base price while a discount is active or already scheduled.

Curated homepage slots are chosen by Valve. The docs say they are not sold. Being eligible to appear in generic “specials” sections is not the same as being promised a feature. Do not pay anyone who claims they can buy that slot.

Use the reports you have, not a curve you imagined

Steamworks sales and activation reports are the measurement. Open them before the first post-launch discount and look at units and revenue at full price, in the currencies you actually sell. The discount doc’s own advice is to be careful about discounting while plenty of people are still buying at full price, and to tie a discount to a content update when you can. It also suggests stepping discounts deeper over a long time rather than jumping to a very deep cut right after launch. Those are Valve’s general notes. They are not a schedule for your title. Your reports are.

A practical first year, with the rules above and no fake forecasts:

• Let the post-launch weeks happen. Read the report. Do not schedule a custom discount inside the 30-day release wait.
• Ship an update people can notice, then discount if the waits allow it, and discount the base package, not only a deluxe edition, if you want the wishlist notification the docs describe.
• Enter a seasonal sale only when the release and price-increase waits allow it. The discount-to-discount wait does not block the seasonal event itself.
• When the discount ends, compare that period with the weeks before it in your own report. Keep the csv. The next decision gets easier. The first one should not pretend to be precise.

Refunds can change the net after a sale starts. Read the current refund policy and wait for the report to settle before you tell yourself the weekend was a specific success or failure. Day-one gross is not the last word.

Bundles stack: the bundle’s own percentage applies on top of discounts on the packages inside it. The Bundles documentation says a bundle discount does not, by itself, send wishlist notifications. Discount the package if the notification is what you are trying to trigger. Confirm that in the current bundle and wishlist pages before you rely on it.

What you still cannot know

You cannot know the conversion rate from wishlists to sales until those sales exist in the dashboard. You cannot know whether Valve will curate the game. You cannot know regional mix, refunds, or the long tail in advance. You can know the cooldown rules, the permission you need, and what your last report already showed.

Price the base game in the pricing tools Steamworks provides, including regional prices, using the current pricing docs. This article does not name a dollar amount that “works.” Players and costs differ. If you raise the price, remember the 30-day discount wait starts, and you cannot do it in the middle of a scheduled sale.

Check the fee documentation when you model income. Do not subtract a percentage you half-remember. When the report, the cooldown, and the update notes agree, schedule the next discount and leave it alone until it starts. You can edit or clear a discount until it goes live, by setting the percentage to zero in the dashboard, according to the current discounting FAQ. After it starts, it is live data, not a draft.