Stay organized with collections
Save and categorize content based on your preferences.
This section covers the stability and performance of Playables.
1 Initial bundle size
To properly test this requirement, the game may need to be ingested with
the developer portal and then tested in the test suite. Alternatively hosting
with compression on or zipping all of the initial loaded content can provide a
good approximation.
Game initial bundle size MUST be less than 30 MiB.
Game initial bundle size SHOULD be less than 15 MiB.
2 Total bundle size
By default, the game total bundle size MUST be less than 250 MiB.
Exceptions to this can be found in the FAQ.
Game SHOULD only load the minimal amount of data needed to enable
interactivity and lazy load the other data as needed.
3 Individual file size
Every individual file within the game MUST be less than 30 MiB.
Every individual file within the game SHOULD be less than 512 KiB.
4 Saved game size
Saved game size MUST be less than 3 MiB.
Saved game size SHOULD be less than 500 KiB.
5 Load time
Game SHOULD finish loading and allow user interaction in under 5
seconds.
6 Crashes
Game MUST NOT have consistently reproducible crashes.
Game MUST NOT exceed a peak JavaScript heap size of 512 MB. See the memory usage restrictions faq on why this causes crashes on iPhones.
Game MUST NOT crash the YouTube app, YouTube website, or other user
software.
7 Technologies used
Game MUST be based on standards-compliant Web APIs (e.g., JavaScript,
Canvas, WebGL) as defined by standards bodies (e.g., W3C, WHATWG).
Playables MUST be compatible with all browsers that YouTube supports
(including Edge, Chrome, Firefox, etc.)
Playables MUST be compatible with the YouTube app on Android and iOS.
8 File references
Game MUST only use relative paths when referring to other files in the
game bundle.
Game MUST NOT use absolute paths, as they will fail to load.
9 File names
Files in the game bundle MUST only contain alphanumeric and a few
special characters: _, -, ..
You can use the Playables bundle analyzer to conduct an initial validation of
the game bundle. This validation will assess the size of each individual file,
the overall bundle size, and any potential filename inconsistencies.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-06-24 UTC."],[[["Playables must have an initial bundle size under 15 MB and a total bundle size under 250 MB, ideally striving for 5 MB and 15 MB respectively."],["Individual files within the Playable should not exceed 30 MB, with a recommended size of less than 512 KB."],["Saved game data must be kept under 3 MB and should ideally be less than 500 KB to ensure efficient storage."],["Playables are expected to load and be interactive within 5 seconds to provide a seamless user experience."],["Games must be built using standard web technologies, be compatible with all YouTube-supported browsers, and not have reproducible crashes or exceed specified memory limits."]]],["Playables' initial bundle size must be under 15 MiB, ideally under 5 MiB, to ensure quick loading. The total bundle size should be below 15 MiB, with a maximum of 250 MiB allowed in some cases. Individual files must not exceed 30 MiB, ideally staying below 512 KiB. Saved game sizes should be kept below 500 KiB, with a limit of 3 MiB, and load time should be under 5 seconds. Games must avoid crashes, adhere to standard web APIs, use relative file paths, and utilize permitted file names.\n"]]
