A shared album for wedding guests: why Google Photos, iCloud and WhatsApp fall short

Four things. Every guest can add photos, whatever phone they have and whether or not they have an account anywhere. Adding takes seconds from the phone they are holding. The photos arrive at a usable size, not shrunk for a chat. And the result is one place, in order, that you can download in one go and that stays private.

Measure the usual suspects against those four and the gaps show quickly.

Create an album, turn on collaboration, share the link. Anyone with the link can view, but to add photos a guest has to be signed in to a Google account. Most Android users are; many iPhone users are not, and signing in on a phone at a wedding is where they stop. Google Photos also quietly stores what guests add in their own account, which some guests do not want, and the album sorts by upload time by default rather than the time the photo was taken.

Good for: a family where everyone already uses Google Photos. Weak for: a mixed guest list of 100 people.

iCloud shared albums are easy for Apple users, and you can turn on a public website so anyone can view. But only people you invite with an Apple ID can add photos, and they need an iPhone, iPad or Mac to do it. Android guests can look and cannot contribute. Shared albums also reduce photos to a smaller size and cap how many photos an album holds, which at a wedding you can reach.

Good for: an all-Apple family. Weak for: any room with Android phones in it, which is every wedding.

Everyone has WhatsApp, so a group feels like the obvious answer. It is also the one that loses most. Photos sent the normal way are compressed, so a crisp phone photo arrives soft and small; sending as a document avoids that but almost nobody does it. The group fills with 400 messages of which 60 are photos, mixed with replies and stickers, in the order they were sent rather than taken. Getting them out means saving one by one or trusting the auto-download folder, and the group goes quiet within a fortnight.

Good for: telling people where the taxi rank is. Weak for: being the archive of your wedding.

A shared folder with upload permission collects full-size files, and that is its strength. Guests see a file picker rather than a gallery, uploads from a phone browser are slow and fiddly, nothing is sorted by capture time, and a folder anyone can edit is a folder anyone can delete from. WeTransfer is for one person sending files once, not for 100 people over a weekend. These suit a handful of close family sharing full-resolution files after the event, not the whole room on the night.

PICVIN starts from the guest at the table. They scan a QR code, the upload page opens in the browser, and they pick photos or take one, with no app and no account on any phone. Photos land in one private gallery, sorted by the time they were taken, with albums if you want them. You can delete anything from the dashboard, anyone in a photo can request its removal from the gallery, and you download the whole event as one ZIP. Videos are included on the Premium and Permanent plans.

It is not free. You pay once per event, from US$10.99 including VAT for 1 year on Standard, with a free trial of 3 days and 20 photos first. What you buy is the half of the room that a shared album or a group chat would have lost.

• Any phone, no account: scan and upload from the browser.
• One gallery, sorted by capture time, with optional albums.
• Private by link, with deletion from the dashboard and removal requests from the gallery.
• ZIP download of everything, whenever you like.

Use it for the people it suits. An iCloud album for the Apple side of the family, a Google Photos album for the Android side, and accept that you will spend an evening merging them. Make the QR code on the table point at the option most of your guests can use, say so on the card, and send the other link to the rest in the final details email. Or use one gallery that works for everyone, and spend the evening looking at the photos instead.