Skip to cookie settings

macOS Sequoia System Data huge: causes and fixes

A huge System Data number on Sequoia has a handful of usual causes. Check them one by one, fix the safe ones, and leave the system's own files alone.

Part of: System Data on Mac: what is inside and how to reduce it safely (System Data)

If System Data looks far too big on Sequoia, the cause is almost always one of four things. For what the label contains in general, read the System Data guide first. This guide checks them in order, so you do not have to guess. The commands below are read-only: they only look.

A note on versions: the steps are the same ideas as on other recent macOS releases, so this guide stays general. Menu names can differ slightly between versions.

Cause 1: Local snapshots

Time Machine can keep local snapshots on the disk, and system updates can keep one too. Check:

tmutil listlocalsnapshots /

An empty list rules this cause out. A long list of Time Machine snapshots is worth reading about in the local snapshots guide. macOS releases this space when it needs room, so it is often not a problem to fix.

Cause 2: Caches and logs

These add up over years. See how large yours are:

du -sh ~/Library/Caches
du -sh ~/Library/Logs

Several gigabytes in Caches is normal for a Mac in daily use. Clearing the caches of apps you can name is safe, and apps rebuild them. The caches guide says which to leave alone.

Cause 3: App data in your Library

Find the largest folders:

du -sh ~/Library/* 2>/dev/null | sort -h | tail -5

Application Support is often the biggest. It holds real data for apps, such as local databases, downloaded content and project files. Check which app each subfolder belongs to before touching anything. Removing leftovers of an app you already uninstalled is fine. Removing data of an app you use is how people lose settings.

Cause 4: The Trash

Files in the Trash still use space until you empty it. The Trash guide covers this and why the number sometimes lags.

Safe, Risky, Never

Safe

  • Emptying the Trash after a last look.
  • Clearing caches and old logs of apps you can name.
  • Restarting, which lets macOS recount and release temporary files.

Risky

  • Application Support folders of apps you still use.
  • Local snapshots you did not create.
  • Caches for offline content, which you would need to download again.

Never

  • Files inside /System or hidden system folders.
  • Anything you cannot identify, only because it is large.

What if nothing is big?

Sometimes the parts add up to much less than the System Data figure. The Storage bar is an estimate, and it can include space macOS can free on demand. Compare it with the plain disk numbers:

df -h /System/Volumes/Data

If Avail is healthy, you may not have a problem. The purgeable space guide explains the gap.

A worked example

Imagine System Data shows a large figure. You run the Library check and the biggest folder is Application Support. You look inside it with du -sh on a few subfolders and find one app holds most of the space. Now you have a real question to answer: do I still use that app?

  • If you do not, uninstall it properly and remove its leftovers. The app leftovers guide shows where they live.
  • If you do, open the app and look for its own storage or cleanup setting. Many apps can clear their downloaded content themselves, which is safer than removing folders.

That small loop, measure then ask what owns the space, works for every cause on this page.

Write down what you find

Before you change anything, note three things: the Used figure from df -h /System/Volumes/Data, the size of your Library check, and the date. After each step, run the same checks again. That way you know which step helped, and you avoid repeating steps that did nothing. If nothing moved, leave it alone and stop. A big number is not a problem by itself.

How often to check

There is no need to check every week. A look every few months, or after a large update, is enough for most people. If you work with video, virtual machines or large development projects, check more often, because those can add many gigabytes quickly.

When the cause is a specific kind of app

Some apps are known for writing a lot of data in your Library: video editors that keep render caches, chat apps that keep downloaded media, browsers with large profiles, and developer tools with build products. These are also the easiest wins, because the apps usually have a setting to limit or clear that data. Start there before manual removal.

If you use Xcode, its folders can be very large and rebuild on demand. See the Xcode cleanup guide for what is safe.

Check it in one scan

DiskJoy is our product. Its scan is read-only today and removes nothing; it reports allocated size, and its reclaimable figure is a lower-bound estimate. To see caches, logs and large folders together, run the scan.

Frequently asked questions

Why is System Data so large on macOS Sequoia?

The usual causes are local snapshots, large caches and logs, app support data from heavy apps, and an unemptied Trash. Which one it is differs between Macs, so check them in turn.

How do I reduce System Data on Sequoia?

Find the large part first with the commands below, then reduce only that part. Clearing caches and logs of apps you can name is the safest step. Leave system folders alone.

Can I delete System Data on Sequoia?

Not as a whole. It is a label for many different files. Some are yours to manage and some belong to macOS.

Tags:System DatamacOS SequoiaStorage settings

See what’s taking up space on your Mac

DiskJoy explains every item and removes nothing until you review it.
Download for Mac

Cookies on diskjoy.com

Your browser sends a Global Privacy Control signal. We honoured it: analytics and marketing cookies are off.

Necessary cookies run this site. Analytics shows us how it is used: if you accept it, Google receives data about your visit. Change this anytime in Cookie Settings. How Google uses data Cookie Policy Privacy policy

Customize

Purpose
Needed for the site to work and to remember your cookie choice.

Cookies

  • sy_consent - Stores your cookie choice (Retention: 12 months)

Other browser storage

  • sy_consent_pending (localStorage) - Queues your choice until it reaches our server (Retention: until deleted)
Purpose
Show us which pages are visited and how the site is used, so we can improve it. Provider: Google Ireland Ltd (Google Analytics 4).

Cookies

  • _ga - Distinguishes visitors to count them (Retention: 400 days)
  • _ga_TP2XMLG27P - Keeps the state of your current visit (Retention: 400 days)

Recipients

Data controller

Sylentis Group sp. z o.o.. Contact: support@diskjoy.com. Privacy policy

Google may process data outside the European Economic Area (EEA). Safeguards: EU-US Data Privacy Framework, standard contractual clauses.

Right to withdraw

You can withdraw consent at any time, as easily as you gave it. Withdrawal does not affect the lawfulness of processing before it.