Steam Direct Fee Explained: The $100 Rule and How to Recoup It

The Steam Direct fee is a one-time payment of $100 USD for each new app you publish on Steam. You pay it during Steamworks signup, it is not refundable, and Valve returns the $100 once that app reaches $1,000 in Adjusted Gross Revenue from Steam Store sales or in-app purchases. The fee is charged per app, not per developer, so a studio shipping three separate games pays $300 in total, and each recouped $100 shows up as a separate line item in your monthly payout report.

That is the whole rule in four numbers: $100, per app, $1,000 to recoup, gone if you never get there. I verified each of them against the official Steamworks Steam Direct fee documentation in October 2026, because Steam policy has moved enough over the years that old forum answers are unreliable. The rest of this post covers what the fee does and does not include ( DLC and soundtracks follow different rules ), where the $100 sits inside the real cost of shipping on Steam, the tax withholding that catches non-US developers, and the plain math on how many sales it takes to earn the fee back.

The Steam Direct fee is the entry toll for the Steam Direct publishing system, the process Valve introduced in 2017 to replace Steam Greenlight. Think of it as a per-app deposit rather than a subscription or a platform license. You pay $100, you get one App ID, and that App ID is where your store page, builds, and depots live.

A few specifics that the official documentation states plainly and that people still get wrong:

• •It is per app, not per developer or per account. Every new base game needs its own $100 fee. Your Steamworks account is free to create; the fee attaches to each product.
• •You pay it during signup, as part of the digital paperwork. Existing partners can also buy an app credit separately for a future product and redeem it later with “Create new app”.
• •Only a user with Admin permissions on the Steamworks partner account can pay it. If you are a contractor or a junior team member, you cannot press the button.
• •You cannot pay with Steam wallet funds. Valve accepts “any payment method that Steam supports in your country, excluding Steam wallet funds”, so the store credit sitting in your account from selling trading cards will not cover it.

One more detail for the tax-minded: Valve charges VAT, GST, or similar consumption taxes on the fee where they apply, and the invoice is issued to the individual user account that paid, not automatically to your company. If your accounting needs a company invoice, sort that out before you pay.

Not refundable. Recoupable. Those are two different words and the difference is the entire point.

“Not refundable” means you cannot pay the $100, change your mind, and ask for it back. Once it is paid, there is no refund path.

“Recoupable” means Valve credits the $100 back to you once the app earns enough. The exact threshold, quoted from the docs: you receive the fee back “once your product has at least $1,000.00 Adjusted Gross Revenue for Steam Store or in-app purchases”. When that happens, the repayment appears “as a separate line item in your monthly report”, so you can watch it land.

Adjusted Gross Revenue ( AGR ) is the revenue Steam counts after refunds, chargebacks, and applicable taxes, and before the revenue split with Valve. It is the same figure that decides your revenue share tier later. So the recoupment trigger is not “net $1,000 into your own pocket” - it is “$1,000 of counted gross on the store”.

The honest read: if your game reaches $1,000 in gross Steam revenue, the fee costs you nothing in the end. If it never reaches $1,000, the $100 is the price you paid to find that out. Most commercial releases clear $1,000 within their first days. Many tiny experimental apps never do.

Short answer: DLC does not. A standalone soundtrack usually does. A soundtrack attached to a game you already sell does not.

Here is the reasoning, because the fee documentation itself does not itemize this and I had to cross-read three Steamworks pages to be sure.

DLC: each piece of downloadable content gets its own App ID, but that App ID is created under your existing base game at no additional Steam Direct fee. You pay $100 once for the base game; the expansions, character packs, and cosmetic bundles that hang off it are free to register. This is a big part of why DLC is such an efficient revenue lever: there is no per-item toll to test one.

Soundtracks split into two cases, per the Steam soundtrack documentation:

• •A soundtrack “associated with a Steam game” you already sell is treated as additional content, similar to DLC, and does not need its own $100 fee.
• •An “independent” soundtrack, one not tied to a game you sell on Steam, is a standalone application and takes the standard $100 Steam Direct fee like any other new app.

The pattern is simple once you see it: the $100 fee buys a top-level product. Anything that lives under a product you already paid for is free to add.

The fee is the only mandatory upfront payment Valve asks for. Everything else Steam takes is a cut of revenue, not a bill. That makes the $100 almost a rounding error next to the real cost of a launch, but it is worth seeing the whole stack in one place.

Steam’s revenue share is 30% of gross, and it steps down as a single game earns more:

Those tiers apply per app, and only to revenue above each threshold, not retroactively to the first dollar. For the large majority of indie titles, 30% is the number that matters, and the $100 fee is a one-time line on top of it.

Set against the real budget of a release - art, engine, audio, QA, and marketing - the $100 barely registers. Our breakdown of indie game development costs puts most commercial indie budgets in the tens of thousands of dollars and up. If the Steam Direct fee is the number giving you pause, the fee is not really your problem. The full publishing process is where the actual cost and time go.

This is the section that surprises people, and it has nothing to do with the $100 fee itself. Before Valve pays you a single dollar of revenue share, you complete a tax interview inside Steamworks, and the form you submit sets how much the US government takes off the top.

I confirmed the following against the Steamworks tax FAQ:

• •Non-US developers submit a W-8BEN ( individuals ) or W-8BEN-E ( companies ). You later receive a 1042-S showing your US-source income and any tax withheld.
• •US developers submit a W-9 and receive a 1099, unless the business is a C or S corporation.
• •If your country has no income tax treaty with the US, Valve is required to withhold 30% of your revenue share payment and remit it to the IRS. That is 30% on top of Steam’s 30% cut.
• •If your country does have a treaty, you can retake the tax interview and provide a US or foreign Tax ID to reduce the withholding rate, often down to 0% to 15% depending on the treaty.

Read that third point twice if you are outside the US. A developer in a no-treaty country who skips the tax ID keeps 70% of 70%, which is 49% of gross. A developer in a treaty country who fills in the interview correctly can keep the full 70%. The difference is paperwork, not sales. The revenue share explainer walks through how these layers stack on a real payout.

Two different questions hide inside “when does the fee pay for itself”, and mixing them up is where the confusion starts. Let me separate them at a $10 price point, and label all of this illustrative - your real figures shift with regional pricing, VAT, and refunds.

First question: when has the fee paid for itself in profit? At a $10 sticker price, Steam’s 30% cut leaves you about $7 per sale. $100 divided by $7 is roughly 15 sales. After about 15 copies, the profit you have banked covers what you spent on the fee.

Second question: when does Valve actually hand the $100 back? That is the $1,000 AGR trigger, and it does not care about your profit, it counts gross. At $10 a copy, $1,000 of Adjusted Gross Revenue is about 100 sales. That is when the separate line item shows up in your monthly report.

So at $10, the fee is “earned back” around 15 sales and “refunded” around 100 sales. Higher prices reach both marks faster:

One caveat on that chart: outside the US, sticker prices usually include VAT, so the AGR per unit is a little lower than the sticker and the true sale count is a little higher. Treat the numbers as the optimistic end. If you want your own figure with your price, region mix, and expected refund rate, the Steam fee calculator does the exact arithmetic, and the revenue calculator extends it to full lifetime revenue.

For a game priced with any real pricing strategy, both marks arrive fast. The recoupment threshold only becomes a live risk for genuinely tiny or free products.

For most developers, it does not. If you are shipping one commercial game at $10 or more, the fee is a footnote you will recoup in the first day or two of any launch that works at all. Pay it and move on.

The $100 becomes a real decision in two situations.

The first is when you are shipping many small or free apps. A hobbyist who wants to publish ten tiny $2 experiments is looking at $1,000 in fees, and the free ones can never recoup, because a free app struggles to reach $1,000 AGR at all. If your plan is a portfolio of micro-releases, the fee is a genuine per-title cost you should budget, and it is a strong argument for bundling several ideas into one paid app instead of ten separate ones.

The second is when you are not sure the project will sell. The fee is non-refundable until you clear $1,000 gross. If there is a real chance your app never finds 100 buyers at $10, then the $100 is money you might not see again. That is not a reason to skip Steam. It is a reason to be honest about the project’s floor before you pay.

My recommendation is straightforward. If you are making one serious commercial release, ignore the fee as a cost and treat it as a formality. If you are making many small or free apps, count the fee as a real per-app expense, consolidate where you can, and expect never to recoup it on the free ones. The fee is designed to do exactly this: small enough to be nothing for a real game, large enough to discourage flooding the store with a hundred throwaway App IDs.

Run this list before an Admin on your account clicks pay:

• •Confirm you actually need a new App ID. If it is DLC or a soundtrack for a game you already sell, you do not owe another $100. Only a new base product does.
• •Pay from an Admin account with a non-wallet method. Steam wallet funds are not accepted, and only Admin-permission users can complete the payment.
• •Finish the tax interview first. Submit your W-8BEN, W-8BEN-E, or W-9 and, if you are treaty-eligible, add your Tax ID so Valve does not withhold 30% by default. This saves more money than the fee itself.
• •Budget the fee per title, not per studio. Three games is $300. Ten is $1,000. Plan accordingly if you release in volume.
• •Expect the $100 back at $1,000 gross, not before. Watch for the separate line item in your monthly report once the app clears the threshold.

Once the fee is paid and the App ID exists, the work that decides whether you ever hit that $1,000 is the store page itself. Run yours through the free Steam Page Analyzer to see what a first-time visitor sees, and model your break-even in dollars with the Steam fee calculator before you commit to a price.