How to Find Large Files on Mac

A single 40GB virtual machine image or a folder of untouched 4K video exports can do more damage to your free space than months of accumulated caches and browser junk combined. When you're trying to work out what is taking up space on Mac, it's tempting to reach straight for a general cleanup — clearing caches, emptying the Trash, removing a few unused apps. Those steps genuinely help, but they chip away at a problem that's often dominated by a small number of oversized files sitting quietly in ordinary folders. Learning to find large files on Mac first is usually the fastest way to actually free Mac storage, and it's worth doing before you spend time on smaller clutter.

Why a few large files matter more than you think

Junk files — logs, temporary data, small caches — tend to be numerous but individually tiny. You can delete a thousand of them and reclaim a few hundred megabytes. A large file finder Mac users actually need looks for the opposite pattern: a handful of files, each measured in gigabytes, that got created once (a screen recording, a client video render, a downloaded disk image) and were simply never cleaned up afterward.

The reason these files are so easy to miss is that they don't behave like clutter. They don't multiply, they don't show up in every folder, and they usually live somewhere reasonable — Downloads, a project folder, a Photos library. Nothing about them looks wrong at a glance. But storage math doesn't care whether a gigabyte came from one file or ten thousand; a few large files can be the difference between a Mac that feels fine and one that's throwing "storage almost full" warnings.

There's also a practical argument for starting here rather than with general cleanup: reviewing ten or twenty large files takes minutes, while sorting through thousands of small cache and log files takes much longer for a fraction of the space. If you're short on time and just need to free Mac storage quickly before a system update or a big project, large files are almost always the higher-leverage place to look first.

Where large files commonly hide

Before searching, it helps to know what you're actually looking for. Some of the most common sources of wasted space include:

• Old video exports and renders — final cuts, intermediate renders, and screen recordings from projects you finished months ago and never moved off the internal drive.
• Virtual machine disk images — files like .vmdk, .vdi, or .qcow2 created by Parallels, VMware, VirtualBox, or UTM. These are often pre-allocated to a fixed size and can sit at 20–100GB even when barely used.
• Xcode DerivedData and simulator files — developers routinely accumulate tens of gigabytes in ~/Library/Developer/Xcode/DerivedData and old iOS Simulator devices that are never removed.
• Photos library originals and duplicated exports — full-resolution originals stored alongside exported copies of the same photos or videos, effectively doubling their footprint.
• Old Time Machine local snapshots — macOS keeps local backup snapshots on your internal drive between backups; these are usually managed automatically but can occasionally linger longer than expected.
• Large email attachments saved to disk — video files or archives someone sent you that got downloaded once and forgotten in Downloads or a Mail Downloads folder.
• ISO and DMG installers — installer images for apps or operating systems that are still sitting around long after the software was installed and is running fine.
• Forgotten downloads — the Downloads folder in general, which for most people is the single largest source of files nobody remembers keeping.

How to find large files using Finder

Finder can search for large files without any extra software, and it's worth knowing how to do it manually:

• Open a new Finder window and press Cmd+F to start a search.
• Set the search scope to This Mac (not just the current folder) so it covers your whole drive.
• Click the + button to add a search criterion, and change the first dropdown to File Size, the second to is greater than, and enter a threshold — 500MB is a reasonable starting point.
• Once results appear, switch to list view and click the Size column header to sort with the largest files first.

This works, and it costs nothing, but it has real limits. A full "This Mac" search is slow — Spotlight has to crawl a huge portion of your file system — and it can still miss files in locations that are hidden, inside app bundles, or otherwise excluded from Spotlight indexing. It also doesn't distinguish well between a file that's fully downloaded and an iCloud placeholder that only looks large but hasn't actually been pulled onto your disk yet, which can make the results confusing to interpret. It's a fine tool for a quick check, but it isn't a complete answer to what is taking up space on Mac.

Finding large files with Terminal (advanced)

If you're comfortable in Terminal, command-line tools can dig up large files more directly than Finder's search. For example, this command lists every file over 500MB in your home folder:

find ~ -type f -size +500M

The du command is useful for finding which folders are largest rather than individual files. A common pattern is running something like du -sh */ | sort -rh from a folder you suspect is bloated, which lists subfolders sorted from largest to smallest so you can drill down toward the actual offending files.

This approach is genuinely powerful, but it's aimed squarely at technically comfortable users. It's easy to point these commands at the wrong directory, misinterpret sizes reported in different units, or run into permission errors when a search reaches system-protected folders. There's also no built-in safety net — Terminal will show you a path, but it won't tell you whether that file is safe to remove or something a running app still depends on. If any of that sounds like more risk than you want to take on, a graphical tool that presents results in a clear, sorted list is the safer route.

What to do once you find a large file

Finding a large file is only half the job — the next step is deciding whether it's safe to remove. A quick process that works well:

• Check when it was created or last modified. A render from a project you shipped a year ago is a very different decision than a file from yesterday.
• Open it if you're unsure what it is. A quick preview (Space bar in Finder works for most file types) usually tells you immediately whether you still need it.
• Archive it if there's any doubt. Moving a file to an external drive or a cloud storage service gets it off your internal disk without permanently losing it.
• Delete it if you're confident you don't need it — but remember that moving a file to the Trash doesn't free up space on its own. You have to empty the Trash afterward for the space to actually be reclaimed.

If your Mac is already showing storage warnings rather than just running low, our guide on what to do when Mac storage is full covers the more urgent version of this process. And if large files turn out to be only part of your problem, the broader guide to freeing up space on Mac walks through caches, unused apps, and everything else worth checking.

A faster way: automatic large file scanning

Manually searching Finder or running Terminal commands works, but neither gives you a single, reliable answer to "what's actually taking up my space" across the whole drive. CleanMyApple's large file finder scans your entire Mac and presents the biggest files it finds in one sorted list, so you're reviewing a short set of real candidates instead of hunting folder by folder. It only identifies and presents files for you to review — nothing is removed until you confirm it, and anything you do delete goes to the Trash like normal, so it's never a one-way action.

Between the two approaches, the right one depends on how often you expect to do this. A one-off check before a big project is fine to do by hand in Finder. If storage keeps creeping back up every few months, a tool built specifically to find large files Mac-wide will save you from repeating the same manual search every time.