About Cookie Editor

Cookie Editor (cookieeditor.net) exists for one job: to explain, clearly and completely, how to install and use the Cookie-Editor browser extension, and how browser cookies themselves work. If you have ever stared at a cookie list wondering which entry keeps you signed in, why a preference will not stick, or what a field like SameSite actually does, this site was written for you.

What you will find here

The site is organised around the questions people actually ask. The Installation & Setup guides walk through getting Cookie-Editor into Chrome, Firefox, Microsoft Edge, Safari on iPhone, iPad and Mac, and Firefox for Android, one browser at a time, including how to find the extension again after installing it. Using Cookie Editor covers the everyday work: viewing a site's cookies, editing a value and proving the edit worked, creating and deleting cookies, and moving a cookie set between browsers with import and export. Cookie Basics explains the ideas underneath, what cookies are, what every field means, and how session, persistent and third-party cookies differ. Troubleshooting collects the failures people hit most, a missing icon, an empty list, edits that revert after reload, permission blocks, with a fix for each. Privacy & Testing is about working safely: why a sign-in cookie is effectively a password, how to choose between editing, deleting and clearing, and how testers use the extension properly.

How these guides are researched

Every guide starts from the official sources: the extension's own store listings on the Chrome Web Store, Mozilla Add-ons, Microsoft Edge Add-ons, the Apple App Store and Opera Add-ons, and the project's public documentation and version history. Browser behaviour is checked against the browser makers' own help pages. Where sources disagree, or where a detail could not be confirmed, the guide says so rather than guessing. Steps are written for the current versions of the browsers and the extension, and screenshots in the guides are illustrations drawn with example data, never captures of anyone's real cookies.

The safe-examples rule

Every practical exercise on this site uses harmless examples, a theme or language preference on a page you control, and there is a reason for that discipline. A cookie that holds a sign-in session is a credential. Editing, copying or sharing one can hand someone else your account, and no tutorial is worth that risk. So the guides teach the full technique, view, edit, create, delete, import, export, on data where a mistake costs nothing, and they explain plainly which cookies to leave alone and why. If you follow the guides exactly as written, you will learn everything the tool does without ever putting a real session at risk.

About the extension itself

Cookie-Editor is a free, open-source browser extension created by Christophe Gagnier (Moustachauve) and contributors. It gives you a small panel, opened from the browser toolbar, that lists the cookies for the site you are viewing and lets you change them. This website documents that extension; the extension is developed and published by its own project, and every download on this site sends you to the project's official listing on the relevant browser store, where the store handles the installation. Nothing is downloaded from this website itself.

A note on names

Several unrelated products use similar names, and the guides are careful about the difference. This site covers Cookie-Editor, the open-source extension named above. Other extensions with look-alike names, including editors that appeared after the well-known EditThisCookie was removed from the stores, are different software by different publishers, and the EditThisCookie guide explains how to tell them apart and what to check before trusting any of them with cookie access.

Corrections and suggestions

Browsers change their menus, stores change their layouts, and the extension itself is updated from time to time, so a step can drift out of date even after careful checking. If you spot a step that no longer matches what your browser shows, or a topic you wish were covered, please say so through the contact page. Corrections are checked against the official sources and the guides are updated. Please never send cookie values, session data or passwords with a message; they are never needed to fix a guide.

How a guide is made

Each guide on this site goes through the same process, and it is worth describing because it explains both the site's strengths and its occasional gaps. First, the question is pinned down precisely: not 'cookies' in general, but the one job or failure a reader is facing. Second, the official sources are read, the store listing for each browser, the project's documentation and version history, and the browser makers' help pages, and the facts the guide will rely on are taken from those sources only. Third, the steps are written around a safe example that any reader can repeat without risking an account. Fourth, the finished guide is checked for the things readers trip on: profile differences, private windows, mobile browsers that behave differently, and steps that assume a menu in a place your browser moved last update. When a reader's correction arrives, it re-enters the same process at step two.

What this site deliberately does not do

Three absences are policy, not oversight. The site does not host or mirror the extension, because downloads belong on the official stores where versions, permissions and reviews are visible. It does not publish 'top ten tools' listicles or paid placements, because a documentation site that ranks its own subject for money stops being documentation. And it never demonstrates a technique on a real account, a real session, or a site the writer does not control, because the safe example always teaches the same skill. If you arrived here from a page that promised shortcuts around any of those, you were reading a different kind of site.

Who reads this site

Three kinds of reader shape everything published here. Everyday users arrive with a preference that will not stick or a sign-in that will not stay, and they need the shortest safe path to an answer. Developers and testers arrive with a state they must reproduce, an expiry to check, a consent flow to prove, and they need precision about fields, scopes and formats. And cautious users arrive with a safety question, about an extension that can read their sessions, and they deserve evidence and habits rather than reassurance. A guide that serves all three has to be plain without being shallow, and complete without being padded, which is the standard the word counts on this site are held to.