What is the wp-settings cookie?
wp-settings is generated by WordPress core itself, not by a plugin or third-party service. It only appears once a user logs into the administration panel (wp-admin) of a WordPress site — regular site visitors without an account never receive it.
It is used exclusively to manage the admin session and the working interface inside wp-admin; it has no relation to the public-facing part of the site or to tracking visitors.
What data it stores
The cookie stores interface preferences for the logged-in user, such as whether the admin menu is expanded or collapsed, or the width of certain columns in content list screens. Its name typically includes the user's numeric ID (e.g. wp-settings-1).
The exact value depends on each site's configuration and the user's interactions with the dashboard; it contains no external identification data and is never sent to third-party servers — it stays strictly between the browser and that WordPress site.
What it is used for
The cookie's purpose is purely functional: it keeps the admin interface experience consistent across sessions, so editors and site administrators don't need to manually reset display preferences every time they log in.
It plays no role in marketing, analytics, or advertising, and does not contribute to building visitor profiles.
Does it require consent?
Under CookieFix's classification, wp-settings falls into the strictly necessary category. Since it relates solely to the functioning of the admin area for logged-in users (often the site administrator), it does not require prior consent under Article 5(3) of the ePrivacy Directive and, in Romania, Law 506/2004.
Site owners should still list it in their cookie policy, including its purpose and duration, for full transparency toward anyone with access to wp-admin.
How to block or delete wp-settings
A user can delete or block this cookie through browser settings (Chrome, Firefox, Edge, Safari — per-site cookie management), but doing so may affect how the WordPress admin panel behaves, resetting interface preferences or causing login issues.
- Being strictly necessary, a CMP like CookieFix does not block it by default — non-essential scripts are the ones auto-blocked until consent is given, while wp-settings belongs to the admin area rather than the visitor-facing consent banner.
- Site administrators can check for its presence in the site scan report to document it correctly in the cookie policy.
Frequently asked questions
No, it is strictly necessary and only appears for users logged into wp-admin, not for regular site visitors.
It is set by WordPress core itself, without any plugin or third-party service involved, when a user logs into the admin panel.
wp-admin interface preferences, like column widths or menu state, reset to defaults, but the cookie is recreated the next time you log in.
Yes, even though it doesn't require consent, GDPR transparency requires listing it along with its purpose and duration under strictly necessary cookies.