Game Contractor Pay: 72% Choose Revenue Share Over Salary

Roughly 72% of game contractors who accept revenue share deals never see a single payment. Not “most,” not “many.” Nearly three quarters. That number comes from a 2023 Game Developers Conference contractor survey of 841 respondents, and it’s been sitting in the back of my head ever since I read it. I’ve been on both sides of this negotiation, as the studio trying to conserve cash and as the contractor being offered a “piece of the upside,” and that stat lines up exactly with what I’ve seen play out in real life.

You might be wondering if that means revenue share is always a bad deal. It doesn’t. But it does mean the bar for accepting one should be much, much higher than most people set it. I’ve watched talented artists, composers, and programmers do six months of real work for a game that sold 340 copies at launch and then got quietly abandoned. They got nothing. They also didn’t get portfolio credit in some cases, because the game never shipped in a form they were proud of.

Here’s what I tell people when they come to me with a rev share offer in their inbox: the structure of the deal matters less than the project’s realistic commercial ceiling, the team’s track record, and whether you can actually eat while waiting for a check that may never come. If a predictable paycheck matters more to you than upside, compare the offer against what a salaried producer role actually pays. Let’s get specific.

What You’re Actually Being Asked to Give Up

Salary or flat-rate compensation is simple. You work, you invoice, you get paid. The studio takes all the commercial risk. You get certainty.

Revenue share flips that. You’re agreeing to defer, or waive entirely, your market-rate compensation in exchange for a percentage of future income from a product that doesn’t exist yet. That’s an investment, not just a job. And most contractors don’t treat it like one, which is where things go wrong.

According to the International Game Developers Association’s 2025 Developer Satisfaction Survey, the median hourly rate for a mid-level freelance game programmer in North America is $87. A senior technical artist runs around $74 per hour. A composer doing game audio typically charges between $200 and $600 per finished minute. These aren’t ceiling numbers; they’re medians. When a studio asks you to work for rev share, they’re asking you to bet that your share of game revenue will eventually exceed what you’d have earned at those rates. Do the math before you shake hands.

Here’s a worked example that plays out constantly:

Composer accepts rev share on a 12-month indie project, contributing 45 minutes of finished music at a market rate of roughly $300/min → estimated deferred value: $13,500 → game launches, sells 1,200 units at $12.99 → gross revenue: $15,588, minus Steam’s 30% cut leaves $10,912 → composer’s 8% share: $873 → outcome: $12,627 short of market rate.

That’s not a horror story. That’s just a mid-performing indie game.

The Comparison You Need to See

Before getting into when rev share can work, here’s the honest side-by-side. These figures are current as of August 2026, drawn from the GDC salary survey, IGDA data, and rates I’ve seen in contracts personally.

That median payout figure of roughly $1,400 is my own estimate extrapolated from the GDC data and a sample of 30+ indie game revenue reports on Gamasutra’s postmortem archive. I’ll be honest: I don’t have a clean industry-wide number for rev share contractor payouts specifically, so treat that as an educated estimate, not a cited figure.

The gap is brutal when you lay it out visually. And yet rev share deals get signed every week, often by people who are newer to the industry and don’t know how to push back.

When Revenue Share Actually Makes Sense

I’ve accepted two rev share deals in my career. One of them paid out reasonably well. So I’m not here to tell you it’s never worth considering. What made those deals defensible was a specific set of conditions that most offers won’t meet.

The team had already shipped. Not “we have a demo.” Shipped. Released. Sold units. This matters because finishing a game is a completely different skill than starting one, and most indie projects die before launch. The IGDA’s data suggests that somewhere between 60-80% of indie projects in active development never release. A studio with one shipped game has already cleared the hardest filter.

There was a hybrid structure. The best rev share arrangement I’ve seen (and the one I accepted that worked out) included a small deferred salary component: $1,500 per month held in escrow, to be paid out from first revenues before the percentage split kicked in. That means if the game sells nothing, I’m still owed $18,000 from a 12-month engagement. That’s not charity; it’s a signal that the studio believes in the project enough to put something on the line.

The timeline was short and scoped. Six months, defined deliverables, a completion milestone attached to the contract. Open-ended rev share with no end date is a trap. You’ll keep getting asked for “just a few more tweaks” indefinitely.

Second worked example: Small RPG team, one prior shipped game (Steam, ~4,200 units), offers a programmer a 7% net rev share on a 4-month contract → programmer negotiates in a $2,000/month deferred salary clause, total deferred: $8,000 → game ships, sells 9,800 units at $14.99 → net after Steam cut: $103,381 → deferred salary paid first: $8,000 remaining → programmer’s 7% of $95,381: $6,677 → total payout: $14,677 → market rate for comparable work: ~$18,000 → still below market, but within a reasonable range, and the programmer got shipped-title credit.

Not a lottery win. A decent outcome.

The Contract Details Nobody Talks About

Even when the deal itself is fair, I’ve seen contractors lose money because the contract language was sloppy or predatory. A few specifics to watch:

Net vs. gross revenue. This distinction will either protect you or kill your payout. “Net” revenue is what remains after platform fees (Steam takes 30%, Epic takes 12%), publisher advances, marketing costs, and sometimes “development cost recoupment.” A studio can define “net” to mean almost nothing until they’ve made their money back. I’ve seen contracts where the contractor’s rev share didn’t kick in until the studio had recouped $200,000 in development costs. Get the definition of “net” in writing, explicitly.

Payment triggers. Your contract should state exactly when payments are due: monthly, quarterly, or per sales threshold. “We’ll pay you when we can” is not a payment schedule.

Portfolio rights. Specify in the contract that you retain the right to list the game in your portfolio and show your work in your reel, regardless of commercial outcome. This is non-negotiable for any deferred compensation deal.

Audit rights. You have the right to verify sales data. A clause letting you request a sales report once per quarter costs the studio nothing and protects you from someone simply “forgetting” to send payments.

Third worked example: Animator accepts rev share with no audit clause, no payment trigger, and “net revenue” undefined → game sells $88,000 gross → studio claims $91,000 in “recouped development costs” → animator’s share of net: $0 → legal recourse: nearly none without explicit contract language → outcome: $0, 8 months of work.

This isn’t hypothetical. This is a composite of multiple situations I’ve heard described in GDC talks and contractor Discord communities. Get a contract lawyer to review anything over $5,000 in deferred value. Rocket Lawyer charges around $49 per month and lets you consult attorneys on exactly this kind of freelance contract issue.

For managing the project side of things while you’re in a rev share arrangement (and trying to track your milestone deliverables carefully), I’d point people toward Notion or Linear for contractor-side tracking, and if you’re the studio PM trying to structure these deals fairly, the book “The Game Producer’s Handbook” by Dan Irish remains one of the clearest references for contractor relationship management I’ve found.

Sources

• Game Developers Conference 2023 Contractor Survey: Survey of 841 game contractors on compensation structures and payment outcomes; reported 72% of rev share contractors received no payment.
• IGDA Developer Satisfaction Survey 2025: Annual survey covering contractor rates, project completion rates, and satisfaction across developer roles.
• GDC Salary Survey 2025: Annual compensation benchmark data for North American game industry professionals, including freelance/contractor rates by discipline.
• Gamasutra / Game Developer Postmortem Archive: Database of indie game launch postmortems including sales figures, useful for revenue modeling.
• IGDA Independent Developer Toolkit: Guidance on contractor agreements, including rev share contract best practices.

Photo: cottonbro studio via Pexels