Indie Game Rev-Share Agreements: What Developers and Studios Need to Know

A question I see come up regularly in game dev communities goes something like this: “We’re doing a rev-share project. What should our agreement look like?”

The answers are all over the map. Some developers swear by them. Others call them amateur hour. One Reddit commenter put it bluntly: “No one can realistically enforce that.” Another said working on a rev-share project was fine, because he put it on his resume and got a salaried job, even though the game never shipped and he never saw a cent.

That range of outcomes tells you something important: rev-share agreements aren’t inherently good or bad. The legal structure (and the game’s success, of course) determines which one you get.

This post covers what rev-share agreements actually are, the risks on both sides of the table, and what needs to be in writing before anyone opens a single project file.

Quick Facts: Indie Game Rev-Share

• The majority of indie rev-share projects never reach a sellable state. Community estimates put it above 90%.
• IP does not transfer automatically. Without a written assignment clause, contributors may retain ownership of the work they create.
• Rev-share contributors can be misclassified as employees if the studio controls their work, creating tax and penalty exposure.
• There is no industry standard for rev-share splits, vesting, or structure, which is exactly why the agreement matters so much.
• Platform fees eat first. Steam takes 30% of gross revenue before any split is applied.

What Is a Rev-Share Agreement?

A revenue-sharing agreement is a deal where contributors (artists, programmers, composers, writers, sound designers) work on a project without upfront pay in exchange for a percentage of the game’s future revenue.

The appeal is obvious. Studios with limited cash can bring on skilled collaborators. Contributors get a stake in the game’s success.

Everyone is aligned toward shipping.

The legal reality is more complicated. Unlike traditional employment or contractor arrangements where compensation is clear and immediate, rev-share introduces a web of contingencies:

• Will the game ship?
• Will it sell?
• How is revenue defined?
• What happens when someone leaves?
• Who owns what was built?

Without written answers to those questions, you don’t have a deal. You have an assumption that will eventually collide with reality.

From the Developer’s Side: A Bet on the Future

If you’re a developer being offered rev-share work, you need to walk in with clear eyes about what you’re actually agreeing to.

You May Work for Free

This is the fundamental risk of rev-share: if the game doesn’t ship, or doesn’t sell, your compensation is zero. Community consensus on this is blunt.

The overwhelming majority of indie rev-share projects never reach a sellable state. Even among those that do, revenue after platform fees (Steam takes 30%), taxes, and other deductions can leave each contributor’s cut smaller than expected.

This doesn’t mean rev-share is never worth it. Some contributors use the work for portfolio or resume value, which has real career benefits. Others genuinely believe in the project.

But you should enter with the assumption that you may never see a payment, and make your decision from there.

Enforcement Is a Real Problem

If the studio doesn’t pay out what’s owed, your practical legal options may be limited, especially in cross-border arrangements.

The cost of pursuing litigation often exceeds the potential recovery for a small indie title.

Before signing, make sure the agreement specifies exactly how and when payments are made, not just that they will be made.

IP Rights Are Not Automatic

This is the detail that catches the most people off guard. In the United States, the creator of a work owns the copyright to that work by default.

If you write code, create art, or compose music for a rev-share project without a written IP assignment clause or work-for-hire provision, you may legally retain ownership of what you created — even if you were working under a rev-share arrangement.

This sounds like it protects you, but it creates a problem for everyone: the studio can’t ship a game it doesn’t fully own, and a dispute over IP rights can kill a project or result in lengthy litigation.

The right answer is a clear written assignment in the agreement, not ambiguity.

What to Look for Before Signing

Before you commit to any rev-share arrangement, the agreement should clearly define:

• How revenue is calculated. Gross vs. net? Which platform fees and costs are deducted before the split applies? This is the single most important definition in the agreement.
• When and how you get paid. Quarterly? After certain revenue thresholds? Payments should be automatic, not discretionary.
• What happens if the project is abandoned. Do you retain any rights to the work you created? Does the studio?
• Dispute resolution. If there’s a disagreement, how is it resolved, and in which jurisdiction?

From the Studio’s Side: Smart Leverage, Real Risks

Rev-share is an appealing tool when cash is tight. You can bring on skilled contributors without upfront costs, and when everyone has a stake in the outcome, the incentive to ship a quality game is real.

But most studios don’t think carefully enough about the legal risks until something goes wrong. Here are the three areas I see cause the most problems.

Vesting and Performance Provisions

What happens when a contributor leaves midway through development? Or when someone isn’t delivering what the project needs?

Without explicit provisions, someone who contributed for two weeks before disappearing could theoretically claim the same rev-share as someone who worked on the project for two years.

That’s not a hypothetical, it’s the kind of dispute that kills studios and friendships alike. I’ve seen it fairly often in my work.

Your agreement needs to address all of the following:

• Vesting schedules. The contributor’s percentage vests (is earned) incrementally over time or upon hitting defined project milestones, rather than all at once at signing.
• Reduced share for early departure. If a contributor leaves before a defined milestone, their earned share decreases proportionally to reflect their actual contribution.
• Performance thresholds. What happens if agreed deliverables aren’t met, or quality standards consistently fall short? The agreement should include a mechanism to address this.
• Termination for cause. A clear process to remove a contributor from the rev-share arrangement entirely in the case of serious breach, misconduct, or abandonment.

This structure protects contributors, too. It makes the expectations clear from the start and gives everyone a defined path to earning their share.

The Employee Misclassification Risk

This is the issue that gets the least attention in rev-share discussions, and it’s potentially the most expensive.

If your “independent rev-share contributor” looks like an employee, you may have a worker misclassification problem under state and federal law. This means that you set their hours, control how and where they work, require attendance at regular meetings, and restrict them from working for other clients.

The consequences include back taxes, penalties, and potentially being required to provide employee benefits retroactively.

The safeguard is to ensure contributors are genuinely independent. They should:

• Set their own working hours
• Use their own tools and equipment
• Be free to work for other clients simultaneously
• Be paid based on deliverables, not time spent

Document that independence in the agreement. Alternatively, if the arrangement is better described as a partnership among co-creators, consider structuring it as an actual partnership or LLC rather than a studio/contractor relationship. That clarity can avoid misclassification exposure entirely.

Our guide to hiring game development contractors covers the independent contractor vs. employee distinction in more detail.

IP Assignment Must Be Explicit

As noted above, IP ownership does not transfer automatically when you commission work. A rev-share agreement that doesn’t include an explicit IP assignment clause (or a work-for-hire provision where applicable under the law) means contributors may legally retain ownership of what they built.

This is non-negotiable for any studio that wants to actually ship and sell the game. The IP assignment clause needs to:

• Cover all work created in connection with the project
• Be signed in writing by each contributor
• Specify that the assignment is effective at the time of creation, not just at launch
• Include a “moral rights” waiver where relevant (particularly for international contributors)

Note that “work for hire” has a specific legal meaning in the US and does not apply to all types of work or all contributor relationships. A game attorney can help you get the language right for your specific situation.

What a Rev-Share Agreement Should Include

Whether you’re drafting one or reviewing one, here’s the minimum a rev-share agreement needs to cover:

Revenue definition. What counts as revenue? At minimum, define it as net revenue after platform fees. Specify which deductions apply, and cap any additional deductions at a level you agree to in advance. Vague revenue definitions are where payment disputes start.

Split percentages. Each contributor’s share, stated clearly as a percentage. If the split changes over time (escalating tiers, milestone bonuses), those terms should be spelled out explicitly.

Vesting schedule. How and when does each contributor’s share vest? Tied to time, milestones, or some combination? What happens to unvested shares if someone leaves?

Early departure terms. Reduced share for contributors who leave before defined milestones. The reduction formula should be clear, not discretionary.

Performance provisions. What qualifies as a deliverable? What happens if the standard isn’t met? Who decides?

IP assignment. All work created in connection with the project is assigned to the studio. Signed by each contributor at the time of the agreement, not at launch.

Independent contractor status. A clause confirming the contributor’s independent status and the behaviors that support it.

Payment timing. When are payments made? Quarterly is common. Specify the timing, the reporting format, and the right to request supporting documentation.

Termination. Under what conditions can either side terminate the arrangement, and what happens to the share upon termination?

Dispute resolution. Governing law, jurisdiction, and whether disputes go to arbitration or court.

Common Red Flags to Watch For

On both sides of the table, these are warning signs that an agreement isn’t ready to sign:

• No revenue definition. “We’ll split revenue” is not an agreement.
• No IP assignment clause. The studio doesn’t own what’s being built.
• No vesting or departure provisions. Two weeks of work equals two years of work.
• No payment timeline. “When the game makes money” is not a payment schedule.
• No dispute resolution clause. Jurisdiction and governing law matter a lot when the studio and contributors are in different states or countries.
• Pressure to start work before the agreement is signed. This is the most common mistake. Once work has started without a written agreement, the leverage to negotiate shifts dramatically.

Action Steps

Whether you’re a contributor evaluating a rev-share offer or a studio putting one together:

• Get it in writing before work starts. Not after a few weeks. Before the first file is opened.
• Define “revenue” precisely. Gross? Net? After which deductions? This one definition shapes every payment that follows.
• Include a vesting and milestone structure. It protects contributors by making expectations clear, and protects studios from full shares for minimal contribution.
• Address IP ownership explicitly. Every contributor should sign an IP assignment before work begins.
• Classify contributors correctly. If the relationship looks like employment, treat it like employment — or restructure it into a genuine partnership.
• Have a game attorney review the agreement. The cost of a review is small compared to a dispute over game ownership after launch, or a tax bill from a misclassification finding.

FAQ

Is a verbal rev-share agreement enforceable?

Technically, verbal contracts can be enforceable, but proving the terms of a verbal rev-share agreement is extremely difficult. Without written documentation of the revenue split, vesting terms, IP ownership, and payment structure, disputes become a he-said/she-said situation. Always get it in writing before work begins.

Who owns the IP in a rev-share project?

This is one of the most common and costly oversights in rev-share deals. In the US, the creator of a work owns the copyright by default. If a contributor creates art, code, or music without a written work-for-hire clause or IP assignment in the agreement, they may retain ownership of that work. Get explicit IP assignment language signed before work begins. See also our post on contracts every game developer needs.

Can rev-share contributors be classified as employees?

Yes, and it’s a real risk. If the studio controls when, how, and where a contributor works, that person may look like an employee under state or federal law. Misclassification can result in back taxes, penalties, and benefit obligations. Make sure contributors are genuinely independent and document that independence in the agreement.

What happens if the game never ships?

In most arrangements, if the game doesn’t ship, contributors receive nothing. The agreement should address what happens to IP rights if the project is abandoned and whether contributors retain any rights to the work they created. Without explicit provisions, this becomes a costly legal question.

What should a rev-share agreement include?

At minimum: a clear definition of revenue, the split percentage for each contributor, a vesting schedule or milestone structure, provisions for early departure or underperformance, IP assignment or work-for-hire language, payment timing and frequency, independent contractor status language, and a dispute resolution clause.

Should I hire a lawyer to review a rev-share agreement?

Yes. The cost of a legal review is small compared to a dispute over IP ownership or unpaid revenue after a game launches. A game attorney will catch missing provisions around IP, vesting, and employee classification before they become expensive problems. Set up a consultation here.