Skip to content
HTML5 and playable ads

Playable Ad Tester

Drop a playable ad file, run it in a phone frame with a mock ad-network SDK, and see size, install call, MRAID and errors checked.

Last checked

Files never leave your device. Everything runs in this tab.

One HTML file up to 5 MB with every resource embedded as base64, no network calls, MRAID 2.0 with mraid.open() for the click-through, wait for the ready event, both orientations, timer and sound only after the first touch, no store redirect on the first tap.

Source: AppLovin support, creative best practices (official).

  • Size against the network limit, for an HTML file or a ZIP
  • One self-contained file, no external requests or store links
  • The install call the network expects
  • MRAID ready and viewability handling
  • Runs in a phone frame, portrait and landscape
  • Event log: ready, first touch, install calls, errors, auto-redirects

How to use it

  1. Pick the network you are building for under Check against.
  2. Drop the playable .html file or ZIP, or try the Guitar Tuner playable from my Lab.
  3. Read the checks, then tap through the ad in the phone frame. Use Send to background to test that it pauses, rotate it with Landscape, and watch the event log for the install call.

What it checks and why

A playable ad is one HTML file that a network runs inside its own wrapper. The wrapper tells the ad when it is ready and when it is on screen, and the ad tells the wrapper when the player taps install. Getting any of those calls wrong means the ad does not start, does not pause, or does not send the player to the store.

The tester stands in for the wrapper. It injects a mock SDK with the same names and call shapes as the real one, runs your file in a sandboxed frame, and logs every call. Networks without MRAID get a document visibilitychange when you send the ad to the background. The static checks look for the things reviewers reject: a file over the size limit, scripts or images loaded from outside the file, a plain store link, and a missing install call.

The mock SDKs are test doubles, not the networks' own code. They show that your ad makes the right calls at the right time. A real network can still add review steps and rules that no script can see.

Specs and sources

Limits

  • AppLovin's and Unity's rules come from their own documents. The Mintegral limits and calls, Meta's ZIP option and the Google and Meta install calls come from third-party tables; check each network's current document before you traffic.
  • TikTok, Liftoff and Moloco have no mode yet.
  • The frame is sandboxed without storage access, so an ad that depends on localStorage logs an error here.
  • Sound is not tested: browsers block audio until a tap, and the tester does not measure loudness.

Questions

How do I test an AppLovin playable ad before upload?
Pick AppLovin under Check against and drop the HTML file. The tester checks AppLovin's stated rules: one file up to 5 MB, no network calls, waiting for the MRAID ready event, mraid.open() for the click-through and never from a timer, both orientations, no sound before the first touch, and a WebGL fallback. Then preview it on AppLovin's own Playable Preview page.
What is a playable ad?
A short interactive ad, usually a mini-game, packaged as one HTML file. The player tries it for about 30 seconds and then taps a button that opens the app store.
How big can a playable ad be?
AppLovin allows 5 MB per file and Unity under 5 MB for one minified index.html (both official). Google takes a ZIP of up to 5 MB and 512 files. Meta takes one HTML file under 2 MB; third-party tables add a 5 MB ZIP option. Tables list 5 MB for Mintegral. Many teams aim for 2 MB or less so the ad loads fast on mobile data.
Do I need to include mraid.js?
Not for Unity: its webview injects MRAID, so no script tag is needed. Keeping a <script src="mraid.js"> tag is common in MRAID templates and is not counted as a missing file here.
Can the first tap open the app store?
No, not on AppLovin or Unity. The store opens through mraid.open() only from a tap on the call to action after the player has interacted with the game. A redirect without a tap is not allowed either.
What changes between MRAID 2.0 and 3.0?
MRAID 3.0 adds events such as exposureChange and audioVolumeChange and standardises the close control. Unity requires MRAID 3.0; AppLovin's guidelines name MRAID 2.0. The mock reports the version each network uses.
What is MRAID?
Mobile Rich Media Ad Interface Definitions, a standard from the IAB Tech Lab. The ad waits for the ready event, checks whether it is viewable, and calls mraid.open(url) to send the player to the store.
Why does my playable work in the browser but not in the network's preview?
The usual causes are a call to the wrong install function for that network, a script that starts before the ready event, a file loaded from outside the HTML, or storage that the container blocks. The checks and the event log point at each of these.