Mac Photos app

[cappers]

Even though I do not have the ‘copy items to the photo library’ ticked/checked within the photo app on my Mac, whenever I import photo into the app, the photos library.photolibrary file still becomes bloated and increases with imports.


Why is this? Surely if it is not being imported it should not, or only very marginally with only a reference to the location of the photo. Seems rather excessive if this is all it needs?

 

[chabig]

All photos imported into the Photos app are stored in its library. The small text below the ‘copy items to the photo library’ explains that the setting affects iCloud behavior.

 

[cappers]

Research showed me that;

• A managed Library: This is the default. With "Copy items to the Photos Library" enabled, Photos will import the photos and store a copy of the original photo inside the library. This way the photos are protected and you do not risk to delete them accidentally.
• A referenced Library: Photos does not create a copy inside the library, but is referencing the photo you added in the original location. You are responsible to keep track of the location of the original files. You must not delete ore modify, or move the original file after you added it to Photos, because there will be no copy in the Photos Library. This is a risky set-up, because it is not well supported in Photos:

Based on this it should not import and only makes a reference to where the file is stored rather than importing an actual copy. This does not explain why the the photos library.photolibrary file still becomes bloated and increases with imports if it unchecked. It shod only reference the photos not import?

 

[chabig]

Managed library is the default as you said, and the library will grow as you add photos. That’s normal.

 

[cappers]

Managed library is the default as you said, and the library will grow as you add photos. That’s normal.

I have referenced library with it unchecked, but it still grows as I add photos, more so than just a reference to the location of the original photo

 

[chabig]

It’s still generating previews and building its database. You don’t get the organizational features for nothing. You haven’t said how large your library file is. How big is it?

 

[maflynn]

photos library.photolibrary file still becomes bloated and increases with imports.

Bloated? How much does it grow?

The library will contain things even when using referenced photos, so it will grow regardless. I forget if the library holds the previews, but if your library is growing by a lot, that could be one reason

 

[chabig]

You might also find this link interesting. It discusses the disadvantages of using referenced photos.

Disadvantages of a Referenced Library in … - Apple Community

discussions.apple.com

 

[cappers]

It’s still generating previews and building its database. You don’t get the organizational features for nothing. You haven’t said how large your library file is. How big is it?

Not big for this reason. I use referenced library for just selected photos. Although I have 1000’s pics it would use a huge chunk of my HD if I referenced them all because if this. I’m guessing it is metadata and thumbnails which increase a referenced library size

 

[cappers]

Bloated? How much does it grow?

The library will contain things even when using referenced photos, so it will grow regardless. I forget if the library holds the previews, but if your library is growing by a lot, that could be one reason

Seems to be I guess

 

[gilby101]

• A managed Library: This is the default. With "Copy items to the Photos Library" enabled, Photos will import the photos and store a copy of the original photo inside the library. This way the photos are protected and you do not risk to delete them accidentally.
• A referenced Library: Photos does not create a copy inside the library, but is referencing the photo you added in the original location. You are responsible to keep track of the location of the original files. You must not delete ore modify, or move the original file after you added it to Photos, because there will be no copy in the Photos Library. This is a risky set-up, because it is not well supported in Photos:

I don't agree with your comments about risk. Nothing is protected unless you have a good backup. The Photos Library is not a backup because if you delete a photo by mistake the photo is deleted on all your devices. For minimising risk, I prefer a referenced library as I know I have good backup strategies with straight forward recovery (using TM/CCC and ArqBackup).