YouTube Device Certification: 2028 Hardware & 2027 Software Changes

Draft requirements become public on March 24. Partners have until May 1 to submit feedback through the official form, and they may send multiple submissions. The final requirements are locked in on July 1, after which no further changes are possible.

2028 Hardware Requirements

All devices that support 4K resolution must include an AV1 decoder; VP9 remains optional when AV1 is present. Premium users gain 4× variable‑speed playback, and “decode to texture” returns to keep UI animations synchronized with video frames. Widevine OEM crypto version 20 is required for DRM protection. Audio must comply with the IMF standard, while partial‑frame exceptions apply to EAC3, AC3, and IMF streams.

2027 Software Requirements

Voice & Assistant Integration

When YouTube runs in the foreground, every voice query routes directly to YouTube, except for command‑and‑control requests. Device assistants must stay silent and avoid pausing playback while YouTube handles the query. Wake‑word data is stripped from the query payload, and soft‑mic support is mandatory to enable YouTube’s specialized speech‑to‑text engine.

App Integrations & Connected Experiences

The Recommendations API replaces the older data API, and universal search adapts to LLM‑driven multi‑turn chat. Google Cast and Cast Connect become “should” requirements, while handheld gaming devices are exempt from DIAL compliance.

Rendering & Performance

Devices must support Vulkan 1.4, OpenGL ES 3.2, and EGL 1.5. During UI transitions, devices retain the previous frame to prevent black or white flashes, and a “change type” API eliminates full media element teardown.

Telemetry & App Health

Memory reporting shifts from generic system RAM metrics to app‑specific memory APIs. A new OS‑level app‑exit enumeration identifies termination reasons such as out‑of‑memory or non‑responsiveness. An API detects app updates in stores to trigger user nudges, and an absolute‑volume API manages audio peaks and low‑volume scenarios.

Connectivity & General Standards

IPv6 support is mandatory on devices that natively handle it. HDMI connections must transmit proper AV1 info‑frame signals to disable TV overscan. Devices report a user‑friendly name through the Starboard protocol, and combined AI/mic remote buttons must behave identically to standard mic buttons.

Policy & Testing Updates

Security rules now block unauthorized third‑party apps from spoofing TV endpoints. Testing adopts DAB 2.1 as a required component, streamlining automated test suites. Adding or removing a YouTube button triggers a partial certification, while smart monitors and projectors sharing an OS or SoC with existing TVs may use “paper certification.”

“The only request and the only ask I have is to please be as specific and as detailed as possible so we can take the appropriate action.”

“Once we publish the final requirements we won't be able to make any other changes.”

“Routing these queries to YouTube ensures a frictionless and importantly a context‑aware experience for our mutual users.”

“We are eliminating the need for complex music or video related routing logic.”

“We are establishing explicit rules to block unauthorized third‑party apps from spoofing our TV endpoints.”