Certification
Stay organized with collections
Save and categorize content based on your preferences.
To verify smooth and safe experiences for players on YouTube, all Playables must
go through a review process before being publicly launched. This includes
required APIs, relevant restrictions, Trust and Safety, Privacy, and other
content requirements.
Review the contact information on the support contact page.
Requirements
The review process is intended to confirm the Playables meet various
requirements. Check the navigation to review the different types of
requirements.
Test
Use the test suite to validate your integration the with
Playables SDK.
Release
Speak to your Partner Manager for details on this process.
Definitions
The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", "MAY" and "EXPECT"
used throughout these documents are to be interpreted as described in RFC
2119. An abridged list is included here for reference:
- MUST: This word, or the terms "REQUIRED" or "SHALL", means that the
definition is an absolute requirement of the specification. If a Playable
cannot meet any of such requirements, it will not be allowed to publish on
YouTube.
- MUST NOT: This phrase, or the phrase "SHALL NOT", means that the
definition is an absolute prohibition of the specification.
- SHOULD: This word, or the adjective "RECOMMENDED", means that there may
exist valid reasons in particular circumstances to ignore a particular item,
but the full implications must be understood and carefully weighed before
choosing a different course. Completing those requirements would help
Playables get better visibility.
- SHOULD NOT: This phrase, or the phrase "NOT RECOMMENDED" mean that there
may exist valid reasons in particular circumstances when the particular
behavior is acceptable or even useful, but the full implications should be
understood and the case carefully weighed before implementing any behavior
described with this label.
- MAY: This word, or the adjective "OPTIONAL", means that an item may or
may not be implemented at the discretion of the implementer.
- EXPECT: This word is used exclusively to indicate requirements that
YouTube EXPECTS to make required (aka MUST) in the subsequent version of
these requirements, but which is optional for this document (MAY).
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-20 UTC.
[[["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-08-20 UTC."],[[["\u003cp\u003eAll Playables on YouTube undergo a review process before public launch to ensure safety and smooth user experiences.\u003c/p\u003e\n"],["\u003cp\u003ePlayables must meet various requirements relating to APIs, content, privacy, and trust & safety, with definitive guidance provided in the English versions of those requirements.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers can utilize the provided test suite to validate their Playables' integration with the Playables SDK.\u003c/p\u003e\n"],["\u003cp\u003ePlayable release procedures involve communication with a designated Partner Manager.\u003c/p\u003e\n"],["\u003cp\u003eThe requirements documentation uses RFC 2119 keywords to indicate the strictness of each requirement, ranging from absolute necessities (MUST) to optional implementations (MAY).\u003c/p\u003e\n"]]],["Playables on YouTube must undergo a review process encompassing API requirements, restrictions, Trust and Safety, Privacy, and content standards before public launch. Developers should use the test suite to validate SDK integration and consult their Partner Manager for release details. Key terminology like \"MUST,\" \"SHOULD,\" and \"MAY\" define the strictness of the requirements. English versions of requirements are the definitive guidance. Contact information can be found on the support contact page.\n"],null,[]]
