What Is ~/Library/Cookies on Mac?
Your user folderUpdated
- Full path
~/Library/Cookies
- Scope
- Your user folderInside your home folder — one copy per user account.
- Freshist & this folder
- Freshist checks this folder when uninstalling an app. When you uninstall an app, Freshist looks here for items that belong to it. Matches on the app's bundle ID can be pre-selected; name-only guesses are labeled “not sure” and never pre-selected. Removed items go to the Trash, so you can undo.
From Freshist's own cleaning rules — the same catalog the app uses.
What a cookie file is
Websites store small pieces of data, called cookies, to remember that you're signed in, what's in your cart or which settings you chose. Apple's networking stack saves them on disk in a binary format with the extension .binarycookies. Apple's file system guide lists ~/Library/Cookies as the folder that "contains data files with web browser cookies."
Over the years, Apple has moved where cookies land. Current versions of Safari keep their main cookie store inside Safari's own container, under ~/Library/Containers/com.apple.Safari/Data/Library/Cookies, and many apps now write cookie files into ~/Library/HTTPStorages. ~/Library/Cookies still exists and can still hold cookie files and related data, such as settings for sites that require secure connections, depending on your macOS version and the apps you've used.
Why it's protected
Cookies can contain live session tokens: anyone who copies them may be able to act as you on a website. macOS therefore blocks apps from reading this folder unless you've given them Full Disk Access. Try ls ~/Library/Cookies from a Terminal without that permission and you get "Operation not permitted."
What deleting it does
| You remove | Result |
|---|---|
| Safari cookies | Signed out of websites, consent banners return, site preferences reset |
An app's .binarycookies file | That app's web sessions end; you sign in again |
| The folder contents in general | Very little space back, usually a few megabytes at most |
Nothing here is a document or a setting of macOS itself. The cost is convenience, and the gain in space is negligible, so there's rarely a storage reason to clear it.
The right way to clear cookies
For Safari, use the app. Apple's steps:
- Open Safari and choose Safari → Settings, then click Privacy.
- Click Manage Website Data.
- Select sites and click Remove, or click Remove All.
Apple notes that removing website data in Safari may also change or remove it in other apps, since they share the same underlying storage. For other browsers, use their own "clear browsing data" options.
Checking it read-only
If you've given Terminal Full Disk Access, this shows size and file names without changing anything:
du -sh ~/Library/Cookies
ls -la ~/Library/Cookies
When uninstalling an app
An uninstalled app may leave a cookie file named after its bundle ID here or in HTTPStorages. Removing it is harmless; the app isn't there to use it. Don't remove Cookies.binarycookies or files with com.apple. names to tidy up, since those belong to Safari and macOS services you still use. For a broader look at what Mac apps leave behind, see the complete uninstall guide.
Sources
- Clear your cache and cookies in Safari on Mac, Apple Support
- macOS Library Directory Details, Apple File System Programming Guide
- HTTPCookieStorage, Apple Developer Documentation
Frequently asked questions
Are my Chrome or Firefox cookies in ~/Library/Cookies?
No. Chrome, Firefox and other browsers with their own engines keep cookies inside their profile folders in ~/Library/Application Support and clear them from their own privacy settings.
Why does Terminal say 'Operation not permitted' for ~/Library/Cookies?
macOS protects this folder. Apps, including Terminal, need Full Disk Access to read it. That protection exists because cookies can hold active sign-in sessions.
Will deleting cookie files remove saved passwords?
No. Passwords live in iCloud Keychain and the Passwords app, not in cookie files. You'll stay able to sign back in; you just won't be signed in automatically.