Photos for Mac: A Take Control Crash Course
by Jason Snell

Price: $10
More Info


Follow us on


Table of Contents

Import from iPhoto into Photos

If Photos is the spiritual successor to iPhoto, it’s only right that Photos can import your iPhoto library, and do so while keeping it intact—more or less . Because the features of Photos don’t align precisely with those in iPhoto, some information from iPhoto ends up in unexpected locations.

**①** An iPhoto library (left) migrates to Photos (right).

An iPhoto library (left) migrates to Photos (right).

You’ll need to get used to the changes in Photos—and be prepared to change your approach to organizing your media—but Apple has worked to make the migration process as painless as possible.

First Time’s the Charm

The first time you launch Photos, it searches your system for iPhoto and Aperture libraries. If only one library fits the bill, it imports that library. Otherwise, it opens the Choose Library dialog (see Use Multiple Photos Libraries). Choose a library from the list, and Photos prepares the library for import.

In some cases, OS X may import your iPhoto library before you ever open Photos. Don’t worry—iPhoto will warn you if this has happened, and you can delete that unedited Photos library and re-import from iPhoto at any time without penalty.

Note: Want to consolidate multiple iPhoto libraries prior to import? See Consolidate iPhoto Libraries, ahead.

Import Any Time

Hold down Option when you launch Photos to bring up the Choose Library dialog. From that dialog, you can select any iPhoto or Aperture library to import.

Don’t Use iCloud (Yet!)

On first launch, Photos asks if you’d like to use iCloud Photo Library. I strongly recommend that you decline for now, and read the Sync with iCloud Using Photos chapter before committing.

Don’t worry—it’s quite easy to turn on iCloud Photo Library at any time.

Behind the Scenes

When you import an iPhoto library into Photos, your existing library remains intact. The net result of the import is that you’ll have two separate libraries on your Mac’s drive: your old iPhoto library and a new Photos library . They’ll even have the same name—unless your library contained the word iPhoto, in which case you’ll see it replaced with the word Photos. (So a library called 2010 iPhoto Library will be imported to a library called 2010 Photos Library.)

**②** Your iPhoto library remains intact (left), but a new Photos library (right) comes into being.

Your iPhoto library remains intact (left), but a new Photos library (right) comes into being.

If you have a large library, you’re probably worried that a second version of the same library will take up twice the space. But in fact, importing an iPhoto library into Photos uses almost no additional disk space. See the nearby sidebar, “Hard Facts about Hard Links,” for the nerdy details.

Note: Once your iPhoto library has been imported into Photos, you can continue to use iPhoto as before. But if you edit an image or add a keyword in iPhoto post-import, those changes won’t transfer to Photos. For all practical purposes, the libraries have become two completely separate sets of data.

On import, Photos makes hard links to all iPhoto media assets in the new Photos library it’s creating, using the same directory structure as iPhoto . Think of a hard link as a cousin of a Finder alias—rather than existing in one place with an alias in a different location, a file that is hard linked appears to live in two places at once, but takes up only the space of a single file.

**③** The libraries say they’re roughly the same size, but in fact, they’re sharing disk space via hard links.

The libraries say they’re roughly the same size, but in fact, they’re sharing disk space via hard links.

So what happens if you edit one of those files? Something clever, it turns out: if I use Photos to edit a file imported from iPhoto, the version in the Photos library is altered—but the version in the old iPhoto library remains untouched. Basically, the act of modifying a hard-linked file (in either library) will cause the link to break. Now there are two different files, both taking up disk space, living independently.

For Mac users accustomed to the a-file-is-a-file approach of the Finder, this one’s a bit of a head-scratcher, but it’s a smart move by Apple to allow us to migrate to Photos without duplicating an entire library and eating all of our free disk space—or worse, never bothering to upgrade to Photos because we don’t have the room.

Making the Move

Apple has endeavored to transfer your data from iPhoto to Photos, even though several features (Events, star ratings) no longer exist. Here’s a guide to what gets imported, and what has changed during the transition.

What’s Still There

What’s Missing

**④** Photos doesn’t have a concept of Events, so iPhoto Events are imported as albums.

Photos doesn’t have a concept of Events, so iPhoto Events are imported as albums.

Note: Instead of rating photos with stars, Photos wants you to think binary: photos are Favorites, or they’re not. Mark a photo as a Favorite by clicking the heart icon in the upper-left corner or pressing the Period (.) key.

Catch a Falling Star Rating

Star ratings are gone from Photos, but if you used star ratings to organize your photos, that information hasn’t been lost. Upon import, Photos transmogrifies every star rating into a special keyword. A photo you gave three stars in iPhoto will appear in Photos with the keyword 3 Star.

If you have existing smart albums tagged to ranges of star ratings, Photos will update them to search for the proper set of star-based keywords. You can create new smart albums, too, that take advantage of those particular keywords.

As you add new photos, you can either:

Share this tip and chapter on

“Photos for Mac doesn’t support iPhoto’s star ratings or Events, but they’re imported as keywords and albums.”

Discuss “Import from iPhoto into Photos” via
comments powered by Disqus