Save Mac storage space by cleaning out abandoned log files

Whenever I have a mystery to uncover about lost storage space, I fire up DaisyDisk, a disk-usage visualization app. While the $9.99 price tag may seem steep for its purpose of plotting out what is occupying your drives’ storage, I find it invaluable in tracking down the giant sucking sound of lost space. It’s also a lot cheaper than buying a larger drive. (There’s also a free trial that lets you test out many features.)

Recently, my MacBook Air’s 512GB of storage was running low. With just 50GB left, I start to get nervous about running out of space when the system needs to write temporary files to disk or I need to transfer large files. DaisyDisk revealed the culprit: an ocean of abandoned log files.

Log files are critical troubleshooting tools, but little else. When you contact technical support, you’re often asked to find and send a log file, or enable a feature in software to dump extra debugging information to a log that you can send the next time a problem occurs. I know many a bug that was squashed because tech support could check my logs and figure out the description I gave them of what occurred.

IDG

IDG

IDG

But a lot of software is terrible at log purging. These apps or processes write log files and then abandon them willy-nilly. One thousand 1MB files adds up. My laptop is the end migration of many, many years of previous laptops, and there were nearly 25GB of log files, none of them useful in any way to my current needs. Stamps.com left a 5GB footprint of miscellany behind, and Adobe scattered years of multi-megabyte files that serve no discernable purpose.

You can find most of your log files in your home directory at ~/Library/Logs. In the Finder, choose Go > Go To Folder and paste that path in. You can then sort by size to see the biggest culprit, and sort by date to find ancient log files no longer needed. If a log files hasn’t been touched by software in a few days or longer, you can typically just delete it. If it’s an enormous file and has a recent date stamp, I suggest making sure the associated app isn’t running and then you can delete the log file.

Ask Mac 911

We’ve compiled a list of the questions we get asked most frequently along with answers and links to columns: read our super FAQ to see if your question is covered. If not, we’re always looking for new problems to solve! Email yours to mac911@macworld.com including screen captures as appropriate, and whether you want your full name used. Not every question will be answered, we don’t reply to email, and we cannot provide direct troubleshooting advice.