What is safe to delete on a Mac?

Short answer: caches, logs, old installers in Downloads, the Trash, and stale iOS backups are almost always safe to delete on a Mac — macOS or the app that owns them rebuilds what you need. Anything inside /System, anything named com.apple.*, and anything synced through iCloud Drive or Dropbox is not something to delete locally unless you mean to delete it everywhere. The rest of this guide walks through exactly which folders fall into which category, with real paths, and a worked example on a nearly-full 512 GB MacBook so you can see what actually gets reclaimed.

The three tiers, in plain terms

Every "what can I delete" question on a Mac comes down to one of three answers: yes, this gets rebuilt automatically and costs you nothing to remove; maybe, this is real data that happens to live somewhere you don't normally look; or no, this belongs to the system or an app you still use, and touching it will break something. Here's the breakdown with actual folder paths.

Tier 1 — safe to clean

• ~/Library/Caches — every app stores rebuildable cache data here, one subfolder per app (usually named after its bundle ID, like com.google.Chrome). Delete the contents and the app rebuilds what it needs on next launch. This is the single biggest reclaimable category on most Macs — several gigabytes after a few months of normal use is typical.
• ~/Library/Logs — diagnostic logs apps write for debugging. You'll never read most of them. Safe to clear.
• ~/Downloads — specifically old .dmg and .pkg installers left over after you already installed the app. The installer's job is done the moment the app is in /Applications.
• The Trash — items in Trash are already marked for deletion; emptying it just finishes the job. macOS can do this automatically after 30 days via "Empty Trash automatically" in Finder settings.
• ~/Library/Application Support/MobileSync/Backup — local iOS/iPadOS device backups made by Finder or the old iTunes. Worth keeping only if it's your sole backup of a device you still own. If the phone is also backed up to iCloud, or you no longer have it, an old local backup here is dead weight — often 5–15 GB per device on a Mac that's synced phones for years.
• ~/Library/Developer/Xcode/DerivedData — build artifacts Xcode regenerates every time you build a project. Doesn't exist if you're not a developer. If you are, it's one of the fastest multi-gigabyte wins on the disk, and Xcode rebuilds it automatically next time you open a project.

Tier 2 — review before you touch it

• Large media also in cloud sync — a folder of videos or RAW photos also sitting in iCloud Photos, Dropbox, or Google Drive isn't automatically safe to delete locally. Deleting the local copy can delete the cloud copy too, or just remove the local copy and leave the cloud version — it depends on the service and whether "optimize storage" or "download and keep originals" is turned on. Check that setting before deleting anything in a synced folder.
• Mail attachments — Apple's own storage recommendations flag these because they add up, but attachments are real mail data, not a cache. Review one in Mail before removing the message if you're not sure you'll want it again.
• Time Machine local snapshots — macOS creates these automatically on your internal disk between backups, so you have restore points even offline from your Time Machine drive. They're managed by the OS, not sitting in a folder you browse in Finder, and macOS deletes older ones on its own as space is needed. Tools that report "System Data" usage are often counting these, which is why that number can look alarmingly large on Macs with Time Machine enabled.
• Language files inside apps — some larger apps ship every supported language and only use one. Removing unused localizations reclaims a modest amount of space, but it means editing inside an app bundle, and an update usually puts them right back. Low reward, non-zero risk — worth it only if you're already deep into cleanup.

Tier 3 — leave alone

• /System and /Library — these belong to macOS itself. Since macOS Catalina, the entire System volume is sealed and read-only at the OS level specifically to stop this kind of damage, so you likely can't delete here even if you try.
• ~/Library folders for apps you still use — specifically Application Support, Preferences, and Containers. This is where apps keep your settings, saved data, and license state. Deleting the wrong folder here rarely frees meaningful space and does reset the app to a blank slate or break it outright.
• Anything named com.apple.* — wherever you see this prefix, in Caches, Preferences, or Containers, it belongs to a built-in macOS component. Some are safe caches, but plenty aren't — they're state files for Messages, Photos, Mail, and Notes that hold your actual data. Treat the prefix as a signal to slow down, not a blanket "always keep."
• Cloud-synced folders — iCloud Drive, Dropbox, Google Drive, OneDrive — this is the one that causes real damage. If a folder is actively synced, deleting it locally isn't a local action; it can propagate to every other device on that account within seconds. Pause sync for the folder, or verify in the service's own settings that the file exists safely elsewhere first.

Worked example: reclaiming 40 GB on a 512 GB MacBook

Say you're looking at a 512 GB MacBook Air with "58 GB available" in System Settings and it feels tighter than it should. Walking the tiers above in order, here's a realistic breakdown of where 40 GB of genuinely reclaimable space might be hiding, and how you'd actually go find each piece.

• 12 GB — ~/Library/Caches. Three years of Chrome, Slack, Spotify, and a dozen smaller apps, each leaving a few hundred MB to a couple of GB behind.
• 6 GB — ~/Library/Logs plus old installers in ~/Downloads. A handful of forgotten .dmg files from apps installed a year ago, plus logs nobody's opened.
• 9 GB — the Trash. Files moved there over months, never emptied, quietly still counted against your free space.
• 8 GB — a stale iPhone backup at ~/Library/Application Support/MobileSync/Backup, left over from a phone that's now backed up to iCloud instead.
• 5 GB — Xcode DerivedData, if you dabble in iOS development and haven't cleared it since your last few projects.

That's 40 GB, entirely from Tier 1 — nothing here required touching a cloud-synced folder or a system file.

How to actually find and clear each one

Finder hides most of these folders by default, so casual users don't stumble into ~/Library by accident. The fastest way in is Finder's "Go to Folder" command:

1. Open Finder, then press Shift+Command+G (⇧⌘G).
2. Type the path — for example ~/Library/Caches — and press Return.
3. Switch to list view (Command+2) and turn on the "Size" column via View > Show View Options, so you can sort folders largest-first.
4. Select a subfolder and press Command+I for an exact size, or just eyeball the sorted list for the biggest offenders.
5. Delete what you're confident about by dragging to Trash — not Command+Delete-then-empty in the same motion. Let items sit in Trash first so you can pull something back if an app misbehaves afterward.

Repeat the same ⇧⌘G trick for ~/Library/Logs, ~/Downloads, and ~/Library/Application Support/MobileSync/Backup. For DerivedData, the path is ~/Library/Developer/Xcode/DerivedData — safe to delete entirely with Xcode closed; it rebuilds on the next build.

For the Trash itself, right-click the Dock icon and choose Empty Trash, or turn on automatic 30-day emptying in Finder > Settings > Advanced.

What Apple's own storage tools already do for you

Before folder-hunting by hand, check System Settings > General > Storage. Apple's own support article on freeing up storage space on Mac covers the same ground from the built-in side: check your storage breakdown, delete unused media, clear Downloads, erase junk mail, remove backups for devices you no longer use. Apple's storage-optimization guide explains what "Store in iCloud," "Optimize Storage," and "Empty Trash Automatically" do — Optimize Storage, for instance, removes watched iTunes/TV content and keeps only recent Mail attachments once space runs low. Useful, but these tools describe categories at a high level ("System Data," "Documents") rather than naming the specific folder and the specific number — that's the gap a dedicated tool fills.

Where SwoopByte Disk fits

This is the exact problem SwoopByte Disk is built around: turning "System Data is 45 GB" into a named, itemized list you can act on. The free version maps your whole disk, ranks your largest files and folders, and gives every finding one of four plain labels — Safe to clean, Review first, Keep, or Protected — so you're never guessing which tier a folder falls into. It also breaks down System Data specifically: Time Machine local snapshots, old iPhone/iPad backups (with device name and last-backup date), Docker's disk image, and app caches and logs, each with a real size and a plain-language reason.

The one-click "safe clean" in the free version handles the Tier 1 category from this guide — user caches and logs — plus Empty Trash, and every item goes to the Trash, never straight to permanent deletion. Anything cloud-synced or belonging to Apple's own components is shown so you know it's there, but it's locked from the removal list rather than pre-checked — safety isn't a paywalled feature. The one-time $14.99 Pro unlock adds batch reclaim for developer caches (Homebrew, npm, Yarn, pip, cargo), duplicate file removal, and swoop-to-swoop history so you can see what actually grew since last time.

If you actually want to remove an entire app you no longer use, that's a related but different job with its own gotchas around leftover files — see our guide on completely uninstalling a Mac app.

FAQ

Is it safe to delete everything in ~/Library/Caches?

Yes, for the vast majority of apps — cache folders are rebuildable by design, and clearing them just means a slightly slower first launch while the app regenerates what it needs. Close apps first if you're clearing their caches by hand, especially anything mid-download.

What is System Data on Mac and can I delete it?

System Data is Apple's catch-all label in System Settings > General > Storage for things that don't fit its other categories: caches, logs, Time Machine local snapshots, Docker images, and similar. Some of it (app caches and logs) is safe to clear; some of it (Time Machine snapshots) is managed by macOS itself and isn't something you delete directly. Treat "System Data" as a category to investigate, not a single button to press.

Will deleting cache files break my apps?

Almost never. Worst case is a slower first launch or briefly being logged out of a website in your browser. Genuine breakage from clearing a Caches folder is rare enough that it isn't a real risk for most apps.

Can I delete files inside iCloud Drive or Dropbox to free up space?

Be careful — these folders are actively synced, so a local delete can propagate to every device signed into that account, sometimes within seconds. If you want the file gone everywhere, that's fine and expected. If you only meant to free local disk space, check the service's own settings first (iCloud's "Optimize Mac Storage," Dropbox's Smart Sync, or similar) rather than deleting directly.

Is it safe to delete an old iPhone backup from my Mac?

Yes, if that device is backed up elsewhere (iCloud, or a more recent local backup) or you no longer own it. These backups live at ~/Library/Application Support/MobileSync/Backup and can easily be several gigabytes each. Check the device name and last-backup date in Finder's backup management (or a tool that surfaces it) before deleting, so you don't remove the only backup of a phone you still use.

Related guides