NotchMindSystem Data is one of the least helpful labels to see when your Mac is nearly full. It sounds like a single thing you could remove, but it is a broad storage category. The number does not tell you which files are valuable, which are temporary, or which application owns them.
The safe response is to investigate a concrete pattern. Did space disappear after a large project import? Does one app keep growing? Is the Mac actually short of available capacity, or are you reacting to the chart’s proportions? Those questions lead to better actions than deleting unknown folders.
Understand what the category means
Apple describes System Data, sometimes called Other, as a general category for Apple and third-party files that do not fit more specific categories. Its storage support article explains this classification.
That means a large value is not a diagnosis by itself. It is a prompt to inspect storage using more specific information. You still need to determine which data is involved and whether a supported way exists to manage it.
Do not assume that everything counted there is a cache, or that everything called a cache is harmless to remove in any situation. Names and categories are weaker evidence than knowing the owning application and the documented purpose of its files.
Check whether capacity is actually constrained
Open Storage settings and note available space, not just the size of the colored segment. Then identify the operation that is failing or the amount of room you need for current work.
A large category can be concerning without being the immediate cause of a problem. Conversely, modest-looking categories can still leave insufficient capacity for a large import or update. Measure the situation instead of comparing the chart to a screenshot from someone else’s Mac.
Apple’s Storage settings guide explains which categories provide management controls and which primarily report size.
Establish when the growth began
Think back to recent changes: a new development environment, a video project, a device backup, a game, or a large mail import. These are leads to investigate, not proof that the application is faulty.
Write down the approximate date and the tasks involved. If you can reproduce the growth with one app, note available space before and after a normal session. Do not create a huge test workload on an already full disk just to gather a number.
A simple observation such as “available space drops after each export and does not return” is more useful than “System Data looks too big.” It suggests a specific workflow to inspect.
Review known application storage through the app
Look for supported controls in the application that owns the suspected data. A media app may manage downloads or render files; a development tool may document its build artifacts or simulators; a backup utility may have its own retention settings.
Use those controls where they fit. Avoid guessing at internal folder names and deleting their contents in Finder. An application may store preferences, indexes, originals, and temporary data near one another.
For an important project, save work and confirm a backup before changing storage management. If a cleanup option says it will remove generated material, make sure the sources needed to regenerate it still exist.
Review ordinary storage first when you need room now
If the immediate need is capacity, inspect files you understand: old installers, redundant exports, and downloaded media that can be obtained again. You may solve the urgent problem without touching ambiguous System Data at all.
The safe storage cleanup guide gives an order of operations. It emphasizes verifying copies before removing originals and using the owning app for managed libraries.
This is not avoidance. It is choosing an action whose consequences you can evaluate. Freeing a known redundant export is often more useful than spending hours trying to make one category’s label shrink.
Treat backup history as protection, not clutter
Before removing anything associated with backups or recovery, understand what protection it provides and how the relevant system manages it. Do not delete backup-related files merely because an online tip promises a large reduction.
If a backup drive is unavailable or backups are stale, fix that problem directly. Sacrificing recovery history while your primary data remains unprotected can make a storage issue more consequential.
Use the Time Machine guide to verify current protection. If you need to change a backup policy, use the supported settings and check that you can still recover important files afterward.
Avoid broad cleanup commands
Commands that remove entire cache, Library, or support folders are difficult to review when copied from a generic article. They may affect more than the application you are investigating, and a typo can make the consequences much worse.
A safer cleanup names the owning app, the exact disposable data, the documented removal method, and the expected effect. If those details are missing, pause and seek the app’s official guidance.
Also avoid disabling security controls to make a cleanup tool work. Storage pressure does not justify granting unexplained access to an application that cannot clearly describe what it will remove.
Collect evidence for persistent unexplained growth
If available space continues to fall after ordinary cleanup, record the macOS version, recent changes, affected apps, and a few measurements over time. Include any storage or backup errors.
Share only the information needed to demonstrate the pattern. Directory listings can contain sensitive filenames, so inspect them before sending them to support. A summary may be enough for the first conversation.
The performance troubleshooting guide can help if low capacity accompanies slow behavior, but keep the symptoms distinct. Storage growth, memory pressure, and CPU activity require different evidence.
Common questions
Is System Data safe to delete? It is a category, not a single removable item. Safety depends on the actual files and the supported management method.
Why is another Mac’s number smaller? Different apps, projects, histories, and workloads produce different storage use. Compare your own capacity and behavior over time.
What is the quickest safe action? Review known large files and recreatable downloads first, while preserving backups and important originals.