While Photo Stream is a great feature of iCloud, if you self manage your iPhone photos, it can quickly end up eating tons of disk space on a Mac hard drive. How, might a reasonable individual ask? Well, it may be unintentionally adding duplicates of all the photos you’re already importing yourself. This happens because Photo Stream automatically copies images from the iPhone (or iPad and iPod touch) to the Mac. But if you’re self managing your photo collection, you’re doing this as well, thus you’ll end up with duplicates stored on the hard drive, whether you know it or not, and those dups can add up to a lot of storage space rather quickly.
Where are the Photo Stream duplicates stored? A not-so-little directory called iLifeAssetManagement. Thus, if you do not rely on Photo Stream to bring iPhone pictures to a Mac, then you will probably want to turn the feature off, and in doing so you might just save many gigabytes of precious drive capacity in the process. This is somewhat complicated, and is therefore a good addition to the other , particularly because it turns off a major feature of iCloud in OS X.
Before beginning, let’s define self management for iPhone photos, because that is who this is going to apply to: in short, that means you transfer pictures from the iPhone to the Mac yourself, manually with a USB connection, through one of the various methods of transfer to copy pictures to the computer using apps like iPhoto, Image Capture, or Aperture, treating the iPhone as if it was a regular digital camera. In other words, you do not rely on Photo Stream to get the pictures from an iOS device automatically copied to something like iPhoto on the Mac, and you do not use the trick to gain . This means you do not use iCloud’s Photo Stream on the Mac at all, this needs to be made abundantly clear because this trick depends on disabling the stream feature in OS X.
Manually back up iLifeAssetManagement before proceeding. This is important. You will want to do this because the folder contains pictures, and it’s up to you to find out whether you have those stored elsewhere or not. It’s better to play it safe and back the folder up then to potentially lose photos you don’t have saved already. Manually backing te directory up is just a matter of copying it onto an external backup drive that has abundant storage. This insures that if you discover you did actually use Photo Stream or you did need those pictures after all, you can get them all back quickly.
Backed up? Good, now let’s free up the disk space by ditching this folder and stopping it from refilling itself.
Now that you have iLifeAssetManagement backed up (just in case), let’s turn off Photo Stream completely. This is necessary otherwise the iLifeAssetManagement folder will just create itself again after you’ve deleted it.
You’ll notice that the control panel says something about images being deleted from the computer, and that’s great but it doesn’t always happen right away. Thus, the next step is to manually ditch the folder and recover all the disk space it has been consuming.
On some occasions, the content of this folder will already have been removed by the previous step, but it can be faster to just manually delete the folder yourself:
You can also delete the entire iLifeAssetManagement folder if you want, though deleting the sub folder is the most precise. If the /Library/Application Support/iLifeAssetManagement/assets/sub/ is even 1/4 as large as it was on my Mac, it can take quite a while to delete, so just let it go.
Also, as we mentioned in Step 2, don’t just trash that folder without disabling Photo Stream, otherwise the folder will just recreate itself and repopulate with all the images you deleted.
How much space does removing iLifeAssetManagement and turning off the Photo Stream duplicates free up? This is going to vary widely per user and how many photos they take with their iPhone, but in my case I freed up 18GB (!) of space. That’s roughly 1/6th of all available storage on this MacBook Air 128GB SSD, just by deleting a folder that I forgot existed, created by a feature I never use.
If you import your own iPhone photos and don’t use Photo Stream, I highly recommend looking into how much disk space iLifeAssetManagement is taking up on your Mac. It’s fairly easy to not notice this ‘feature’, let alone that it’s storing images on your hard drive, until it’s too late and suddenly your Mac is out of hard drive space. Whether that’s user error, or (more likely) because this aspect of iCloud and Photo Stream is just not explained well, who knows, but even the images inside the directory are not easily accessible (go dig around in iLifeAssetManagement, it’s a disaster with each individual image stored in it’s own subdirectory… who on earth thought that was a good idea?), and combined with it eating up a lot of disk space it’s ultimately far more annoying than helpful for those of us who import manage photos from iOS ourselves.
Before deleting the folder, or if you just want to recover the pictures from the backup you made, here’s what you’ll want to do:
That’s the easiest method, but offers an AppleScript that may or may not work for you to do this as well, it did NOT work in our testing and just crashed the Finder in OS X 10.8 (perhaps due to the huge folder size in our case), nevertheless, the guy who runs 512pixels is a smart cookie so it’s probably worth a shot if you’re determined to go the AppleScript route and don’t mind tweaking the script slightly.
Got another solution? Let us know on , , , or send us an . Comments are still disabled.