Try for free
Learn/Specs by network

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

Where playable ad file size really goes (base64, video, fonts, engine code) and how to get under 5 MB, with 2 to 3 MB as the practical target.

Written by Yonathan Avivi, Head of Marketing, Genie Labs

Technical review by Yotam Wolf, CTO · Published Sep 26, 2026 · 7 min read

Most playables go over 5 MB for four reasons: base64 inlining adds about a third to every asset, the lead-in video is too heavy, full fonts and oversized images slip in, and the engine code itself takes a big share before any art loads. Every major network caps playables at about 5 MB, so the fix is a budget, not a last-minute squeeze. Aim for 2 to 3 MB in total. That leaves room for localized versions and a second orientation, and it loads faster on the phones your players actually use.

Key takeaways
Base64 makes every inlined asset at least 33% bigger. An 800 KB PNG turns into about 1.1 MB inside the file.
The usual suspects, in order: lead-in video, uncompressed images, full font files, engine code, audio.
Set a size budget per asset type before you build. Cutting at the end costs quality.
Pick a light engine. Phaser's full build is about 980 KB of minified JavaScript before a single sprite.
Genie Playable packages every playable to each network's size rules from one source, so your team isn't hand-shrinking files per network.

Why does my playable get bigger when I export it?

Because networks want everything inside the file. AppLovin, Unity and Moloco take one HTML file with every image, sound and font embedded, usually as base64 text. Base64 is at least four thirds the size of the original data. One real example: an 800 KB PNG grew to about 1.1 MB once inlined.

Gzip doesn't save you here. Compressed base64 shrinks back close to the original size, but the 5 MB check runs on the file you upload, not on what travels over the network. Where a network accepts a ZIP (Google, Meta, TikTok, Mintegral, Snapchat), the ZIP compression does count toward the limit, which gives you a little more room.

AppLovin also accepts base122, which is about 14% smaller than base64. The trade-off: it decodes slower and compresses worse, so it helps most on single-file uploads.

Where does the file size actually go?

AssetWhy it gets heavyWhat to do
Lead-in videoAround nine in ten top playables open with video, and it's often the single biggest assetKeep it to a few seconds, lower the resolution to what the placement shows, cut the bitrate
ImagesSource art exported at full resolution. A 3000 px image shown at 1080 px carries about eight times the pixels you needResize to display size, convert to WebP, pack into sprite sheets
FontsA full TrueType file is 100 to 500 KBSubset to the characters you use, or use a system font
Engine codePhaser's full build is about 980 KB minified. A graphics-only custom build is about 404 KBUse a custom build, a lighter framework, or plain JS and Canvas for simple mechanics
AudioLong music tracks at full qualityShort loops, lower bitrate, mono. Phone speakers won't show the difference
3D modelsRaw meshes and texturesCompress geometry (Draco cut one model from 7.6 MB to 0.8 MB) and compress textures separately

How do I get my playable under 5 MB?

1. Set a budget before you build

Decide the total first, then split it. PlayableAdsMaker suggests rough targets by format: under 300 KB for an end card, under 600 KB for an end card with effects, and under 1.5 MB for a mini-game. A full playable with a lead-in video usually lands between 2 and 4 MB. Write the budget down per asset type and check it on every build.

2. Shrink the video first

It's the biggest win. Trim the lead-in to the few seconds that set up the play moment. Export at the size the ad actually renders, not at your trailer's resolution. If the video only works at a high bitrate, it's probably too long.

3. Fix images at the source

Resize every image to its display size. Convert to WebP, which runs about 25% to 34% smaller than JPEG at the same visual quality. Pack small sprites into atlases so you ship one compressed image instead of dozens.

4. Subset fonts and trim audio

Keep only the glyphs on screen. Cut music to a short loop, drop to mono, and lower the bitrate until you can hear the difference on a phone speaker, then go one step back.

5. Cut engine weight

Use a custom build that includes only the modules you need. For a simple drag, tap or swipe mechanic, plain JavaScript and Canvas often beat a full engine. Godot is the cautionary tale: an empty export is already over the limit. Defold, with the right settings, has example playables under 1 MB.

6. Check the file you'll upload

Measure the final packaged file for each network, not your project folder. A build that fits as a ZIP for Google can go over as a single HTML file for AppLovin.

One build. The right size for every network. Genie Playable builds from your game and packages each version as a single HTML file or a ZIP, depending on where it runs. The size check happens before you upload, not after a rejection.

Try it free on your game

Is 5 MB the real target?

No. 5 MB is a rejection line, not a production goal. Three things eat the headroom: localized text and voice, a second layout for the other orientation, and the next variation you'll ship in two weeks with one more character in it. Players on mid-range Android phones on mobile data also feel every extra megabyte in load time, and a playable that loads slowly loses players before the first tap. The honest read: if you're at 4.8 MB, you're already over budget for version two.

What are the most common file size mistakes?

·Exporting art at source resolution and resizing in code.
·Shipping the whole font family for a headline and a button.
·Measuring the ZIP when the network wants a single HTML file.
·Mixing two mechanics in one playable. Double the assets, double the size, and it usually tests worse anyway.
·Adding "just one more" character per variation until a later version gets rejected.

Where does Genie fit?

Size is a packaging problem as much as an art problem, and it repeats for every network and every version. 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 scratch from a brief. It then exports network-ready versions for Meta, AppLovin, Unity Ads, Liftoff, Google Ads, TikTok Ads, Pangle and Mintegral, with Moloco coming soon, each packaged to that network's rules. Your team works on the creative. Try it free on your game.

FAQ

Sources

  1. 01Base64 overhead (Daniel Lemire)
  2. 02Base122
  3. 03PlayableAdsMaker, size limits and reduction
  4. 04Google WebP study
  5. 05Phaser custom builds
  6. 06Defold playable ads example
  7. 07Draco compression (Cesium)
  8. 08Alconost, playable file size limits
  9. 09AppLovin creative specs

Keep reading

All articles →
Playable ads · 7 min read

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

Playable ads · 6 min read

AppLovin playable ad requirements and how to test before you upload

Hook,tutorial,end card.
Playable ads · 7 min read

Anatomy of a playable ad: hook, tutorial, fail state, end card

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?