The Clear-Site-Data header clears browsing data (cookies, storage, cache) associated with the requesting website. It allows web developers to have more control over the data stored locally by a browser for their origins.

Header type Response header
Forbidden header name no


The Clear-Site-Data header accepts one or more directives. If all types of data should be cleared, the wildcard directive ("*") can be used.

// Single directive
Clear-Site-Data: "cache"

// Multiple directives (comma separated)
Clear-Site-Data: "cache", "cookies"

// Wild card
Clear-Site-Data: "*"


Indicates that the server wishes to remove locally cached data (i.e. the browser cache, see HTTP caching) for the origin of the response URL. Depending on the browser, this might also clear out things like pre-rendered pages, script caches, WebGL shader caches, or address bar suggestions.
Indicates that the server wishes to remove all cookies for the origin of the response URL. HTTP authentication credentials are also cleared out. This affects the entire registered domain, including subdomains. So as well as, will have cookies cleared.
Indicates that the server wishes to remove all DOM storage for the origin of the response URL. This includes storage mechanisms such as:
Indicates that the server wishes to reload all browsing contexts for the origin of the response (Location.reload).
"*" (wildcard)
Indicates that the server wishes to clear all types of data for the origin of the response. If more data types are added in future versions of this header, they will also be covered by it.



If a user signs out of your website or service, you might want to remove locally stored data. You can achieve that by adding the Clear-Site-Data header to the response of

Clear-Site-Data: "cache", "cookies", "storage", "executionContexts"

Clearing cookies

If this header is delivered with the response at, all cookies on the same domain and any subdomains (like, etc), will be cleared out.

Clear-Site-Data: "cookies"


Specification Status Title
Clear Site Data Working Draft Initial definition.

Browser compatibility

FeatureChromeEdgeFirefoxInternet ExplorerOperaSafari
Basic support61 ?621 2 ?48 ?
FeatureAndroid webviewChrome for AndroidEdge mobileFirefox for AndroidOpera AndroidiOS SafariSamsung Internet
Basic support6161 ?621 248 ? ?

1. See bug 1470111 for enabling this by default.

2. From version 62: this feature is behind the dom.clearSiteData.enabled preference (needs to be set to true). To change preferences in Firefox, visit about:config.

See also

Document Tags and Contributors

Contributors to this page: fscholz
Last updated by: fscholz,