Find large files on a Mac without buying software

Large files rescue or ruin cleanup sessions. One forgotten virtual machine pays for an afternoon; misjudging a Library container loses irreplaceable data. Free built-in tools find the giants reliably, provided you interpret what they surface before acting on it.

Finder search by size, done properly

Start a Finder window on Macintosh HD, press Command-F, add a Kind filter set to Other, choose File Size, then Greater Than and enter a threshold around 500 megabytes. Switch scope from This Mac to the specific home folder when system locations distract. Results arrive unsorted; click the Size column to rank them. Giant installers, iOS backups, disk images and exported video dominate honestly run queries like these.

Sort the obvious jungles manually

Downloads, Desktop and Documents yield fast to manual sorting: open the folder, switch Finder to list view, sort descending by size. Manual passes catch oddly named behemoths search filters sometimes miss, such as database files without extensions or huge spreadsheets storing embedded media. Move winners immediately into a staging folder named for today before deciding their fate; momentum matters less than accuracy at this stage.

When trees beat searches

Finder searches individual files well yet stays mute about folders whose many medium entries accumulate into mountains. Depth measurements expose cumulative weight instead, which is precisely the situation where du commands printed folder costs line by line outclass search. Visual thinkers reach identical conclusions faster through treemap-style utilities surveyed in the analyzer comparison piece; both roads respect the same principle, measure branches before pruning.

Reading results responsibly

Three checks precede any delete button. First, provenance: do you recognize creating this file or app? Second, uniqueness: archives and personal projects lack replacement sources, unlike cached media streams. Third, location: items beneath Library or hidden system prefixes deserve suspicion rather than reflexive destruction. When identity remains uncertain, quarantine instead: relocate questionable giants onto an external drive and continue; reversibility costs disk rental pennies versus permanent loss.

Record what left

Note each removed item, its size and the justification in one line. Beyond satisfying curiosity later, logs convert future sessions from archaeology into maintenance. The printable sheet sitting on the field kit download page gives those lines structure, pairing naturally with the ordering discipline explained in the master cleanup sequence. Giants found and judged become reclaimed gigabytes; giants found and guessed become support tickets.

A threshold worth keeping

Whatever tool finds them, keep one constant number in your head as the notice-me line, five hundred megabytes is a serviceable default on any modern Mac. Files below it rarely justify solo attention; collections of small files below it matter only in aggregate, which folder-level measurements from the du walkthrough surface instead. Thresholds turn an open-ended hunt into a bounded pass, and a bounded pass finishes, which is the difference between an audit and an afternoon that disappears into Library folders nobody should be browsing casually anyway.

A five-minute starter sweep

Readers wanting proof before commitment can time-box the whole craft tonight. Set a timer for five minutes; open Downloads, sort by size, drag anything older than one year into a folder named Quarantine rather than Trash; empty the main Trash when the timer ends and rerun your measurement. That single bounded sweep demonstrates every principle this page teaches at pilot scale: threshold thinking, quarantine instead of destruction, before-and-after honesty. Whatever the yield, the habit it teaches pays for years, and the printable record of it starts your ledger worksheet off with its first honest line.

Grouped suspects that single-file searches miss

Size-ranked searches answer "which file", but households usually need "which habit". Two groupings repay attention after the giants are handled: installers and archives scattered across Desktop folders, harmless individually yet heavy in chorus; and export outputs from editing apps, which regenerate with every project and belong in dated archive folders rather than on the working drive. Neither grouping shows under a five-hundred-megabyte filter because neither owes its weight to one file. Folder totals from the du walkthrough catch what filename hunting cannot, which is why both passes share every serious audit this desk runs.