An HTML5 game has no app store, no install step and no platform fee. That makes distribution easy and monetization harder, because the revenue tooling built over the last decade was built for installed mobile apps. This page sets out what actually earns on the web in 2026, which ad format belongs in which kind of game, and where rewarded video stops making sense.

What is HTML5 game monetization?

HTML5 game monetization is the practice of generating revenue from a game that runs in a browser rather than as an installed application, using advertising, in-game purchases, subscriptions, or licensing the game to portals and publishers. Because browser games are free to enter and carry no install friction, the dominant model is free-to-play supported by ads, with purchases layered on top where the game has an economy deep enough to support them. The structural difference from mobile app monetization is where the money comes from. A mobile game earns from an audience that downloaded it and will probably return. An HTML5 game earns from an audience that arrived from a link, a portal or a search result and may play once. That shapes everything: the ad formats that work, the CPMs available, and how aggressively you can ask a player for anything.

How do HTML5 games make money?

HTML5 games make money through four channels, and most successful titles use more than one. The practical question is not which single model to pick, but which combination matches your session length and audience size.

• • Rewarded video ads. The player opts in to watch a video in exchange for something concrete — a continue, a hint, doubled currency. Highest CPMs of any web ad format, and the only one players choose.

• • Interstitial and pre-roll ads. Full-screen ads at a break point or before the game loads. No opt-in, so they trade player goodwill for guaranteed impressions. Our breakdown of rewarded video versus interstitial ads covers the eCPM difference in detail.

• • Display and banner inventory. Page-level ads around the game canvas. Low CPMs, but they run continuously and cost nothing in player attention if placed outside the play area.

• • In-game purchases and licensing. Cosmetics, currency packs, ad removal, or flat licensing fees from portals that want your game on their site. Purchases on the web convert at lower rates than in app stores, because there is no stored payment method waiting.

For most indie and mid-size HTML5 titles, ads carry the revenue and purchases are the upside. The hybrid model of rewarded ads plus IAP works when the game has an economy players already care about; where it does not, adding a store is engineering time that returns nothing.

What is the best ad format for HTML5 games?

Rewarded video is the best ad format for HTML5 games in the majority of cases, because it is the only format where the player agrees to the ad in advance and receives something for it. That opt-in is what supports the price: advertisers pay more for a completed view from a player who chose to watch than for an impression served to someone who was trying to get past it. The intrusiveness data supports the ordering. Research from IPG Media Lab found that 17% of users consider pre-roll ads intrusive, against 60% for out-stream and 72% for mid-roll placements. Any format that interrupts active play is paying for its impressions in retention.

Format	Player opts in	Web CPM	Best fit
Rewarded video	Yes	$4+ with AppLixir	Games with lives, currency, hints or continues
Interstitial / pre-roll	No	[DATA NEEDED]	Session boundaries in short-session arcade and .io games
Display / banner	No	$0.50–$2 typical	Page real estate around the canvas, always-on baseline
Offerwall	Yes	[DATA NEEDED]	Deep economies where players will complete multi-step tasks

The honest ranking: rewarded video first, display as a baseline that costs nothing, interstitials only at genuine session boundaries, offerwalls only if your economy is deep enough to justify them. If you are weighing the last two, the comparison of rewarded ads versus offerwalls for web games lays out where each one earns.

HTML5 game ad revenue: what CPMs look like on the web

HTML5 game ad revenue is driven by three numbers multiplied together: CPM, impressions per daily active user, and fill rate. AppLixir delivers $4+ CPM on web rewarded video across a network serving more than 100 million monthly impressions, compared with roughly $0.50–$2 for typical web display inventory. That gap is the entire argument for rewarded video on the web. CPM alone does not tell you what a game earns. A $4 CPM at one rewarded view per daily active user is a very different business from the same CPM at three views. The lever most studios have is not price but opportunity: how many natural moments in the game call for a reward, and how many players take the offer. Our guide to how much rewarded video ads pay on web games works through the arithmetic with worked figures. Two factors move CPM in ways you do not control directly. Geography matters — traffic concentrated in high-value markets prices above traffic that is not. And seasonality matters: Q4 advertiser budgets lift rates, and January resets them. Plan annual revenue against an average, not against a December screenshot.

Do Unity Ads, AdMob or AppLovin work for HTML5 games?

No. Unity Ads, Google AdMob, AppLovin and ironSource are mobile application networks. Their SDKs target iOS and Android app builds, their demand is bought against app install and in-app event targeting, and they do not serve browser inventory. An HTML5 game, a WebGL build hosted on a page, or an .io game is outside what those networks sell. This catches a lot of teams out, particularly studios porting a mobile title to the browser or shipping a Unity WebGL build and assuming the Unity ad integration comes with it. It does not. We walk through exactly what breaks and why in Unity Rewarded Ads and AdMob on WebGL. AppLixir exists for the inventory those networks leave behind. It is a rewarded video platform built for web games and browser-based content from the start, not a mobile SDK wrapped for the browser. That is the distinction worth checking before you commit integration time to any network: does it sell browser inventory, or does it sell app inventory?

How to monetize an HTML5 game with rewarded video

To monetize an HTML5 game with rewarded video, you add a container element to the page, call the AppLixir rewarded video ads SDK when a player accepts an offer, and grant the reward only when the ad reports completion. The SDK runs in the browser; there is no native build step and no app wrapper.

initializeAndOpenPlayer({
  apiKey: "YOUR_API_KEY",
  injectionElementId: "applixir-ad-container",
  adStatusCallbackFn: (status) => {
    if (status.type === "complete") grantReward(); // only a completed ad earns the reward
  },
});

Full setup, including keys, the container element and ads.txt, is in the AppLixir documentation, and there is a step-by-step walkthrough in our guide to adding rewarded video ads to an HTML5 game.

Place the offer where the player already wants something

The code is the small part. Placement decides revenue. Offer the rewarded video at the moment the player has just lost a life, run out of currency, or hit a wall they would pay to get past. An offer surfaced during active play gets dismissed; an offer surfaced at the point of need gets taken.

Make the reward change the next minute of play

A reward that is purely cosmetic or trivially small does not earn repeat views, however often you offer it. A continue, a doubled run payout, a hint on a stuck level — these are worth the player’s attention. State the reward before the ad starts, and deliver it immediately after the completion callback fires.

Cap frequency and verify completion server-side where it matters

Cap offers per session and space them apart. Where the reward has real economic value in a persistent game, validate it rather than trusting the client alone — see our notes on preventing rewarded ad fraud and reward abuse.

When rewarded video is the wrong answer

Rewarded video is not the right format for every HTML5 game, and the fastest way to waste an afternoon is to integrate it into a game that has nothing to reward. There are three clear cases where it does not fit.

• • No in-game economy. If the game has no lives, currency, hints, continues or unlocks, there is nothing to grant on completion. Build the economy first, or run display inventory around the canvas and leave it there.

• • Audience below the threshold. AppLixir’s minimum publisher threshold is 5,000 daily active users. Below that, rewarded video revenue will not justify the integration and reporting overhead, and your effort is better spent on traffic.

• • Sessions too short to reach a decision point. A game a player opens for twenty seconds never arrives at a moment of need. Lengthen sessions before monetizing them.

Enterprise studios add a fourth consideration: retention risk. The way large web studios add rewarded ads without hurting retention is to ship the offer to a traffic slice first, hold a control group, and compare day-1 and day-7 retention alongside revenue before a full rollout. If retention moves the wrong way, the placement is wrong, not the format.

Where Poki, CrazyGames and other distribution platforms fit

Poki, CrazyGames and similar portals are distribution, not competition. They bring players to a browser game at a scale most studios cannot reach on their own domain, and they handle monetization on their own properties. AppLixir sits alongside that: it monetizes the traffic you own — your own site, your own domain, your embeds, your direct players — on terms you control. The practical setup for a studio running both is straightforward. Portals supply reach and a portal-side revenue share. Your own site supplies a smaller but fully owned audience where you run your own rewarded video ads and keep the relationship with the player. The two stack; neither replaces the other. For the broader picture on owned-traffic revenue, see our guide to how browser games earn revenue.

Which metrics tell you HTML5 game monetization is working

Four metrics tell you whether HTML5 game monetization is working, and they have to be read together. A gain in one at the cost of another is usually not a gain.

• • eCPM — effective revenue per thousand impressions, the blended price you actually realise across all fills.

• • ARPDAU — average revenue per daily active user, which captures price and frequency in one number. Our guide to improving ARPDAU covers what moves it.

• • Completion rate — the share of started ads that run to the end and trigger the reward. Low completion usually means the offer was taken reluctantly or the placement interrupted something.

• • Fill rate — the share of ad requests that return an ad. An unfilled request is a player who asked for a reward and got nothing, which costs trust as well as revenue.

Judge every change to placement, frequency or reward value against retention as well as revenue. A placement that lifts ARPDAU 15% and drops day-7 retention is a loss on a thirty-day view.

FAQ

How do I monetize an HTML5 game?

Monetize an HTML5 game by combining rewarded video ads at natural points of need with display inventory around the game canvas, and add in-game purchases only if the game has an economy worth buying into. Rewarded video carries the revenue for most browser titles because it earns the highest CPM and the player opts in. Start with the ad format, measure ARPDAU and retention together, and layer purchases on later.

How much do rewarded video ads pay on web games?

AppLixir delivers $4+ CPM on web rewarded video, against roughly $0.50–$2 for typical web display inventory. Actual earnings depend on how many rewarded views each daily active user takes, your audience geography, and seasonality — Q4 prices above Q1 across the market. The full revenue arithmetic is in our guide to what rewarded video pays on web games.

Do Unity Ads or AdMob work for WebGL and browser games?

No. Unity Ads, AdMob, AppLovin and ironSource serve mobile application inventory and do not serve browser inventory, so they cannot monetize a WebGL build running on a web page or an HTML5 game on your site. Teams porting a mobile title to the browser often discover this after the port is complete. A browser game needs a network that sells web inventory, which is what AppLixir does.

Are rewarded video ads GDPR compliant for players in Europe?

Yes, when consent is collected and signalled correctly. AppLixir has TCF 2.4 and GDPR compliance built in via Didomi, so consent is gathered and passed to demand partners as part of the ad request rather than being left for the publisher to assemble. For enterprise studios with players across the EU, that removes a significant compliance build from the integration.