Your First Playable Ad: The Honest Beginner Walkthrough
You can have something playable in twenty minutes. It will probably not be good, and that is the correct outcome for a first attempt — what matters is knowing which of the things that went wrong are worth fixing.
In short
- Start with Tap Target, not a match board. The simplest mechanic teaches you the editor without the mechanic itself competing for your attention.
- A playable ad is one self-contained file that runs inside somebody else's app. That constraint explains nearly every rule you are about to meet.
- The size cap is the one that surprises people: 5 MB on most networks, 4 MB on the tightest. That is for everything — art, sound, code.
- The editor blocks an export with no click-through, because an ad nobody can tap through is the single most common first-timer mistake.
- Your first ad will probably be bad. Build it anyway — the second one is much faster, and nothing in this format is learned by reading.
Every walkthrough for this format has the same problem: it is written by somebody who already knows the answers, for somebody who does not know the questions. The result reads smoothly and leaves you stuck at the first thing it assumed you already understood.
So this one is written differently. It goes in the order a real first attempt goes, it says where people actually get stuck, and it is honest about the fact that the thing you make today will not be very good. That is not discouragement. A first playable ad is a way of finding out what you do not know, and it is much faster than reading about it.
What a playable ad actually is
Worth thirty seconds, because almost every rule you are about to meet follows from this.
A playable ad is a small interactive thing that runs inside another app. Somebody is playing a game or scrolling a feed, your ad appears in that app, they interact with it, and they either tap through to your store page or close it and go back to what they were doing.
It is not a web page you link to. It is not an app. It is one self-contained file that gets handed to an ad network, which hands it to thousands of other apps, which run it on phones you will never see. Everything it needs — images, sounds, logic — is inside that single file.
That is the whole constraint, and it explains the rest: why there is a tight size limit, why it has to work without a network connection once loaded, and why it has to be understood by a stranger in about a second.
What you do not need
You do not need to write code. You do not need a designer, to start — every template ships with placeholder art you can play immediately. You do not need an ad network account to build or preview one. You need an account with a network only when you want to actually run the ad, which is a separate problem from making it.
The first twenty minutes
Do this in order. Resist the urge to start with the mechanic you eventually want.
- 1
Open the editor and add Tap Target
Start a playable project and pick Tap Target — 'Tap what appears'. It is the simplest mechanic in the list and that is exactly why you want it first. You are learning the editor right now, and a complicated mechanic means learning two things at once while being unsure which one is confusing you.
A canvas at phone proportions with something to tap and a button at the bottom.
- 2
Press Play immediately
Before changing anything. Every template ships in a state that already works, and seeing the working version first gives you something to compare against when you break it later — which you will.
A round you can actually play through to an ending.
- 3
Change one thing and play again
Any one thing. A colour, a piece of text, a number on the Rules tab. Then play it again. This is the loop you will spend the rest of your time in, and doing it deliberately once is how you learn that the preview is the source of truth rather than the canvas.
Your change showing up when you press Play, not just on the canvas.
- 4
Set the click-through
Select the call-to-action button and give it an Open URL action pointing at your store page. Do this now rather than at the end, because it is the single most forgotten step and the editor will refuse to export without it.
No blocker on the click-through step when you open the export dialog.
- 5
Export it and open the file
Export, then open the resulting file in a browser. This is the moment the thing stops being a project and becomes an ad. Play it there — what you see in that file is what a stranger will see.
A single file that plays in a browser with no editor around it.
That is a playable ad. It is probably not a good one, and the rest of this piece is about the gap between those two things.
The five things that actually go wrong
Not hypothetical problems. These are the ones that come up first, in roughly the order people hit them.
What breaks, why, and what to do about it:
| The problem | What is happening and how to fix it |
|---|---|
| **The file is too big** | The cap is about 5 MB on most networks and 4 MB on the tightest — and that is for everything at once: images, sounds, and the code that runs it. It is almost always the images. Export at a lower resolution than feels right; a phone screen is smaller than the one you are designing on, and art drawn at twice the size it displays at costs twice as much for no visible gain. |
| **Nothing opens when you tap** | The button has no Open URL action, or it has one pointing at nothing. The editor treats this as a blocker rather than a warning for a reason: an ad nobody can tap through cannot produce a single install, however good it is. If you are running on both platforms, fill in both the iOS and Android addresses — with only one set, the other platform's users open the wrong store. |
| **It looks wrong sideways** | Phones turn. Ad networks will show your creative in whichever orientation the host app is in, so both have to work. Check the landscape layout before exporting rather than after, because discovering it in a live campaign means pulling the creative and re-uploading. |
| **Nobody knows what to do** | The hardest one, and it will not show up in any warning. You know what your ad wants because you built it. A stranger has about a second and no instructions. If you have to explain the mechanic to somebody before handing them your phone, the ad has a problem no amount of tuning fixes. |
| **It is fine on your phone and bad on a real one** | You are probably testing on a better device than most of your audience has. Animations that are smooth on a current flagship can stutter on mid-range hardware, and a tap target that feels generous to you may not be. Test on the oldest phone you can find, not the newest. |
If you have to explain the mechanic before handing somebody your phone, the ad has a problem that tuning will not fix.
The honest part
Three things a walkthrough usually leaves out.
Your first one will not be good, and that is fine. Not because you lack talent, but because this format has a set of constraints nobody has intuitions about until they have run into them — a stranger's attention span, a size cap, a screen held one-handed, a viewer who did not ask for any of this. You cannot reason your way to those. The first build is how you acquire them, and the second one takes a third of the time.
The editor is the easy part. Genuinely. Learning where the buttons are takes an afternoon. Working out what your ad should *do* — which mechanic represents your product honestly, what to cut, where to stop — is the actual job, and it is the same job whatever tool you use. If you are stuck, you are more likely stuck on the design question than on the software.
Some products should not have a playable at all. We sell the tool and we still think this. If your product has no action a stranger can perform in a few seconds, you will end up inventing one, and an ad demonstrating a mechanic your product does not contain is a worse outcome than no playable ad. Worth reading about before you spend a week on it.
The test that saves the most time
Hand your phone to somebody who has not seen the ad and say nothing at all. Watch where they hesitate. Do not explain, do not prompt, and do not defend it afterwards — just watch. Ten seconds of that tells you more than an hour of your own testing, because you cannot un-know how your own ad works and they do not know yet. Every hesitation is a place the ad failed to communicate.
Where to go next
Once the first one exists, the useful next step is a real mechanic rather than a simpler one. The three walkthroughs in this section each take a complete mechanic apart — a match board, an idle builder, a driving round — and explain not just the clicks but why each default is the number it is.
Pick whichever is closest to the product you are actually advertising. If none of them are close, that is useful information too, and worth taking seriously rather than working around.
Questions beginners actually ask.
How long should a playable ad be?
Most work in the region of fifteen to thirty seconds, but the number matters less than the shape: the first meaningful interaction should happen within a few seconds, and the round should reach a real ending rather than being cut off. An ad that stops rather than finishes leaves the viewer with no moment at which tapping through felt like the natural next thing.
Do I need different files for different ad networks?
Usually one build, exported per network, because the networks differ in how the file is packaged and how the tap-through is called rather than in what the ad is. The size caps differ too — the tightest is 4 MB where most are 5 — so a file that fits everywhere is easier than maintaining several. Build to the smallest cap you intend to run on.
Can I use my game's real art?
Yes, and you should — it is the single thing that most improves an ad's honesty, because the person who installs gets the thing they were shown. The only constraint is size: export at the resolution the ad actually displays at rather than the resolution the game ships at, which is usually where a first build goes over the cap.
What if I do not have a designer?
Build it on the placeholders first and get the mechanic right, then bring art in. This is the correct order regardless of whether you have a designer, because it means you are testing whether the thing is fun before anybody spends time drawing for it — and a mechanic that is dull with placeholder squares is dull with beautiful art.
Editorial
The Play Ads Maker team
We build the editor behind this site, which means we spend our days inside the format — its constraints, its export limits, and the question of what actually makes someone tap. We write about what we learn doing it.
The fastest way to understand the format is to build one
The editor is free to open, runs in the browser, and needs no code. Start from a template and have something playable within the hour.
Keep reading
Build a Match Cascade Playable
A complete build of a swap-and-match ad, from an empty canvas to a file a network will take — with the reasoning behind every default, including the ones you should change.
10 min readWhen a Playable Ad Is the Wrong Choice
We make a tool for building playable ads, and we think a significant share of the people considering one should not build it. Here is how to tell whether you are one of them, before you spend the money.
8 min readWhat 50 Playable Ads Have in Common
Watch enough interactive advertising and the same skeleton appears everywhere. The interesting part is the short list of things that show up only in the ones that hold together.
10 min read