[{"data":1,"prerenderedAt":55},["ShallowReactive",2],{"blog-en-mac-system-data-too-large":3},{"meta":4,"html":14,"headings":15,"raw":54},{"title":5,"description":6,"topic":7,"date":8,"author":9,"icons":10},"Mac System Data Too Large? What It Is and How to Shrink It","System Data is the catch-all category in Mac storage. Learn what fills it, what you can safely clear, what to leave to macOS, and how to make it smaller.","mac-cleanup","2026-10-29","WashBear Team",[11,12,13],"hard-drive","database","analysis","\u003Cp>In System Settings > General > Storage, System Data is often the longest part of the bar, sometimes tens of gigabytes, and there's no Info button to open it. That's because it isn't a folder you can empty; it's an accounting category. To make it smaller, you first need to know what's in it.\u003C\u002Fp>\n\u003Ch2 id=\"what-it-is\">\u003Ca class=\"heading-anchor\" href=\"#what-it-is\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>What System Data is\u003C\u002Fh2>\n\u003Cp>According to Apple, System Data contains files that don't fall into the other categories. It mainly includes files and data used by the system, such as log files, caches, VM files and other runtime resources, as well as temporary files, fonts, app support files and plug-ins. macOS manages this content, you can't manage it from Storage settings, and its size varies with the current state of your Mac. In older versions of macOS, the category was called Other.\u003C\u002Fp>\n\u003Cp>In practice, anything macOS can't place under Applications, Documents, Photos, iOS Files or another category ends up here. A lot of it belongs to apps you installed yourself, and you can manage it in the Finder or in those apps.\u003C\u002Fp>\n\u003Ch2 id=\"whats-inside\">\u003Ca class=\"heading-anchor\" href=\"#whats-inside\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>What's usually inside\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Caches and temporary files\u003C\u002Fstrong>: mostly in \u003Ccode>~\u002FLibrary\u002FCaches\u003C\u002Fcode> and in the per-user temporary folders macOS keeps under \u003Ccode>\u002Fprivate\u002Fvar\u002Ffolders\u003C\u002Fcode>. Browsers, messaging apps, and video and design tools can each hold several gigabytes.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Logs and diagnostic reports\u003C\u002Fstrong>: in \u003Ccode>~\u002FLibrary\u002FLogs\u003C\u002Fcode> and \u003Ccode>\u002FLibrary\u002FLogs\u003C\u002Fcode>. Usually small, but they grow quickly when an app keeps crashing.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>App data\u003C\u002Fstrong>: \u003Ccode>~\u002FLibrary\u002FApplication Support\u003C\u002Fcode>, \u003Ccode>~\u002FLibrary\u002FContainers\u003C\u002Fcode> and \u003Ccode>~\u002FLibrary\u002FGroup Containers\u003C\u002Fcode> hold app databases, offline downloads, chat history and attachments. Messaging apps such as WeChat or Slack are often the single biggest item; for WeChat, see \u003Ca href=\"\u002Fen\u002Fblog\u002Fwechat-mac-storage\">WeChat for Mac taking up tens of GB?\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Developer data\u003C\u002Fstrong>: Xcode's build caches, simulators and device support files in \u003Ccode>~\u002FLibrary\u002FDeveloper\u003C\u002Fcode>, plus disk images used by container tools such as Docker. See our guides to \u003Ca href=\"\u002Fen\u002Fblog\u002Fclear-xcode-storage\">Xcode\u003C\u002Fa> and \u003Ca href=\"\u002Fen\u002Fblog\u002Fdocker-disk-space-mac\">Docker Desktop\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Virtual memory files\u003C\u002Fstrong>: in \u003Ccode>\u002Fprivate\u002Fvar\u002Fvm\u003C\u002Fcode>, managed automatically by macOS.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Local snapshots\u003C\u002Fstrong>: Time Machine saves a local snapshot of your startup disk about every hour and keeps it for 24 hours, plus another one before installing a macOS update. Apple says your Mac counts the space used by snapshots as available storage, and deletes snapshots as they age or when space is needed.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Apple puts iPhone and iPad backups and firmware in the iOS Files category, so they aren't counted here.\u003C\u002Fp>\n\u003Ch2 id=\"why-it-grows\">\u003Ca class=\"heading-anchor\" href=\"#why-it-grows\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>Why it suddenly grows\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>A macOS update was just downloaded or installed.\u003C\u002Fli>\n\u003Cli>A big video, design or development project filled up caches and build data.\u003C\u002Fli>\n\u003Cli>A messaging app has piled up photos, videos and files.\u003C\u002Fli>\n\u003Cli>Storage settings are still calculating right after you open them, so the number may not be accurate yet. Wait a moment and look again.\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 you can clear and what to leave alone\u003C\u002Fh2>\n\u003Cdiv class=\"table-wrap\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Content\u003C\u002Fth>\u003Cth>Location\u003C\u002Fth>\u003Cth>Advice\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>App caches\u003C\u002Ftd>\u003Ctd>App folders in \u003Ccode>~\u002FLibrary\u002FCaches\u003C\u002Fcode>\u003C\u002Ftd>\u003Ctd>Safe to clear after quitting the app; they're rebuilt\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Old logs\u003C\u002Ftd>\u003Ctd>\u003Ccode>~\u002FLibrary\u002FLogs\u003C\u002Fcode>\u003C\u002Ftd>\u003Ctd>Older logs can go; keep them while you're troubleshooting\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Xcode build cache\u003C\u002Ftd>\u003Ctd>\u003Ccode>~\u002FLibrary\u002FDeveloper\u002FXcode\u002FDerivedData\u003C\u002Fcode>\u003C\u002Ftd>\u003Ctd>Safe to delete; the next build takes longer\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>App data\u003C\u002Ftd>\u003Ctd>\u003Ccode>Application Support\u003C\u002Fcode>, \u003Ccode>Containers\u003C\u002Fcode> and similar\u003C\u002Ftd>\u003Ctd>May hold chat history and settings; clean up inside the app, never delete the whole folder\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Local snapshots\u003C\u002Ftd>\u003Ctd>Managed by Time Machine\u003C\u002Ftd>\u003Ctd>Usually nothing to do; macOS deletes them automatically\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>System files\u003C\u002Ftd>\u003Ctd>\u003Ccode>\u002FSystem\u003C\u002Fcode>, \u003Ccode>\u002Fprivate\u002Fvar\u002Fdb\u003C\u002Fcode>, \u003Ccode>\u002Fprivate\u002Fvar\u002Fvm\u003C\u002Fcode>\u003C\u002Ftd>\u003Ctd>Don't delete by hand\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Ch2 id=\"manual\">\u003Ca class=\"heading-anchor\" href=\"#manual\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>Investigate it yourself\u003C\u002Fh2>\n\u003Ch3 id=\"finder\">\u003Ca class=\"heading-anchor\" href=\"#finder\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>Look inside Library in the Finder\u003C\u002Fh3>\n\u003Cp>Your personal Library folder is hidden by default. In the Finder, choose Go > Go to Folder (Shift-Command-G), type \u003Ccode>~\u002FLibrary\u003C\u002Fcode> and press Return. Switch to list view, choose View > Show View Options, select "Calculate all sizes", then sort by size to see which subfolder is largest. You can also select a folder and press Command-I to see its size in the Info window.\u003C\u002Fp>\n\u003Ch3 id=\"terminal\">\u003Ca class=\"heading-anchor\" href=\"#terminal\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>Sort folders by size in Terminal\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-bash\">du -sh ~\u002FLibrary\u002F* 2>\u002Fdev\u002Fnull | sort -h | tail -n 15\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This command only reads sizes and changes nothing; the last lines are the largest folders. Once you find one, run the command on it to go a level deeper, for example \u003Ccode>du -sh ~\u002FLibrary\u002FApplication\\ Support\u002F* 2>\u002Fdev\u002Fnull | sort -h | tail -n 15\u003C\u002Fcode>. If Terminal doesn't have Full Disk Access, protected folders are skipped and the totals come out lower than they really are.\u003C\u002Fp>\n\u003Ch3 id=\"snapshots\">\u003Ca class=\"heading-anchor\" href=\"#snapshots\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>Check local snapshots\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-bash\">tmutil listlocalsnapshots \u002F\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You usually don't need to delete snapshots by hand. If you really want them gone, use Apple's method: in System Settings > General > Time Machine, click Options, set Backup Frequency to Manually, wait a few minutes for the local snapshots to be deleted, then switch back to your previous setting.\u003C\u002Fp>\n\u003Ch2 id=\"washbear\">\u003Ca class=\"heading-anchor\" href=\"#washbear\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>Find and clear it with WashBear\u003C\u002Fh2>\n\u003C!--demo:analysis-->\u003Cp>Start with \u003Cstrong>Disk Space Analysis\u003C\u002Fstrong> to find the biggest contributors. Choose your system disk or your home folder, click \u003Cstrong>Start Analysis\u003C\u002Fstrong>, and click down through the largest block in the \u003Cstrong>Treemap\u003C\u002Fstrong> or \u003Cstrong>Sunburst\u003C\u002Fstrong>. You'll usually see quickly which app inside \u003Ccode>Library\u003C\u002Fcode> is using the space. It only counts what WashBear can read, so the total may differ from Storage settings.\u003C\u002Fp>\n\u003C!--demo:deepClean-->\u003Cp>Then use \u003Cstrong>Deep Cleanup\u003C\u002Fstrong> for the parts that can be cleaned. Click \u003Cstrong>Start Scan\u003C\u002Fstrong>, and results are grouped into categories such as \u003Cstrong>System caches\u003C\u002Fstrong>, \u003Cstrong>User cache files\u003C\u002Fstrong>, \u003Cstrong>Application caches\u003C\u002Fstrong>, \u003Cstrong>Developer tools\u003C\u002Fstrong>, \u003Cstrong>Xcode data\u003C\u002Fstrong> and \u003Cstrong>Container caches\u003C\u002Fstrong>. The items most closely tied to System Data are:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Old temporary files\u003C\u002Fstrong> and \u003Cstrong>Inactive system cache\u003C\u002Fstrong>: only content that hasn't been updated for more than seven days.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Old diagnostic logs\u003C\u002Fstrong>: user-level logs and crash reports older than seven days.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Additional user caches\u003C\u002Fstrong>: app caches that aren't listed separately. Not selected by default, and caches in use are skipped.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Xcode data\u003C\u002Fstrong>: build caches, device support files, simulator runtimes and more. Not selected by default; pick only what you need.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>App leftovers\u003C\u002Fstrong>: data left behind by removed apps that can be clearly linked to them.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>After the scan, \u003Cstrong>Smart recommendation\u003C\u002Fstrong> preselects lower-risk items. Expand any item to see what it is, how cleaning it affects you and where it lives. Cleanup deletes files directly without using the Trash, and the result is recorded in \u003Cstrong>Operation History\u003C\u002Fstrong>. Some app data is protected by macOS and can be read only after you turn on access under \u003Cstrong>Settings → Scanning & analysis → Full Disk Access\u003C\u002Fstrong>. See \u003Ca href=\"\u002Fen\u002Fdocs\u002Fdeep-clean\">Deep Cleanup\u003C\u002Fa> for details.\u003C\u002Fp>\n\u003Ch2 id=\"faq\">\u003Ca class=\"heading-anchor\" href=\"#faq\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>Frequently asked questions\u003C\u002Fh2>\n\u003Ch3 id=\"normal-size\">\u003Ca class=\"heading-anchor\" href=\"#normal-size\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>How big should System Data be?\u003C\u002Fh3>\n\u003Cp>There's no standard size. The apps you use, any development projects and your habits all affect it. Rather than watching this one number, check whether you have enough available space and whether it keeps shrinking.\u003C\u002Fp>\n\u003Ch3 id=\"not-shrinking\">\u003Ca class=\"heading-anchor\" href=\"#not-shrinking\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>I cleaned up, but System Data didn't get smaller. Why?\u003C\u002Fh3>\n\u003Cp>First check whether available space went up; the System Data figure often updates slowly. Caches grow back as you use your apps, which is normal. Local snapshots and purgeable caches already count as available space, so removing them won't change available space much. Don't delete unfamiliar system files just to shorten the bar.\u003C\u002Fp>\n",[16,20,23,26,29,32,36,39,42,45,48,51],{"depth":17,"id":18,"text":19},2,"what-it-is","What System Data is",{"depth":17,"id":21,"text":22},"whats-inside","What's usually inside",{"depth":17,"id":24,"text":25},"why-it-grows","Why it suddenly grows",{"depth":17,"id":27,"text":28},"safe-vs-risky","What you can clear and what to leave alone",{"depth":17,"id":30,"text":31},"manual","Investigate it yourself",{"depth":33,"id":34,"text":35},3,"finder","Look inside Library in the Finder",{"depth":33,"id":37,"text":38},"terminal","Sort folders by size in Terminal",{"depth":33,"id":40,"text":41},"snapshots","Check local snapshots",{"depth":17,"id":43,"text":44},"washbear","Find and clear it with WashBear",{"depth":17,"id":46,"text":47},"faq","Frequently asked questions",{"depth":33,"id":49,"text":50},"normal-size","How big should System Data be?",{"depth":33,"id":52,"text":53},"not-shrinking","I cleaned up, but System Data didn't get smaller. Why?","\nIn System Settings > General > Storage, System Data is often the longest part of the bar, sometimes tens of gigabytes, and there's no Info button to open it. That's because it isn't a folder you can empty; it's an accounting category. To make it smaller, you first need to know what's in it.\n\n## What System Data is {#what-it-is}\n\nAccording to Apple, System Data contains files that don't fall into the other categories. It mainly includes files and data used by the system, such as log files, caches, VM files and other runtime resources, as well as temporary files, fonts, app support files and plug-ins. macOS manages this content, you can't manage it from Storage settings, and its size varies with the current state of your Mac. In older versions of macOS, the category was called Other.\n\nIn practice, anything macOS can't place under Applications, Documents, Photos, iOS Files or another category ends up here. A lot of it belongs to apps you installed yourself, and you can manage it in the Finder or in those apps.\n\n## What's usually inside {#whats-inside}\n\n- **Caches and temporary files**: mostly in `~\u002FLibrary\u002FCaches` and in the per-user temporary folders macOS keeps under `\u002Fprivate\u002Fvar\u002Ffolders`. Browsers, messaging apps, and video and design tools can each hold several gigabytes.\n- **Logs and diagnostic reports**: in `~\u002FLibrary\u002FLogs` and `\u002FLibrary\u002FLogs`. Usually small, but they grow quickly when an app keeps crashing.\n- **App data**: `~\u002FLibrary\u002FApplication Support`, `~\u002FLibrary\u002FContainers` and `~\u002FLibrary\u002FGroup Containers` hold app databases, offline downloads, chat history and attachments. Messaging apps such as WeChat or Slack are often the single biggest item; for WeChat, see [WeChat for Mac taking up tens of GB?](\u002Fblog\u002Fwechat-mac-storage)\n- **Developer data**: Xcode's build caches, simulators and device support files in `~\u002FLibrary\u002FDeveloper`, plus disk images used by container tools such as Docker. See our guides to [Xcode](\u002Fblog\u002Fclear-xcode-storage) and [Docker Desktop](\u002Fblog\u002Fdocker-disk-space-mac).\n- **Virtual memory files**: in `\u002Fprivate\u002Fvar\u002Fvm`, managed automatically by macOS.\n- **Local snapshots**: Time Machine saves a local snapshot of your startup disk about every hour and keeps it for 24 hours, plus another one before installing a macOS update. Apple says your Mac counts the space used by snapshots as available storage, and deletes snapshots as they age or when space is needed.\n\nApple puts iPhone and iPad backups and firmware in the iOS Files category, so they aren't counted here.\n\n## Why it suddenly grows {#why-it-grows}\n\n- A macOS update was just downloaded or installed.\n- A big video, design or development project filled up caches and build data.\n- A messaging app has piled up photos, videos and files.\n- Storage settings are still calculating right after you open them, so the number may not be accurate yet. Wait a moment and look again.\n\n## What you can clear and what to leave alone {#safe-vs-risky}\n\n| Content | Location | Advice |\n| --- | --- | --- |\n| App caches | App folders in `~\u002FLibrary\u002FCaches` | Safe to clear after quitting the app; they're rebuilt |\n| Old logs | `~\u002FLibrary\u002FLogs` | Older logs can go; keep them while you're troubleshooting |\n| Xcode build cache | `~\u002FLibrary\u002FDeveloper\u002FXcode\u002FDerivedData` | Safe to delete; the next build takes longer |\n| App data | `Application Support`, `Containers` and similar | May hold chat history and settings; clean up inside the app, never delete the whole folder |\n| Local snapshots | Managed by Time Machine | Usually nothing to do; macOS deletes them automatically |\n| System files | `\u002FSystem`, `\u002Fprivate\u002Fvar\u002Fdb`, `\u002Fprivate\u002Fvar\u002Fvm` | Don't delete by hand |\n\n## Investigate it yourself {#manual}\n\n### Look inside Library in the Finder {#finder}\n\nYour personal Library folder is hidden by default. In the Finder, choose Go > Go to Folder (Shift-Command-G), type `~\u002FLibrary` and press Return. Switch to list view, choose View > Show View Options, select \"Calculate all sizes\", then sort by size to see which subfolder is largest. You can also select a folder and press Command-I to see its size in the Info window.\n\n### Sort folders by size in Terminal {#terminal}\n\n```bash\ndu -sh ~\u002FLibrary\u002F* 2>\u002Fdev\u002Fnull | sort -h | tail -n 15\n```\n\nThis command only reads sizes and changes nothing; the last lines are the largest folders. Once you find one, run the command on it to go a level deeper, for example `du -sh ~\u002FLibrary\u002FApplication\\ Support\u002F* 2>\u002Fdev\u002Fnull | sort -h | tail -n 15`. If Terminal doesn't have Full Disk Access, protected folders are skipped and the totals come out lower than they really are.\n\n### Check local snapshots {#snapshots}\n\n```bash\ntmutil listlocalsnapshots \u002F\n```\n\nYou usually don't need to delete snapshots by hand. If you really want them gone, use Apple's method: in System Settings > General > Time Machine, click Options, set Backup Frequency to Manually, wait a few minutes for the local snapshots to be deleted, then switch back to your previous setting.\n\n## Find and clear it with WashBear {#washbear}\n\n::demo analysis\n\nStart with **Disk Space Analysis** to find the biggest contributors. Choose your system disk or your home folder, click **Start Analysis**, and click down through the largest block in the **Treemap** or **Sunburst**. You'll usually see quickly which app inside `Library` is using the space. It only counts what WashBear can read, so the total may differ from Storage settings.\n\n::demo deepClean\n\nThen use **Deep Cleanup** for the parts that can be cleaned. Click **Start Scan**, and results are grouped into categories such as **System caches**, **User cache files**, **Application caches**, **Developer tools**, **Xcode data** and **Container caches**. The items most closely tied to System Data are:\n\n- **Old temporary files** and **Inactive system cache**: only content that hasn't been updated for more than seven days.\n- **Old diagnostic logs**: user-level logs and crash reports older than seven days.\n- **Additional user caches**: app caches that aren't listed separately. Not selected by default, and caches in use are skipped.\n- **Xcode data**: build caches, device support files, simulator runtimes and more. Not selected by default; pick only what you need.\n- **App leftovers**: data left behind by removed apps that can be clearly linked to them.\n\nAfter the scan, **Smart recommendation** preselects lower-risk items. Expand any item to see what it is, how cleaning it affects you and where it lives. Cleanup deletes files directly without using the Trash, and the result is recorded in **Operation History**. Some app data is protected by macOS and can be read only after you turn on access under **Settings → Scanning & analysis → Full Disk Access**. See [Deep Cleanup](\u002Fdocs\u002Fdeep-clean) for details.\n\n## Frequently asked questions {#faq}\n\n### How big should System Data be? {#normal-size}\n\nThere's no standard size. The apps you use, any development projects and your habits all affect it. Rather than watching this one number, check whether you have enough available space and whether it keeps shrinking.\n\n### I cleaned up, but System Data didn't get smaller. Why? {#not-shrinking}\n\nFirst check whether available space went up; the System Data figure often updates slowly. Caches grow back as you use your apps, which is normal. Local snapshots and purgeable caches already count as available space, so removing them won't change available space much. Don't delete unfamiliar system files just to shorten the bar.\n",1793258439532]