index.html and config.json, click-through wired to window.openAppStore() instead of MRAID. One honest caveat: Pangle expects its own hosted SDK script tag before that call does anything, and PlayableKit couldn't confirm the current CDN URL from Pangle's public docs, so that's flagged in the build report for you to add or verify rather than guessed at.
What Pangle actually requires
The specifics below come from TikTok Ads Manager's own help documentation, which is where Pangle playable creatives are specified and submitted (Pangle campaigns run through TikTok for Business tooling). Two things stand out compared to the networks PlayableKit already builds for: Pangle explicitly rejects the MRAID format that most other networks rely on for click-through, and it uses its own hosted JS SDK instead.
Package format and size
- The creative must be a single
.ziparchive. - Total size must be under 5MB after compression.
- The entry HTML file must sit in the first-level directory and be named
index.html. - The first-level directory must also contain a
config.jsonfile declaring orientation support via aplayable_orientationfield:0for either orientation,1for portrait only,2for landscape only. - Recommended/supported resolutions are 1280×720 (landscape) and 720×1280 (portrait).
- Supported placements are interstitial and rewarded ad formats.
Self-contained delivery — no exceptions
Pangle's documentation is unusually strict here: the creative "must not make any HTTP requests," must not load "dynamic materials via external networks," and must not contain "any JS redirects." In practice that means every image, audio file, and font has to be embedded directly in the package (as inline data rather than fetched at runtime) — a stricter, more explicit version of the self-contained requirement that AppLovin and Meta also enforce.
Click-through: not MRAID
This is the detail most likely to trip up a build coming from another network. Pangle's own spec states the creative "should not be in mraid.js format" — it doesn't use the mraid.open() call that AppLovin and Unity Ads expect. Instead, Pangle expects its own hosted SDK script tag placed at the bottom of <body>, before any of the creative's own JS, after which the CTA element calls window.openAppStore() directly rather than the developer wiring up a redirect or download handler themselves.
| Requirement | Pangle spec |
|---|---|
| Package format | .zip archive |
| Size limit | < 5MB after compression |
| Entry file | index.html in the first-level directory |
| Orientation config | config.json with playable_orientation: 0/1/2 |
| Resolutions | 1280×720 or 720×1280 |
| Ad formats | Interstitial, Rewarded |
| External requests | Not permitted — no HTTP requests, no external asset loading, no JS redirects |
| Click-through | Pangle-hosted JS SDK script tag + window.openAppStore() — explicitly not mraid.js |
Two caveats worth flagging plainly: first, Pangle's public documentation on this is thinner than Google's or Meta's — we could not find a distinct "Pangle developer portal" spec page separate from the TikTok Ads Manager help articles, so treat the SDK script URL and exact CTA wiring as accurate to what's published today but subject to change without much public changelog. Second, ad review and creative policy details (content restrictions, review turnaround) live in a separate part of Pangle's documentation and aren't covered here — this page is scoped to packaging and click-through mechanics only.
How PlayableKit builds for Pangle
PlayableKit's converter matches Pangle's package shape directly: a ZIP with a first-level index.html and a config.json declaring playable_orientation (0/1/2, per TikTok Ads Manager's own docs for Pangle campaigns), all assets embedded as inline data, and the CTA wired to call window.openAppStore() instead of MRAID. The one piece PlayableKit doesn't fabricate is Pangle's hosted SDK script tag itself — its current CDN URL isn't published anywhere we could confirm, so the build report flags it for you to add or verify before submission, rather than shipping a guessed URL that could silently point nowhere.
Test a Pangle build today
Upload your Unity Playworks/Luna export and PlayableKit generates a Pangle-shaped package automatically. Use the free validator and free size checker alongside it to catch general structural or size problems before you submit.