Cookie Editor on iPhone, iPad and Safari (macOS)
Safari gets Cookie-Editor through an App Store app that you then switch on in Safari's settings. Full steps for Mac, iPhone and iPad.
Safari is the one browser where Cookie-Editor arrives as an app first. You download the Cookie-Editor app from the Apple App Store, then switch the extension on inside Safari's settings. Until you enable it, Safari will not show the extension anywhere, that single extra step is responsible for most “I installed it but it's missing” reports on Apple devices.
Enable Cookie-Editor in Safari on macOS
- Get the app
Open the Apple App Store listing for Cookie-Editor (linked from the homepage downloads) and click Get.
- Open Safari Settings
In Safari, open Settings (or Preferences on older macOS) and go to the Extensions tab.
- Tick Cookie-Editor
Select Cookie-Editor in the list and tick it to enable the extension. Safari may ask which websites it can access, start with the sites you test.
- Find the toolbar icon
The Cookie Editor icon appears in Safari's toolbar. If it is hidden, right-click the toolbar and customise it to add the icon.
Enable Cookie-Editor on iPhone and iPad
- Install the app from the App Store
Download Cookie-Editor on the device itself so the extension registers with that device's Safari.
- Open Settings and find Safari
On recent iOS versions, Safari's settings sit under Settings → Apps → Safari; on older versions, under Settings → Safari. Open Extensions.
- Turn Cookie-Editor on
Tap Cookie-Editor and switch it on. Review the “Allow on these websites” options and grant access to the site you want to inspect.
- Open Safari and test
Visit a page you control in Safari, tap the puzzle / extensions control in the address bar, and open Cookie-Editor.
About Safari's site permission prompts
Safari asks per-site permission more often than other browsers. If the panel opens but shows nothing, the site probably has not been granted yet: check the extension's website access list in Safari settings and allow the domain you are testing. The permissions guide explains how each browser phrases this.
Safari profiles and private browsing
Safari on macOS supports profiles (work, personal and so on), and extensions are enabled per profile: if Cookie-Editor shows in one Safari window and not another, open Settings, then Profiles, and check the Extensions list for the profile you are using. Private Browsing windows add a second wrinkle: a private window's cookies are temporary and separate, so a preference you set in a normal window will not appear there, and anything you inspect in a private window disappears when the window closes. Test in a normal window first, then repeat in private if that is the behaviour you care about.
Keeping macOS and iOS in step
Installing the app on your Mac does not enable anything on your iPhone, and the reverse is also true, each device's Safari has its own extension switch and its own cookie store. If you are comparing behaviour across devices, enable the extension and run the same preference test separately on each, and compare the cookie's name, value and expiry rather than assuming the phone copied the Mac. iCloud syncs your Safari history and open tabs; it does not sync site cookies between devices.
What you should see when it works
On the Mac, a working setup shows Cookie-Editor listed under Safari Settings, then Extensions, ticked on, and its icon available in the toolbar or the extensions area of the toolbar. On iPhone and iPad, Settings, then Safari, then Extensions shows it switched on, and Safari's address-bar menu offers it on a page. In both cases the real proof is the same: open a page that saves a preference, open Cookie-Editor, and see that preference listed. Until that loop works, keep fixing the setup; after it works, the usage guides apply exactly as written.
Per-website permission prompts
Safari may ask, the first time you open the extension on a site, whether it may access that site, with choices like allowing it for a day or always. This is Safari's own gate, not an error. For a test page you control, allowing access is the point of the tool. For sites you did not mean to inspect, deny it and move on; the prompt will simply appear again if you open the extension there later. If the panel ever seems empty on one site but fine elsewhere, a denied prompt in the past is the first thing to check.
When the extension is missing from Safari entirely
If Cookie-Editor does not appear in Safari's Extensions list at all, the app side is the problem, not Safari. Open the Cookie-Editor app itself once, some builds finish their setup there, then look again. Confirm the app is installed under the same Apple ID and, on a Mac, that you are checking the profile you actually browse in. Deleting and reinstalling the app is safe: it holds no cookies of yours, so nothing about your websites changes.
| Check | What confirms it |
|---|---|
| App installed | Cookie-Editor app present on the device |
| Extension on | Ticked or switched on in Safari's Extensions settings |
| Permission granted | The extension opens on your test page without a blocking prompt |
| First test passed | A theme or language preference appears with the expected value |
Frequently Asked Questions
Does Cookie-Editor work in Chrome on iPhone?
No. All iPhone browsers are built on Apple's WebKit, and Cookie-Editor's iOS build is a Safari extension. Use Safari on iPhone and iPad.
I enabled it but the panel is empty. What now?
Check the per-site permission for the page you are on, reload the page, and make sure the site actually saves a cookie, change a theme or language preference first.


