What is the wp_lang cookie?
wp_lang is a native WordPress cookie generated by the CMS core itself, not by a third-party plugin. It typically appears when a user interacts with the login screen (wp-login.php) or the admin dashboard (wp-admin) of a multilingual WordPress site, where an admin interface language can be chosen.
On most WordPress sites running a single admin language, this cookie never appears for public visitors — it's mainly relevant to administrators, editors, and other authenticated users.
What data it stores
The cookie stores the selected language code (typically a WordPress locale-style code such as ro_RO or en_US), without explicit personal data such as name, email, or advertising identifiers.
It is sent only to the site's own domain (a first-party cookie) and is not shared with third-party servers, since WordPress is self-hosted software running on the site owner's infrastructure.
What it is used for
The cookie's purpose is purely functional: it remembers the admin interface's language preference for the duration of the session, so the user doesn't need to reselect it on every page of wp-admin or on the login screen.
It is not used for statistical analysis, advertising, or tracking visitor behavior across the site.
Does it require consent?
In CookieFix's classification, wp_lang falls under preferences (functional). As a session cookie tied almost exclusively to the admin area and authenticated users (not the general public), it can often be treated as strictly necessary for backend functionality, though its exact classification can vary depending on site configuration.
- If it only appears for logged-in users in
wp-admin, the impact on regular visitors is generally none. - If a theme or multilingual plugin exposes it to public visitors as well, the site owner should list it correctly in the cookie policy under Law 506/2004 (Romania's ePrivacy transposition) or the equivalent local law, and verify whether consent applies.
How to block or delete wp_lang
A visitor can delete or block this cookie from browser settings (Chrome, Firefox, Edge, Safari — per-site cookie management), keeping in mind that blocking it may reset the admin interface language preference on next login.
For site owners who want centralized control over all cookies, including those generated by WordPress core or plugins, a CMP platform like CookieFix can automatically block scripts that set non-essential cookies until visitor consent is obtained, in line with GDPR and ePrivacy requirements.
Frequently asked questions
No, it's a functional cookie that only remembers the interface language, without tracking visitor behavior or collecting personal data.
Usually not; it's mainly tied to the admin area (wp-admin) and logged-in users, not the general public visiting the site.
Yes, any cookie set by the site should be listed in the cookie policy, even if it's strictly necessary and doesn't require prior consent.
On the next login to wp-admin, the interface may revert to the default language, and the user will need to reselect their preferred language.