Free Up Space on a Mac Without Deleting Photos (2026)

Your Mac says storage is full, and your first instinct is to open the Photos app and start deleting — but that's the wrong place to start. You can almost always free up space on a Mac without deleting photos by targeting the junk your system quietly accumulates on its own: caches, logs, leftover app files, and gigabytes of "System Data" that macOS is perfectly happy to discard. This guide walks you through every safe move, in order of effort, so your photo library stays exactly where it is.

Why "System Data" Gets So Large (And What Is Safe to Remove)

Open Apple menu > System Settings > General > Storage and you'll likely see "System Data" consuming anywhere from 10 GB to 50 GB or more. This category is a catch-all that includes:

• Application caches — temporary files apps write to speed up future loads
• User caches — browser data, thumbnail databases, font caches
• Log files — system and app diagnostic logs that accumulate forever
• Temp files — files written to /tmp and ~/Library/Caches during normal use
• Purgeable space — data macOS has marked as safe to reclaim (iCloud-backed items, old Time Machine snapshots) but hasn't freed yet

None of these categories contains your photos. Your photo library lives in ~/Pictures/Photos Library.photoslibrary and is never touched by cache-cleaning operations. You can safely delete caches, logs, and temp files without risk to any image or video.

Step 1 — Clear Application and User Caches Manually

macOS stores per-user cache files in ~/Library/Caches. On a machine used for a year or more, this folder can hold 5–15 GB of data from browsers, Xcode, Spotify, Electron apps, and dozens of other sources.

1. Open Finder, press Shift-Command-G, and paste ~/Library/Caches.
2. Look for large folders. Common culprits: com.apple.dt.Xcode, com.spotify.client, Google/Chrome, com.microsoft.teams.
3. Delete the contents of a folder, not the folder itself, to avoid confusing the app on next launch.
4. Empty the Trash.

Apps will recreate their cache folders automatically on next launch; you lose nothing except load time for the first run after cleaning.

The system-level cache directory at /Library/Caches also accumulates data. You can inspect it, but deleting files there requires administrator credentials and more caution — skip it unless you know what a specific folder contains.

Step 2 — Delete Log Files

macOS and third-party apps write diagnostic logs to two locations:

• ~/Library/Logs — per-user logs, safe to delete entirely
• /Library/Logs and /var/log — system logs; safe to clear old entries but leave the folders themselves

To remove user logs from the Terminal:

rm -rf ~/Library/Logs/*

This is non-destructive to any app functionality. The worst outcome is that you lose diagnostic history if you need to file a bug report — which most people never do.

Step 3 — Free Purgeable Space and Local Snapshots

macOS APFS stores "purgeable" data — content that is already backed up to iCloud or marked as evictable — and counts it against your used storage until pressure forces it out. Time Machine also creates local snapshots on APFS volumes that can consume several gigabytes.

To list and delete local Time Machine snapshots:

# List snapshots
tmutil listlocalsnapshots /

# Delete a specific snapshot (replace the date string)
sudo tmutil deletelocalsnapshots 2026-05-15-031022

Alternatively, temporarily disabling and re-enabling Time Machine forces macOS to purge all local snapshots immediately:

sudo tmutil disable
sudo tmutil enable

On machines with iCloud Drive enabled, purgeable space often collapses on its own once you open a disk-space dialog or apply storage pressure — macOS waits for a trigger. Running a first-party tool that requests available space causes this purge to happen immediately.

Step 4 — Uninstall Apps and Remove Their Leftover Files

Dragging an app to Trash removes the .app bundle, but leaves behind support files, caches, preferences, and logs scattered across ~/Library. For a large app like Adobe Creative Cloud, these leftovers can exceed the app itself in size.

Leftover locations to check manually after dragging an app to Trash:

• ~/Library/Application Support/[AppName]
• ~/Library/Caches/[bundle-identifier]
• ~/Library/Preferences/[bundle-identifier].plist
• ~/Library/Containers/[bundle-identifier]
• ~/Library/Group Containers/[shared-group-id]

This is tedious to do by hand because bundle identifiers don't always match the app's display name. Crumb's Uninstall tab surfaces each app alongside all leftover files it finds on disk, so you can review and remove everything in one pass rather than hunting through Library folders manually.

Step 5 — Find and Remove Duplicate Files

Duplicates accumulate from download folders, project backups, and synced cloud storage. A file that was copied twice takes twice the space regardless of whether it's a document or a video. The safest place to look for duplicates is ~/Downloads and ~/Documents — not your Photos library, which already deduplicates its own assets internally.

To find large duplicate files from the Terminal using fdupes (install via Homebrew):

brew install fdupes
fdupes -r ~/Downloads ~/Documents

Review the output carefully before deleting. fdupes will list every set of byte-identical files; you decide which copy to keep.

Step 6 — Clear Browser Caches

Browser caches are safe to delete and often hold 1–4 GB on a regularly used machine.

• Safari: Safari menu > Settings > Advanced > Show features for web developers, then Develop menu > Empty Caches
• Chrome: Settings > Privacy and security > Clear browsing data > Cached images and files
• Firefox: Settings > Privacy & Security > Cookies and Site Data > Clear Data

What NOT to Delete

Not everything in ~/Library is expendable. Avoid deleting these without a clear reason:

If you're ever unsure whether a specific folder is safe to remove, that hesitation is worth acting on. Crumb's "Is this safe to delete?" AI explains what any folder contains and what the consequence of removing it would be — useful when you encounter an obscurely named directory and don't want to guess.

How Much Space Can You Realistically Recover?

Results vary by machine age, installed apps, and how long since the last cleanup. Typical ranges from doing all of the above:

• User caches: 3–15 GB
• Log files: 0.5–2 GB
• Local Time Machine snapshots: 5–20 GB
• App leftovers from uninstalled apps: 1–10 GB
• Browser caches: 0.5–4 GB

On a machine that hasn't been cleaned in a year or more, it's realistic to recover 20–40 GB without removing a single photo, document, or piece of media you intentionally kept.

One-Click Alternative for the Manual Steps

The cache, log, temp-file, and purgeable-space steps above are safe but repetitive. If you'd rather not navigate Library folders, download Crumb and run its one-click Clean — it targets the same locations (system caches, user caches, logs, temp files, purgeable System Data) automatically, and your Photos library is never in scope. The Visualize tab then shows a disk treemap so you can see what's still consuming space and decide what to tackle next.

Conclusion

Freeing up space on a Mac without deleting photos is not only possible — it's the correct first move. Caches rebuild themselves, logs are diagnostic artifacts, purgeable space is already earmarked for removal, and app leftovers are pure waste. Work through the steps above in order and you'll likely recover tens of gigabytes before ever needing to touch your photo library. Clean deliberately, understand what you're removing, and your memories stay exactly where you left them.