Shared Album Invite Not Working? Fix It on Any Platform (2026)

Why Isn't My Shared Album Invite Working?

Most shared album invitations fail because they were sent to an address that is not the one on the recipient's account. The invitation is a match, not a message: iCloud matches it to an Apple Account, Google Photos to a Google account. If the address does not match, the invitation arrives and still will not open.

That last sentence is the part nobody says out loud, and it is why this problem eats an entire evening. The email lands. Your mum can see it. She taps it and nothing happens, or a page asks her to sign in to something she has never heard of. Both of you conclude the message did not arrive properly, so you send it again, to the same address, and it fails again in exactly the same way.

There are only two ways an invitation can fail, and they look completely different from each other. A delivery failure means the invitation never reached a screen she looks at - wrong inbox, spam folder, notifications switched off. Those are irritating but findable. An identity failure means the invitation arrived perfectly and still cannot be accepted, because the address you typed does not resolve to the account she is signed in with. That one is invisible, and it is the one you are almost certainly hitting.

Everything below was checked against each vendor's own support documentation on 29 July 2026, because most of the advice online for this problem is years stale. The single most-repeated fact in it - that a free WeTransfer link lasts seven days - is no longer true. WeTransfer's own help centre now says three.

What an Invitation Actually Is on Each Platform

The useful question is not "why did the invite fail" but "what has to be true before this person can get in". The answer is different on every platform, and on two of them it is not an invitation at all.

Read down the third column and the pattern is obvious. Every platform that sends an invitation is really performing an identity check, and an identity check has a failure mode that a link does not have. The two rows at the bottom are not better products - they are a different mechanism, one where there is no match to get wrong.

iCloud Shared Albums: The Address Has to Match the Apple Account

Apple's Shared Albums fail in a specific, repeatable way, and it is the failure I have had to explain most often. When you invite someone you type an email address or an iMessage phone number, and Apple looks for an Apple Account that answers to it. The invitation itself can then surface in three different places - a notification on their Apple devices, an email, or a text message - and Apple publishes no rule for which one you get. That alone causes half the confusion, because the person is often hunting in the wrong place for the wrong thing.

This is the crux of it: an Apple Account can answer to several addresses, and the one your friend gives out is often not one of them. Her Apple Account might be an old @icloud.com address she has not thought about in a decade, while the address in your contacts is the Gmail she actually reads. The invitation lands in the Gmail. The Photos app on her iPhone has no idea it exists, because it is looking for an invitation addressed to her account, and nothing was.

Apple says this outright, and it is the most useful sentence in its documentation on the subject (checked 29 July 2026): "If you want subscribers to be able to view the shared album from an iPhone or iPad, be sure to use the email addresses they use to sign in to their Apple Account." That is the whole failure in one line. There are exactly two documented fixes, and no amount of resending to the same address is either of them.

Fix one: put the address on the account. Apple lets you attach extra addresses to an Apple Account at account.apple.com, under Sign-In and Security, then Email & Phone Numbers, then Add - and it names Photo Sharing as a service this helps with. One catch Apple also documents: the address cannot already belong to a different Apple Account, which is exactly the household where someone once set up a second one and forgot. Fix two: resend. The owner opens the album, taps the person in the subscriber list, and taps Resend Invitation - worth doing only after fix one or after confirming the address out loud, because the same wrong address produces the same silence.

Three other iCloud failures, all of them documented

Shared Albums is switched off on the device. It is a separate toggle from iCloud Photos, at Settings, then their name, then iCloud, then Photos. Apple's own troubleshooting page says that if this setting was off, the fix is to switch it on and ask the sender to resend the invitation. On a phone restored from a backup or handed down, it is off surprisingly often.

They once clicked "Don't Send Me Shared Album Emails". Every Shared Album invitation email carries that opt-out at the bottom, and one stray tap years ago silently suppresses every invitation since. Apple documents the undo: open any old invitation email and click "Undo this change". If there is no old invitation left to open, Apple's documented remedy is to contact Apple Support and ask to be re-enabled. In my experience nobody guesses this one, and nothing on either end hints at it.

The album or the sender has hit a published ceiling. Apple caps a shared album at 100 subscribers and 5,000 photos and videos, and caps the owner at 200 invitations per day and 200 shared albums (Apple's iCloud system limits page, last published 27 February 2025, checked 29 July 2026). A large family album that has quietly filled up is a real cause, and it looks identical from the outside to every other cause on this page.

There is one genuinely useful escape hatch, and it is the fastest fix Apple offers. The album owner can switch on Public Website, which publishes the album to an iCloud.com address where, in Apple's wording, anyone with the URL can view the album in an up-to-date browser - no Apple Account involved. Only the owner can turn it on, and adding photos stays governed by a separate subscribers-only setting, so it solves looking rather than contributing. If the goal tonight is simply that your mum sees the photos, use it.

One forward-looking note, because this page will outlive the software it describes. Apple says iOS 27 is coming this fall, which on its recent cadence means September 2026, though Apple has not named a month; everything above is current behaviour. When that update lands, check Apple's own pages rather than any article written before it, this one included. To bridge iPhone and Android right now, the working options are in sharing a photo album between iPhone and Android.

Google Photos: The Wrong Account Is Usually Already Signed In

Google Photos fails differently, and more quietly. The invitation almost always arrives - Google is good at delivering email. What goes wrong is which account is holding the browser when the recipient taps it.

Almost everyone is signed in to more than one Google account: a personal one and a work or school one, often in the same Chrome profile. When your friend taps the invitation, Chrome opens it as whichever account is first in that list, not the one you invited. Google then does the only correct thing available to it and refuses, with a permission error or a request-access screen that names an account your friend was not expecting to see. Nothing about that screen tells them the fix is an account switcher.

The fix takes ten seconds once you know it: open the invitation in a private or incognito window and sign in as the invited account, or use the account switcher in the top-right corner and reload. Worth knowing before you spend an hour on it - Google does not document this failure anywhere in its Photos help pages, so searching for it turns up forum threads rather than an answer.

Google's own documentation (checked 29 July 2026) does draw a line that solves the problem from the other end. Sharing to specific people and turning on a shareable link are two different actions, and the link is the one built for people outside the Google ecosystem: "If your contact doesn't have a Google Account, you can send them a link or share using another app instead." Google describes that link as "a URL that people can't guess on their own" - worth remembering, because it is the same security model this page recommends later, and Google reached for it first.

Two Google specifics that matter when things go wrong. Contribution is not tied to being invited by name - if Collaborate is on, "anyone who has the link to your shared album can add photos". And removal is weaker than people assume: "if you remove someone from a shared album, but have link sharing turned on, anyone with the original link can still view the album". Locking someone out takes both steps, not one. What each platform requires before someone can upload is a longer story, laid out in what each platform requires before someone can upload.

Check These Seven Things Before You Resend Anything

The scannable version, cheapest first. Six of the seven cost nothing but a question.

• The address, asked out loud - not the one in your contacts, the one their account actually uses.
• A second account in the same browser - have them open the invitation in a private window.
• A work or school account - if a personal address works and the managed one does not, that is your answer.
• The other inboxes - Promotions, Updates, Social, spam, and the unified phone inbox that folds one account into another.
• The Shared Albums toggle on iPhone - Settings, their name, iCloud, Photos, then have the invitation sent again.
• A forwarded message rather than the invitation - a forwarded copy never works. Go back to the owner.
• An expired transfer - a free or Starter WeTransfer stays online three days, after which nothing is wrong except that the files are gone.

If you have been through all seven and it still will not open, stop troubleshooting the invitation. Two failed attempts is the point where the mechanism is the problem, not your execution of it.

The Version of This That Cannot Fail: A Link With No Invitation

There is a third mechanism, and it is the reason this article exists rather than being another list of fixes. A link can carry the access itself. No invitation is sent, so nothing can be misaddressed. No acceptance step exists, so nothing can be declined. No account is matched against, so nobody can be signed in to the wrong one. Every failure above needs a match to get wrong, and there is no match.

Viallo is a private photo sharing platform that stores photos on EU servers at full resolution, does not train AI on them, and opens a shared album in any browser with no account. An album link is the access: you send it, the other person taps it, and they are looking at the photos. There is no invitation to accept, no address to match, and nothing to type - not even a name. Album links, the option to share only some of your albums rather than all of them, and guest contribution all work on every plan, including the free one, which covers 2 albums, 200 photos and 10 GB. Paid plans start at $5.99 a month if you outgrow it.

The obvious objection deserves a straight answer. If there is no invitation, what stops anyone opening it? The honest answer is two things, and neither of them is a password, because Viallo does not offer password-protected links at all. The first is the address: a Viallo share link is 16 random bytes rendered as 32 hexadecimal characters, which is not a thing anyone guesses or crawls, and it is treated as a credential rather than a URL - it is stripped out of Viallo's own analytics rather than logged. The second is revocation: revoke the link and it stops working immediately, for everyone, including an upload that is already in progress.

For sharing with people who keep failing to get in, a link is the better choice; for an album where you need to see and remove individuals one at a time, an invitation is. That trade is real and worth stating plainly. An invitation ties access to named people you can audit and remove one by one. A link does not know who is holding it - you revoke it for everybody or nobody. If the album is a family holiday, that is a fine trade. If it is a client's wedding proofs, it may not be. The related case, where the recipient needs to look but not join anything, is covered in no account needed just to look.

If You Are the One Who Sent It

The other half of this problem is being the person whose invitation is not landing, watching someone you love fail to open something you made for them. Work through it in this order.

1. Confirm the address rather than guessing it. Ask which address their Apple Account or Google account signs in with. Your address book is the least reliable source you have, and this one question resolves more of these than every other step combined.
2. Remove the pending invitation before sending another. Two live invitations to two addresses for the same person is how you end up debugging the wrong one. Delete the first, then re-invite.
3. Re-send to the address they confirmed, not the one you have always used. If those turn out to be the same address, you have ruled out the most common cause in one move.
4. Ask which account their browser is signed in to. On Google Photos this is the whole answer often enough to be worth asking before anything else."Open it in a private window" is the fastest version of the question.
5. Switch mechanisms after two failures. Send a link instead: a Google Photos shareable link, an iCloud public website address, or an album link that needs no account. Do not send the same invitation a third time. It will fail the same way.

The principle is worth more than the steps. Anything that has to match an address to an account can fail at the match, silently, on both ends at once. Once someone has failed to get in twice, the fastest remaining fix is almost never a better-addressed invitation - it is a mechanism with no invitation in it.

Frequently Asked Questions