Emma Rodriguez had been a freelance graphic designer for six years when her MacBook Pro started to betray her at the worst possible moment. It was a Monday morning in late autumn, and she had a client presentation in 90 minutes. She opened her design files. The app bounced in the dock. And bounced. And bounced. A beach ball appeared where a canvas should have been.

She restarted. Things improved for about four minutes before the same sluggishness returned. She checked for updates — nothing pending. She looked at her storage and nearly choked: of 256 GB, only 9 GB remained. The rest was labeled with categories she barely recognized: Applications, System Data, Other.

A colleague told her to look at her Library folder. What she found there surprised her: 14 GB just in application caches. Another 3 GB of old browser data. Hundreds of megabytes of crash logs and diagnostic reports that macOS had been quietly accumulating for years. None of it was doing any work anymore. It was just sitting there, eating space and, in many cases, slowing things down as the system attempted to index and manage it all.

She made it to the call — barely — and spent the following weekend going through her Mac systematically. What follows is essentially what she learned: a clear, methodical way to understand the different kinds of accumulated data on a Mac and how to address each one.

What is cache, and why does it build up?

Cache is a technical term for data that an application saves locally to avoid having to retrieve or recalculate it again. When your browser visits a website, it stores copies of images, fonts, and scripts so the page loads faster on the next visit. When a photo editing app generates a thumbnail for an image you’ve opened, it may save that thumbnail in a cache folder so it doesn’t need to regenerate it from scratch each time.

In theory, this is efficient. In practice, cache files multiply quickly because apps rarely clean up after themselves proactively. They save data assuming it might be needed again, but over time the proportion of actually reused cache data versus forgotten, stale data shifts dramatically toward the latter. A two-year-old MacBook used daily accumulates a surprisingly large amount of this kind of residue.

Beyond caches specifically, Macs also accumulate other categories of non-essential data: system logs, crash reports, leftover support files from applications you deleted long ago, duplicate font sets, old iOS backups, and temporary installer files that should have been removed after installation.

The six major categories to know about

1. User library caches

This is typically the largest single category. Your Mac maintains a hidden Library folder inside your home folder (the one with your name), and inside it lives a Caches folder. Every installed app that wants to store local data — from music apps to productivity tools to creative software — gets its own subfolder here.

To reach it, open Finder and use the Go menu at the top of your screen. Hold the Option key on your keyboard while that menu is open and you’ll see a Library option appear that is normally hidden. From there, navigate into the Caches folder. You’ll find a list of subfolders, each named after an app. The size of each folder is visible if you right-click and select Get Info, or if you arrange the view by file size.

When reviewing these folders, it is generally safe to delete the contents of most app cache subfolders while the app in question is closed. The app will simply regenerate a fresh cache the next time it runs. The two exceptions to be aware of are system-level folders whose names suggest they belong to macOS itself, and any folder from an app you actively depend on where regenerating the cache would require significant time (such as a large media application rebuilding its entire thumbnail library).

2. Browser cache

Web browsers maintain their own caches independently of the system-level caches described above. Safari stores its cache in a location managed by the system, while Chrome, Firefox, and other third-party browsers keep theirs within their own application support or caches folders.

Each browser provides a built-in way to clear this data. In Safari, the option is available under the Develop menu (which you may need to enable in Safari’s settings first via the Advanced tab). In Chrome and Firefox, the relevant option is typically found in the Settings or Preferences area under a section called Privacy or History. The option to clear browsing data will let you remove cached files, cookies, and history independently or together.

Clearing browser cache does not remove saved passwords or bookmarks. Those are stored separately. What you’ll lose is the local copies of visited pages, which simply means those pages will take a moment longer to load the first time you revisit them after the clear.

3. System and application logs

macOS generates extensive log files as it operates. These logs record events, errors, application behaviors, and system diagnostics. They are invaluable to developers and support technicians when something goes wrong, but for most users on most days, they are never read.

Logs accumulate in several locations within the Library folder, both at the user level and at the system level. The system-level logs (inside the main Library folder at the root of your drive, not your personal one) require administrator permission to modify, so approach them carefully. User-level logs are more accessible.

macOS does have some automatic log management that rotates and compresses old logs, but this process is not always aggressive enough to prevent meaningful accumulation on machines used for years. Reviewing the Logs folder within your personal Library and deleting entries older than a few months is generally safe.

4. Crash reports and diagnostic data

When an application quits unexpectedly, macOS writes a crash report. These are plain text files that capture the state of the application at the moment of failure. Useful for developers, irrelevant for most users after more than a day or two. These files live in a folder called Diagnostic Reports within your personal Library. If you see dozens or hundreds of them accumulated over months, they can be safely deleted.

5. Leftover app data from uninstalled applications

When you drag an application to the Trash, macOS removes the app itself but typically leaves behind the folders that app created in your Library. This includes preference files, support data, cache folders, and sometimes quite large databases of user-generated content that the app managed.

These leftover folders are found in three main places within your personal Library: Preferences (for settings files, usually small), Application Support (for larger data like databases and content libraries), and Caches (for temporary data). Searching these folders for names of apps you no longer use and removing the corresponding subfolders is a reliable way to reclaim space.

6. Temporary and download files

Installer packages you downloaded but no longer need, disk images (files ending in .dmg) sitting in your Downloads folder after you’ve already installed the app, and document versions you no longer use all contribute to unnecessary storage use. macOS keeps a versions history of documents you create in apps like Pages and TextEdit, which can accumulate significantly over time.

How to approach this systematically

Rather than attempting to clear everything at once, a methodical approach works best. Start with the browser caches since those are the easiest to clear and have the least risk of any side effects. Then move to your user Library caches, reviewing each app’s folder individually. Next, check the Application Support folder for apps you no longer use. Finally, look through your Downloads folder and remove any disk images, installer packages, and other files you no longer need.

Before you start

It is good practice to make sure your Mac is backed up before making significant changes to your Library folders. macOS has Time Machine for this purpose. If you use it regularly, you can clear cache and log files with confidence knowing a restore point exists. If you are not currently using any backup system, this is a good moment to set one up — the Backup section of System Settings will guide you through connecting an external drive to Time Machine.

Using the built-in storage tools in macOS

macOS includes a storage management utility that you can reach by opening the Apple menu, choosing System Settings (or System Preferences on older versions), and then navigating to General and Storage. This screen shows you a breakdown of what is using your space and offers several automated recommendations.

The Reduce Clutter option within that panel allows you to review large files by category and date. It’s particularly useful for identifying large files you may have forgotten about — especially in the Downloads and Documents folders. This tool will not automatically delete anything; it simply surfaces information and lets you decide.

The Optimize Storage option, if enabled, allows macOS to automatically remove Apple TV content you have already watched, and to keep older email attachments in iCloud rather than on your local drive when space is needed. These are modest but useful options for users who rely heavily on Apple services.

What to avoid

A few cautions worth noting: do not delete entire folders from locations you are not certain about. The Library folder contains both data you can safely clear and data that your apps depend on to function correctly. Preference files (usually ending in .plist) tell your apps how you have configured them; deleting them means those settings will reset to defaults. That might occasionally be desirable (if you are troubleshooting a misbehaving app) but is generally not something to do routinely.

Also, the system-level Library folder at the root of your drive — not inside your user folder — contains files that macOS itself depends on. Changes there should be made with care and only when you have a specific reason. Most of the productive cleaning work happens within your personal user Library, not the system one.

How often should you do this? A light review every three to four months is reasonable for most users. If you regularly work with large files, do creative work, or keep your Mac for many years between replacements, checking more frequently — perhaps every six weeks — helps prevent the kind of situation Emma found herself in.

What happened to Emma

After spending a few hours working through her Library folders methodically, Emma recovered nearly 22 GB. App launches were noticeably faster. The fan was quieter. She set up a repeating calendar reminder to do a quick storage review every two months.

She also enabled Time Machine on an external drive she had owned but never set up — something she later said should have been the first thing she did when she got the machine. The experience, frustrating as it was in the moment, turned into a useful set of habits that her Mac has benefited from since.