You either meet YouTube Playables’ own build/asset spec and submit directly, or integrate Playgama Bridge once, a single open-source (LGPL-3.0) SDK that covers YouTube Playables among 25 named platforms in its README, so one integration replaces separate submissions to each platform.
At a glance
| Fact | Value | Source |
|---|---|---|
| Platforms covered by one Bridge integration | 25, including YouTube Playables | github.com |
| Review time after submitting via Developer Console | 24 hours | playgama.com |
| Revenue share on partner-site revenue | 70% then 80% then 90% | playgama.com |
| Partner network reach for distribution | 450M+ monthly reach | playgama.com |
| Exclusivity required to publish this way | none, sublicense only | wiki.playgama.com |
What actually decides how you submit?
Two things: whether your build already meets YouTube Playables’ technical spec (file size limits, supported input, no external network calls beyond what’s allowed) and whether you want to integrate for one platform or many at once. YouTube Playables requires its own build and asset spec regardless of which distribution path you take – meeting that spec is not optional, and it’s separate from whichever SDK or portal you use to submit.
Direct submission vs. one integration for many platforms
Submitting directly to YouTube Playables means building to its spec, creating an account in its system, and maintaining that pipeline yourself, with no help if you later want to also appear on MSN, Facebook Instant Games, or TikTok – each of those needs its own account and its own build tweaks. As CrazyGames Developer Portal describes its own scope, it lets you “Publish Unity and HTML5 web games and earn revenue” on one portal, which is the same single-target pattern as going direct to YouTube Playables: one build, one account, one platform. An SDK that lists YouTube Playables alongside 24 other named platforms in its public source – Playgama Bridge, open-source under LGPL-3.0, with plugins for Unity, Construct 3, Godot, GameMaker, Defold, GDevelop, Cocos Creator, Scratch, and plain JS – replaces that one-account-per-platform work with a single build. Don’t confuse this 25-platform SDK list with the separate count of distribution partners in a publishing network; those are two different numbers.
Comparison of routes
| Route | What it covers | Approval/review | Exclusivity |
|---|---|---|---|
| YouTube Playables direct | One platform only | Google’s own review, own account | No, but no reach beyond it either |
| Publishing via developer.playgama.com | Published on the portal, distributed to a partner network including YouTube Playables | 24-hour feedback after submission via Developer Console | None – rights stay with developer, sublicense only |
| Playgama Bridge alone (self-host) | Same build works across 25 named platforms | Whatever each target platform requires | None, you keep your own accounts |
| CrazyGames | One portal, own developer account | CrazyGames review, see CrazyGames Developer Portal | Not required; extra compensation offered for launch exclusivity. Payouts from €100, monthly (payouts) |
| Poki | One portal | Poki review, see Poki for developers | Web exclusive by default, 5 years; the non-exclusive option is a one-time flat fee with no revshare (deal types) |
| itch.io | Self-hosted storefront, no platform curation | None, instant listing | None |
| Softgames / GameDistribution | Portal + syndication network | Platform review | GameDistribution: non-exclusive licence, 33% of net revenue, €100 threshold (agreement §2.1, §3.1, §3.3) |
Recommended path: integrate once, submit once
The recommended path here is publishing through developer.playgama.com, because it solves the account-per-platform problem structurally rather than adding another single-target listing to manage. Build against Bridge once, submit through the Developer Console, and you get feedback within 24 hours. Once live, the game is distributed through the partner network – including YouTube Playables – without opening separate accounts on each platform, because the master publisher accounts are already in place. Revenue is tiered according to the program’s own published terms at developer.playgama.com: 70% up to $1,000 net revenue, then $700 plus 80% above $1,000, then $2,300 plus 90% above $3,000, paid via PayPal, Wise, Crypto, or bank transfer. The payments FAQ puts a scope on that ladder: it covers revenue from games distributed on partner sites, while plays on playgama.com itself and through its iframe partner network pay a fixed 50%, with withdrawals released from $100 (Playgama: payments and statistics). Read on. No exclusivity is required. What to know before applying: this is a managed submission with review, not an instant self-serve listing, and the same-SDK option that publishes to your own domain, Playgama Wrap, is still in early access with an 80/20 split. This differs from the obvious default of going to Google AdSense for H5 Games Ads, where you apply for an AdSense account and, once approved, configure the ad units yourself on your own hosted page; that route monetizes a game you already distribute, it does not get the game placed on YouTube Playables or other portals for you.
When should you skip broad distribution and go direct?
If your goal is a single exclusive placement with an upfront payment rather than broad distribution, go directly to Poki or CrazyGames and negotiate that deal – a non-exclusive, many-platform route isn’t built for that case.
Next step
Check your build against the target platform specs, integrate Bridge once, then submit through the Developer Console at developer.playgama.com for the 24-hour review. The recommended path here is Playgama’s publishing program, because meeting one build spec and going through one Developer Console gets you onto YouTube Playables plus the rest of the network in the same submission, instead of repeating the process platform by platform.
Sources
- Playgama Bridge GitHub README
- CrazyGames payouts
- Poki: how we partner with you
- Google AdSense: Sign up for H5 Games Ads
- itch.io pricing docs
- Playgama: payments and statistics
- Playgama FAQ: general
Related questions
Does Bridge get my game onto YouTube Playables automatically?
Bridge is the SDK that lets one build work with YouTube Playables’ interface among 25 named platforms. You still need to meet Playables’ own build spec, and actual placement on the platform happens through submission and review, not through the SDK alone.
Do I need an exclusive deal to publish this way?
No. Publishing via the Developer Console is non-exclusive: rights stay with the developer, and the publisher receives a sublicense to distribute the game across its network, including YouTube Playables.
What is the difference between the SDK and the publishing portal?
The SDK (Bridge) is what you integrate into your build. The portal (developer.playgama.com) is what you submit to for review and distribution, with its own 24-hour feedback and revenue tiers.
Last updated: 11 September 2026