Find large files on your Mac.
And see the space they really use.

1. In Storage settings

Go to System Settings → General → Storage, click ⓘ next to Documents, then Large Files. You can sort by size and delete from the list. It only looks in your own documents, not in app data.

2. With a Finder search

1. Open Finder and press ⌘F.
2. Choose This Mac or a specific folder.
3. Click the Kind menu, choose Other…, tick File Size and click OK.
4. Set it to is greater than 500 MB.
5. Click Save to save the search as a Smart Folder if you want to check again later. The + button adds another search criterion.

3. In Terminal

# files over 1 GB in your home folder
find ~ -type f -size +1G 2>/dev/null

# the 20 largest items in a folder, by space on disk
du -sh ~/Downloads/* 2>/dev/null | sort -h | tail -20

Why a file can look bigger than it is

Some files report a size far larger than the space they occupy:

• Sparse disk images, such as Docker's Docker.raw, claim their maximum size but only use what is written. Finder may say 60 GB while the file uses 4 GB.
• Files kept in iCloud only show their full size but take almost nothing on your Mac. Deleting one removes it from every device.
• Copies made with Finder's Duplicate command can be APFS clones that share storage, so deleting one may free less than its logical size.

du reports space on disk; Finder's size and ls -l report the size a file claims.

Decide what “large” means for this job

Searching for files larger than 500 MB is a useful starting example, not a universal cleanup rule. If you need room for a small document, an old installer may be enough. If you are preparing a video export, the output and temporary working files may need a much larger margin. Start with the space requirement of the task that failed.

Keep the search scope deliberate. A folder search answers what is large inside that folder. A This Mac search is broader but still depends on what Finder can find and what you can access. A missing result does not prove a file is absent from the disk, particularly when it is in application-managed storage or an excluded location.

Inspect a result before deciding it is unnecessary

In Finder, look at the path as well as the name. A file called final.mov could be an export you can recreate, the original recording, or the only copy delivered by a client. Use Quick Look or open it in the owning application when that helps establish its purpose. A filename is not a retention policy.

Check modification and last-opened information as clues, not proof. A file can remain important without being opened recently, and a background application can touch a file without you using it directly. If the item belongs to a shared project, confirm its role before removing it.

For a folder, examine a few levels rather than trashing the whole parent. One large child may be replaceable build output while another contains source material. This is where the System Data investigation and application-specific storage controls become more useful than a broad search.

Use a short decision table

An example of choosing the right action

Suppose a Downloads search finds an exported presentation video, a disk image and an archive containing a current project. This is an illustrative example, not a scan result. The disk image may be a simple candidate after confirming the app is installed. The video needs a check against the original presentation. The archive may be the recovery copy you need to keep.

Moving all three to the Trash because they meet the size filter would ignore those differences. A better outcome might be deleting the installer, archiving the video to a backed-up external disk, and keeping the project archive until another recovery copy is verified. The goal is usable space with an understandable recovery plan.

How to read Terminal results carefully

The find command above lists matching files and does not delete them. Permission errors are hidden by its final redirection, which makes the list easier to read but also means it is not a complete account of protected locations. If completeness matters, examine those limitations rather than assuming the output represents every byte on the Mac.

The du example compares non-hidden items matched by the shell in Downloads. Files beginning with a dot are not included by a simple asterisk. Empty folders, unusual names and application packages also need interpretation. These commands are inspection aids, not a reliable input for an unattended removal script.

Check what happened after the change

Record the same available-space measurement before and after your chosen action. A move to another folder on the same disk is organization, not storage reclamation. A move to the Trash leaves the item recoverable but usually still occupying space. Copying to an external disk also leaves the original until you deliberately remove it.

If an archived project needs linked media, test the archive from its new location before emptying the original from Trash. Keep the backup separate from the working archive where possible. The fact that a copy operation completed does not establish that every application dependency was captured.

Questions about large-file searches

Why does Finder show less than a disk analyzer?

The tools may have different access, search scope and size definitions. Finder results may omit app-managed or unindexed locations, while an analyzer may report allocated folder sizes. Compare the path and measurement being shown before treating the numbers as contradictory.

Can I delete a large file inside Library?

Only after identifying its owner and purpose. A large file can be a cache, a database or an entire virtual machine. Follow the relevant application’s controls rather than assuming that a hidden location makes the file disposable.

Should I keep searching after I have enough room?

Not necessarily. Finish the task that required space, then make a longer-term storage plan if growth keeps recurring. Stop when the next candidate is uncertain rather than chasing the largest possible cleanup total.

Can I search an external drive the same way?

Choose that drive or a specific folder as the search scope and check what the filesystem and permissions allow. Do not assume that cloud behavior, APFS sharing or Trash handling matches your startup disk in every case. Verify the selected path and the owning application before changing a large package or project on another volume.

References

• Apple: free up storage space on Mac
• Apple: narrow Finder search results