How to submit your HTML5 game to YouTube Playables Builder
How I Submitted My HTML5 Game to YouTube Playables Builder
I built this small game last month. Nothing fancy. Just a simple color matching thing. Tap the right color before time runs out. My friends liked it. They said, put it somewhere people can find it.
Then I heard about YouTube Playables Builder. Honestly, I did not even know YouTube took games. I thought it was just videos. But turns out, YouTube now lets you upload small HTML5 games directly to them. And people can play those games right inside YouTube. No downloads. No extra clicks.
So I tried it. And after a few rejections, I finally got my game live. Let me tell you exactly how I did it. Not the official YouTube help center version. The real version. The one with mistakes and confusion and small victories.
First, I Had to Understand What This Thing Actually Wants
YouTube Playables Builder is not for big games. Forget 3D graphics. Forget heavy Unity builds. They want small, quick HTML5 games. The kind that loads in two seconds. The kind you play while waiting for a video to buffer.
My game was already HTML5, so that was fine. But I learned quickly that YouTube is very picky about file size. My first version had high quality background images. Each image was nearly one megabyte. The game took six seconds to load on my phone. That is too slow for YouTube.
So I compressed everything. I changed images from PNG to JPG where I could. I removed one sound effect that I did not really need. The game size dropped from twelve megabytes to three megabytes. Much better.
The Rules Nobody Reads But Everyone Should
Before you upload anything, you need to know what YouTube will reject. Because they will reject you. Probably more than once. And each rejection takes days.
First rule that surprised me: no ads inside your game. I am not talking about YouTube ads. I mean your own ads. You cannot put an AdSense banner inside your game. You cannot put a popup saying "watch this ad for extra life." YouTube handles all the ads themselves. Your job is just to make a clean game.
Second rule: no external links. Your game cannot have a button that says "visit our website" and then opens a new tab. YouTube blocks that during review. I had a small credit line in my game that linked to my portfolio. I had to remove it.
Third rule: everything must be inside the zip file. Do not load anything from the internet. No Google Fonts. No CDN for jQuery. No external sound files. If your game needs it, put it in the folder. I learned this the hard way. My game used a nice font from Google Fonts. YouTube rejected it because the game tried to fetch that font after loading.
Getting My Files Ready for Upload
I created a folder on my desktop. I named it simply "colormatch" no spaces.
Inside that folder, I put my index.html file. That is the main file. Then my style.css and my script.js. I also made a subfolder called assets. Inside assets, I put all my images and sounds.
I made sure every file path was relative. Meaning, instead of writing "C:/Users/name/desktop/image.png" I wrote "assets/image.png". This is important because YouTube will run your game on their server. Absolute paths break everything.
Then I selected all these files and folders, right clicked, and chose "compress" to make a zip file. Not rar. Not 7z. Just plain zip.
Finding the Submission Page Was Tricky
This part confused me for a while. YouTube Playables Builder is not inside every YouTube account. I logged into my YouTube Studio and looked everywhere. No Playables tab.
Turns out, you need to request access first. I went to YouTube's creator support page. I filled out a short form. I said I have an HTML5 game and I want to submit it to Playables. They took about four days to reply. Then they enabled the Playables tab in my studio.
Once that tab appeared, I clicked it. Then I clicked "submit a new playable". A form opened up.
Filling the Form Honestly
The form asked for basic things. Game title. I wrote "Color Match Quick Tap" nothing fancy. Description. I wrote two lines only. "Tap the color that matches the word. Finish before time runs out." Short and true.
Category. I chose puzzle. Language. English. Thumbnail. I made a simple 1280x720 image. Just the game screen with the title on top. No flashy arrows or fake play buttons. Just honest.
Then I uploaded my zip file. Clicked submit.
The Sandbox Test Saved Me
After uploading, the game did not go for review immediately. It went to something called a sandbox. Basically a private testing area where I could play my game exactly how YouTube sees it.
This is where I found problems I did not know existed.
On my desktop browser, the game worked fine. But when I switched to mobile view in the sandbox, the tap area was too small. My fingers kept missing the buttons. I had to go back, increase button sizes in my CSS, and upload a new zip file.
Also, the game sound was too loud. I mean, really loud. It scared me when I clicked start. So I lowered the volume in my code and uploaded again.
I tested maybe eight versions over two days. Each time finding something small. Each time fixing it. This step felt annoying at first, but later I realized it saved my game from rejection.
Hitting the Submit Button
After I stopped finding issues, I clicked "submit for review". Then I waited.
The first time I submitted, I got a rejection email after five days. The reason was "game does not work properly on small screens." I thought I had fixed that. But apparently not fully. So I tested again. Found out that on very small phones, the score text overlapped with the timer. Fixed that. Resubmitted.
Second rejection came after four days. This time they said "loading time too long on mobile networks." I went back and optimized one more image. Also removed an unnecessary animation that used heavy CSS. Resubmitted.
Third time, approval came. Seven days after that submission. I almost missed the email because I had stopped checking.
What Approval Looked Like
YouTube gave me a link. A direct link to my game. Anyone who clicks it can play inside YouTube. On desktop, the game shows up right below the video player. On mobile, it opens full screen but still inside the YouTube app.
I shared the link with my friends. They played. Some shared further. That was it. No big celebration. Just a quiet satisfaction that my game actually worked on YouTube.
What I Learned From the Whole Process
If I had to do it again, I would save myself a lot of time by doing three things from the start.
First, test on an actual small phone. Not just browser developer tools. Real phones show real problems.
Second, remove everything that is not absolutely needed. Every image, every sound, every line of code. Ask yourself, does this make the game better? If not, delete it.
Third, read the rejection reasons carefully. YouTube does not give vague rejections. They tell you exactly what failed. My first two rejections were my fault. I did not test properly. Once I started taking their feedback seriously, approval came quickly.
Should You Try This?
If you have a small HTML5 game sitting on your computer, yes. Absolutely try. The submission process is free. The sandbox testing is free. Getting your game on YouTube gives you exposure you cannot buy.
But do not expect to get rich. YouTube does not pay you directly for playables right now. At least not in most countries. The real value is people discovering your game, then finding your channel, then watching your other content.
For me, the best part was seeing strangers play my game. People I never met. In countries I have never visited. That feeling alone was worth the rejections.
So clean up your game. Compress those images. Test on a real phone. Then submit. And when they reject you the first time, fix and submit again. That is how it works. That is how I did it.