Apple, 200 Shared Albums is an absurd, barely-documented limit that just wrecked years of memories
My wife and I have used iCloud Shared Albums for every event, trip, and milestone for years. It’s genuinely been a great system — effortless uploading from iPhone, everything organized and easily shared with other iPhone users, and even friends on Android could just tap a link and see the photos. No app, no account, no friction. For a mixed iPhone/Android friend group, it was honestly the best solution we’d found.
Then a few days ago we went to create a new album and got hit with an error. Turns out there’s a hard cap of **200 shared albums per account** — and nowhere, at any point, does Apple warn you this is coming inside the actual product. No heads-up at 180, no email at 190, nothing in Settings or the Photos app itself.
Yes, it’s technically “documented” — there’s a support page (support.apple.com/en-us/108916) that spells out the limit in a bullet point along with a bunch of other caps like photos-per-album and comments-per-photo. But burying a hard, un-overridable ceiling on a support page nobody reads until they hit the wall isn’t the same as telling your users up front. And it’s not like this number is even stable or well understood — Apple has quietly raised it over the years (100 → 150 → 200) with zero fanfare, and there are threads full of people confused about what actually counts toward it, since some users report hitting different totals under seemingly identical conditions.
So now what? Delete old albums full of memories just to make room for new ones? That’s not a real option. We looked into self-hosting alternatives like Immich, and while the feature set is honestly impressive, it’s just not something my wife wants to manage day-to-day. Shared Albums worked *because* it was invisible — no server, no maintenance, no learning curve. Losing that ease of use is its own kind of loss.
The worst part is this isn’t a storage limit or a cost issue Apple is protecting themselves from — it’s an arbitrary ceiling on an app that’s supposed to be about preserving memories. If you’re going to cap something people build years of family history around, at least surface it *in the product* before people slam into it. I’d gladly continue paying for iCloud-storage as my needs expand, but that is not even possible.
Anyone else hit this wall? Anyone found a workaround that doesn’t involve nuking old albums or migrating to a totally different ecosystem?