What is the elementor cookie?
elementor is a key stored in the browser's localStorage by the Elementor plugin, a widely used page builder for WordPress. It appears on any site running Elementor (free or Pro version) and is created automatically as soon as a page loads in the browser, both for regular visitors and for users editing the site from the back end.
Unlike an HTTP cookie, this entry is not automatically sent to the server with every request; it stays stored locally in the visitor's browser until it is manually cleared or site data is wiped.
What data it stores
The exact content of the value is not publicly documented in detail and may vary depending on the Elementor version and the active theme/page settings. Generally, this type of Elementor entry retains interface-related preferences and frontend behavior for elements built with the editor (for example, states of visual components or display settings that persist in the browser).
The data stays stored locally in the browser's localStorage and is not sent to external Elementor or third-party servers; it is only read by the Elementor script loaded on that page.
What it is used for
The purpose of this entry is functional: it allows the Elementor script to keep certain display settings consistent across page loads, without recalculating them each time. For site administrators, this translates into a smoother experience for visitors interacting with elements built in Elementor.
It is not used for advertising or traffic analytics purposes, but strictly to support the proper functioning of the theme's visual components.
Does it require consent?
CookieFix classifies elementor under the preferences (functional) category. Under GDPR and the ePrivacy Directive (transposed in Romania via Law 506/2004), storing data on a user's device for preference/functionality purposes that are not strictly necessary to deliver the service explicitly requested by the visitor generally requires prior consent.
- Site administrators should declare this entry in their cookie policy, under the "preferences" category.
- The Elementor script generating this entry should ideally load only after consent for the preferences category is obtained, rather than by default on page load.
- If a site only uses Elementor's strictly necessary layout-rendering functions without interactive elements depending on this value, behavior should be checked individually, as it may vary between versions.
How to block or delete elementor
A visitor can delete or block this entry directly from the browser: privacy settings allow clearing locally stored data (localStorage) for a given domain, or the visitor can use private/incognito mode, where such data does not persist after the session ends.
At the site level, administrators need a Consent Management Platform (CMP) that intercepts Elementor scripts writing to localStorage and holds them back until the visitor gives consent for the preferences category. CookieFix, for example, automatically blocks such scripts until acceptance, based on scanning and classifying the scripts detected on the site.
Frequently asked questions
It is a localStorage entry, not a classic HTTP cookie, but under the ePrivacy Directive and GDPR it is treated the same way because it stores data on the user's device.
Yes, since it is classified as preferences/functional and is not strictly necessary, it generally requires prior consent before being set.
It is persistent, meaning it remains in the browser's localStorage until manually cleared or site data is wiped, without a fixed expiration date like classic cookies.
Usually it does not affect the core page content, but some settings or behaviors of elements built with Elementor may not persist across visits.