Your future mother-in-law suggests Google Photos. It's free, it's familiar, it's Google. You create a shared album, add the link to your wedding website, and feel like you've solved the problem. Then the actual wedding happens.

Your photographer's assistant asks if anyone can share the album link. Half the table doesn't have Google accounts. One guest has an account from 2011 she can't log into. Another gets the invitation email, doesn't recognize the sender, and marks it as spam.

The account problem is real

A lot of iPhone users don't have Google accounts, or they set one up years ago and have no idea what the password is. Asking them to sign in mid-reception to upload photos is not going to work. You'll get a polite "sure" and they'll forget about it before they finish their drink.

Google's shared album invitations go out by email. That email arrives in a crowded inbox, looks vaguely like spam, and has to compete with everything else happening after the wedding. People open it with good intentions and then close it and move on.

Storage lands on you

When guests upload to a shared album you created, it counts against your Google storage quota. Not theirs. Google gives you 15GB free, shared across Gmail, Drive, and Photos. A wedding with 50 active uploaders can fill that fast, especially if anyone uploads video.

Google also compresses photos if you're not on a Google One paid plan. The compression isn't always obvious, but it's there. You end up with something close to the original but not quite, which matters if you want to print anything larger than a 4x6.

The confusion factor

The album link confuses people who aren't tech-fluent. What they see when they click depends on what device they're on, whether they have the app installed, and whether they're logged in. One guest might see a clean upload interface. Another might get a permissions error. Another might see the album but have no idea how to add photos to it.

Google's automatic organization tries to group photos by date and place, which sounds helpful. In practice it makes finding a specific photo feel like archaeology. The ceremony photos end up mixed with photos from someone's dinner the night before because the timestamps overlapped.

When it actually works

If your entire extended family is on Android and regularly uses Google Photos, a shared album is fine. The flow is familiar, it's free, and everyone knows how to use it. Some families genuinely live in the Google ecosystem and this causes them zero problems.

But the average wedding guest list is a mix. Some Android, some iPhone, some people who still call everything "the cloud" like it's a single place. For a mixed crowd, Google Photos creates just enough friction to lose a significant chunk of your photos.

The better option for mixed crowds is a browser-based upload that skips the account requirement entirely. Guests scan a QR code, pick photos, upload in 30 seconds. No sign-in, no email invitation, no quota math. You get photos from people who would have given up three steps into the Google Photos flow.

Google Photos works if every guest already lives in the Google ecosystem. For a real wedding with a mixed guest list, the login requirement will cost you a significant chunk of uploads. Remove it.