Cookie-Editor is a free, open-source browser extension that lets you create, edit, and delete the cookies of the current tab, aimed at web developers testing pages and privacy-conscious users who want manual control over what a site stores.

What it is

Cookie-Editor is a browser extension and add-on written in JavaScript and released under the GPL-3.0 licence. It presents a simple interface over the cookie store of the page you are visiting, so standard cookie operations can be performed quickly from a popup instead of through browser developer tools or hand-built scripts. The project lives in the browser-extension ecosystem and ships official builds for Google Chrome, Firefox, Safari, Microsoft Edge, and Opera, with a touch-optimised interface for Firefox for Android, Safari for iOS, and Edge on Android and iOS. It is distributed through the Chrome Web Store, the Firefox Add-ons site, the Apple App Store, the Microsoft Store, and the Opera Extensions site.

The concrete problem it solves is the friction of reading and mutating cookies while developing or testing a page. Creating a test cookie, changing an existing value, or clearing a messy session normally means digging through developer panels or writing throwaway console code. Cookie-Editor replaces that with direct manipulation: you create, edit, or delete a cookie for the current page, and a dedicated button mass-deletes every cookie for that page when you want a clean slate.

Key capabilities

• Create, edit, and delete cookies for the current tab through a single interface.
• Mass delete all cookies for the current page with one button.
• Official packages for Google Chrome, Firefox, Safari, Microsoft Edge, and Opera.
• Touchscreen-optimised interface for Firefox for Android, Safari for iOS, and Edge on Android and iOS.
• Safari builds for both Mac and iOS, tested on Mac, iPhone, and iPad.
• Build from source with npm install followed by the grunt command, which writes all output files to the dist directory.
• CI runs through a npm-grunt.yml GitHub Actions workflow with ESLint.

Who uses it and how

• Web developers debugging authentication, session, and consent behaviour on a page without leaving the browser.
• QA and support engineers who need to reproduce a first-visit state by mass-deleting cookies for a site.
• Privacy-minded individuals who inspect and remove cookies manually rather than trusting a site's own controls.
• Mobile testers working on Firefox for Android or Safari for iOS, where desktop developer tooling is not available.

Getting started

Install the packaged extension from the relevant store: Chrome Web Store, Firefox Add-ons, Apple App Store, Microsoft Store, or Opera Extensions. To build from source, run npm install, then run grunt; the finished files land in the dist directory. Safari requires building in Xcode, tested against Xcode 15.

How it compares

No competing or paid products are named in the available facts, so it stands alone in this registry. There is no subscription tier, no account, and no hosted service to compare against; the extension is GPL-3.0 and runs entirely in the browser.

When to use it — and when not to

Choose it when you need fast, manual cookie control in a supported browser and want an auditable, GPL-3.0 tool with no account. Avoid it if you need programmatic or automated cookie handling across many pages, or if you expect vendor support: the project is community-run, carries 69 open issues, and its README states it is not an official Google project, is not supported by Google, and that Google disclaims all warranties. Building from source also means operating Node, npm, and Grunt yourself, with Xcode 15 required for Safari targets.