[{"data":1,"prerenderedAt":45},["ShallowReactive",2],{"blog-en-clear-cache-on-mac":3},{"meta":4,"html":13,"headings":14,"raw":44},{"title":5,"description":6,"topic":7,"date":8,"author":9,"icons":10},"How to Clear Cache on Mac: What's Safe to Delete and What Isn't","Caches can be rebuilt, but they sit next to sign-ins, chat history and offline downloads. Tell them apart, then clear caches in apps, the Finder or WashBear.","mac-cleanup","2026-10-29","WashBear Team",[11,12],"deep-cleanup","scrub-brush","\u003Cp>A cache is data an app keeps so it doesn't have to repeat work: images and scripts from web pages, video thumbnails, compiled graphics shaders, installers it has already downloaded. What makes it a cache is that it can be recreated after you delete it, and Apple describes the \u003Ccode>Caches\u003C\u002Fcode> folder as the place for exactly that kind of discardable, re-creatable data.\u003C\u002Fp>\n\u003Cp>The catch is that caches often sit right next to data you shouldn't delete casually. One app's folder can hold several gigabytes of cache alongside your chat history and offline downloads. Before you clear anything, it helps to know which is which.\u003C\u002Fp>\n\u003Ch2 id=\"where-caches-live\">\u003Ca class=\"heading-anchor\" href=\"#where-caches-live\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>Where caches live on a Mac\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ccode>~\u002FLibrary\u002FCaches\u003C\u002Fcode>: app caches for your user account. Most apps create a folder here named after the app or its identifier, such as \u003Ccode>com.apple.Safari\u003C\u002Fcode> for Safari.\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002FLibrary\u002FCaches\u003C\u002Fcode>: caches shared by all users; changing them requires an administrator password.\u003C\u002Fli>\n\u003Cli>\u003Ccode>~\u002FLibrary\u002FContainers\u002F<app identifier>\u002FData\u002FLibrary\u002FCaches\u003C\u002Fcode>: apps from the App Store run in a sandbox and keep their caches inside their own container.\u003C\u002Fli>\n\u003Cli>Browser profile folders: besides \u003Ccode>~\u002FLibrary\u002FCaches\u003C\u002Fcode>, Chrome and similar browsers keep code and GPU caches in their profile folders under \u003Ccode>~\u002FLibrary\u002FApplication Support\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fprivate\u002Fvar\u002Ffolders\u003C\u002Fcode>: per-user temporary files and caches that macOS manages itself.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"safe-vs-risky\">\u003Ca class=\"heading-anchor\" href=\"#safe-vs-risky\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>What's safe to delete and what isn't\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Usually safe to delete\u003C\u002Fstrong>, because apps rebuild them as needed:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>browser web, code and GPU caches;\u003C\u002Fli>\n\u003Cli>the contents of app folders inside \u003Ccode>~\u002FLibrary\u002FCaches\u003C\u002Fcode>;\u003C\u002Fli>\n\u003Cli>preview thumbnails generated by Quick Look;\u003C\u002Fli>\n\u003Cli>download caches from tools such as npm, Homebrew and pip, and Xcode's build cache.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Think before deleting\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Cookies and website data\u003C\u002Fstrong> aren't just cache. Removing them usually signs you out of websites.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Offline downloads\u003C\u002Fstrong>: music and videos saved by streaming apps have to be downloaded again.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Cache folders you don't recognize\u003C\u002Fstrong>: find out which app they belong to first. A running app's cache may refuse to delete or come right back.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Leave alone\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>the whole \u003Ccode>~\u002FLibrary\u003C\u002Fcode>, \u003Ccode>~\u002FLibrary\u002FApplication Support\u003C\u002Fcode> or \u003Ccode>~\u002FLibrary\u002FContainers\u003C\u002Fcode> folder, which hold settings, databases and chat history;\u003C\u002Fli>\n\u003Cli>system locations such as \u003Ccode>\u002FSystem\u003C\u002Fcode>, \u003Ccode>\u002Fprivate\u002Fvar\u002Fdb\u003C\u002Fcode> and \u003Ccode>\u002Fprivate\u002Fvar\u002Fvm\u003C\u002Fcode>;\u003C\u002Fli>\n\u003Cli>files inside your Photos library; let the Photos app manage it.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"in-app\">\u003Ca class=\"heading-anchor\" href=\"#in-app\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>Clear caches from inside the app\u003C\u002Fh2>\n\u003Cp>If you only want to clear one app, look in its own settings first. The app knows best which data is cache and which is yours.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Safari\u003C\u002Fstrong>: choose Safari > Settings, click Privacy, then click Manage Website Data. You can remove data for individual websites or click Remove All. Apple notes that this removes cookies and website data, so it may sign you out of websites.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Chrome\u003C\u002Fstrong>: click the More icon in the upper right, choose Delete browsing data, set the time range to All time, select only Cached images and files, then click Delete data. To stay signed in, leave cookies unselected.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Messaging and office apps\u003C\u002Fstrong>: many offer an option in their settings to clear the cache or manage storage. Use it when it's there. See our guides to \u003Ca href=\"\u002Fen\u002Fblog\u002Fwechat-mac-storage\">WeChat\u003C\u002Fa> and \u003Ca href=\"\u002Fen\u002Fblog\u002Foffice-chat-apps-cache-mac\">DingTalk, Lark and WeCom\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Developers can clear download caches with the tools' own commands; for pnpm, Yarn and more, see \u003Ca href=\"\u002Fen\u002Fblog\u002Fclear-js-package-caches\">how to clear npm, pnpm and Yarn caches\u003C\u002Fa>:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">brew cleanup\nnpm cache clean --force\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Xcode's build cache lives in \u003Ccode>~\u002FLibrary\u002FDeveloper\u002FXcode\u002FDerivedData\u003C\u002Fcode>. Quit Xcode before deleting it; the next build will take longer. For simulators and device support files, see our \u003Ca href=\"\u002Fen\u002Fblog\u002Fclear-xcode-storage\">Xcode guide\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"finder\">\u003Ca class=\"heading-anchor\" href=\"#finder\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>Clear caches by hand in the Finder\u003C\u002Fh2>\n\u003Col>\n\u003Cli>Quit the app you want to clean.\u003C\u002Fli>\n\u003Cli>In the Finder, choose Go > Go to Folder, type \u003Ccode>~\u002FLibrary\u002FCaches\u003C\u002Fcode> and press Return.\u003C\u002Fli>\n\u003Cli>In list view, select "Calculate all sizes" (View > Show View Options), then sort by size.\u003C\u002Fli>\n\u003Cli>Open the largest app folder and drag its contents to the Trash, keeping the folder itself.\u003C\u002Fli>\n\u003Cli>Once you've confirmed the app still works properly, empty the Trash.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>To see how big each cache folder is first, you can also run this in Terminal:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">du -sh ~\u002FLibrary\u002FCaches\u002F* 2>\u002Fdev\u002Fnull | sort -h | tail -n 20\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>One advantage of deleting by hand is that files go to the Trash first, so you can put them back until you empty it.\u003C\u002Fp>\n\u003Ch2 id=\"washbear\">\u003Ca class=\"heading-anchor\" href=\"#washbear\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>Clear caches in one place with WashBear\u003C\u002Fh2>\n\u003C!--demo:deepClean-->\u003Cp>Comparing caches across many apps folder by folder takes a while. Open \u003Cstrong>Deep Cleanup\u003C\u002Fstrong> and click \u003Cstrong>Start Scan\u003C\u002Fstrong>. WashBear groups the results into categories such as \u003Cstrong>System caches\u003C\u002Fstrong>, \u003Cstrong>User cache files\u003C\u002Fstrong>, \u003Cstrong>Application caches\u003C\u002Fstrong>, \u003Cstrong>Browser data\u003C\u002Fstrong> and \u003Cstrong>Developer tools\u003C\u002Fstrong>, and shows the size of each item.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Read before you select\u003C\u002Fstrong>: expand an item to see what it is, how cleaning affects you and its exact locations. The Chrome cache item, for example, states that passwords, cookies, history, extensions and bookmarks are kept.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Caches only\u003C\u002Fstrong>: switch \u003Cstrong>Selection\u003C\u002Fstrong> at the bottom to \u003Cstrong>Select none\u003C\u002Fstrong>, then select the caches you want. You can also start from \u003Cstrong>Smart recommendation\u003C\u002Fstrong>, which preselects only lower-risk items that can usually be recreated.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Apps that must close\u003C\u002Fstrong>: some items show \u003Cstrong>Close the app before cleanup\u003C\u002Fstrong>. After you click \u003Cstrong>Clean\u003C\u002Fstrong>, select those apps under \u003Cstrong>Close running apps (optional)\u003C\u002Fstrong> in \u003Cstrong>Confirm cleanup\u003C\u002Fstrong>, and WashBear closes them first. Save your work before you do.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Additional user caches\u003C\u002Fstrong>: app caches that aren't listed separately are not selected by default, and caches in use are skipped. Expand the item to see which apps they belong to before selecting it.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Safari's cache can be cleared on its own as \u003Cstrong>Browser cache\u003C\u002Fstrong> in \u003Cstrong>Privacy Cleanup\u003C\u002Fstrong>. Smart recommendation there also selects records such as browsing history, so if you only want the cache, switch to \u003Cstrong>Select none\u003C\u002Fstrong> first and select it by itself. Cookies and website data are in Privacy Cleanup too; if your selection could sign you out, you have to tick an acknowledgment before you can confirm.\u003C\u002Fp>\n\u003Cdiv class=\"callout callout-warning\">\u003Cp class=\"callout-title\">Warning\u003C\u002Fp>\u003Cp>Files cleaned by WashBear don't go to the Trash and can't be recovered. The items and results of every cleanup are recorded in \u003Cstrong>Operation History\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003Ch2 id=\"faq\">\u003Ca class=\"heading-anchor\" href=\"#faq\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>Frequently asked questions\u003C\u002Fh2>\n\u003Ch3 id=\"sign-out\">\u003Ca class=\"heading-anchor\" href=\"#sign-out\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>Will clearing the cache sign me out?\u003C\u002Fh3>\n\u003Cp>Clearing the cache alone usually won't. Sign-ins are stored in cookies and website data, which are a different thing. When you clean up in a browser, make sure you don't select cookies along the way.\u003C\u002Fp>\n\u003Ch3 id=\"faster\">\u003Ca class=\"heading-anchor\" href=\"#faster\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>Will my Mac be faster after clearing caches?\u003C\u002Fh3>\n\u003Cp>Not necessarily. Caches exist to make things load faster, so right after you clear them, apps and web pages have to download and rebuild that data, and the first load is slower. Clearing caches mainly frees space, or helps rule out a problem when an app misbehaves.\u003C\u002Fp>\n\u003Ch3 id=\"how-often\">\u003Ca class=\"heading-anchor\" href=\"#how-often\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>How often should I clear caches?\u003C\u002Fh3>\n\u003Cp>There's no need to clear them on a schedule. Caches grow back as you use your apps, which is normal. Clear them when space is tight, or when one app's cache has grown unusually large.\u003C\u002Fp>\n",[15,19,22,25,28,31,34,38,41],{"depth":16,"id":17,"text":18},2,"where-caches-live","Where caches live on a Mac",{"depth":16,"id":20,"text":21},"safe-vs-risky","What's safe to delete and what isn't",{"depth":16,"id":23,"text":24},"in-app","Clear caches from inside the app",{"depth":16,"id":26,"text":27},"finder","Clear caches by hand in the Finder",{"depth":16,"id":29,"text":30},"washbear","Clear caches in one place with WashBear",{"depth":16,"id":32,"text":33},"faq","Frequently asked questions",{"depth":35,"id":36,"text":37},3,"sign-out","Will clearing the cache sign me out?",{"depth":35,"id":39,"text":40},"faster","Will my Mac be faster after clearing caches?",{"depth":35,"id":42,"text":43},"how-often","How often should I clear caches?","\nA cache is data an app keeps so it doesn't have to repeat work: images and scripts from web pages, video thumbnails, compiled graphics shaders, installers it has already downloaded. What makes it a cache is that it can be recreated after you delete it, and Apple describes the `Caches` folder as the place for exactly that kind of discardable, re-creatable data.\n\nThe catch is that caches often sit right next to data you shouldn't delete casually. One app's folder can hold several gigabytes of cache alongside your chat history and offline downloads. Before you clear anything, it helps to know which is which.\n\n## Where caches live on a Mac {#where-caches-live}\n\n- `~\u002FLibrary\u002FCaches`: app caches for your user account. Most apps create a folder here named after the app or its identifier, such as `com.apple.Safari` for Safari.\n- `\u002FLibrary\u002FCaches`: caches shared by all users; changing them requires an administrator password.\n- `~\u002FLibrary\u002FContainers\u002F\u003Capp identifier>\u002FData\u002FLibrary\u002FCaches`: apps from the App Store run in a sandbox and keep their caches inside their own container.\n- Browser profile folders: besides `~\u002FLibrary\u002FCaches`, Chrome and similar browsers keep code and GPU caches in their profile folders under `~\u002FLibrary\u002FApplication Support`.\n- `\u002Fprivate\u002Fvar\u002Ffolders`: per-user temporary files and caches that macOS manages itself.\n\n## What's safe to delete and what isn't {#safe-vs-risky}\n\n**Usually safe to delete**, because apps rebuild them as needed:\n\n- browser web, code and GPU caches;\n- the contents of app folders inside `~\u002FLibrary\u002FCaches`;\n- preview thumbnails generated by Quick Look;\n- download caches from tools such as npm, Homebrew and pip, and Xcode's build cache.\n\n**Think before deleting**:\n\n- **Cookies and website data** aren't just cache. Removing them usually signs you out of websites.\n- **Offline downloads**: music and videos saved by streaming apps have to be downloaded again.\n- **Cache folders you don't recognize**: find out which app they belong to first. A running app's cache may refuse to delete or come right back.\n\n**Leave alone**:\n\n- the whole `~\u002FLibrary`, `~\u002FLibrary\u002FApplication Support` or `~\u002FLibrary\u002FContainers` folder, which hold settings, databases and chat history;\n- system locations such as `\u002FSystem`, `\u002Fprivate\u002Fvar\u002Fdb` and `\u002Fprivate\u002Fvar\u002Fvm`;\n- files inside your Photos library; let the Photos app manage it.\n\n## Clear caches from inside the app {#in-app}\n\nIf you only want to clear one app, look in its own settings first. The app knows best which data is cache and which is yours.\n\n- **Safari**: choose Safari > Settings, click Privacy, then click Manage Website Data. You can remove data for individual websites or click Remove All. Apple notes that this removes cookies and website data, so it may sign you out of websites.\n- **Chrome**: click the More icon in the upper right, choose Delete browsing data, set the time range to All time, select only Cached images and files, then click Delete data. To stay signed in, leave cookies unselected.\n- **Messaging and office apps**: many offer an option in their settings to clear the cache or manage storage. Use it when it's there. See our guides to [WeChat](\u002Fblog\u002Fwechat-mac-storage) and [DingTalk, Lark and WeCom](\u002Fblog\u002Foffice-chat-apps-cache-mac).\n\nDevelopers can clear download caches with the tools' own commands; for pnpm, Yarn and more, see [how to clear npm, pnpm and Yarn caches](\u002Fblog\u002Fclear-js-package-caches):\n\n```bash\nbrew cleanup\nnpm cache clean --force\n```\n\nXcode's build cache lives in `~\u002FLibrary\u002FDeveloper\u002FXcode\u002FDerivedData`. Quit Xcode before deleting it; the next build will take longer. For simulators and device support files, see our [Xcode guide](\u002Fblog\u002Fclear-xcode-storage).\n\n## Clear caches by hand in the Finder {#finder}\n\n1. Quit the app you want to clean.\n2. In the Finder, choose Go > Go to Folder, type `~\u002FLibrary\u002FCaches` and press Return.\n3. In list view, select \"Calculate all sizes\" (View > Show View Options), then sort by size.\n4. Open the largest app folder and drag its contents to the Trash, keeping the folder itself.\n5. Once you've confirmed the app still works properly, empty the Trash.\n\nTo see how big each cache folder is first, you can also run this in Terminal:\n\n```bash\ndu -sh ~\u002FLibrary\u002FCaches\u002F* 2>\u002Fdev\u002Fnull | sort -h | tail -n 20\n```\n\nOne advantage of deleting by hand is that files go to the Trash first, so you can put them back until you empty it.\n\n## Clear caches in one place with WashBear {#washbear}\n\n::demo deepClean\n\nComparing caches across many apps folder by folder takes a while. Open **Deep Cleanup** and click **Start Scan**. WashBear groups the results into categories such as **System caches**, **User cache files**, **Application caches**, **Browser data** and **Developer tools**, and shows the size of each item.\n\n- **Read before you select**: expand an item to see what it is, how cleaning affects you and its exact locations. The Chrome cache item, for example, states that passwords, cookies, history, extensions and bookmarks are kept.\n- **Caches only**: switch **Selection** at the bottom to **Select none**, then select the caches you want. You can also start from **Smart recommendation**, which preselects only lower-risk items that can usually be recreated.\n- **Apps that must close**: some items show **Close the app before cleanup**. After you click **Clean**, select those apps under **Close running apps (optional)** in **Confirm cleanup**, and WashBear closes them first. Save your work before you do.\n- **Additional user caches**: app caches that aren't listed separately are not selected by default, and caches in use are skipped. Expand the item to see which apps they belong to before selecting it.\n\nSafari's cache can be cleared on its own as **Browser cache** in **Privacy Cleanup**. Smart recommendation there also selects records such as browsing history, so if you only want the cache, switch to **Select none** first and select it by itself. Cookies and website data are in Privacy Cleanup too; if your selection could sign you out, you have to tick an acknowledgment before you can confirm.\n\n> [!WARNING]\n> Files cleaned by WashBear don't go to the Trash and can't be recovered. The items and results of every cleanup are recorded in **Operation History**.\n\n## Frequently asked questions {#faq}\n\n### Will clearing the cache sign me out? {#sign-out}\n\nClearing the cache alone usually won't. Sign-ins are stored in cookies and website data, which are a different thing. When you clean up in a browser, make sure you don't select cookies along the way.\n\n### Will my Mac be faster after clearing caches? {#faster}\n\nNot necessarily. Caches exist to make things load faster, so right after you clear them, apps and web pages have to download and rebuild that data, and the first load is slower. Clearing caches mainly frees space, or helps rule out a problem when an app misbehaves.\n\n### How often should I clear caches? {#how-often}\n\nThere's no need to clear them on a schedule. Caches grow back as you use your apps, which is normal. Clear them when space is tight, or when one app's cache has grown unusually large.\n",1793258439446]