Try for free
Learn/Specs by network

AppLovin playable ad requirements and how to test before you upload

AppLovin's 2026 playable rules: 5 MB single HTML, MRAID 2.0, mraid.open. Plus how to test with Playable Preview and fix common rejections.

Written by Yonathan Avivi, Head of Marketing, Genie Labs

Technical review by Yotam Wolf, CTO · Published Sep 26, 2026 · Last verified Sep 29, 2026 · 6 min read

AppLovin requires playable ads to be a single HTML file of 5 MB or less, with every asset embedded (base64 or base122), MRAID 2.0 support, and mraid.open for the click to the store. The playable has to work in portrait and landscape, stay muted until the first interaction, and never redirect on the first tap. Test it in AppLovin's Playable Preview web tool, then on a real device through the Playable Preview app, before you upload.

Key takeaways
One file, 5 MB at most, no external resources or network calls.
Wait for MRAID to be ready before any MRAID call or layout decision. It's the most common reason AppLovin playables freeze.
Click out through mraid.open only. The first tap plays; it doesn't redirect.
Violations can get assets blocked or the account banned, so test every build, not only the first.
Genie Playable builds AppLovin-ready playables from your own game, packaged to these rules alongside nine other networks.

What are AppLovin's playable ad requirements in 2026?

RequirementAppLovin's rule
File size5 MB or less
FormatOne single HTML file. Images, audio, fonts and scripts embedded as base64 or base122
External resourcesNot allowed. No external files, no network calls
MRAIDMust support MRAID 2.0. Wait for the ready event, or check that mraid.getState isn't 'loading', before calling MRAID or deciding the layout
Click to storemraid.open. Other methods make the click-through fail
OrientationMust work in portrait and landscape
AudioMuted until the first interaction; stopped or muted when the ad closes or is hidden
TimerAny in-ad timer starts only after the first interaction
RedirectsNo store redirect on the first tap; no auto-click or auto-redirect
LoadingMust load and become interactive "in a reasonable time frame"
WebGLAppLovin's older guidelines ask for a fallback UI if WebGL fails or loses context

Why does AppLovin matter so much for playables?

AppLovin carries the largest share of playable ad traffic, around 59%, and most new playable experiments, according to AppAgent's analysis of Apptica data. For many small studios, AppLovin is the reason they need playables at all. Its Axon engine leans heavily on interactive creatives, and practitioners put the realistic floor for testing a campaign there at about $500 a day. At that budget, a broken playable is an expensive way to learn.

How do I test an AppLovin playable before uploading?

01Open the Playable Preview web tool at p.applov.in/playablePreview?create=1.
02Load your playable. Paste a URL to your hosted.html file, or drag and drop the file.
03Play it in the simulated device. Use the Rotate button to check both orientations.
04Tap your CTA. A working mraid.open shows "You have successfully clicked."
05Scan the QR code at the bottom of the page with the Playable Preview app (AppLovin, iOS and Android). It runs the playable inside the AppLovin SDK on a real device, which is as close to production as you'll get before launch.
06Test on a low-end Android phone. Check load time, frame rate, and that sound stays off until you tap.

The tool also warns that playables should be "made using Runtime Analysis", or they may freeze and be disabled. AppLovin doesn't define the term publicly. If you see freezes in preview, check MRAID readiness first.

Built for AppLovin from the start. Genie Playable packages every playable as a single inlined HTML file with MRAID handled and mraid.open wired in, so your team spends its time on the creative, not the rejection list.

Try it free on your game

Why do AppLovin playables get rejected or disabled?

ProblemWhy it breaksFix
MRAID called before it's readyThe ad freezes or the layout is wrongListen for the MRAID ready event before any MRAID call
Over 5 MBRejectedCompress assets and aim for 2 to 3 MB, since base64 adds about a third
External or relative asset pathsBlank or broken assets inside the SDKInline everything into the single HTML file
Click through window.open or a linkClick-through failsUse mraid.open
First tap opens the store, or an auto-redirectPolicy violationLet the first tap play; show the CTA later
Sound autoplaysPolicy violationStart muted; unmute after interaction
Portrait-only layoutBroken on landscape placementsResponsive layout for both

AppLovin's demand partner policies allow it to block assets or ban accounts for violations. Test every version.

What should I check before every AppLovin upload?

·Single.html file, 5 MB or less
·No external URLs in the code (search it for "http")
·MRAID ready check before any MRAID call
·CTA uses mraid.open and shows the success message in Playable Preview
·First tap plays, no redirect
·Muted until the first interaction
·Works in both orientations (Rotate button)
·Tested on a device through the Playable Preview app

How do I ship AppLovin playables faster?

The build is rarely the hard part. The loop is. AppLovin creatives fatigue fast, so the studios that do well ship steady variations of a winning playable, such as a new hook, a different fail state or an event skin, instead of one hero file. Genie Playable builds AppLovin-ready playables from your own game, from a format that's already working, or from a brief, and lets your team make the next version from the last one. Try it free on your game.

FAQ

Sources

  1. 01AppLovin creative specs and guidelines
  2. 02AppLovin legacy best practices
  3. 03AppLovin Playable Preview
  4. 04Playable Preview app (App Store)
  5. 05AppAgent, State of Playable Ads 2025
  6. 06RocketshipHQ, testing creatives on AppLovin
  7. 07PlayableKit, AppLovin playable ads

Keep reading

All articles →
Playable ads · 7 min read

Playable ad specs by network (2026): size limits, MRAID and file format

Playable ads · 7 min read

Why is my playable ad over 5 MB? How to cut file size

Firstapplovintest.
Playable ads · 7 min read

Your first playable for your first AppLovin campaign

Ready to ship playables from your game?

Try for freeBook a demo

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 fixedOpen 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.

The full list lives in our Playable ad specs by network (2026).

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.

Try it free on your game

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.

Book a demo

Where does Genie fit?

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.

Where to go next

First playable? Follow how to make a playable ad step by step, then run it through the playable ad best practices checklist. Once it's live, read how to know if your playable ad is working and how to A/B test playable ads.

FAQ

{{ f.a }}

Sources

  1. {{ s.n }}{{ s.name }}

{{ a.h1a }} {{ a.h1b }}

{{ a.desc }}

Written by {{ a.author }}

{{ a.meta }}

Ready to ship playables from your game?