Cookie Inspector for Safari
Manage and edit cookies
About
This Safari extension allows you to view, search, edit, create, and export cookies for the current website. It offers a privacy-first design with a user-friendly interface for seamless integration into your browsing workflow.
What's New in Cookie Inspector for Safari
1.0.3
May 28, 2026
Bug fixes and performance improvements.
Developer apps
FAQ
What is Cookie Inspector for Safari?
Cookie Inspector for Safari is a Safari Extension designed to help users view, manage, and edit cookies for the website they are currently visiting. It allows for searching, deleting, creating, and exporting cookies directly within Safari.
How much does Cookie Inspector for Safari cost?
Cookie Inspector for Safari is a paid application priced at $2.99. There are no in-app purchases or advertisements associated with this extension.
Does Cookie Inspector for Safari have ads?
No, Cookie Inspector for Safari is ad-free. The developer has stated a privacy-first design, ensuring no data collection, tracking, or logging, and the extension does not contain advertisements.
What devices is Cookie Inspector for Safari compatible with?
Cookie Inspector for Safari is compatible with macOS, iPhone, iPad, and iPod devices. It seamlessly integrates into the Safari browser across these Apple platforms.
How often is Cookie Inspector for Safari updated?
The latest version, 1.0.3, was released on May 28, 2026, indicating recent development activity. The initial release date was May 14, 2026.
Can I export cookies from Cookie Inspector for Safari?
Yes, you can export all cookies from the current site in a structured JSON file. This feature is useful for debugging, analysis, or backup purposes.
What is the age rating for Cookie Inspector for Safari?
Cookie Inspector for Safari has an age rating of 4+. This indicates it is suitable for users of all ages, with no content restrictions.
Are there any limitations to Cookie Inspector for Safari?
Some cookies, particularly certain HttpOnly cookies, may not appear. This is due to Safari's restrictions on extension access to protected cookie data.