What is the wd cookie?
„wd” is an HTTP cookie set by the .facebook.com domain, typically when a page loads a Facebook element such as a „Like” button, a social plugin, an embedded video, or a comments widget. It is not set directly by the site the visitor is browsing, but by Facebook scripts running within that page (often inside an iframe).
The cookie is created on the first interaction between the browser and Facebook resources, and it is refreshed or reset whenever the browser window size changes.
What data it stores
According to Facebook's publicly available documentation, „wd” stores the browser window's dimensions (width and height, in pixels) at the moment the Facebook resource loads. The exact value format is not documented in detail and may vary.
The value is sent to Facebook's (Meta Platforms, Inc.) servers, where it is used on their side to render embedded content correctly — not by the host website itself.
What it is used for
Its main purpose is to optimize the display of embedded Facebook elements on third-party pages: the video player adapts to available space, and social plugins (like, share, comments) resize correctly without breaking the page layout.
For the site owner, this cookie provides no functionality of its own — it's simply a side effect of embedding a Facebook widget or plugin on the page.
Does it require consent?
CookieFix classifies „wd” under preferences (functional). In practice, however, since it is set by a third-party domain (Facebook) for display-related purposes, most European regulatory guidance treats third-party cookies of this kind as requiring prior consent under ePrivacy rules (implemented in Romania via Law 506/2004) and GDPR's requirements for freely given consent.
- Don't automatically classify it as „strictly necessary” just because it looks technical.
- List it in your cookie policy, naming the provider (Facebook/Meta) and duration (approx. 1 week).
- Make sure the script that generates it (widget, button, embedded Facebook video) only loads after consent, if the visitor hasn't accepted the preferences/functional category.
How to block or delete wd
A visitor can manually delete the cookie from browser settings (Chrome, Firefox, Edge, Safari – cookie management for the relevant site or for facebook.com), or use private/incognito browsing to avoid it being stored.
For site owners, effective blocking means preventing Facebook scripts and widgets from loading before consent is obtained. A CMP like CookieFix can automatically block such third-party scripts until the visitor gives consent for the relevant category, preventing Facebook cookies from being set prematurely.
Frequently asked questions
It's a technical cookie set by Facebook, used to store the browser window's dimensions when a page loads Facebook content such as a plugin, button, or video.
Since it's a third-party cookie set by Facebook for display purposes, it should generally be treated as requiring prior consent under Law 506/2004 and GDPR, though some classifications list it as functional.
Its typical duration is about one week, after which it is reset or refreshed on a new interaction with Facebook resources.
You can't control Facebook's cookies directly, but you can prevent them from being set by blocking Facebook widgets/plugins from loading until consent is obtained, for example through a CMP.