What is the yt-remote-device-id cookie?
yt-remote-device-id is not a classic HTTP cookie but an entry stored in the browser's localStorage. It is created by the YouTube video player when a visitor interacts with a YouTube video embedded on a website.
It typically appears only when a page contains an active YouTube player or when a visitor uses YouTube's remote-control features (controlling a player from another device, such as a phone controlling playback on a TV or screen). It is set by the youtube.com/Google domain, not by the host website itself.
What data it stores
It stores a unique identifier associated with the device accessing the YouTube player, used to recognize that device across future viewing sessions. The exact value format is not publicly documented by Google and may vary.
As a localStorage entry, the data stays stored locally in the browser and is read by YouTube scripts loaded on the page; it is not transmitted as a classic HTTP header, but the information can be used by Google's scripts when communicating with YouTube/Google servers.
What it is used for
Its main purpose is functional: it lets the YouTube player recognize the current device to synchronize video control across devices (for example, a phone acting as a remote for a video shown on another screen) and to retain certain playback-related preferences between visits.
For the site owner, this cookie does not provide analytics or direct marketing data — it is part of the technical infrastructure of the embedded YouTube player.
Does it require consent?
CookieFix classifies yt-remote-device-id as preferences (functional). Although it serves a technical role tied to player functionality, it is not strictly necessary for basic page loading, so it is treated as requiring visitor consent under Romania's Law 506/2004 (transposing the ePrivacy Directive) and the GDPR, since it stores information on the user's device without being indispensable to the site's operation.
- The site owner must list it in the cookie policy under the preferences/functional category.
- The YouTube player should not load automatically before the visitor has given consent for this category.
How to block or delete yt-remote-device-id
A visitor can delete or block this entry through the browser's site data settings (cookies and locally stored data) for the youtube.com domain, or by using private/incognito mode.
For site owners, the recommended solution is a Consent Management Platform (CMP) such as CookieFix, which automatically blocks the YouTube player and its associated scripts from loading until the visitor accepts the „preferences” category, replacing the embed with a placeholder until consent is given.
Frequently asked questions
It is a localStorage entry, not a classic HTTP cookie, but it is treated similarly under ePrivacy/GDPR since it stores data on the user's device.
Yes, since it is classified as preferences/functional, it requires the visitor's prior consent before being set.
It is persistent, meaning it remains in localStorage until manually cleared by the user or the browser.
It is set automatically by any embedded YouTube player on the page, regardless of whether the site owner or visitor has a Google account.