Jay Taylor's notes

back to listing index

osx - How can I figure out what's slowly eating my HD space? - Ask Different

[web search]
Original source (apple.stackexchange.com)
Tags: os-x hdd apple.stackexchange.com
Clipped on: 2013-04-04

I've had a very similar issue, and so I decided to compile several methods for solving it. So, following, there are those options and some of them I got from the answers already provided here. I understand this is a little bit offtopic from the question, but it's in tune with the answers. This has many parts and those are all softwares I could try myself somehow.

update: It's generally a good idea to pay close attention for using the sudo options below so the software can have access to every file, which will likely include some big hidden ones.

Here's a brief list of apps for checking the disk usage:

  • Image (Asset 1/11) alt=

    There is also a different approach, of apps for scanning specific expected places and files for space usage in non-optimal ways. They basically gather some known things about the system that can be bloating your disk all in one nice interface so you can see and decide what to delete.

    • Image (Asset 2/11) alt= CleanApp is basically the same as CleanMyMac: lists applications, preference panes, languages, caches... But it also adds community to it - shows how many people deleted each file or bundle. There's yet another feature, the logging, which logs for activity of moving files and running apps, and all the "links" it can find for each thing. It's much more technical and detailed. It also offers a Treemap kind of view, but I'd highly advise using another option for that.

    • Image (Asset 3/11) alt=

      Another approach is looking for duplicate files. There are many commercial options, some may be better than the listed below, I haven't tried them all. Anyway, I'm listing my choice of apps considering which ones I was able to try.

      • Image (Asset 4/11) alt=

        Next I'll briefly discuss on a similar approach by quoting relevant parts about two other things that can be done to look for missing disk space, without installing anything new, just using the command line (the Terminal).

        This (long but good) one is from MacFixIt forums (go there for more options and details):

        In most cases, there really are files occupying part of the volume, but the files are invisible in normal use of the Finder.

        Using the Finder’s Go to Folder feature (in the Go menu), look at the sizes of the contents of these folders, by pasting in these pathnames:




        The /private/var/vm directory contains the swapfiles used by virtual memory. New ones are made as more data is swapped from RAM to the hard drive. The entire process of creating them begins at each reboot or restart; do not attempt to remove them yourself. Check the total size of all the swapfiles, right after you boot, and as the disk fills up. In Panther, the first two swapfiles are 64MB, then each new one is twice the size of the preceeding one (128MB, 256MB, 512MB, 1 GB) up to a maximum size of 1 GB. In Tiger, the first two swapfiles are 64 MB, the next one is 128 MB, and any additional swapfiles are 256 MB.

        If you do not run the daily, weekly, and monthly maintenance scripts (either by using a utility, or by running the commands sudo periodic daily, sudo periodic weekly, and sudo periodic monthly in Terminal), the logs on the startup volume can become too large. If an error is occurring frequently and is being logged, you can have a very large file at /private/var/log/system.log.

        The files in /Volumes should be aliases to your mounted volumes. Do not remove these aliases, because anything you do to them happens to the contents of the corresponding volumes. If you are not confident that you can explore this folder without mishap, before you begin, properly unmount any volume other than the startup volume, if the missing disk space problem affects only that volume. External FireWire drives can be disconnected after proper unmounting.

        Sometimes, backup programs that cannot find an intended destination (or target) volume for a backup create a folder with the same name as the destination, and put the folder into the /Volumes directory. There are cases in which the entire startup volume has been backed up on itself, in a folder inside /Volumes. If the amount of missing space is about the size of your user folder, such a backup is likely to be the explanation. If you use Carbon Copy Cloner or another backup or cloning utility and have its preferences configured to create a backup on a schedule, and the intended destination volume is not mounted or is sleeping at the scheduled time, the backup is created in the /Volumes directory.

        To check the size of the normally invisible /Volumes directory on the active startup volume, open a new Finder window. Select the startup volume in the list at the left, then choose column view (the one at the right of the three views). From the Finder’s Go menu, choose Go to Folder, and paste in:


        The /Volumes directory becomes visible in the Finder; find its size by selecting it and typing Command I. My /Volumes directory is reported to be 12K.

        This other one is from Mac OSX Hints forums (not much more to see there):

        You may want to run a du in terminal to see what is all going on. This could take a few minutes to run.

        An example would be to open up terminal.app then run these commands:

        sudo du -h -d 1 -c /

        Input your password when it prompts for it then let it go, it will take a few minutes to run so be paitent.

        du stands for Disk Usage. There's also df. I like including the -x to the above command:

        sudo du -cxhd 1 /

        Adding to that command line option, I just tested something that might work very nicely. You can mix any of the before mentioned apps (I tested this with Grand Perspective just because I've been using it for longer) with this:

        Image (Asset 5/11) alt=

        Finally, there's a complete newbie guide on "The X Lab" that I just won't quote here for it's too long.