Distribution Platform Agreements: What Indie Developers Need to Know About Steam, Epic, and Console Store Terms

The Contract You Clicked Through Matters More Than You Think

Every developer who uploads a game to Steam, Epic Games Store, or a console storefront signs a contract before doing so. Most don't read it. Under the federal E-SIGN Act and the Uniform Electronic Transactions Act (UETA), that doesn't matter — clicking "I agree" carries the same legal weight as a handwritten signature, and courts have enforced those clicks regardless of whether the developer reviewed the terms. In Feldman v. Google, Inc., the court held that clicking a checkbox to accept terms constituted a valid, binding contract.

Platform agreements are not passive boilerplate. They determine what the platform can do with your game, when it can remove it, what revenue you'll receive, and whether you have any recourse when something goes wrong. The Steamworks SDK Access Agreement states explicitly that Valve has no obligation to distribute developer software via Steam — meaning your game's presence on the platform is a revocable privilege, not a right.

The real-world stakes are significant. Indie studio Santa Ragione invested approximately $100,000 developing Horses and faced potential studio closure after Valve banned the game. After two years of failed appeals, Valve's final position was that it would not accept further submissions, even with modifications. No arbitration, no cure period, no path forward — all consistent with terms the developer had accepted at sign-up. Reviewing platform distribution agreements before you publish isn't just good practice; it's the baseline for understanding what you're actually agreeing to.

Revenue Share Structures

The headline number every developer knows is 70/30 — the developer keeps 70%, the platform takes 30%. But the actual structure varies across stores, and the differences matter more as a game's lifetime sales grow. Steam uses a tiered model: 70/30 on the first $10 million in lifetime revenue, 75/25 above $10 million, and 80/20 above $50 million. These thresholds have been unchanged since October 2018 and apply across game packages, DLC, and in-game sales. For the overwhelming majority of indie titles that never approach $10 million, the 70/30 rate is permanent.

Epic Games Store operates differently. The standard split is 88/12 — developers keep 88% after the first $1 million per product per year. For that first million in net revenue, developers keep 100%. Epic's First Run program pushes this further: games that launch exclusively on EGS for their first six months of PC availability receive 100% of net revenue throughout that exclusivity window. The tradeoff is audience reach — Steam's install base still substantially exceeds Epic's, and exclusivity carries the risk of missing launch momentum on the larger platform.

Console platforms generally apply a standard 30% cut. Microsoft maintains 70/30 on Xbox console but shifted to 88/12 on the Microsoft Store for PC, effective August 2021. Nintendo reports a standard 30% platform cut on Switch eShop. Sony's PlayStation Store applies a similar structure. Only 3% of developers surveyed in a Game Developer state-of-industry poll believed the standard 70/30 split was economically justified — but for most indie studios distributing on Steam or console, it is the non-negotiable starting point.

IP Ownership and Licensing Clauses

Uploading a game to Steam does not transfer ownership of the game's IP — but it does grant Valve a broad license to use it. Under Valve's terms, developers grant a worldwide, non-exclusive, royalty-free license to use, reproduce, modify, create derivative works from, distribute, and publicly display developer content for the operation, distribution, and promotion of Steam. That license runs for the full duration of the underlying intellectual property rights. For content posted to Steam Game Sites specifically — including promotional materials uploaded to your store page — the license is perpetual and irrevocable, meaning Valve can continue using that content even if you later terminate the relationship.

The Steamworks SDK itself operates under a nonexclusive, royalty-free, terminable, worldwide license — but here the balance tips toward developers, because the SDK license terminates when the agreement does. The irrevocable promotional content license is the more consequential provision: screenshots, trailers, and marketing assets you upload to your Steam store page may remain in Valve's hands after departure.

None of this changes the fundamental rule that you must own what you upload. Indie studios frequently enter platform agreements before securing clean IP assignments from every contractor who contributed to the game. Without written assignments, contributors own their work jointly by default — regardless of what was paid. That means the studio may not hold clear title to the game it's distributing. Secure written IP assignments and, where applicable, moral rights waivers from all contributors before signing any platform agreement. An IP protection strategy that covers contractor agreements is a precondition, not an afterthought.

What Valve Can Do: Steam's Developer Terms

The Steamworks SDK Access Agreement gives Valve broad unilateral authority over the distribution relationship. Valve may terminate immediately upon written notice — including email — without cause. The agreement terminates automatically upon any developer breach. There is no cure period, no notice-and-fix window, no contractual obligation to provide reasons. Combined with the absence of any obligation to distribute in the first place, this structure means Steam access is held entirely at Valve's discretion.

Content moderation is exercised the same way. Valve can unilaterally ban a game based on its own content judgment, with no obligation to accept modifications and no binding appeal process. The Santa Ragione situation was not an edge case — it was the contract working as written. When Valve declined Horses, it stated it would not accept further submissions, even with changes, and two years of appeals produced no different outcome.

Steam's refund policy creates a separate structural risk for developers. The 2-hour/14-day refund window flows costs directly to developer accounts as reduced net revenue. For short indie games — those completable in under two hours — this effectively enables players to experience the full game and receive a complete refund. The developer of Summer of '58 announced they were leaving game development after reporting that the game did not reach the two-hour threshold by Steam's standards, and refunds significantly outpaced revenue despite positive reviews. One meaningful shift: in November 2024, Valve removed mandatory arbitration and class action waiver provisions from its Subscriber Agreement, shifting dispute resolution to court — a change that broadens developer litigation options in the event of a dispute.

Epic Games Store: Content Policies and Account Suspension

Epic's enforcement framework is tiered and explicit. According to Epic's published sanctions policy, the progression runs: warning, social ban (temporary or permanent loss of chat functionality), product ban (loss of access to a specific game or service, including associated virtual items and account balances), and account ban — permanent disabling of the Epic account with loss of all rights to games, virtual items, account balances, and any other in-account assets. A permanent account ban is not simply a termination of the developer relationship; it wipes every in-account asset, including purchased games and currency held by the account.

The commercial terms offer more upside than Steam for smaller studios. The standard 88/12 split after the first $1 million per product per year is the baseline; the Epic First Run program boosts that to 100% of net revenue for the first six months of a PC launch in exchange for exclusivity on third-party PC stores. Developers can still sell directly through their own website during the exclusivity window using Epic's keyless distribution system, which preserves some flexibility.

For larger studios, Epic has historically used upfront cash and minimum revenue guarantees to secure exclusivity deals. Ooblets' developers received a floor matching their projected multi-platform earnings plus upfront cash; Control received approximately $10.5 million as an advance; Borderlands 3 reportedly involved a total deal value of approximately $115 million. These structures are not available to most indie developers — but understanding that Epic negotiates them at scale clarifies what the platform's standard 88/12 offer actually costs them.

Console Cert Requirements as Contractual Obligations

Releasing on PlayStation, Xbox, or Nintendo Switch requires more than a distribution agreement — it requires passing platform certification, and the certification requirements are themselves contractual obligations. All three major console platforms condition SDK access and devkit approval on signing a developer agreement that incorporates technical requirements, content guidelines, and platform policies. Failing certification is not merely a technical setback; it is a failure to perform under the terms of the agreement that grants you platform access in the first place.

Sony's Technical Requirements Checklist (TRC), Microsoft's Xbox Requirements (XRs), and Nintendo's production standards each govern a wide range of game behaviors — from save system architecture to accessibility features to content warnings. Microsoft requires all products to pass Build Verification Testing before entering full certification. Nintendo requires developers to sign a publishing agreement, obtain an age rating, and submit for review before any eShop listing goes live.

The cost of failing certification compounds quickly. Console platforms commonly enforce a "three strikes" policy: if three minor failures or one major failure are identified during a submission, all testing halts. Each rejection cycle can cost weeks of delay, thousands of dollars in labor, and missed marketing windows — especially damaging for small studios managing launch budgets carefully. Ixie Gaming's compliance QA documentation describes this structure as one where a single overlooked requirement can halt a game's launch entirely. For indie developers planning console releases, budgeting for multiple certification cycles is not pessimism — it is contract compliance planning.

Refund Obligations and Chargebacks

Steam's 14-day/2-hour refund policy was introduced globally in 2015, modeled on the EU Consumer Rights Directive's withdrawal right for digital goods. Rather than limiting the policy to EU customers, Valve extended it worldwide. The costs flow directly to developers: refunds are deducted from net revenue before any payout. One developer reported 13 refunds from 18 sales — a 72% rate — in the period shortly after the policy launched.

Short games face a structural disadvantage under this framework. Players can complete a focused, short indie game within the two-hour window and still qualify for a full refund. Valve has not published clear definitions of refund abuse, which means studios cannot reliably predict or prevent the pattern. A developer can launch a well-reviewed game and still see a net-zero revenue outcome on a significant portion of sales. This is not a theoretical risk — it is one the developer of Summer of '58 cited when announcing they were leaving game development.

Chargebacks operate differently from refunds and carry additional costs on Epic Games Store. When a customer disputes a charge through their bank, the chargeback is deducted from gross sales proceeds — before the developer's 88% share is calculated. Each chargeback also incurs a $15 fee. Merchants who exceed Visa's chargeback thresholds can be enrolled in Visa's Monitoring Program, which triggers additional fees and scrutiny. For context on EU obligations: the directive's 14-day withdrawal right applies to digital goods, but only until a user expressly consents to immediate delivery. Non-compliant implementation of the digital content waiver can extend the return window to one year. Developers distributing in EU markets should confirm their platform handles this consent mechanism correctly.

Key Negotiation Points for Larger Studios

For most indie developers, platform agreements are take-it-or-leave-it. Steam's revenue tiers are fixed and automatic. Epic's standard 88/12 split requires no negotiation. But studios with commercial leverage — catalog titles, franchise sequels, games with demonstrated wishlist momentum — have more room to negotiate, particularly on Epic's exclusivity deals and publisher agreements.

Steam's tiered revenue thresholds represent the primary structural "negotiation" available without direct leverage: 75/25 above $10 million in lifetime revenue, 80/20 above $50 million. These rates apply automatically once thresholds are crossed. Beyond that, Steam offers no individual revenue negotiation for the vast majority of titles. The structure, as a GeekWire analysis noted at the policy's launch, was described as "an olive branch extended to big developers" — not a mechanism for indie studios.

For publisher agreements, developer resource site LTPF recommends prioritizing deal terms in this order: upfront payment, post-recoupment rate, pre-recoupment rate. In traditional publishing deals, publishers typically take 50–70% of net revenue until recoupment, then 30–50% thereafter. If concessions must be made, the pre-recoupment rate is the most defensible place to yield — it is the only rate that applies to unguaranteed revenue with a ceiling. Beyond revenue, the terms worth fighting for include: IP reversion rights if the publisher fails to perform, marketing approval rights, audit rights over revenue calculations, porting rights, and options on sequels or remasters. Epic's minimum guarantee structure — used in deals like Ooblets, Control, and Borderlands 3 — shows what is possible when studios have leverage. The floor is negotiable; getting there requires having something the platform or publisher actually wants.

What Indie Developers Should Do Before Signing

Platform agreements should be reviewed before you publish, not after a dispute arises. The four clauses that matter most in any distribution agreement are: termination triggers (under what conditions the platform can remove your game or account, and whether you get notice), content moderation clauses (what content the platform can unilaterally reject, and what the appeal process looks like), revenue calculation methodology (are fees applied to gross or net revenue, how are refunds and chargebacks handled, what is the payout schedule), and dispute resolution (what forum governs disputes and whether arbitration clauses have been removed or modified, as Steam's were in November 2024).

Before uploading anything, secure written IP assignments from every contractor and collaborator. Without written agreements, contributors own their work jointly by default — regardless of payment. Written assignments should cover all deliverables, including moral rights waivers that allow editing, localization, and porting. Register trademarks for your game title before launch: platforms require proof of trademark ownership to process takedown requests against unauthorized copies, and trademark registration takes months or years. Starting the process at launch means you may not have protection when you need it.

The IGDA Legal SIG publishes a Contract Walk-Through document that helps developers frame the right questions before engaging an attorney. That document is a starting point, not a substitute for legal review — but it is a useful tool for identifying where a particular agreement departs from industry norms. Developers entering console distribution should also budget for certification cycles: plan for at least two submission rounds and treat the certification requirements checklist as a contractual obligation, not a quality benchmark. A platform agreement review and IP audit before launch is substantially cheaper than resolving a distribution dispute after one.