YouTube Playables certification checklist, area by area

Every published YouTube Playables certification area as a checklist, with MUST and SHOULD kept as Google states them and one link per area to the official page.

Published
Sources checked

Every Playable goes through a certification review before it launches on YouTube. Google publishes the requirements as eight areas, each on its own page, and writes them with RFC 2119 keywords. This checklist follows those pages as of 2026-10-01, keeps each item’s keyword as published, and links each area once. For SDK calls and code, see YouTube Playables SDK basics; for the portal summary, see the YouTube Playables page.

How to read the keywords

The certification overview defines the terms:

  • MUST / MUST NOT: absolute. A Playable that fails any MUST item is not allowed to publish.
  • SHOULD / SHOULD NOT: may be skipped for a valid reason after weighing the implications. Meeting SHOULD items helps a Playable get better visibility.
  • MAY: optional.
  • EXPECT: optional today, expected to become MUST in the next version of the requirements.

The same page says the review is holistic. Besides these requirements, YouTube looks at the creator’s history on YouTube and past Playables performance, and the English versions of the requirements are the definitive ones. The certification pages carry their own revision dates; the revision history lists changes as recent as 2026-08-25.

Integration

Integration requirements

  • MUST load the Playables SDK before any game code.
  • MUST call firstFrameReady while a loading or splash screen tells the player loading is under way.
  • MUST call gameReady only once the game accepts input; MUST NOT call it while splash or loading screens are still showing.
  • MAY send scores with sendScore; if it does, the best score sent MUST match the best score in the save.
  • MUST save material progress with saveData, MUST NOT use any other save mechanism, MUST await loadData before the first saveData, and MUST read saves from earlier versions without errors. Games designed to restart every session are exempt from the save rule.
  • SHOULD auto-save at milestones. The exit save is best effort and capped at 64 KiB.
  • MUST respect system audio, device volume and the YouTube mute through isAudioEnabled and onAudioEnabledChange; SHOULD NOT show an overall in-game mute button.
  • MUST pause all execution on onPause and resume only on onResume; MUST NOT use the Page Visibility API. SHOULD save on pause.

Stability and performance

Stability and performance requirements

Item MUST SHOULD
Initial bundle (bytes until gameReady) under 30 MiB under 15 MiB
Total bundle (all hosted files) under 250 MiB by default load only what interactivity needs, lazy-load the rest
Any single file under 30 MiB under 512 KiB
Saved game under 3 MiB under 500 KiB
Load time none interactive in under 5 seconds
File count at most 8,000 none

Also on that page: MUST NOT have consistently reproducible crashes, exceed a 512 MB peak JavaScript heap, or crash the YouTube app or site; MUST use standards-based web APIs, work in every browser YouTube supports and in the YouTube Android and iOS apps; MUST use relative paths only; file names MUST stick to letters, digits, underscore, hyphen and dot.

The certification FAQ adds that initial size is measured after HTTP compression, that the per-file limit has no exemptions, and that games which lazy-load can ask support about a larger total bundle. Size tactics are in keeping web game builds small.

Design

Design requirements

  • MUST be playable at every aspect ratio and adapt when the viewport changes; SHOULD fill the viewport, and if it does not, MUST be centered with letterbox or pillarbox.
  • MUST NOT lock orientation or posture; MUST keep game state across resizes.
  • MUST support touch and mouse for all interactions; SHOULD support keyboard for directional or text input; SHOULD let Esc close dialogs and MUST NOT call preventDefault() on Esc.
  • Haptics are optional, but if present MUST have an on/off toggle.
  • MUST render text and graphics sharply at every resolution and density.
  • MUST provide all required metadata and MUST NOT put branding or logos in thumbnails, title or description.
  • MUST tell the player when there is no more content.
  • MUST NOT show in-game sharing prompts, clickable external links, extra user agreements, look-alike copies of YouTube’s own controls next to them, or an exit button.

Google keeps optional advice in a separate design best practices page.

Accessibility

Accessibility requirements

  • SHOULD make a best effort toward WCAG AA.
  • SHOULD add Accessible Games Initiative tags to the listing; MUST NOT pick tags that misrepresent the game.

Internationalization and localization

i18n and L10n requirements

  • MUST support English.
  • MAY read the locale with getLanguage; MUST NOT use navigator.language or navigator.languages.

Privacy and data

Privacy and data requirements

  • MUST follow the Google Privacy Policy.
  • MUST NOT call any external URL or service other than Google or YouTube APIs, or try to get around that block. The certification FAQ says all game data must currently ship in the bundle.
  • MUST NOT draw anything that looks like or works as a QR code.
  • MUST NOT read the clipboard except on an explicit paste; MUST NOT ask for or collect personal data, or show anything resembling a login or sign-up screen.
  • MUST NOT obfuscate code. Minification and plain TypeScript transpilation are allowed.
  • MUST be a single-page application. YouTube may decline games it cannot evaluate because of WebAssembly, eval() or web workers, and limits the code size its tools can scan.

Trust and safety

Trust and safety requirements

  • MUST follow the YouTube Community Guidelines; MUST NOT target kids; MUST suit a general 13+ audience.
  • Title, thumbnail and description may not mislead.
  • MUST comply with the YouTube Developer Terms of Service.
  • MUST have cleared IP, trademark, music and personality rights; MUST be original, authorized or licensed; MUST NOT duplicate or closely copy a Playable already on YouTube.
  • Dev and staging links MUST NOT be shared outside certification testing.

Monetization

Monetization requirements

  • MUST NOT monetize, advertise or sell in-app items through off-platform services.
  • MAY show ads through YouTube’s own ad functions; if it does, mute and pause handling MUST keep working, and the ads MUST be switched on in the Developer Portal’s monetization settings.

How to use this before you submit

  1. Run the build through the SDK test suite. The test suite guide also gives a Content-Security-Policy string to set as a local header override, so CSP violations show up before review.
  2. Check sizes, file names and file counts with the bundle analyzer, then confirm the initial size with compression on.
  3. Search the code for fetch, XMLHttpRequest, WebSocket URLs and analytics tags; any call outside Google or YouTube APIs breaks the privacy rules, and any clickable outbound link breaks the design rules.
  4. Walk the design list at a tall, a square and an ultra-wide viewport, with touch and with a mouse.
  5. Upload the ZIP in the Developer Portal and test the dev link on desktop web, mobile web, Android and iOS, as the Developer Portal guide instructs.
  6. Submit. Only one release can be in certification at a time; to replace it, ask the Playables Ops team to reject the staging release.

The time-to-first-frame guide covers the timing side of firstFrameReady and gameReady.

What is not published

The requirement pages do not publish review times, a pass rate, the maximum code size YouTube’s tooling can scan, or exact thumbnail sizes (those are shown only inside the Developer Portal). They also do not describe how failed items are reported back; the overview only sends release questions to your Partner Manager.

Questions

What happens if a Playable misses a SHOULD requirement?
Google's definitions say a SHOULD item may be skipped for valid reasons once the implications are weighed, and that meeting SHOULD items helps visibility. Only MUST items block publishing outright.
Is the 30 MiB initial bundle limit measured before or after compression?
After. Initial bundle size counts the bytes downloaded until gameReady, and YouTube serves files with HTTP compression where possible, so a local test without compression can overstate it.
Can a Playable send analytics to my own server?
No. The privacy requirements forbid external calls except to Google or YouTube APIs, and the certification FAQ says internal analytics are not exempt.

Sources

  1. Certification overview and definitions (YouTube Playables)developers.google.com, accessed
  2. Integration requirements (YouTube Playables)developers.google.com, accessed
  3. Stability and performance requirements (YouTube Playables)developers.google.com, accessed
  4. Design requirements (YouTube Playables)developers.google.com, accessed
  5. Accessibility requirements (YouTube Playables)developers.google.com, accessed
  6. Internationalization and localization requirements (YouTube Playables)developers.google.com, accessed
  7. Privacy and data requirements (YouTube Playables)developers.google.com, accessed
  8. Trust and safety requirements (YouTube Playables)developers.google.com, accessed
  9. Monetization requirements (YouTube Playables)developers.google.com, accessed
  10. Certification FAQ (YouTube Playables)developers.google.com, accessed
  11. Test suite guide (YouTube Playables)developers.google.com, accessed
  12. Developer Portal guide (YouTube Playables)developers.google.com, accessed
  13. Revision history (YouTube Playables)developers.google.com, accessed