Features Pricing GDPR cookie banner Google Consent Mode v2 WordPress plugin Cookiebot alternative For Agencies GDPR ePrivacy About Contact
RO | EN
Start Free →
Necessary

wp-settings- Cookie (WordPress) — What It Is & Purpose

wp-settings-[ID] is a technical cookie set by the WordPress platform for users logged into the admin dashboard (wp-admin). It stores interface preferences, such as menu states or column layouts in editing screens. It is strictly necessary for the admin panel to function and does not track visitors on the public site.

Name
wp-settings-…
Provider
WordPress
Category
Necessary
Type
HTTP cookie
Lifetime
1 year
Consent
No, but it must be listed in the cookie policy
Prevalence
found on 4 Romanian sites scanned by CookieFix

What is the wp-settings- cookie?

The wp-settings-[ID] cookie is part of WordPress's internal cookie set, the most widely used content management system (CMS). The full name includes a unique numeric identifier (the WordPress user account ID), for example wp-settings-1.

It is set automatically by WordPress core, not by a theme or plugin, when a user logs into the admin area (/wp-admin). It does not appear for regular visitors of the public site, only for logged-in account holders (administrators, editors, authors).

What data it stores

The cookie value is a string of key-value pairs separated by &, encoding the user's wp-admin interface preferences — for example, the open/closed state of sidebar panels, the order and width of columns in post lists, or the timezone shown in the editor. The exact format can vary between WordPress versions.

Data is stored only locally in the user's browser and sent solely to the site's own domain (first party), to the admin area. It is not shared with third-party servers and has nothing to do with tracking visitor behavior.

What it is used for

The purpose of this cookie is purely functional: it keeps the WordPress admin dashboard experience consistent across sessions and pages, so a logged-in user finds the interface configured the way they left it (menus, columns, visual filters). It has no analytics, marketing, or advertising role.

Does it require consent?

Under CookieFix's classification, wp-settings-[ID] is a strictly necessary cookie, since it is essential to how login and the admin interface function — it has no cookie-free equivalent and is not used for marketing or public-traffic statistics.

Under GDPR and the ePrivacy Directive (transposed in Romania via Law 506/2004), strictly necessary cookies do not require prior visitor consent. Still, site owners should declare it correctly in their cookie policy, noting its purpose, duration, and that it only applies to logged-in wp-admin users, not the general public.

How to block or delete wp-settings-

A logged-in user can delete or block this cookie via browser settings (Chrome, Firefox, Edge, Safari — per-site cookie management), though the effect is losing saved wp-admin interface preferences, not being automatically logged out.

  • Since it only affects the admin area, it should not be included in the list of scripts blocked by the consent banner shown to public visitors.
  • A CMP platform like CookieFix automatically blocks scripts from categories that require consent (statistics, marketing) until visitors accept, but strictly necessary cookies like this one stay active, since they are essential to the site's operation.

Frequently asked questions

It represents the unique ID of the logged-in WordPress user account, so each user's interface preferences are stored separately.

No, it's a strictly necessary cookie for login and admin panel functionality, so it doesn't fall under the prior-consent requirement of GDPR/ePrivacy, but it should still be listed in your cookie policy.

No. It is only set for users logged into wp-admin and has nothing to do with tracking the behavior of public site visitors.

Your saved admin interface preferences (e.g. panel or column states) reset to defaults, but you won't be logged out of your WordPress account.

Updated 7 September 2026 · Information comes from the provider’s public documentation and CookieFix scans; it is not legal advice.