How to find large files on Mac
A handful of large files usually accounts for more space than everything else combined. Finding them takes a minute with tools you already have; knowing which ones you can let go of takes one extra column.
With Finder, in about a minute
Where Finder falls short
Finder measures files, not folders. It will happily show you a 4 GB video and stay silent about a cache folder holding 60 GB in eighty thousand small files — which is exactly how most Macs actually fill up. It also cannot see inside library packages or report on space macOS considers system data. A file-by-file search answers "what is my biggest file", not "where did my disk go".
The Terminal one-liners
- du -sh * inside a folder prints the size of each item in it, one directory level at a time.
- du -h -d 1 ~ does the same for your home folder and is usually where the surprise is.
- find . -type f -size +1G lists every file over a gigabyte under the current folder.
- df -h shows what the volume itself reports as free, which is often not what Finder shows.
- All of them skip folders they lack permission to read, and none of them draw you a picture.
Why a map beats a list
A list of the twenty biggest files tells you about twenty files. A map sized to scale tells you which branch of the disk is heavy, which is the question you actually have. Once you can see that Developer holds 148 GB, the individual filenames stop mattering — you delete the branch and move on. Sift draws the whole volume as one three-ring map, then offers a Large and old view: over 1 GB, untouched for six months, with the date you last opened each one and nothing pre-selected. Scanning and browsing are free forever.
Map your disk with Sift — scanning is freeCommon questions
How do I find files over 1 GB on Mac?
Press Command-F in Finder, choose This Mac, then set File Size is greater than 1 GB and sort by size. For a whole-disk picture including folders and caches, use a disk space analyzer instead.
Where are the biggest files usually hiding?
Downloads, Movies, the Photos library, virtual machine images, and on developer machines the Xcode folders in ~/Library/Developer. Disk images and old macOS installers are the most commonly forgotten.
Is it safe to delete a large file I do not recognise?
Check its path before its name. Inside your own Documents, Downloads or Movies you are on solid ground. Inside a Library folder or a system path, leave it: it may be app data something depends on. Sending it to the Trash first keeps the decision reversible either way.