$200, $500 or $800 for the Same Non-Exclusive Game: Pick the Payment Model Before You License HTML5 Games

Published rates to license HTML5 games differ by a factor of ten. Flat fee, term licence, revenue share and buyout price one thing: who carries traffic risk. Read a quote as a risk position rather than a price and the spread stops looking like disorder.

Most buy-side procurement conversations open the wrong way. Someone asks what a game costs, gets three answers that do not agree, and concludes the market is opaque. It is not opaque. It is priced. The number moves because buyer and licensor are agreeing, in each case, on a different answer to one question: if nobody plays this catalogue, who is out of pocket?

Answer that honestly about your own traffic and the payment model picks itself. Answer it dishonestly — which is what a confident forecast with no evidence behind it amounts to — and you will either pay for certainty you did not need or take on risk you cannot absorb.

💵 Three Published Price Lists, Three Different Answers

Start with what is actually written down, because a surprising amount of this market is public. Three sources published rates in the last two years and none of them agree.

• MDN Web Docs, Mozilla's developer documentation, puts the usual cost of a non-exclusive HTML5 licence at around $500, an exclusive at $2,000 to $5,000, and describes a subscription alternative at $20 to $50 per game per month. It also gives the revenue-share norm as a 70/30 or 50/50 split, collected monthly (MDN, Game monetization).
• Genieee's 2025 state-of-licensing write-up gives a much wider band: non-exclusive $200 to $2,000, exclusive $3,000 to $15,000+, revenue share 30–70% with 50/50 as the common landing point (Genieee, 2025).
• Playgama's 2026 monetization guide quotes non-exclusive licences at $300 to $800 per platform and exclusive buyouts at $5,000 to $25,000+.

The honest summary: a single non-exclusive HTML5 title trades somewhere between roughly $200 and $2,000, an exclusive between roughly $2,000 and $25,000, and the source-to-source disagreement is wide enough that any single figure quoted at you is a negotiating position, not a market rate. Two of the three sources are vendor-published, which is worth holding in mind. None of them is wrong. They are describing different games, different rights, and different levels of licensor involvement.

Note what the Playgama figure quietly reveals: it is priced per platform, not per game. The unit you think you are buying is not the unit the licensor is selling. The unit is a right, and rights are cut by platform, territory, domain, term and format.

🎚️ Every Payment Model Prices the Same Thing: Certainty Now Against Share Later

The clearest published evidence for how this trade is priced comes from an adjacent market. Voyer Law's 2026 market report reviewed more than 130 developer–publisher agreements signed between 2017 and 2026. Two numbers in it matter here.

Where the deal included an advance, the developer's revenue share averaged 57.9%. Where it did not, the average was 67.9%. Roughly ten points of ongoing share is what money-up-front cost. The report also found that 94.7% of advances were recouped, that 80.3% of advance deals used stepped revenue shares, and that in stepped deals the opening stage averaged 24% to the developer before rising to 60.3% after recoupment (summarised at Legal Moves Law Firm's 2026 royalties guide).

That is a publishing market, not a catalogue-licensing market, so do not port the percentages across. Port the physics. Whoever takes uncertainty off the other party's books gets paid for it, and the payment shows up as a worse split, a higher fee, or a longer commitment. There is no model in which you avoid the charge — only a choice about which side of it you sit on.

The useful question before you buy HTML5 games is therefore not "what is the cheapest way to pay for this?" but "how well can I forecast plays?" If you can forecast within a factor of two, buy certainty — it is cheap for you and expensive for the licensor. If you genuinely cannot, do not buy certainty at any price.

🧾 Model One: The Flat Fee Per Title

You pay once, you get the build, you run it. This is the model most people mean by HTML5 game licensing and it is the one the published price lists above are mostly describing.

The critical detail is scope, and MDN states it plainly: a non-exclusive licence is often a site-locked deal — the buyer gets the right to publish the game on their own given portal and cannot redistribute it further. A flat fee therefore buys one destination, not your business. Three domains, a white-label instance for a client and an APK wrapper is potentially four scopes, and a per-platform price list is telling you so before you ask.

Flat fee is right when: you need a small, known number of titles; you want permanence and no renewal exposure; your traffic is either already proven or irrelevant to the purchase, as with a booth game or a campaign microsite. It is wrong when: you need volume. Multiply the middle of any of those published ranges by 200 titles and you have a number no portal launch budget survives.

📚 Model Two: The Catalogue Term Licence

You pay for access to a defined set of titles for a defined term. Per-title cost collapses against flat-fee rates, because the licensor is amortising work already done across many licensees rather than pricing each transaction as a one-off.

What you are buying changes shape, though. A flat fee buys an asset. A term licence buys a rate — a continuing right that stops when the term does. That is not a defect; most operating costs work this way. But it puts renewal on your risk register permanently, and your catalogue becomes only as durable as your diligence about notice dates.

Term licence is right when: title count is the binding constraint, you are launching a white-label game portal or a carrier deck, and you need breadth on a fixed date. It is wrong when: you need one specific game to be yours indefinitely, or when your commercial model depends on owning something you can resell.

📈 Model Three: Revenue Share

Nothing up front. The licensor takes a percentage of what the games earn. On paper this is the buyer-friendly model, and for a first portal with unproven traffic it often genuinely is — you have moved forecast risk onto the party who has seen a thousand forecasts and can price yours.

The published norms cluster tightly: MDN gives 70/30 or 50/50, and Genieee's 2025 figures give a 30–70% band with 50/50 as the common outcome. If you are quoted far outside that band in either direction, ask what else in the deal is doing the work.

Three clauses decide whether a revenue share is a good deal, and none of them is the percentage:

• What counts as revenue. Gross ad revenue, net of ad-network fees, or net of ad-network fees plus your hosting and payment costs are three materially different bases for the same percentage. Get the definition in writing with a worked example attached.
• Who reports, and can you check. Voyer Law's 2026 sample found audit rights in 88.4% of deals with an advance but only 66.7% of deals without one — the deals with no money changing hands up front are exactly the ones where verification gets dropped. If the licensor's dashboard is the only source of truth, that dashboard is the contract.
• Whether the share steps. Stepped shares are standard in publishing and appear in licensing too. A rate that improves after a threshold is fine. A rate that quietly worsens after a term renews is not.

Revenue share has one upside flat fees structurally cannot: it aligns the licensor with your traffic. A licensor paid once has no financial reason to care whether your portal works. A licensor on a share has a direct one.

🔒 Model Four: Exclusivity and Buyout

The most expensive option and the narrowest. Exclusive rates in the published sources run from roughly $2,000 at the bottom of MDN's range to $25,000 and beyond at the top of Playgama's. You are paying a multiple of the non-exclusive price to stop anyone else running the same title.

Be honest about whether that is worth anything. For a general-audience arcade it usually is not: players do not choose portals by title uniqueness, so you are buying a differentiator nobody is shopping for. Exclusivity earns its price in narrower cases — a hero title a brand is putting media spend behind, a game carrying a client's IP, a carrier tender where a named exclusive is a scored requirement. If your reason is a general feeling that competitors should not have your games, you are about to pay a large premium for a feeling.

🧮 Which Model Your Traffic Argues For When You License HTML5 Games

Four buyer scenarios, and the model each one actually points to:

• 200 titles live on a carrier portal in six weeks. Term catalogue licence. Per-title flat fees at published rates are arithmetically out of reach at that count, and nothing you commission arrives in six weeks. Placement is contractual, so you are not buying protection against a traffic miss.
• One game for a trade-show booth, live for three days. Flat fee, single title, scope bought narrow. No revenue to share, no second destination. This is also the scenario where commissioning a bespoke game can genuinely beat licensing — a licensed catalogue is the wrong tool when the game itself is the creative.
• An APK catalogue for an OEM preload or an operator app store. Term licence with APK game licensing scope written explicitly, because HTML5 rights do not imply Android packaging rights and a store listing is a redistribution act. Ask for the format matrix before the price.
• A first portal, self-funded, no audience yet. Revenue share, and resist the urge to look clever by pre-buying. You do not have a forecast. Buying certainty against a number you invented is the most common way small operators lose a launch budget.

⚠️ Five Ways Buyers Misprice the Model

1. Comparing per-title cost across models. A flat fee, a per-title slice of a term licence and a revenue share are a purchase, a rent and a contingent liability. Normalise to cost per title per year of expected use first.
2. Assuming "per platform" means "per company". It rarely does. Domains, apps, client instances and formats are commonly separate scopes. Count yours before you request a quote, not after you sign one.
3. Taking a revenue share with an undefined revenue base. The percentage is the part everyone negotiates; the definition is the part that decides the money.
4. Buying a buyout for a title with a twelve-month shelf life. Perpetual rights on content you will rotate out next year is the purest form of overpaying in this market.
5. Treating the licence fee as the cost. Integration, QA across your device matrix, localisation, hosting and merchandising do not scale down just because the licence did. A catalogue arriving cheap does not arrive free.

📋 Questions to Put to a Licensor Before the Price Conversation

Ask these before anyone quotes you a number. The answers determine what the number even means.

• What exactly is one unit of scope here — a domain, an app, a client, a territory, a format?
• Which formats come under one licence conversation: HTML5 builds, Android APK builds, source where applicable?
• If I want a title on my web portal and in an Android app, is that one licence or two?
• On a revenue share: what is the revenue base, who reports it, and do I have an audit right?
• On a term licence: what is the notice date, and what happens to live URLs the day the term ends?
• Can I rebrand, re-skin, or change the splash and logo, and does that change the price?
• Are you the rights holder or a reseller — and if a reseller, can you show the chain?

That last question separates supplier categories more than price does. Self-serve marketplaces and asset sellers are efficient at handing you files. Aggregators are efficient at breadth. A direct licensor answers for the rights themselves, which is what you need when a client's legal team asks where the game came from. Our licence and pricing overview sets out how scope is structured for each of these cases.

🎮 What You Actually Get When You License HTML5 Games From a Direct Licensor

Forestry Games has operated since 2017 and licenses a catalogue of 1,049 titles, with games also published on Google Play and the Apple App Store and HTML5 development done in-house. A licence conversation here covers HTML5 builds and Android APK builds together rather than as two procurements, with source where applicable, branding and re-skin options, and hosting on either side.

The practical value of catalogue depth is not the headline count — it is that scope, format and volume can be matched to one use case at a time. A carrier deck, a kids' section, a single event game and a white-label game portal are four different cuts of the same catalogue, priced against what each actually needs. You can license HTML5 games for a web portal, license Android games as APK builds for stores and preloads, or take both under one agreement. Distribution and monetization support sit alongside the licence rather than as a separate engagement — which matters most to the buyers choosing a revenue-share model precisely because they do not yet have the traffic.

🏰 Licensing Branded Games on Top of a Catalogue

Branded titles price differently for a structural reason: a branded licence carries a second rights holder, whose approval process and financial terms sit on top of yours. In brand licensing generally, advances commonly run between 25% and 50% of the guaranteed total, according to licensing platform Flowhaven — a reminder that branded content is a commitment model, not a per-unit purchase.

Forestry Games works with branded IP and has brand partnerships including Disney, Nickelodeon, Cartoon Network and Warner Bros. Businesses can license branded games through the catalogue for campaigns, portals, events and apps. If branded content is in scope, raise it at the start rather than after the generic licence is drafted — the approval calendar, not the fee, usually sets your launch date. Ask for a licence scope or request a portal demo, and bring the seven questions above with you.

🧭 Decide the Model, Then Ask the Price

A non-exclusive game is quoted at $200 by one source and $800 by another not because somebody is overcharging, but because "a game" is not a unit of anything. The unit is a right, cut by scope, term and format — and the payment model you pick is a statement about how much of your own traffic forecast you are willing to underwrite.

So work in that order. Write down your title count, your destinations, your formats and your honest confidence interval on plays. Pick the model those four facts argue for. Then put them in front of a licensor and ask what it costs. You will get a straighter answer, and you will be able to tell whether it is a good one. If you already know your numbers, start with a licence scope for the titles you need rather than a price list for titles you do not.