Download Cookie Editor for Your Browser and Learn to Manage Cookies

Find the extension for your browser, then follow setup and troubleshooting steps for managing cookies.

Download Cookie Editor
Cookie Editor illustration with sample theme and language preferences

Browser & Device Compatibility

Install Cookie Editor separately in each browser and profile where you want to use it. Check the table for the setup route that matches your device.

PlatformSupported BrowsersDevices
DesktopChrome, Firefox, Edge, Safari or OperaWindows, macOS or Linux, depending on browser
AndroidFirefox for AndroidAndroid phones and tablets
iPhone and iPadSafari extension setupiPhone and iPad

Download the Cookie Editor Extension

Choose the store that matches your browser. Follow the store’s installation prompt.

Installation steps

Choose Add to Chrome, review the prompt and open Cookie Editor from the Extensions menu.

Installation steps

Choose Add to Firefox, confirm the prompt and open the add-on from the Extensions menu.

Installation steps

Get the app, then open Safari Settings and enable Cookie-Editor under Extensions.

Installation steps

Choose Add to Opera and check the extension manager if the toolbar icon is missing.

Firefox Add-ons for Android

Watch the installation walkthrough

Hear how to choose a browser store, confirm installation and find Cookie Editor in your extensions menu. The install prompt can look different in your browser.

Walkthrough transcript
  1. Choose the browser you use.
  2. Open the store listing and confirm the install prompt.
  3. Open the browser’s extensions menu and select Cookie Editor.

Cookie Editor on Android

Start with Firefox for Android. Open its add-ons menu or the Mozilla listing from inside Firefox and check whether the installation option is available on your device. After installing, open the site you want to inspect and find Cookie-Editor through the browser’s extensions menu. If the option is missing, confirm which browser is handling the store link before you try again.

Cookie Editor on iPhone & iPad

Open the Apple App Store listing on your device, then enable Cookie-Editor in Safari’s Extensions settings after installing it. Open Safari and try it on a page you control. If Safari asks for permission to read the site, check the domain shown in the prompt. Depending on your software version, Safari settings may be grouped under Apps in the Settings app.

Extension Permissions Explained

Cookie Editor uses browser permissions to read and change cookies. Review the install prompt and check which websites the extension can access in your browser settings.

Permissions and data checks
What to checkWhy it mattersWhat to do
Cookie accessViewing and editing cookies requires browser permission.Read the permissions on the browser’s install prompt before proceeding.
Site accessA site restriction can prevent Cookie Editor from reading the active tab’s cookies.Check the extension’s site access settings and start with a page you control.
Values shown on screenSome cookie values may contain private sign-in information.Keep these values out of screenshots, shared files and support requests.
What can I share when asking for help?

Share your browser name, extension version, the steps you followed and the result. If you include a screenshot, use a test cookie such as a theme preference.

Your First Minute With Cookie Editor

Open a test page that you own after installing the extension. Click the extension icon and look for a familiar cookie name such as theme or language. Click the entry to inspect its details. Start by reading a value so you can see how the panel is organized before you make a change. If you want to record what you found, write down the preference name and the result you observed.

Illustration of pinning the extension in a browser toolbar

Inside the Cookie Editor Interface

The search field helps narrow a long list when you already know part of a cookie name. The main list shows cookies for the active tab. Open an entry to see the available fields and controls for that cookie. The illustration uses example data to explain these parts. Your popup can vary by browser and extension version.

If a search returns no results, clear it first and check the unfiltered list. Then narrow the list using part of the preference name. The demo panel here illustrates the parts of the interface, while exact control placement may differ in the version you installed.

Illustrated search field, cookie list and edit controls with sample data
Illustration with example preferences.

How to Read Cookie Details

The name identifies the setting and the value stores its current state. For example, a cookie named theme might contain the value light. Domain and path help determine where the cookie applies. An expiration date indicates when the browser is expected to discard it. Check the domain and path when two entries have the same name. They can refer to different parts of a site.

Use the expiry field to investigate why a preference disappears after a while. If a cookie is still present after a page reload, the site may have written a fresh copy. Compare the name, value and expiry before and after the reload to see what changed.

Nametheme
Valuelight
Domainexample.com
Path/

Create, Edit & Delete a Test Cookie

On a test page you control, try changing a harmless display preference such as theme from light to dark. Save the change and reload the test page to see whether the site reads the new value. To practice deleting, remove a temporary preference you created for the test. A page may restore its default setting or set a new cookie when it reloads. Record what happened so you can tell a saved edit from a change the page made later.

Illustration of changing a test preference from light to dark

Create a Temporary Preference

Create a separate test cookie on a page you control. Use a name you’ll recognize so you can find and remove it later.

  1. Open the test page

    Open Cookie Editor in the same tab. Before adding anything, search for demo_theme so you know whether the name is already in use.

  2. Enter and save a test value

    Use demo_theme for the name and light for the value. Check that the domain and path apply to your test page before saving.

  3. Verify the new entry

    Search again for the exact name. Reopen the extension after a reload and compare the saved value and path with what you entered.

Remove the Preference After Testing

Remove the temporary cookie by name after checking that its domain and path match the record you created.

  1. Find the exact entry

    In your test tab, search for demo_theme. If more than one entry appears, use the domain and path to identify yours.

  2. Delete it and check the result

    Delete that entry, reload the page and reopen Cookie Editor. Search again for the same name.

  3. Notice what the page does next

    If the entry is gone, the cleanup is complete. If the site writes it again, compare the new value and expiry before deciding what to test next.

Why did it come back after I deleted it?

A site can save a default preference when you reload it. Check whether the same name appears again only after loading the page.

Import & Export Formats

The extension offers formats such as JSON, Netscape and an HTTP header string. Choose the format expected by the application that will read your sample data. Test with a single dummy preference file first and inspect it before using it again. Keep actual sign-in cookies private and use sample entries when demonstrating an import or export.

JSON is often convenient when you want to review structured sample data. Select Netscape format when a tool explicitly says it expects that format. Keep the format name in your test notes so you can repeat the same check if a parser rejects the file.

Illustration of a sample file moving between a browser and local storage

Use the Right Browser Profile

Open Cookie Editor in the same browser profile as the tab you want to inspect. Work, personal and guest windows can have separate extensions and cookie data, even when they display the same address.

Which profile should you check?
SituationWhere to look
Cookie Editor appears in another windowCompare the profile names or avatars on both windows. Enable or install the extension in the profile you actually use for testing.
The same site shows a different valueCompare the same site, profile, and cookie name. A preference saved in a personal profile can differ from the one saved in a work profile.
The extension is missing in a private windowCheck whether your browser allows it in private windows. Use a normal window for your first test.

Common Cookie Editor Issues and Fixes

Find the symptom you’re seeing, then follow the checks in its box.

The extension icon is missing

What’s happening
Cookie Editor was installed, but its icon is hidden in the extensions menu or the extension is disabled in this profile.
How to fix it
Open the browser’s extensions menu. If Cookie Editor is listed, open it there or pin it when your browser offers that option. Otherwise, check the extension manager for its enabled status.

The cookie list is empty

What’s happening
The active tab may be on a different site, the page may not have saved a cookie yet, or a search term may be hiding the entries.
How to fix it
Confirm the active tab and clear the search field. Reload your test page and reopen Cookie Editor. If the list is still empty, check site access in your browser settings.

A cookie edit reverts after reload

What’s happening
The website may write a new value as the page loads. Cookies with the same name can also have different domains or paths.
How to fix it
Compare the cookie’s name, domain, path and value before and after refreshing. Test one preference at a time so you can identify what changed.

Cookie Editor opens in one profile only

What’s happening
Browser profiles can have different extensions installed and their own cookie stores. A personal tab and a work tab may open the same page with different settings.
How to fix it
Switch to the profile you want to inspect, check that Cookie Editor is enabled there and open your test page again.

The extension does not open on mobile

What’s happening
You may be using an in-app browser, or the extension may still need to be enabled in your mobile browser.
How to fix it
Open your test page directly in a supported browser. Check the extensions menu in Firefox for Android or Safari’s Extensions settings on iPhone or iPad.

Update or Remove Cookie Editor

Use your browser’s extension manager to check the installed version, pause Cookie Editor or remove it from the profile you’re using.

  1. Check the installed version

    Open the extension manager, select Cookie Editor and note the version. If an update option is available, follow your browser’s prompts.

  2. Disable it for a quick comparison

    Turn the extension off, then reload your test page to see whether the behavior changes. Enable it again when you finish.

  3. Remove it from the browser

    Choose Remove in the extension manager and confirm. Repeat this in any additional profiles where the extension is installed.

Does removing Cookie Editor clear my website cookies?

Removing the extension removes its toolbar controls. To clear cookies stored for a site, use that browser’s site data controls.

Check the Extension After Mobile Setup

Open a test page directly in the supported browser where you enabled Cookie Editor. Start with a page you control that saves a simple preference such as a theme.

  1. Confirm that the browser offers the extension

    On Firefox for Android, check the extensions menu. On an iPhone or iPad, check Safari’s extension settings and open the page in Safari.

  2. Open Cookie Editor from the test tab

    Let the page finish loading, then open the extension so you can see the cookies for that tab.

  3. Look up your test preference

    Clear any search filter and look for the name of the preference you saved. If none appears, check the site’s permission and confirm the test page has actually saved a cookie.

Why is the extension missing when I tap a link in another app?

The link may be opening in that app’s browser view. Open the same address in your supported browser and check its extensions menu again.

Choose a Cookie for a Practice Run

Choose a preference that controls something visible on a page you own. A theme or language setting makes it easy to compare the cookie value with what the page actually shows.

Example practice choices
Cookie typeWhat to check
Display themeSwitch the theme through the test page and see whether an example value changes from light to dark.
Page languageSelect a language on a test page that supports it, then compare the visible language with the saved preference.
Sign-in or checkout dataLeave it alone during practice. Choose a display preference so you can repeat the test without changing account state.

Frequently Asked Questions

Do I install Cookie Editor separately in each browser?

Yes. Use the store that matches each browser where you want to use the extension.

Is Cookie Editor a standalone desktop app?

It is a browser extension. On Apple devices the App Store provides the app used to enable the Safari extension.

Can Cookie Editor manage cookies from another browser?

Open the extension in the browser and profile where the cookies you want to inspect are stored.

Why do I see different cookies on different websites?

Cookie Editor works with the active page. Change tabs or visit the relevant site before opening the extension.

Does Cookie Editor show cookies from every tab?

Open the extension from the tab you want to inspect. The cookie list reflects the active page, so it can change as you switch tabs or navigate to another website.