What is the yt-remote-connected-devices cookie?
yt-remote-connected-devices is not a classic HTTP cookie but a localStorage entry created by the YouTube player script (iframe API). It appears on any page that embeds a YouTube video or player, whether or not the visitor interacts with it.
It is set automatically by Google/YouTube as soon as the player iframe loads, as part of the remote-control feature (for example, pairing the player with a remote, a YouTube TV app, or another device on the same network).
What data it stores
It stores technical information about devices associated with the video playback session, not directly identifying data such as a name or email address. Google does not publicly document the exact value format, and it may vary.
The data stays local in the visitor's browser but is tied to the Google/YouTube player scripts, which may communicate with YouTube servers as part of normal player operation.
What it is used for
Its main purpose is functional: it lets the YouTube player recognize and synchronize devices used to control video playback remotely (for example, a smartphone controlling a video shown on another screen).
For the site embedding the video, this entry brings no direct marketing or analytics benefit — it is part of the YouTube player's technical infrastructure, needed for its advanced features to work correctly.
Does it require consent?
In CookieFix's classification, yt-remote-connected-devices falls under preferences (functional), since it supports a playback personalization feature rather than being strictly necessary for basic page display.
- Under GDPR and the ePrivacy Directive, storing this entry requires the visitor's prior consent, obtained before the YouTube player is loaded.
- Site owners must disclose this cookie/localStorage entry in their cookie policy and correctly group it under the preferences/functional category in the consent banner.
- The YouTube player should not load automatically before consent for that category is obtained.
How to block or delete yt-remote-connected-devices
A visitor can manually clear localStorage data from browser settings (the "Site data" or "Privacy" section) or use private/incognito mode to avoid this entry persisting.
For site owners, proper blocking means preventing the YouTube player from loading (for example, replacing the iframe with a preview image) until the visitor accepts the preferences category. A CMP like CookieFix can do this automatically by intercepting the YouTube player script and releasing it only after consent.
Frequently asked questions
No, it doesn't contain sensitive or directly identifying data. It's a technical entry used by the YouTube player to support the remote playback control feature.
Because it's generated automatically by the YouTube player script when an embedded video loads, regardless of whether the visitor is logged in or uses the remote-control feature.
In most cases yes, since it's classified as preferences/functional, a category that requires prior consent under GDPR and ePrivacy.
Only by removing the embedded YouTube player completely, or by blocking it from loading until consent is given, using a CMP that controls script execution.