What is the dpr cookie?
The dpr cookie is placed by Facebook, usually when a page loads a Facebook social element – a Like/Share plugin, comment box, embedded video, or other Facebook social widget. The name appears to reference "device pixel ratio", a technical parameter used to render Facebook content correctly based on the visitor's screen resolution.
It is set on the .facebook.com domain, making it a third-party cookie from the perspective of the site embedding the plugin, even though it is technically set by Facebook's own infrastructure when the plugin loads.
What data it stores
The cookie appears to store a technical value related to the device pixel ratio of the visitor's screen, used to correctly render Facebook's graphical elements (images, icons, embeds). The exact value format is not publicly documented by Facebook and may vary.
The data is sent to Facebook's servers whenever the browser contacts the .facebook.com domain to load the social plugin, alongside standard HTTP request information (IP address, user agent, referring page).
What it is used for
For Facebook, this cookie helps display its social elements (buttons, embeds, comments) correctly and efficiently across different screens and devices, improving the visual rendering of embedded widgets.
For the website operator, the cookie provides no direct functionality; it is simply a side effect of embedding a Facebook plugin or widget on the page. Without it, Facebook elements may still work, but potentially with less optimized rendering.
Does it require consent?
CookieFix classifies dpr under preferences (functional). Since it is set by a third-party service (Facebook) and is not strictly necessary for the site's core functionality, under the ePrivacy Directive (transposed in Romania via Law 506/2004) and GDPR it generally requires the visitor's prior consent before being placed.
- The site operator should list this cookie in the cookie policy, including provider (Facebook), purpose, and duration.
- The Facebook plugin or widget generating this cookie should load only after consent is given for the preferences category, not by default on page load.
- Periodic rescanning is recommended, since Facebook may change the name or behavior of its cookies without prior notice.
How to block or delete dpr
A visitor can manually delete or block this cookie via browser settings (Chrome, Firefox, Edge, Safari – per-site cookie management), or use browser extensions that block third-party Facebook content.
For site operators, the correct approach isn't manual deletion but preventing the Facebook script or plugin from loading before consent is given. A CMP like CookieFix can automatically block, through scanning and predefined rules, any script that would set this cookie until the visitor accepts the preferences category in the consent banner.
Frequently asked questions
No, it's a technical cookie related to correctly displaying Facebook elements based on the device's screen, and it doesn't store any publicly known sensitive data.
No, it results from embedding a Facebook plugin, so it isn't essential to the site's core functionality and requires consent under ePrivacy/GDPR.
It typically lasts about one week before expiring automatically from the browser.
It appears whenever a site loads any Facebook element (Like button, comments, embedded video), regardless of whether the site itself has a Facebook page.