Why Is My Photos Library So Big on Mac? Free Up Space in 2026

If your Mac's storage graph shows Photos eating up tens — or even hundreds — of gigabytes, you are not alone. The Photos library taking up space on Mac is one of the most common complaints from macOS users, and the reasons it balloons are not always obvious. This guide explains exactly what is inside that library, which parts are safe to remove, and the fastest ways to reclaim storage without accidentally deleting irreplaceable memories.

What Is Actually Inside a Photos Library?

Your Photos library is a single bundle at ~/Pictures/Photos Library.photoslibrary. Right-click it in Finder and choose Show Package Contents to see what is inside. You will find several folders, each serving a different purpose:

• originals/ — Your actual master files: the RAW or JPEG straight off the camera. These are irreplaceable and must never be deleted manually.
• resources/derivatives/ — Rendered previews, thumbnails, and edit outputs. These can be large — sometimes rivaling the originals folder — but macOS can regenerate them.
• resources/modelresources/ — Machine-learning indexes used for face recognition and visual search.
• scopes/ — Database and metadata files Photos uses for albums, People, and Memories.
• private/com.apple.photos.cleanup/ — Temporary staging files left behind after imports or edits.

Understanding which folder is which is the difference between a safe cleanup and a catastrophic data loss.

Why Does the Mac Photos Library Get So Huge?

1. iCloud Downloads Full Originals

When iCloud Photos is set to Download Originals to this Mac, every photo and video you have ever taken is stored locally in full resolution. A library of 50,000 iPhone 15 Pro shots — many captured in ProRAW — can easily exceed 500 GB this way.

2. Edit Renders Accumulate

Every time you adjust exposure or apply a filter, Photos writes a rendered JPEG or HEIF to derivatives/. These renders are cached so the app opens edits instantly, but they are never automatically pruned. On a library used for years, derivatives can dwarf the originals.

3. Optimized Storage Still Uses Space — Just Less

The Optimize Mac Storage setting in iCloud Photos is supposed to evict full-resolution originals and keep only device-optimized thumbnails. In practice, macOS evicts files only when storage pressure is high, so on a large SSD you may still have full originals sitting locally for months before they are evicted.

4. Duplicate Imports and Merged Libraries

If you have ever merged two libraries, imported from a folder that was already in Photos, or moved a library and re-imported it, you may have true duplicate originals taking up double the space.

5. Videos Are the Biggest Culprit

A 4K video recorded on an iPhone at 60 fps occupies roughly 400 MB per minute. A single family vacation with a few hours of footage can push your library over 50 GB on its own.

iCloud Photos vs Optimized Storage: What Each Setting Does

Safe Ways to Reduce Photos Library Size on Mac

Switch to Optimize Mac Storage

This is the single highest-impact change you can make and it carries no risk if iCloud Photos is on.

1. Open Photos and choose Photos > Settings (macOS 13+) or Photos > Preferences (macOS 12).
2. Click the iCloud tab.
3. Select Optimize Mac Storage.
4. Wait — macOS begins evicting originals only when it detects storage pressure. On a full disk, eviction happens quickly. On a spacious SSD it may take days.

After switching, your library bundle may still appear large in Finder for a while because macOS replaces originals with placeholder files that reserve the same path but contain only a small thumbnail.

Delete What You Never Wanted

1. In Photos, open the Duplicates album (introduced in macOS Ventura). Select duplicates and delete them.
2. Use the Recently Deleted album — deleted photos sit there for 30 days still consuming space. Select all and choose Delete Immediately to reclaim storage now.
3. Sort your library by File Size (open any album, then View > Sort By > File Size) to find oversized videos you forgot about.

Rebuild the Derivatives Cache (Safely)

If your derivatives/ folder has grown unreasonably large, Photos can rebuild it. This is safe because derivatives are generated from your originals.

1. Quit Photos completely.
2. Hold Option + Command while reopening Photos.
3. In the repair dialog, choose Repair. Photos will rebuild thumbnails and previews from your originals. Depending on library size, this can take an hour or more and will temporarily use more CPU.

Note: this rebuilds previews but does not necessarily shrink them below their current size. To actually delete stale derivatives first, see the Terminal approach below.

Delete Derivatives via Terminal (Advanced)

If you are comfortable with Terminal and your originals are safely backed up to iCloud or Time Machine, you can remove the derivatives folder manually. Photos will regenerate it on next launch.

# Quit Photos first. Replace "Photos Library" with your library name if different.
rm -rf ~/Pictures/"Photos Library.photoslibrary"/resources/derivatives/

Do not run this command unless: iCloud Photos is enabled (so originals exist in the cloud), or you have a full backup via Time Machine or another method. Derivatives are regenerable; originals are not.

What Is NOT Safe to Delete

• originals/ — Never touch these manually. Deleting from Finder bypasses Photos' database, leaving orphaned records and corrupting your library.
• scopes/ and database/ folders inside the bundle — These are your album structure, face tags, and Memories. Deleting them loses all your organizational work even if photos survive.
• The .photoslibrary bundle itself via Finder while Photos is open — always quit the app first.

If you are ever unsure whether a particular folder inside the Photos bundle is regenerable, use Crumb's Is this safe to delete? AI: point it at the path and it will explain what that folder contains and whether removing it carries risk. It is a useful sanity-check before running any Terminal command on an unfamiliar macOS path.

Check What Else Is Consuming Your Disk

Photos often gets the blame for a full disk when other culprits are equally or more responsible. System Data, old iOS backups, and duplicate files elsewhere on the drive can collectively add up to more than your Photos library.

To get an honest picture of your whole disk, open Apple menu > System Settings > General > Storage. This gives you a rough breakdown by category but does not let you drill into individual folders. For a folder-level treemap that shows exactly where your gigabytes are hiding — including Photos derivatives, Xcode caches, and old downloads — download Crumb and use its Visualize tab. The whole-Mac audit surfaces the largest directories across every category in one view, so you can make informed decisions about what to tackle first.

A Quick Reference: Photos Storage Fixes by Risk Level

• Zero risk: Switch to Optimize Mac Storage (iCloud Photos must be on)
• Zero risk: Delete duplicates and empty Recently Deleted inside the Photos app
• Low risk: Use Photos' built-in repair dialog to rebuild previews
• Medium risk — backup first: Delete derivatives/ via Terminal
• Never do manually: Delete anything inside originals/ or database/ outside of the Photos app

Conclusion

A mac photos library huge enough to fill your SSD is almost always the result of full-resolution iCloud downloads, years of accumulated derivative renders, or forgotten videos. The safest and highest-impact fix is switching to Optimize Mac Storage, followed by clearing Recently Deleted inside Photos. For anything more surgical — like removing stale derivatives or understanding unknown folders — check your backup status first, use Terminal carefully, and lean on tools that explain what they are touching before they touch it. Your photos are worth the extra thirty seconds of caution.