This section covers interactions between Playables and the YouTube user experience. > [!IMPORTANT] > **Important:** Translated requirements are provided for reference only. Refer to the [English versions of requirements](https://developers.google.com/youtube/gaming/playables/certification/requirements?hl=en) for definitive guidance. ## 1 Aspect ratio and orientation - Game **MUST** follow responsive design: be playable in all aspect ratios and adjust automatically when the viewport changes. Non-exhaustive examples: 9:32, 9:21, 9:16, 3:4, 1:1, 4:3, 16:9, 21:9, 32:9. - Game **SHOULD** fill the available viewport. If the game does not fill the available viewport, the game **MUST** be centered and include a pillarbox (left and right empty padding) or letterbox (top and bottom empty padding). - Game **MUST NOT** lock device orientation or device posture. - Game **MUST** maintain the game state or progress when the window is resized. We recommend not restarting or refreshing the game unless the user can quickly resume from the prior state. Visual examples of these requirements:  For a larger view, [go directly to this image](https://developers.google.com/static/youtube/gaming/playables/certification/images/2025-09-10_size_examples.jpg).
## 2 Interaction methods - Game **MUST** support touch input for all interactions. - Game **MUST** support mouse input for all interactions. - Game **MUST NOT** unintentionally delay or ignore any user input. - Game **MUST NOT** have any errors or unexpected behavior for any UI components. - Game **SHOULD** support keyboard input for directional or text input. - Game **SHOULD** allow users to close modals or dialogs using the Esc key. - Game **MUST NOT** call `preventDefault()` on Esc events. - Game **MAY** use haptic feedback where appropriate. If the game includes haptic feedback, game **MUST** provide a way to toggle haptic feedback on and off. ## 3 Game user interface (UI) This section covers game user interface (UI) requirements. ### 3.1 Rendering - Game **MUST** render all text and graphics clearly (not blurry, pixelated, or stretched) across all screen resolutions, aspect ratios, and densities. ## 4 Metadata Developer **MUST** provide all required metadata fields when using the [Developer Portal](https://developers.google.com/youtube/gaming/playables/developer_portal) to publish games. Full details about metadata requirements can be found in the [Developer Portal](https://developers.google.com/youtube/gaming/playables/developer_portal). Developer **MUST NOT** include any branding or logos in the thumbnails, description, or title. A non-exhaustive list of the types of metadata required are: - Image thumbnails in several different aspect ratios - Game description - Game title - Game genre - Publisher / Developer information ## 5 Completion of content handling - Game **MUST** communicate that there is no more content to engage with, such as after the final level or at the end of game progression. ## 6 Disallowed elements This section covers elements that are disallowed in Playables. ### 6.1 In-game sharing - Game **MUST NOT** display in-game sharing prompts. ### 6.2 External links - Game **MUST NOT** display clickable links that take users directly to external content, such as other sites or games. You may create links on your channel as described on the [channel help page](https://support.google.com/youtube/answer/2657964). ### 6.3 Additional user agreements - Game **MUST NOT** display an additional user agreement. Users agree to relevant YouTube [policies](https://www.youtube.com/howyoutubeworks/policies/overview/), [terms](https://www.youtube.com/t/terms), and [privacy details](https://www.youtube.com/t/privacy). ### 6.4 Elements that create confusion - Game **MUST NOT** place icons that are identical to Playables actions in close proximity to the actual Playables actions, such as the close, mute, or menu buttons. - Game **MUST NOT** have an in-game exit or quit button.