Installation & Setup Cookie Editor guide

Cookie Editor on Android: Firefox Setup Guide

On Android, Cookie Editor runs inside Firefox. Here is how to install it, find it in the menu, and test it on a real page.

Illustration of using Cookie Editor inside Firefox on an Android phone

There is no Cookie Editor app in the Play Store, and Chrome for Android cannot run extensions at all. On Android, Cookie-Editor works inside Firefox for Android, Mozilla's version history confirms the add-on supports Android (Firefox 120.0 and later). The setup takes a couple of minutes, and the panel then behaves like the desktop version, just in a phone-sized menu.

  1. Install or update Firefox for Android

    Get Firefox from Google Play and update it to the latest version, so the add-on support is current.

  2. Open Add-ons inside Firefox

    Tap the three-dot menu in Firefox, choose Add-ons (or Extensions, depending on version), and browse the recommended list, or open the Cookie-Editor listing on Mozilla Add-ons from inside Firefox using the link in the homepage downloads.

  3. Add Cookie-Editor

    Tap the + button or Add, and confirm the permission prompt. Firefox installs the add-on into this browser only.

  4. Find it again later

    Cookie-Editor does not add a home-screen icon. Open Firefox's menu and look under Add-ons / Extensions to launch it while a page is open.

Test it on a mobile page

Open a site you control in Firefox, change a visible preference such as the theme, then open the menu and launch Cookie-Editor. The list shows the cookies for the current tab. Tap an entry to see its value, domain, path and expiry. Mobile panels are narrow, so long values may wrap, that is normal.

When the install option is missing

If Cookie-Editor does not appear in the add-on list, the usual causes are an outdated Firefox build, opening the Mozilla link in a different browser (Chrome or an in-app viewer cannot install it), or a device where Firefox offers a limited add-on catalogue. Update Firefox, open the link from inside Firefox itself, and try again. The homepage's Android section summarises the same checks.

How the Android panel differs from desktop

The panel itself works the same way, you will see the same cookie list, the same fields, and the same create, edit and delete controls, but three things differ on a phone. First, there is no toolbar to pin to: Cookie-Editor always lives in Firefox's menu, under Add-ons. Second, the narrow screen truncates long values, so tap an entry open rather than judging it from the list row. Third, Firefox for Android uses the same cookie store for every tab in the browser, there are no separate Android profiles like desktop, so the personal-versus-work profile trap from desktop does not apply here; private tabs, however, keep their own temporary store.

Testing on mobile like you mean it

Because cookies do not sync between your phone and your computer, a preference that works on desktop can still be missing or different on mobile, and sites know it. When you test, change the preference inside Firefox for Android itself, then read the cookie in the same browser. If your site offers an app, remember the app has its own storage entirely: nothing you see in Firefox tells you anything about the app's state. For a page that behaves differently in Firefox's menu-opened panel than on the live page, reload the tab once after installing the add-on, older page loads can predate the installation.

A realistic first test on your phone

Pick a site you use that has an obvious preference, a news site with a light and dark theme is ideal. Set the theme in Firefox for Android, then open the menu, tap Add-ons, then Cookie-Editor, and find the preference in the list. Change nothing yet; just confirm the name and value match what the site shows. That single loop, set a preference, read it back in the panel, is the whole foundation of mobile cookie work, and every later edit is a variation of it.

Three limits are worth knowing before you need them. It cannot see cookies belonging to other apps, including the same site opened in its own app; app storage is walled off by Android. It cannot run in Chrome for Android at all, because that browser has no extension system. And it cannot inspect a page open in another browser, each browser's store is its own. None of these are faults in the add-on; they are the shape of mobile platforms, and knowing them stops you hunting for a setting that does not exist.

Battery, data and other phone practicalities

Cookie-Editor itself is light: it does nothing until you open it, so it has no meaningful effect on battery or data. The practical phone issues are ergonomic instead. Long cookie values are hard to compare on a small screen, so for detailed work, export the set and read it on a computer, keeping the file private and deleting it afterwards. And if you test on a phone that also holds your real accounts, prefer a separate Firefox installation habit: test in a tab you can close, on sites where a mistake costs nothing.

Frequently Asked Questions

Will my desktop cookies appear on my phone?

No. Cookies live in each browser on each device. Firefox Sync does not copy site cookies to your phone, so test preferences separately on mobile.

Does Cookie-Editor work in other Android browsers?

A few Chromium-based Android browsers experiment with extension support, but the documented, supported route for Cookie-Editor is Firefox for Android. Stick to that for predictable results.