Grow your conversions ★★★★★ 4.9 · 150+ brands
Talk to Our Team →
Skip to content
4.9 on Clutch from 49 reviews150+ brands grown€500M+ ad spend managedOfficial partner ofMetaGoogleTikTokSnapchat
Talk to Our Team

Playable ads / Specs by network

Playable ad specs, checked 19 November 2026

Playable ad specs by network: the 2026 reference

File size, format, MRAID version, CTA call and orientation for every major network, checked against each network's own documentation.

Short answer. Most ad networks cap a playable ad at 5 MB and want one self-contained HTML5 build that makes no network calls. AppLovin wants a single HTML file with MRAID 2.0, Unity a single index.html with MRAID 3.0, Google a ZIP that calls ExitApi.exit(), TikTok a ZIP with a config.json file, and Meta caps a single HTML file at 2 MB. Every network expects its own CTA call.

Reviewed 19 November 2026 by the Admiral Media creative team

One playable, every network

  1. BuildOne HTML5 coreAssets inline, no network calls, both orientations
  2. AdaptCTA and lifecycle per networkmraid.open, ExitApi.exit, FbPlayableAd, openAppStore
  3. PackageHTML or ZIP per networkFile names, config files and size limits differ
  4. TestEach network's previewCheck the store tap, sound and both orientations
Common size cap
5 MB (AppLovin, Unity, Google, TikTok)
Meta single HTML file
2 MB, or 5 MB as a ZIP
ironSource Ads direct demand
Ended 30 April 2026
Apple Ads playable format
None

Master comparison

Playable ad specs for every major network in one table

The last column says how each row was checked. Official means the network's own documentation, read on 19 November 2026.

Playable ad specs by ad network, November 2026
NetworkPackageMax sizeMRAIDCTA callOrientationHow we checked
AppLovin (AppDiscovery)One HTML file, assets inline (base64 or base122)5 MBv2.0 requiredmraid.open()Must work in portrait and landscapeOfficial doc
Unity AdsOne index.html, assets inline as base64Under 5 MB3.0, injected by Unity, full-screenmraid.open, after gameplayOne responsive build for bothOfficial doc
Google Ads (App campaigns)ZIP, at most 512 files, 20 per ad group5 MBNot needed; MRAID equivalent acceptedExitApi.exit(), or Google adds an Install buttonad.orientation meta tagOfficial doc
Meta (Facebook, Instagram, Audience Network)One HTML file or ZIP (max 100 files), plus lead-in video2 MB HTML, 5 MB ZIPNot mentioned in Meta's docsFbPlayableAd.onCTAClick(), mandatoryNot stated by MetaOfficial doc
TikTokZIP with index.html and config.json at top levelUnder 5 MB after compressionMust not use mraid.jswindow.openAppStore() via TikTok SDKconfig.json: 0 either, 1 portrait, 2 landscapeOfficial doc, updated September 2026
MintegralOne HTML file or a ZIP with resources5 MB (network tool table)Not confirmedNot confirmed in official docsNot confirmedReview rules official; size from Playturbo table
MolocoHTML5 file (.html or .htm)Under 5 MB (official listing); 2 MB HTML in third-party tablesNot confirmedNot confirmedPortrait and landscapeOfficial page unreadable; unconfirmed
Liftoff and VungleZIP (Liftoff); HTML or ZIP, main file ad.html (Vungle)5 MB (third-party table)Not confirmedNot confirmedNot confirmedThird-party only, unconfirmed
Digital Turbine (DT Exchange)Programmatic bid response, full-screen2 MB recommended2.0 or plain HTMLNot specifiedPortrait or landscapeOfficial doc
ironSource AdsDirect demand ended 30 April 2026n/an/an/an/aOfficial sunset guide
Apple AdsNo playable formatn/an/an/an/aOfficial placements page

Checked on 19 November 2026. Rows not marked official come from third-party documentation and are unconfirmed: check them with the network before you build. No network we checked publishes a maximum playable length.

Three rules every network shares

No network allows runtime server calls or store redirects without a real tap, and every network that mentions sound wants it off until the player interacts.

Network by network

One spec card per network

The table gives the numbers; these cards give the review rules that cost studios a day when missed.

01AppLovin playable ads

AppLovin carries the largest share of playable traffic in public third-party data.

Review notes
Audio muted until the first interaction and stopped when the ad closes. Timer starts on the first interaction. WebGL needs a fallback. Violating assets can be blocked; repeated violations can lead to an account ban. Test on AppLovin's Playable Preview page.

02Unity playable ads

Unity's spec is the most detailed, and since 2026 it wants one responsive build.

Review notes
Start only after the ready event and when viewable; pause when not. Keep the top and bottom clear for Unity's controls. No fake or custom close buttons. Respect the iOS mute switch (Web Audio API first). No XHR, no self-fired attribution. Android 5+ and iOS 13+. Gambling creatives need a managed account.

03Google playable ads (App campaigns)

Google wants a ZIP with relative paths, billed per engagement.

Review notes
Relative paths only; external references limited to Google Fonts and Google-hosted jQuery, GreenSock and CreateJS. No sound before interaction. Not eligible for pre-registration or engagement campaigns. Billed per engagement at the first interaction; installs within 30 days count.

04Meta playable ads (Facebook and Instagram)

Meta has the tightest single-file limit and a mandatory CTA call.

Review notes
No JavaScript redirects. App installs objective only. Runs in Facebook and Instagram Feed and Stories and Audience Network interstitial and rewarded video (no lead-in video there). Create the ad paused, test on a phone, not an iPad, then activate.

05TikTok playable ads

Since 2026, TikTok playables run only in upgraded Smart+.

Review notes
No HTTP requests and no JavaScript redirects. Smart+ only, under App Promotion. Goals: app install, app event optimisation and value-based optimisation including target ROAS. The preview cannot test the store jump.

06Mintegral playable ads

The help centre covers review, not numbers. Size comes from Mintegral's Playturbo docs; the CTA call is unconfirmed, so ask your Mintegral contact.

Review notes
Manual technical testing, usually 1 to 2 working days. Test first with the playable test link. Upload 1 to 2 playables per batch, early in the launch period. Results show under Playable Included in the Creative Monitor report.

07Moloco, Liftoff and Vungle

Their official spec pages block automated reading, so every figure here is unconfirmed.

Moloco
Under 5 MB, HTML5, portrait and landscape per its help article's search listing; third-party tables say 2 MB HTML or 5 MB ZIP. Moloco guide
Liftoff and Vungle
5 MB in a third-party table; Vungle's main file named ad.html. Vungle guidelines

08Digital Turbine (DT Exchange)

Programmatic: a DSP returns the playable in a bid response.

Close button
DT shows its own close after 2 seconds. A custom close must appear within 5 seconds, or fail-safe close starts at 15 seconds.
Bid response
crtype Playable, attr 13. Any end card lives inside the ad.

Chartboost (3 MB), Snapchat and Pangle (5 MB) list limits in Mintegral's Playturbo table; none confirmed officially.

What changed in 2026

Three changes that make older spec tables wrong

If your spec table still lists ironSource as an upload channel, it is out of date.

  1. ironSource Ads direct demand ended on 30 April 2026

    Unity announced the sunset on 26 March 2026. From 15 April no new ironSource Ads campaigns or creatives; on 30 April direct demand stopped serving. The ironSource Exchange still serves programmatic demand, and Unity advises moving spend to Unity Ads. Unity sunset guide

  2. TikTok playables run in Smart+ only

    TikTok's help page, updated September 2026, says playables run only in the upgraded Smart+ experience, so plan TikTok tests inside Smart+. TikTok playable ads

  3. Apple Ads has no playable format

    Apple Ads builds every ad from App Store Connect metadata and custom product pages. There is no interactive format, so iOS playables run through the networks above. Apple Ads placements

MRAID in plain language

What MRAID is and which networks need it

MRAID (Mobile Rich Media Ad Interface Definitions) is the IAB Tech Lab's common set of JavaScript calls an HTML5 ad uses to talk to the app it runs in.

Think of MRAID as the ad's phone line to the host app. A playable cannot tell whether it is on screen, or open the App Store by itself; it asks the app's ad SDK through MRAID. The IAB's MRAID guideline set one API so the same ad runs in every compliant SDK.

For playables you need four ideas: wait until MRAID is ready, start when the ad is viewable, pause when it is not, and open the store with mraid.open() after a real player tap. Unity does not support expand, resize or custom close in playables.

Not every network uses it. AppLovin requires 2.0, Unity injects 3.0, Digital Turbine takes 2.0 or plain HTML and Google accepts an equivalent. TikTok forbids mraid.js and Meta has its own CTA call.

The MRAID calls a playable actually uses
MRAID callWhat it does in plain wordsWhere it matters
mraid.getState()Tells you if the ad container has finished loading. If it says loading, wait.AppLovin and Unity: check it first
addEventListener('ready')Fires when MRAID is ready to use.AppLovin and Unity
mraid.isViewable() and viewableChangeTells you if the player can see the ad, and when that changes.Unity: start when viewable, pause when not
mraid.open()Opens a URL, in practice the store page.AppLovin and Unity CTA, after a real tap

From the AppLovin and Unity specifications.

The multi-network packaging problem

One playable, every network: the build checklist

Write the game logic once. Only the CTA call, the start and pause hooks and the packaging change per network, so keep those in a thin adapter layer.

  1. Build to the strictest shared rules

    No runtime network calls, every asset inline, sound off until the first interaction, one responsive layout. That core already satisfies AppLovin, Unity, Google and TikTok.

  2. Set the size budget by the smallest target

    If Meta gets a single HTML file, the budget is 2 MB; otherwise 5 MB. Base64 turns every 3 bytes into 4, so a 3 MB asset folder lands near 4 MB once inlined. Compress audio and use sprite sheets first.

  3. Put the CTA behind one function

    The game calls one store() function. Per network it maps to mraid.open() (AppLovin, Unity), ExitApi.exit() (Google), FbPlayableAd.onCTAClick() (Meta) or window.openAppStore() (TikTok). Fire it only after the player has played.

  4. Put start and pause behind one function

    Where MRAID exists, start on ready plus viewable and pause on viewableChange. On TikTok and Meta, start on load. Start the timer on the first interaction.

  5. Handle sound for iOS

    Use the Web Audio API first so the iOS mute switch works, and stop sound when the ad is hidden.

  6. Package per network

    AppLovin: one HTML. Unity: index.html. Google: ZIP with exitapi.js and orientation tag. Meta: HTML under 2 MB or ZIP, plus lead-in video. TikTok: ZIP with config.json and SDK.

  7. Strip tracking that a network forbids

    No self-fired attribution (Unity), no HTTP requests (TikTok), no JavaScript redirects (Meta, TikTok). Simplest rule: the ad sends nothing anywhere.

  8. Test every package in the network's own preview

    AppLovin Playable Preview, Mintegral's test link, a paused Meta ad on a phone, TikTok preview. Tap the CTA everywhere a player can reach it.

This is how Admiral Media's creative team ships one concept to several networks, so playables can be compared fairly against video. See how to test playable ads and what playable ads cost.

Why playables get rejected

The 8 most common rejection causes and how to fix them

Each cause maps to an official network rule. Most come from uploading one network's build to another.

  1. 1. File over the size limit

    Meta rejects one HTML file over 2 MB or a ZIP over 5 MB; most others stop at 5 MB. Base64 is the usual cause. Fix: budget for the smallest target.

  2. 2. Runtime network calls

    AppLovin, Unity and TikTok all ban runtime requests. One forgotten font or analytics call is enough. Fix: inline everything and search the build for http.

  3. 3. Missing or wrong CTA call

    Meta fails the upload without FbPlayableAd.onCTAClick(); Google adds its own Install button without ExitApi. Fix: one CTA adapter per network.

  4. 4. Store opens on the first tap or by itself

    AppLovin and Unity forbid a store redirect on the first tap, and no network allows one without a tap. Fix: open the store only from a CTA after play.

  5. 5. Sound before interaction

    AppLovin and Google want sound off until interaction; Unity also wants the iOS mute switch respected. Fix: Web Audio API, muted by default.

  6. 6. Orientation failure

    AppLovin wants both orientations, Unity one responsive build, Google a meta tag, TikTok a config.json field. Fix: build responsive, declare per network.

  7. 7. Wrong package structure

    Unity wants index.html, TikTok index.html plus config.json at the top, Google at most 512 files, Meta 100. Fix: a packaging script, not hand-zipped files.

  8. 8. Blocked or fake UI and redirects

    Unity bans fake or custom close buttons and reserves the top and bottom of the screen. Meta and TikTok reject JavaScript redirects. Fix: clear those areas, remove redirects.

The rejection no validator catches

On 4 November 2026 the UK Advertising Standards Authority banned ads from King, Scopely, Omnilojo and Vistrex for showing gameplay not in the game; a disclaimer did not save King's ad (mobilegamer.biz). A playable can pass every check and still break ad rules. Build from real gameplay; our genre guide shows which mechanics to use.

FAQ

Playable ad specs: common questions

Short answers to the questions game UA and creative teams ask us most.

What file size should a playable ad be?

Keep a playable ad under 5 MB, and under 2 MB if Meta gets it as a single HTML file. AppLovin, Google and TikTok cap playables at 5 MB, Unity wants under 5 MB, and Digital Turbine recommends 2 MB. Inlining assets as base64 adds about a third to their size, so measure the final package.

What is MRAID and which version do playables need?

MRAID is the IAB Tech Lab's standard set of JavaScript calls that lets an HTML5 ad talk to its host app, for example to check visibility or open the store. AppLovin requires MRAID 2.0 and Unity injects 3.0. TikTok forbids mraid.js and Meta uses its own CTA call.

Can one HTML5 playable run on every ad network?

One game build can run everywhere, but each network needs its own package. The CTA call differs (mraid.open, ExitApi.exit, FbPlayableAd.onCTAClick, window.openAppStore), and so does packaging: one HTML file for AppLovin and Unity, a ZIP for Google and TikTok. Keep the differences in a thin adapter layer.

Does TikTok still accept playable ads?

Yes, but only in the upgraded Smart+ experience, per TikTok's help page updated September 2026. The playable is a ZIP under 5 MB with index.html and config.json at the top level. It must include TikTok's JS SDK, call window.openAppStore(), avoid mraid.js and make no HTTP requests.

Can I still run playables on ironSource?

No, not as direct ironSource Ads campaigns. Unity ended ironSource Ads direct demand on 30 April 2026, with no new campaigns or creatives after 15 April. The ironSource Exchange still serves programmatic demand, and Unity advises moving spend to Unity Ads, which takes one responsive index.html under 5 MB.

Does Apple Ads support playable ads?

No. Apple Ads has no playable or HTML format. Its ads run on the Today tab, Search tab, search results and product pages, built from App Store Connect metadata and custom product pages. To reach iPhone users with a playable, buy through AppLovin, Unity, Google, Meta, TikTok or Mintegral.

How long should a playable ad be?

No network we checked publishes a maximum length, so length is a design choice. The timing rules are what matter: AppLovin starts the timer at the first interaction, Unity starts only when the ad is viewable, and the store may not open on the first tap. Our testing guide covers tuning length.

Sources. Checked on 19 November 2026: AppLovin: creative best practices and guidelines; Unity: playable specifications; Unity: ironSource Ads direct demand sunset; Google Ads Help: HTML5 and playable ads for App campaigns; Meta for Developers: playable ads; TikTok Ads Help: playable ads; Mintegral help centre: ad asset; Digital Turbine: DT Exchange playables; Apple Ads: ad placement options; IAB Tech Lab: MRAID; Moloco: playable and IEC creative guide; Vungle: HTML and MRAID creative guidelines; Mintegral Playturbo: playable upload specs by network; mobilegamer.biz: ASA bans misleading mobile game ads, 4 November 2026. Ad networks change their rules often, so confirm specs in each network’s own documentation before you upload.

Playables for every network

One concept, packaged and tested for each network you buy on

Admiral Media's creative team builds playables from your real gameplay, packages them per network and reads results next to your video and UA data. Tell us which networks you buy on.

Book a meeting

Talk to our team about playables

Tell us the game and the networks you buy on. A creative strategist replies within one working day.


Get in touch with us