Meta playable ad specs: Facebook, Instagram and Audience Network
Meta's 2026 playable ad rules for Facebook, Instagram and Audience Network: 5 MB HTML or ZIP, no mraid.js, FbPlayableAd.onCTAClick, placements and testing.
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
Meta accepts playable ads up to 5 MB, as either a single HTML file with every asset embedded as data URIs or a ZIP with index.html at the root and no more than 100 files. The playable must work without mraid.js, should call FbPlayableAd.onCTAClick for the click to the store, must be built in portrait and responsive, and can't make any external requests. Playables run across Facebook and Instagram Feed, Stories and Reels plus Audience Network, under the App promotion objective, and each one needs a companion video.
Key takeaways
5 MB for both formats. The "2 MB for HTML" figure in many guides doesn't match Meta's own help page.
No mraid.js. This is the most common reason a playable built for AppLovin fails on Meta.
Click to store with FbPlayableAd.onCTAClick. Moloco uses the same call.
Portrait first, responsive, no network requests, and a companion video.
Genie Playable exports a Meta-ready version of every playable from the same source as your AppLovin, Google and TikTok versions.
What are Meta's playable ad requirements?
Requirement
Meta's rule
File size
5 MB for a single HTML file; 5 MB for a ZIP
Format
Single.html or.htm file with all assets as data URIs, or a ZIP with index.html at the root and assets in subfolders referenced by relative paths
ZIP file count
100 files at most
MRAID
Must work without mraid.js or similar frameworks
Click to store
FbPlayableAd.onCTAClick ("strongly recommended"). In a ZIP, call it once
Orientation
Built in portrait, responsive
External requests
None. No XMLHttpRequest, no dynamic asset loading, no JavaScript redirects
Companion video
Required alongside the playable
Objective
App promotion, with the app registered to the ad account
Placements
Facebook and Instagram Feed, Stories, Reels, and Audience Network
Is the Meta playable limit 2 MB or 5 MB?
5 MB. Several widely shared spec guides say Meta allows 2 MB for an HTML file and 5 MB for a ZIP. Meta's help page says 5 MB for a single HTML file and 5 MB for a ZIP of up to 100 files. That said, aim for 2 to 3 MB anyway. Feed and Reels players scroll fast, and a playable that loads slowly loses them before the first tap.
Why does my AppLovin playable fail on Meta?
Usually one of three things:
Problem
Why
Fix
mraid.js included
AppLovin requires MRAID; Meta requires the playable to work without it
Remove MRAID from the Meta build
Click uses mraid.open
Meta's click-out call is different
Use FbPlayableAd.onCTAClick
Landscape-first layout
Meta playables are built in portrait
Portrait-first, responsive layout
The mechanic, art and logic can be shared across networks. The packaging can't. That's why most teams keep one source and generate a separate build per network.
One source. A Meta build and nine more. Genie Playable packages each playable for Meta without mraid.js and with the right click-out call, alongside your AppLovin, Google and TikTok versions.
01Build the Meta version: single HTML with data URIs, or ZIP with index.html at the root.
02Search the code for "mraid" and "http". Neither should be there.
03Check that the CTA calls FbPlayableAd.onCTAClick.
04Upload in Ads Manager under an App promotion campaign and add the companion video.
05Use the preview in Ads Manager, and the "Refresh playable" button after each change.
06Preview on a real phone in Feed, Stories and Reels placements.
Are playables worth running on Meta?
It depends on your mix. Playables run at their biggest scale on in-app SDK networks like AppLovin, and one agency says the format's advantage "does not transfer" to Meta in the same way. The picture is moving, though. In September 2026, Matej Lancaric spotted a vertical playable running in Facebook Reels, the fastest-growing placement on the platform. Our read: test playables on Meta once they're working on AppLovin, and build the Meta version from the same source so the test costs you packaging, not a rebuild.
What should I check before every Meta upload?
·5 MB or less, single HTML or ZIP with at most 100 files
·index.html at the ZIP root, relative paths only
·No mraid.js
·FbPlayableAd.onCTAClick on the CTA
·No XMLHttpRequest, dynamic loading or JavaScript redirects
·Portrait-first, responsive
·Companion video ready
·App registered to the ad account, App promotion objective
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. Each one exports as a Meta-ready build and as versions for AppLovin, Unity Ads, Liftoff, Google Ads, TikTok Ads, Pangle and Mintegral (Moloco coming soon), all from one source. Testing Meta becomes an export, not a new project. 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.