How to Find the Largest Files on Your Mac (and Decide What to Delete)

The first time you really need to free up space on a Mac, you’ll waste an hour clicking through folders looking for something obviously huge. There’s a better way. macOS has had decent file-size search for years — it’s just buried two or three levels deep in menus.

This guide covers five ways to find the biggest files on your Mac, ranked roughly by speed and ease. Use whichever fits the moment.

Method 1: The Storage screen’s secret weapon

This is the fastest built-in option, and most people don’t know it exists. Apple menu → System Settings → General → Storage. Wait for the bar to populate. Then click the small “i” button next to any category — Documents, Applications, Mail, anything with an “i.”

On Sonoma 14 and Sequoia 15, the panel that opens is sortable by size. For Documents specifically, it shows you every file in your home directory’s user-accessible folders, sorted largest first. You can delete directly from this view.

Limitations: it only covers a handful of categories. It won’t find files inside /Library, /var, or other system locations. For the user-facing stuff that’s typically the worst offender, it’s perfect.

Method 2: Finder’s “All My Files” search

Open any Finder window, hit Cmd+F. Then:

1. Set Where: “This Mac” (top toolbar)
2. The default first criterion is “Kind” — click it and change to “File Size”
3. Set the operator to “is greater than”
4. Enter “1 GB” (or whatever threshold you want)

You’ll get a list of every file over your size threshold, anywhere on your Mac. Click the Size column header to sort largest first. Right-click any file → Show in Enclosing Folder if you want to see what’s around it.

This catches everything. Including things you should not delete. Specifically:

• *.dylib and *.framework files in /System or /Library — leave these alone
• Files inside .app bundles — these are part of an installed application
• Anything in /private/var — system stuff

If a file’s path starts with /System, /Library/Frameworks, /private, or is inside a .app package, skip it.

Skip the manual huntSweep finds every cache, log, and forgotten file in seconds — and only removes what you OK. Download Sweep free →

Method 3: Terminal for the impatient

If you’re comfortable in Terminal, this is the fastest method by a mile. To find every file larger than 1GB in your home folder:

find ~ -type f -size +1G -print 2>/dev/null

To get them with sizes, sorted:

find ~ -type f -size +500M -exec ls -lh {} \; 2>/dev/null | sort -k5 -hr | head -50

The 2>/dev/null part hides “permission denied” errors for folders you can’t read. The head -50 caps the output at 50 results — adjust as needed.

For the entire system (will need sudo for some folders):

sudo find / -type f -size +1G -exec ls -lh {} \; 2>/dev/null | sort -k5 -hr | head -50

A few minutes to run, but it returns the absolute biggest files anywhere — including system caches and logs that Finder won’t show you by default.

Method 4: Disk Utility for a different angle

Disk Utility doesn’t directly show file sizes, but it’s the most accurate place to see actual used vs. free space. Open Disk Utility, click Macintosh HD, and look at the top.

More usefully: Disk Utility → View → Show APFS Snapshots. This shows you every Time Machine local snapshot eating space — often 5-30GB worth. You can delete individual snapshots from this view by selecting one and hitting the minus button. macOS does eventually clean these up automatically, but you can force the issue.

Method 5: A purpose-built scanner

For most people, the right answer isn’t manually clicking through Finder. It’s letting something scan the whole disk and present a sortable list with one filter for “stuff that’s safe to delete” and another for “stuff that’s part of macOS.”

Sweep does this in about 90 seconds across the whole startup disk. The “Large Files” view sorts everything by size and pre-categorizes which files are safe to remove (orphaned downloads, abandoned project folders, old DMG installers) versus which are tied to active apps. Nothing gets deleted without your approval.

If you’d rather not install anything, the Finder search method covers most cases. It just doesn’t pre-judge what’s worth keeping.

Make this a one-click jobSweep does the same hunt in seconds. Always shows you what’s about to go. Free for macOS →

Common file types and what to do with each

Once you’ve got a list of big files, here’s how to think about each category:

• Old DMG and PKG installers in Downloads — almost always safe to delete. You can re-download from the original source if you ever need them.
• Video files (.mov, .mp4) over 1GB — check if they’re current projects. If not, move to external or cloud.
• Disk images (.dmg, .iso, .vmdk) — installers can usually go. Virtual machine images need a decision: are you still using that VM?
• Database files like Library.musiclibrary (Music), *.photoslibrary (Photos), .mailbox (Mail) — never delete directly. Use the app itself to manage size.
• *.cache and files in any Cache folder — safe to delete. Apps rebuild as needed.
• *.log files — safe to delete. New ones get created automatically.
• *.framework and *.dylib — never delete unless you really know what they are. They’re shared libraries that apps depend on.
• Files inside .app bundles (right-click → Show Package Contents) — never delete. Either keep the whole app or uninstall it cleanly.
• *.crash and *.diag files — these are crash reports. Safe to delete; you don’t need them unless debugging.

Folders worth checking by hand

Even with great search tools, certain folders are worth eyeballing because the bloat is structural rather than from individual large files:

1. ~/Library/Caches/ — many small cache folders that add up
2. ~/Library/Application Support/ — folders for apps you uninstalled long ago
3. ~/Library/Containers/ — same idea, but for sandboxed apps
4. ~/Library/Developer/ — only if you’ve ever opened Xcode (often 30-60GB)
5. ~/Library/Mail/ — Apple Mail’s local attachment cache
6. ~/Library/Application Support/MobileSync/Backup/ — iOS device backups
7. /Users/Shared/ — sometimes apps drop installer data here
8. ~/Movies/ and ~/Documents/ — your own forgotten files

In Finder, hit Cmd+Shift+G and paste any of these to jump directly. Then use the Cmd+J view options panel to enable “Calculate all sizes” so folder sizes show up next to folder names.

What to do once you’ve identified candidates

A few rules that will save you trouble:

• Don’t shift-delete anything in your first pass. Drag to Trash, restart your Mac, use it for a day, then empty Trash. If something broke, you’ve got an easy rollback.
• Quit the relevant app before deleting its files. Mail, Photos, Music — none of them like having their database files yanked out from under them.
• Move, don’t delete, when uncertain. Copy big files to an external drive first. Once you’ve lived without them for a week, delete from the external too.
• Skip System Integrity Protection-protected files. If macOS asks for your admin password and refuses even with it, that file is meant to stay.

The single biggest mistake people make is deleting framework files inside /System/Library/Frameworks because they showed up in a “biggest files” search. Don’t. They’re protected for good reason. Even if you successfully delete them, you’ll break apps that depend on them.

Finding big files is easy with any of the methods above. The decision-making is harder, and it’s where you should slow down. A 4GB video file that takes you back to a great trip is not the same as a 4GB cache from an app you uninstalled two years ago. Treat them differently.