Google's 2026 rules for HTML5 playables in App campaigns and AdMob inventory: 5 MB ZIP, ExitApi.exit, orientation meta tag, allowed libraries and validation.
Written by Yonathan Avivi, Head of Marketing, Genie Labs
Technical review by Yotam Wolf, CTO · Published Oct 8, 2026 · Last verified Sep 30, 2026 · 6 min read
Google runs HTML5 playables in App campaigns, which also serve on AdMob inventory, and accepts them as a ZIP of up to 5 MB with no more than 512 files. The playable needs a complete HTML structure in UTF-8, uses ExitApi.exit from Google's exitapi.js for the click to the store, and declares its orientation with an ad.orientation meta tag. MRAID isn't required. External requests are limited to Google Fonts and Google-hosted jQuery, GreenSock and CreateJS. Check every build with Google's HTML5 Validator before upload.
Key takeaways
ZIP only, 5 MB at most, 512 files at most, up to 20 ZIPs per ad group.
Click out with ExitApi.exit. If you include neither exitapi.js nor MRAID, Google adds its own CTA.
Declare orientation in a meta tag: portrait, landscape, or both.
Google is the one network that allows a few external libraries, and only those.
Genie Playable exports a Google-ready ZIP of every playable from the same source as your other networks.
What are Google's HTML5 playable requirements?
Requirement
Google's rule
Where it runs
Google Ads App campaigns, including AdMob inventory
File
ZIP, 5 MB at most, 512 files at most
Per ad group
Up to 20 ZIPs
HTML structure
<!DOCTYPE html>, <html> and <body> with explicit end tags, UTF-8
Click to store
Include https://tpc.googlesyndication.com/pagead/gadgets/html5/api/exitapi.js and call ExitApi.exit
MRAID
Not required. Google accepts exitapi.js or an MRAID equivalent; if neither is present it adds its own CTA
Orientation
Meta tag ad.orientation: portrait, landscape, or "portrait,landscape". Sizes 320x480 or 480x320, responsive
Sound
Not enabled before the user interacts
External requests
Only Google Fonts and Google-hosted jQuery, GreenSock and CreateJS
Not eligible
Pre-registration and engagement App campaigns
What goes in the HTML?
A minimal Google playable has three things most other networks don't ask for: the full HTML skeleton with end tags, the orientation meta tag, and the exitapi.js script. For example:
Everything else lives inside the ZIP: images, audio, fonts and your own scripts, referenced by relative paths.
How is Google different from AppLovin and Meta?
Google
AppLovin
Meta
Format
ZIP
Single inlined HTML
Single HTML or ZIP
Click-out
ExitApi.exit
mraid.open
FbPlayableAd.onCTAClick
MRAID
Optional
Required (2.0)
Must work without it
External libraries
A short allowed list
None
None
Orientation
Declared in a meta tag
Both, responsive
Portrait first
The ZIP format helps with size. Because assets don't have to be base64-inlined into one file, a Google build can come in lighter than the AppLovin version of the same playable.
The right package for every network. Genie Playable builds each playable once from your game, then exports a Google ZIP with exitapi.js wired in, next to your AppLovin HTML and Meta build.
01Zip the build with index.html and all assets, and check it's under 5 MB and 512 files.
02Run the ZIP through Google's HTML5 Validator at h5validator.appspot.com/adwords/asset.
03Confirm the CTA calls ExitApi.exit and sound stays off until the first tap.
04Check both orientations if you declared "portrait,landscape".
05Upload to your App campaign ad group and preview.
Google Ads Help also points to Google Web Designer, which has a Google Ads environment for building HTML5 assets.
What are the common Google playable mistakes?
·Missing end tags or DOCTYPE, which the validator flags.
·Loading a library from a CDN that isn't on Google's allowed list.
·No orientation meta tag, so the playable renders in the wrong layout.
·Using the AppLovin build as is, with mraid.open and everything inlined into one file.
·Trying to run playables in a pre-registration or engagement campaign, which isn't supported.
Where does Genie fit?
Genie Playable builds playables from your game (your APK or HTML build plus the assets, narrative and live events in Genie), from a format that's already working, or from a brief. Every playable exports as a Google-ready ZIP and as versions for Meta, AppLovin, Unity Ads, Liftoff, TikTok Ads, Pangle and Mintegral (Moloco coming soon), all from one source. Try it free on your game.
How to make a playable ad from your own game (without rebuilding it)
Three ways to turn your game into a playable ad: engine export, HTML5 rebuild, or building from your APK. Steps, specs, testing and mistakes to avoid.
Written by Yonathan Avivi, Head of Marketing, Genie Labs
Technical review by Yotam Wolf, CTO · Published Sep 26, 2026 · Updated Sep 26, 2026 · 11 min read
A playable ad from your own game is a 30 to 90 second interactive slice of your game: your characters, your art and one clear mechanic, packaged as a small HTML5 file an ad network can run. You can't ship your game build as it is. Networks cap playables at about 5 MB in a single HTML file or ZIP, with strict rules on code and clicks. So you have three options: export a stripped-down scene from your engine, rebuild the moment in an HTML5 framework, or use a tool that builds the playable from your game's build and assets. This guide walks through all three.
Key takeaways
{{ k }}
What does "a playable ad from your own game" actually mean?
It means the player sees your game, not a generic template with your logo on top. Studios that do this well keep three things fixed and treat the rest as open.
Keep fixed
Open to change
{{ r.ak }} {{ r.av }}
{{ r.bk }} {{ r.bv }}
This matches what UA and creative leads tell us. Brand fidelity is non-negotiable. Gameplay is often borrowed from whatever is trending. The catch is policy. The UK ASA now treats even a genuine but non-core mechanic as potentially misleading, and Google Play bans ads that don't represent the app. The closer your playable is to what players actually get, the safer it is, and the better it tends to retain.
Why can't I just ship my game build as a playable?
Ad networks run playables inside their own ad containers, not as apps. Every playable has to fit this box:
SizeAbout 5 MB on every major network (AppLovin, Meta, Google, TikTok, Unity, Mintegral, Moloco, Snapchat). A WebGL export of a real game is usually far bigger. An empty Godot export is already over the limit.
FormatOne self-contained HTML file with every asset inlined (AppLovin, Unity, Moloco), or a ZIP with an index.html (Google, TikTok, Mintegral, Snapchat). Meta accepts both.
No external callsNothing loads from your servers at runtime.
Click-out callmraid.open() on AppLovin and Unity, FbPlayableAd.onCTAClick() on Meta and Moloco, ExitApi.exit() on Google, window.openAppStore() on TikTok, window.install() on Mintegral.
Behavior rulesMuted until the first interaction, no store redirect on the first tap, no auto-redirects, works in portrait and landscape.
What are the three ways to turn my game into a playable?
1. Engine export
2. HTML5 rebuild
3. Build from your APK or HTML and assets
{{ r.k }}
{{ r.a }}
{{ r.b }}
{{ r.c }}
Most studios mix routes: a hand-built hero playable for a launch, and faster tooling for the weekly variations that keep a campaign alive.
What buyers expect to pay and wait: roughly $3,000 to $8,000 and two to four weeks per new playable from an external studio, and roughly $600 to $2,000 in-house once the setup exists. Nobody has a clean source for these numbers, so treat them as market expectations. One mid-size studio we spoke to put it simply: the market norm is "two weeks onwards", and their target is under a week.
Your game is already the brief.
Upload your APK or HTML build. Genie Playable turns it into a playable ad with your own art, characters and live events, ready for 10 ad networks.
How do I make a playable ad from my game, step by step?
01\Pick the moment worth playing
Choose one mechanic a stranger understands in three seconds. Good sources: your core loop at its most satisfying, the live event running now, or a format already converting in your genre. If you can't explain the moment in one sentence, it's too complex. One mechanic beats two.
“Merge plus puzzle looks clever and almost always tests worse.”
Segwise
02\Script the arc
Almost every playable follows the same shape:
{{ a.n }}{{ a.k }}{{ a.v }}
03\Prepare your assets
Export characters, backgrounds, UI and sounds from your game, then cut hard. Compress images, use sprite sheets, trim audio to short loops and subset fonts. Base64 inlining adds about a third to file size, so aim for 2 to 3 MB in total and treat 5 MB as the ceiling.
04\Build it
Whatever route you use, keep the logic in plain HTML and JavaScript, make the layout work in 9:16 and 16:9, and keep sound off until the first tap.
05\Package it for each network
This is where engineer time quietly disappears. "A unit that passes on AppLovin can bounce on Unity," as Segwise puts it. Each network needs the right file format, the right click-out call and any required hooks. Mintegral, for example, expects gameReady() and gameEnd() calls. Build once and generate network variants from one source. Hand-editing copies is how bugs creep in.
06\Test before you upload
{{ t.k }}{{ t.v }}
Then test on a real low-end Android phone. A desktop browser hides most of the problems.
07\Launch and measure
Give each playable enough data before you judge it. A common rule of thumb is about 50 conversions in four days, or 100 in seven. Judge on D7 ROAS and retention, not CPI alone. If you can, add events inside the playable (start, first interaction, win or lose, CTA tap, drop-off point), because network dashboards only show the last step.
08\Plan the next version before this one fatigues
Top-grossing games ship dozens of new playables a month, and most of that volume is variations of a winner. Leading teams put roughly 70% of output into variations and 30% into new concepts. Decide now which single thing you'll change next: the hook, the fail state, the character, the event skin or the end card.
What should I keep from my game, and what can I borrow?
Keep everything that helps a player recognise your game after install: art, characters, UI language, sound. Borrow structure freely, whether that's a proven hook, a pacing pattern or a format working in another genre. Racing and narrative studios often tell us their game "isn't playable". The honest read: a playable doesn't need your full core loop. It needs one true moment from your world.
What are the most common mistakes?
Mistake
What happens
Fix
{{ m.a }}
{{ m.b }}
{{ m.c }}
The next version, not a new brief.
When a playable fatigues, Genie Playable lets your UA or creative team change the hook, the character or the event skin on the last version and ship it again. No dev queue.
Genie Playable takes the third route, and adds two more ways in. You can build from your game: your APK or HTML build together with the assets, narrative, mechanics and live events already in Genie. You can start from a format that's already working and rebuild it with your game inside. Or you can start from scratch and describe the playable to Genie Agent.
Genie Core keeps every version on brand, and Genie Playable exports network-ready variants for Meta, AppLovin, Unity Ads, Liftoff, Google Ads, TikTok Ads, Pangle and Mintegral from one source, with Moloco coming soon. No developer is needed at any step, and your team makes the final call on every version. Sign-up is free and covers your first two playables. Try it on your game.