Exclusivity Is the Most Over-Bought Clause in a Game Licence

Exclusivity is the clause buyers fight hardest for in an HTML5 game licence and the one that matters least. Domain scope, sublicensing and branding rights decide the value.

Sit in on enough licensing calls and the pattern repeats. The buyer opens with exclusivity. Can we have it, what does it cost, can we at least have it in our territory. Twenty minutes go on that. Then the contract arrives, gets a light skim, and gets signed — and nobody has asked how many domains the games may run on, whether the buyer may put them behind a carrier's paywall, or whether the developer's logo has to stay on the loading screen.

Six months later the portal wants to launch a second brand, or an operator asks for a bundled version, and the answer is no. Not because the deal was bad, but because the parts of it that governed those decisions were never negotiated.

🔍 A Licence Is a List of Permissions, Not a Purchase

The word "buy" does a lot of damage here. You are not buying games. You are buying an enumerated set of things you are permitted to do with them, and everything not enumerated is retained by the licensor by default.

Zachary Strebeck's breakdown of term, territory and scope on Game Developer is from 2014 and has aged perfectly, because contract structure moves slower than platforms do. His advice to licensors — be very specific about what rights are being licensed, and license only what is necessary — is exactly the discipline working against you when you sit on the buyer's side of the table. A well-drafted grant is narrow on purpose.

So the useful question is never "is this exclusive?" It is "what am I permitted to do, on how many surfaces, for how long, and can I let someone else do it too?" Write that list before you read the contract. Then check the contract against your list rather than reading it front to back and nodding.

💸 The Published Price Ranges Disagree by an Order of Magnitude

Before negotiating anything, understand that there is no market rate you can look up, and anyone who tells you otherwise is selling something.

Genieee's May 2025 survey of HTML5 licensing rates puts non-exclusive licences at $200–$2,000, exclusive deals at $3,000–$15,000 and up, and revenue-share splits between 30% and 70% with 50/50 as the common landing point. Playgama's April 2025 piece on licensing strategy describes non-exclusive platform deals at $15,000–$40,000 and cites a $130,000 exclusive offer. Practitioners on the html5gamedevs forum have discussed non-exclusive sales in the $400–$600 range with exclusives passing $2,000.

Those are not small discrepancies. The gap between $200 and $40,000 for a nominally identical licence type is not measurement noise — it means "non-exclusive HTML5 game licence" describes a category of transaction, not a product with a price. Both ends are probably honest about the deals their authors see. Both are also published by parties with an interest in the number.

The practical consequence: quoting a range you found online as leverage will mark you as someone who has not done this before. What moves price is title quality, catalogue size, how many surfaces you want, and whether you are asking the licensor to give up other sales.

🌐 Domain Count Is the Clause That Decides Whether You Have a Business

Most non-exclusive licences in this market are scoped to one property. DoonDook Studio's published terms are typical of the shape: a standard non-exclusive licence covers a single website, app or platform, with an unlimited-domain tier sold separately.

Single-domain scope is fine for a company running one portal forever. It is quietly fatal for almost every other plan:

• Multi-brand operators. One licence does not cover your second portal, even if you own both.
• Agencies. Deploying the same title for two clients is two licences, and using client-facing scope for internal demos is usually outside the grant too.
• Telecom and B2B2C deals. An operator portal, a partner's app and your own site are three surfaces. Signing a carrier deal on single-domain licences is how a launch date slips by a quarter while somebody renegotiates.
• App wrappers. Whether a WebView build of your portal counts as the same platform or a different one is a question you want answered in writing, not after the store listing goes live.

Ask what a "platform" means in the contract's own words. If the definition is vague, that ambiguity resolves in the licensor's favour when it matters.

🔁 Sublicensing Is the Clause Everybody Skips

This is the one worth reading twice, and there is a public contract that shows why.

GameDistribution publishes its developer game licence agreement openly. Two clauses matter. The grant is a "worldwide, royalty-free, non-exclusive license" that includes "the right to sublicense to the extent necessary for the proper performance of this Agreement." And the developer's economics: 33% of Net Revenue, paid within 60 days of the monthly report, and only once the balance clears EUR 100.

Read those together and the model is legible. The aggregator takes a non-exclusive grant with sublicensing attached, then passes the games onward to a network of portals. That downstream distribution is the product. Without the sublicensing right there is no network — and the 33% share is the price of it.

Now flip to your side. If you licence a catalogue and plan to place those games with anyone else — an operator, a client, an OEM, a partner site — you need sublicensing rights, and a licence silent on the point does not grant them. This is the single most common gap between what a portal operator thinks they bought and what the paper says. It is also the cheapest thing to fix, because you fix it before signing, in a sentence.

If the licensor will not grant it broadly, the workable middle is a named-partner list you can add to with written consent not to be unreasonably withheld. That gives them control over who ends up carrying their games without making every new deal a fresh negotiation.

🏷️ White-Label Is Sold Separately From Non-Exclusive

Buyers routinely conflate these. Non-exclusive describes who else may licence the game. White-label describes whether you may strip the developer's branding and present it as your own. They are independent, and in this market they are usually priced independently — DoonDook's terms, again typical, state that you may not change or remove the original developer's branding without buying the white-label service.

A splash screen with someone else's logo is not a cosmetic issue for every buyer, but it is decisive for some. Branded campaign work almost always requires it. Operator portals frequently require it. If your business depends on a coherent own-brand experience, that clause is worth more to you than exclusivity and should be where the negotiating energy goes. See white-label games for what that scope typically covers.

Where source code sits in this

Source access is a separate axis again. A running-build licence lets you publish the game. Source lets you modify it — reskin it, change difficulty curves, swap the ad SDK, strip an analytics call a client's legal team objects to. Plenty of buyers discover they needed modification rights only when a compliance requirement lands. If reskins or client customisation are part of the plan, source code terms belong in the first conversation, not a later one.

🗺️ Territory and Term Do Real Work

Territory is where exclusivity gets interesting, and it is the version most buyers should actually be asking for. Strebeck's example is the standard construction: exclusive in one territory, non-exclusive everywhere else. A licensor who will not go exclusive worldwide will often go exclusive in a single market, because it costs them far less. If your business is one country's telecom sector or one language's portal audience, territorial exclusivity gets you the competitive protection you wanted at a fraction of the price.

Term deserves the same scrutiny in the other direction. A one-year licence on a catalogue you are building a portal around means your content costs reset annually with no leverage, because by then you have SEO equity, player accounts and retention data tied to those titles. Multi-year with a renewal option priced at signing is worth more than a discount on year one. Check what happens at expiry, too: whether you must pull the games immediately, and whether players mid-session or mid-progression are contemplated at all.

🎯 When Exclusivity Genuinely Is Worth It

None of this says exclusivity is never worth buying. It says it is over-bought relative to its effect. It earns its price in three situations:

1. Brand and campaign work. If a game carries a client's IP, non-exclusive is incoherent — the whole point is that it exists nowhere else.
2. A title that is genuinely your differentiator. If one game drives a disproportionate share of your retention, protect it. That is usually a handful of titles, not a catalogue.
3. Competitive lockout in a defined market. Almost always better bought as territorial exclusivity than global.

For catalogue depth — the hundreds of titles that make a portal feel populated — exclusivity buys you very little. Players do not comparison-shop match-3 titles across portals. Spending catalogue budget on exclusivity for filler content is the clearest form of over-paying in this market.

🚫 Five Ways Buyers Over-Pay

• Buying global exclusivity to solve a single-market problem. Territorial scope is dramatically cheaper and usually sufficient.
• Negotiating price per title before scope. A cheap single-domain licence you have to buy three times is not cheap. Settle what you may do, then talk money.
• Assuming sublicensing is implied. It never is. If your model involves placing games with third parties, it is a deal term, not a detail.
• Quoting market-size forecasts as leverage. Published estimates for this sector disagree by roughly two-to-one — The Business Research Company puts browser games at $8.01bn in 2026 while several HTML5-specific reports land nearer $6bn — and neither tells a licensor anything about what your deal is worth.
• Treating the licence as a procurement task. The clauses that constrain you are product decisions. Whoever owns the roadmap should read the grant.

🎮 Where Forestry Games Fits

Forestry Games has licensed games since 2017 and maintains a catalogue of 1,049 HTML5 and Android titles, with games also published on Google Play and the App Store. It develops HTML5 games in-house, works with branded IP, and has brand partnerships including Disney, Nickelodeon, Cartoon Network and Warner Bros. Buyers range from telecom operators and agencies to portal owners and event companies — which is why scope questions come up constantly, and why they are worth settling early rather than discovering later. The catalogue and licensing and pricing pages are the place to start if you want to see how the options are structured.

🧭 Before You Sign

Write your permission list first, in plain language, before any contract is in front of you. How many properties, in which countries, for how long, rebranded or not, modified or not, and passed on to whom. Six lines is usually enough.

Then read the grant clause and the definitions section against that list — those two together decide almost everything, and the rest of the document is mostly machinery. Anything on your list that the grant does not clearly permit is a question to raise before signing, not a risk to carry.

Do that and exclusivity stops being the headline term and becomes what it should be: one line item among several, priced against what it actually protects.