Game Publisher Agreements: What Indie Studios Sign Away in IP, Revenue, and Creative Control

Your game has a playable vertical slice. You have a pitch deck, a trailer, and a growing wishlists number. A publisher reaches out, offers to fund the rest of development, handle QA, porting, localization, and marketing. The term sheet arrives. It looks like a lifeline.

It may be. But a game publisher agreement is also one of the most consequential contracts an indie studio will ever sign. It determines who owns your IP, how long the publisher controls distribution, how revenue flows back to you, and whether you can ever get your game back if things go sideways. We have written this guide the same way we approached our breakdown of indie film distribution deals and our talent agreements for streamers: clause by clause, with what to look for, what a developer-favorable version looks like, and what happens when the clause is absent entirely.

Why This Matters Now

Indie game development surged after 2020. More studios are shipping more games, and publishers are aggressively signing talent. But the publisher-developer power dynamic is not symmetrical. The publisher has capital, infrastructure, and distribution relationships. The developer has a game that needs funding. That asymmetry shows up in every clause of the contract.

The risks are not theoretical. In September 2024, the entire 25-person staff of Annapurna Interactive — one of the most respected indie publishers in the industry — resigned after negotiations to spin off into an independent entity collapsed with owner Megan Ellison. Developers who had signed publishing deals with Annapurna were left scrambling to understand what would happen to their funding, QA, localization, and marketing commitments. Annapurna stated it would honor existing contracts, but the episode exposed how dependent a studio becomes on a publisher's continued existence and goodwill — and how little control developers have when the publisher's internal structure changes. (Shacknews, Sept. 2024)

The International Game Developers Association (IGDA) has been tracking developer satisfaction and industry conditions through its biannual Developer Satisfaction Survey, conducted in partnership with Western University. The survey consistently documents quality-of-life issues, job instability, and structural power imbalances that shape how developers experience the industry — including their relationships with publishers. (IGDA, Developer Satisfaction Survey)

If you are an indie studio evaluating a publishing offer, you need to understand the clauses that will determine your financial outcome and your creative future. Here is what they are and what they mean.

IP Assignment vs. Licensing: Who Owns the Game

The first question in any publishing agreement is the most fundamental: who owns the intellectual property? When you create a game, you hold the copyright to it automatically. That copyright gives you the exclusive right to make copies, distribute the game, create derivative works like sequels and merchandise, and display or perform the work. For a publisher to distribute your game, you must grant them rights — but how broad those rights are, and whether they take the form of a license or an assignment, determines whether you keep your IP or give it away. (Sanlo, "What to Know About Game Publishing Deals")

A license grants the publisher specific rights to publish and distribute your game for a defined term, on defined platforms, in defined territories. You retain ownership of the underlying IP — the code, the art, the characters, the universe. This is the developer-favorable structure.

An assignment transfers ownership of the IP to the publisher outright. The publisher becomes the copyright holder. You may retain a license-back to use the IP for limited purposes, but the publisher owns the franchise. Assignments are common when a developer is building a game on an existing IP the publisher already owns (for example, a licensed IP game), but they appear in original-IP deals too — often buried in broad grant language that reads "all right, title, and interest in and to the Game."

The distinction matters because it controls everything downstream. If you assign the IP, the publisher decides whether to greenlight a sequel, whether to license the franchise for film or television, and whether to merchandise the characters. If you license the IP, those decisions remain yours — subject to whatever rights of first refusal or first negotiation the publisher negotiated. (Contractable.ai, "Game Development Revenue Share Agreement")

Watch for language that includes "all rights, now known or hereafter devised" without a carve-out for rights you intend to retain. As we noted in our brand deal contract checklist for streamers, the words "exclusive, worldwide, sublicensable, irrevocable" each expand what the other party owns of your work. The same logic applies here. Each of those words in a publisher grant clause shrinks your future.

Right of First Refusal on Sequels and Derivatives

Even if you retain IP ownership, publishers often negotiate a right of first refusal (ROFR) or right of first negotiation (ROFN) on sequels, DLC, and derivative works. A ROFR requires you to offer the publisher the sequel before you can take it to anyone else. A ROFN requires you to negotiate with the publisher in good faith for a set period before shopping the sequel elsewhere.

These are not inherently unreasonable — a publisher who invested in building an audience for your game has a legitimate interest in continuing the franchise. But an overly broad ROFR can effectively lock you into the same publisher for every future project in the same universe, limiting your leverage in subsequent negotiations. Narrow the scope: limit the ROFR to direct sequels, not "any game set in the same universe," and cap the negotiation window so you are not stuck in limbo for months.

Revenue Splits, Advances, and Recoupment

The revenue section is where a publishing deal either pays you or quietly puts you in a hole. The headline number — "70/30," "60/40" — is a summary, not the full picture. What actually governs your take-home is the interaction between the split percentage, the size of any advance, how the advance is recouped, and how "Net Revenue" is defined.

According to data presented by Kellen Voyer of Voyer Law at GDC Summer, who collected terms from 30 publishing agreements for non-mobile indie games, the average advance to fund a game is $318,000. Counting only deals with an advance, the average rises to $460,000. The lowest advance in the dataset was $100,000 and the highest was $2 million. Eighteen percent of agreements had no advance at all — those deals typically offered a higher revenue share in exchange. (GameDiscoverCo, Aug. 2020, citing Voyer Law GDC talk)

On revenue splits, the same data set found that the average split gives developers 60 percent and publishers 40 percent. That rises to 71 percent for developers in no-advance deals (often near-finished games that only need marketing support) and drops to 55 percent for developers when averaging only deals that include an advance. (GameDiscoverCo, Aug. 2020)

The Recoupment Trap

An advance is not free money. It is almost always recoupable — meaning the publisher recovers the advance from the game's revenue before additional payments flow to you. The critical question is how the advance is recouped:

• Recoup from Net Revenue before the split (publisher-friendly): The publisher recoups its advance and approved costs from Net Revenue first, then the remainder is split. This can delay developer revenue for a long time — sometimes the entire life of the game if sales are modest.
• Recoup from the publisher's share only (developer-friendly): Net Revenue is split immediately, and the publisher recoups the advance from its own portion. The developer gets paid from day one of revenue.

Voyer's data showed that 42 percent of deals require the advance to be fully recouped before developers see a single dollar. The remaining 58 percent allow both parties to receive revenue share while recoupment happens. (GameDiscoverCo, Aug. 2020)

Defining "Net Revenue": Where Deals Are Won or Lost

Most publisher deals split Net Revenue, not Gross Revenue. Net is fine if it is tightly defined. The danger is vague language like "any costs related to publishing" — which lets the publisher deduct an open-ended list of expenses before calculating your share.

A well-drafted Net Revenue definition should enumerate allowed deductions: platform fees (Steam, PlayStation, Xbox, Nintendo, Epic), payment processing fees, refunds and chargebacks, sales taxes actually paid, and third-party licensing fees. It should also explicitly list disallowed deductions: corporate overhead, publisher salaries, unrelated tool licenses, general administrative costs. Without these guardrails, "Net Revenue" becomes whatever the publisher says it is. (Contractable.ai, "Game Development Revenue Share Agreement")

Cross-Collateralization: When One Platform Eats Another

Cross-collateralization is one of the most consequential — and most frequently overlooked — provisions in a game publisher agreement. It means the publisher can recoup costs from one revenue stream using revenue generated by another. For example: if your game underperforms on Switch but performs well on PlayStation, a cross-collateralization clause allows the publisher to use PlayStation revenue to recoup the costs of the Switch port.

This is the same mechanism we warned filmmakers about in our film distribution deal guide, where cross-collateralization allows one revenue window to eat another. In games, the dynamic is identical but the streams are platforms, territories, and SKUs instead of media windows.

Cross-collateralization can seriously reduce your ability to reinvest in your studio. If every strong-performing platform is dragged down by the costs of a weak-performing one, your effective revenue shrinks even when the game is commercially successful on individual platforms.

Your negotiation options, from most to least developer-favorable:

• No cross-collateralization: Each platform recoups its own costs independently. If Switch underperforms, that is the publisher's problem — not PlayStation's.
• Cross-collateralization within the same SKU only: Base game revenue covers base game costs. DLC revenue is not dragged down by base game deficits.
• Separate recoup pools by platform: PC, console, and mobile each have their own recoupment calculations.
• Separate recoup pools by territory: North American revenue is not used to cover European marketing costs.
• Never let Game 2 cover Game 1's deficit: Some publisher agreements include a portfolio cross-collateralization clause that allows the publisher to recoup shortfalls from one game against revenue from an entirely different title. This should be a hard line. (Contractable.ai, "Game Development Revenue Share Agreement")

Milestone Obligations and Acceptance Testing

Publishing agreements typically tie funding to milestones — specific deliverables the studio must produce to unlock the next tranche of advance payments. Common milestones include a completed core game loop, vertical slice, alpha build, beta build, content complete, and release candidate. The milestone schedule serves as both a funding mechanism and a project management framework.

The risk lies in the acceptance criteria. If the publisher's acceptance standard is subjective — "commercially acceptable quality" or "satisfactory to publisher" — the publisher effectively holds a veto over your funding. A publisher can withhold acceptance (and therefore payment) for reasons that have nothing to do with the quality of your build, using the milestone process as leverage to demand changes, add features, or renegotiate terms.

Protect yourself by ensuring milestones have objective deliverables: a specific build version number, a defined feature list, documented performance targets (frame rate, load times, crash rate), and a clear list of known issues that are acceptable at each stage. The contract should specify a defined acceptance period (e.g., 10-15 business days) and state that silence equals acceptance. It should also include a dispute resolution mechanism for milestone rejections — ideally, a neutral third-party evaluator or an escalating process that prevents the publisher from indefinitely stalling. (Contractable.ai, "Game Development Revenue Share Agreement")

Also watch for consequences of delay. Many agreements allow the publisher to terminate or withhold funding if milestones are missed by a defined margin. Make sure the contract includes cure periods — a reasonable window to fix and resubmit — and force majeure provisions that account for circumstances beyond your control. The Annapurna situation demonstrated that publisher-side disruptions can be just as destabilizing as developer-side delays, and your contract should contemplate both directions. (Shacknews, Sept. 2024)

Creative Control: Approval Rights, Veto Powers, and Mandates

Creative control is where the publishing agreement intersects with your studio's identity. Publishers may negotiate approval rights over game design, art direction, narrative content, monetization mechanics, and even character design. The spectrum runs from light consultation to effective creative veto.

Approval rights are not always bad — a good publisher's input can improve commercial viability. The danger is when approval rights become veto power without any obligation on the publisher to propose alternatives or explain reasoning. A clause that says "publisher may reject any deliverable for any reason" gives the publisher unlimited leverage to force changes you disagree with, with no recourse.

Negotiate for a structured approval process: the publisher must provide specific, written feedback within a defined period. Rejections must include actionable reasons. If the parties disagree, there should be an escalation mechanism — not a unilateral publisher veto. Reserve final creative authority over core game design and narrative to the developer, unless the publisher is funding development of an IP they already own.

Porting, Localization, and Additional Content Mandates

Publishers often require developers to support porting (adapting the game for additional platforms), localization (translating and culturally adapting the game for different markets), and post-launch content (DLC, updates, patches). These obligations can be significant — porting alone can consume months of engineering time, and ongoing post-launch support can tie up your team for years.

The contract should specify who is responsible for each of these tasks and who pays for them. If the publisher handles porting through a third-party studio, confirm that the cost is recoupable (and from which revenue stream). If the developer is responsible for porting, make sure the scope is realistic and the timeline is funded. Vague language like "developer shall provide reasonable post-launch support" is an open-ended commitment that can consume your team's capacity indefinitely. (Deviant Legal, "The Game Developer's Guide to Publishing Agreements")

Marketing, Distribution Rights, and Exclusivity

The rights grant defines what the publisher can do with your game, for how long, and in what markets. Key dimensions include:

• Platforms: Which storefronts and consoles the publisher can release on. If the publisher is not funding or executing a platform, consider carving it out or setting a separate split for that platform.
• Territory: Worldwide vs. specific regions. A worldwide exclusive grant means no other publisher can operate anywhere.
• Term: How long the publisher holds the rights. Industry data suggests an average deal duration of approximately 6.5 years. Long terms require strong reversion provisions. (Sanlo, "What to Know About Game Publishing Deals")
• Exclusivity: Full (no self-publishing or other publisher anywhere), timed (exclusive for a defined period, then rights revert), or none. If the publisher wants exclusivity, the economics should reflect that — you are giving up the ability to self-publish or partner with others.

Marketing Commitments: "Best Efforts" Is Not a Promise

Marketing is the most common source of developer-publisher conflict because it is expensive, hard to measure, and often recoupable. Publishers may promise "commercially reasonable efforts" or "best efforts" to market your game. Those phrases are vague and effectively unenforceable — they give you no remedy if the publisher does minimal marketing and your game underperforms.

Instead of vague promises, negotiate for:

• A marketing plan attached as an exhibit to the contract
• Defined deliverables: trailer, store page optimization, PR campaign, influencer outreach, convention presence
• A minimum marketing spend (but be careful — if marketing is recoupable, a high minimum also means a larger recoupment obligation)
• Approval rights for brand-sensitive materials (key art, trailers, social media campaigns)
• Clear ownership and usage rights for creative assets the publisher produces

The goal is transparency and planning, not a large spend commitment that will be deducted from your revenue. (Contractable.ai, "Game Development Revenue Share Agreement")

Audit Rights: Your Safety Net

Audit clauses are often overlooked until something feels off — and by then it is too late. A workable audit clause should specify your right to audit royalty statements and the publisher's books at least once per year, with reasonable notice (10-30 days), using an independent auditor under NDA. The scope should include platform statements and invoices supporting deductions.

On cost: you should pay for the audit unless the audit reveals an underpayment exceeding a defined threshold (commonly 5 percent), in which case the publisher pays for the audit plus interest and correction. If a publisher refuses audit rights entirely, that is a major trust issue in what is supposed to be a long-term partnership. (Contractable.ai, "Game Development Revenue Share Agreement")

Rights Reversion and Termination

What happens when the deal ends? This is the question most developers do not ask until it is too late. The termination and reversion provisions determine whether you get your game back — or whether the publisher retains control indefinitely.

Term and Reversion Triggers

The contract should define a clear term for the publisher's rights — a fixed number of years from release, not from signing. A term that starts at signing means the publisher's clock is ticking during development, eating into the period where the game is actually generating revenue.

Reversion triggers are your safety net. These are conditions that cause publishing rights to revert to the developer before the full term expires. Common reversion triggers include:

• Failure to publish: If the publisher does not release the game within a defined period, rights revert.
• Delisting: If the publisher allows the game to be delisted from major platforms and does not relist within a defined cure period, rights revert.
• Failure to meet minimum marketing spend: If the publisher does not meet committed marketing obligations, rights revert.
• Publisher insolvency or material breach: If the publisher becomes insolvent, files for bankruptcy, or materially breaches the agreement, rights revert.

Without reversion triggers, a publisher can sit on your game indefinitely — not actively marketing it, not investing in ports or DLC, but not releasing the rights back to you either. This is the game industry equivalent of the "shelf" problem in film distribution, where a distributor holds rights without exploiting them. (Promise Legal, "Film Distribution Deals")

What Survives Termination

When the publishing agreement ends, what happens to the publisher's rights, your obligations, and the money? The contract should specify:

• Rights reversion: All publishing and distribution rights revert to the developer, and the publisher's license terminates.
• Recoupment balance: If the advance has not been fully recouped at termination, does the publisher have a claim against future revenue, or is the remaining balance forgiven? Developer-favorable language extinguishes the recoupment obligation at termination.
• Ongoing obligations: Post-launch support, bug fixing, and server maintenance obligations should have defined end dates, not continue indefinitely.
• Key assets: Marketing materials, trailers, key art, and store page content should transfer to the developer upon termination so they can continue selling the game.

The Annapurna Lesson

The Annapurna Interactive restructuring in September 2024 is a real-world case study in why termination and continuity provisions matter. When the entire publishing staff resigned, developers faced immediate questions: Who handles QA? Who manages platform relationships? Who is responsible for marketing commitments? Annapurna stated it would honor contracts, but the situation illustrated how vulnerable studios are to publisher-side disruptions they cannot control. (Shacknews, Sept. 2024)

A well-drafted agreement should contemplate publisher-side disruption. Include a key personnel clause that allows termination if the specific team managing your game departs. Include a change-of-control provision that triggers renegotiation or reversion if the publisher is acquired or restructured. And include a continuity obligation: if the publisher cannot fulfill its commitments, publishing rights revert automatically.

Actionable Next Steps

Before you sign a game publisher agreement, take these steps:

1. Get the full contract, not just the term sheet. Term sheets outline headline terms but omit the definitions, recoupment mechanics, and reversion provisions that determine your actual outcome. The contract is what you are signing. Read the back half.
2. Model the economics. Put the advance, revenue split, recoupment structure, and cross-collateralization terms side by side. Run them against realistic sales figures — not the publisher's projections. Find your break-even before you agree to the deal.
3. Identify every clause that grants rights in perpetuity. "In perpetuity" means forever. Every perpetuity grant — whether for distribution rights, IP, merchandising, or adaptations — should be narrowed to a defined term with reversion triggers.
4. Negotiate the definitions, not just the numbers. The split percentage is a summary. "Net Revenue," "recoupable costs," "cross-collateralization," and "commercially acceptable" are where the deal is actually won or lost. Insist on enumerated lists and caps.
5. Have an attorney review the agreement before signing. A game-literate attorney can spot provisions that shift risk, eliminate your leverage, or create obligations you did not anticipate. The cost of review is a fraction of the cost of a bad deal. If you are an indie studio in Texas or anywhere else in the U.S., we can help.

A publishing deal should be a partnership that gets your game to players and sustains your studio. The contract is the document that defines whether it actually works that way — or whether the publisher's interests are protected and yours are not. Read it like your future depends on it, because it does.