How do guests upload photos?
A guest points their phone camera at the printed code, taps the link that appears, and the album opens in the browser that's already on the phone. They pick photos from the camera roll and tap upload.
There's nothing to install, no account to create, and no password to remember. A first name is the only thing you're asked for, and it's optional.
What a guest does at the table
The whole thing is 4 movements, all of them in the browser, and a guest who has never seen the album before gets through it in under a minute. Nothing is installed on the phone, and nothing is left behind on it afterward.
Photos are chosen from the camera roll rather than taken inside the album. Guests keep using the camera app they already know and send the pictures in batches later, which is why uploads arrive in waves: once after the meal, once at the very end, and once the following morning.
The 4 steps can be repeated as often as a guest likes. After the first visit the album sits in the browser history, so the second and third rounds do not need the printed code at all.
- Point the camera at the code. Any phone sold in the last 8 years reads a QR code from the normal camera app. A link appears across the top of the screen within a second or 2.
- Tap the link. The album opens in Safari, Chrome, or whichever browser the phone already uses. The album name is the first thing on screen, so a guest can see they're in the right place.
- Choose the photos. The upload button opens the camera roll. Several photos can be selected at once, so 30 frames from the dance floor do not go across 1 by 1.
- Tap upload and wait. A progress bar runs while the files transfer, then the screen confirms they've arrived. The album asks once for a first name; skip it and the upload is anonymous.
Do guests need an app or an account?
No. The album is a web page and it runs in the browser that came with the phone, the way a timetable or a menu does. There is no store to visit and nothing to set up.
That removes the largest obstacle of the night. An install is a 3-minute detour with a password at the end of it, and a guest holding a drink at 11pm won't take it. No email address or phone number is asked for either, so there's nothing to confirm and nobody gets signed up to anything for helping you.
Hosts do have an account, because a host has an album to manage, a code to download and other people's photographs to look after. That account is created once, before the event. Guests never see it and never need it.
Guests who aren't comfortable with phones
Most receptions have a table where the phones are older, the eyesight is worse and nobody wants to be the person who breaks something. That table is worth 5 minutes of planning, because it usually holds the guests with the photographs nobody else took.
Print the code larger than feels necessary. 5cm square is the smallest that scans reliably from a seated position, and 8cm is calmer on a table with candles and glasses on it. Put the album web address underneath in plain text, so a guest who can't make the camera behave can type it instead. Then write the instruction as an instruction: open your camera and point it at this square works for everyone in the room, where scan to share assumes the reader already knows what scanning means.
The most effective move is not a printed one. Ask 2 people to walk a table through it once — a best man, a niece, a colleague who is good with phones. The obstacle is rarely the handset. It is the worry of breaking something, and that is fixed by somebody offering.
Which files the album accepts
Guests send whatever their phone produces, so the accepted list is written around phone output rather than around professional formats.
| What the guest sends | Format | What happens to it |
|---|---|---|
| Photo from an iPhone | HEIC | Shown as a JPEG, the original kept for your download |
| Photo from an Android phone | JPEG | Stored at the resolution it arrived in |
| Screenshot or edited photo | PNG or JPEG | Stored as sent |
| Video from either phone | MP4 or MOV | Processed after the upload, then it appears |
Whatever sits in the camera roll goes into the album. Nobody has to convert anything first.
How many photos 1 guest can send
There is no per-guest limit. A guest can send 3 photos or 300, in 1 batch or across the whole evening. The only ceiling sits at album level and comes from the plan you bought, not from the guest.
The practical limit is the phone rather than the album. Selecting more than about 50 photos at once makes the picker slow on older handsets, so 20 to 30 at a time moves a large camera roll more calmly. If the same photo goes up twice, both copies stay: 2 near-identical frames are sometimes genuinely different moments, and removing the spare is 1 tap in the dashboard.
Don't judge the album at 8pm. Guests upload in bursts, usually after dinner and again at the very end of the night, so a quiet album early on is the normal shape of the day, not a sign that something is broken.
When the venue wifi is weak
Most receptions happen in buildings that were never designed for 100 phones at once. The album goes across 1 file at a time rather than all at once, so a dropped signal costs that 1 file and leaves everything already sent in place.
For the guest that means one thing: leave the page open until the bar has run through. Locking the phone or switching tabs pauses the transfer on some handsets, and that is the most common reason a photo never arrives. Reopening the album finishes the job without losing what already went across.
As a host you can do 2 things in advance. Print the guest wifi password on the same card as the code, so nobody has to ask for it. Then say on that card that uploading later is completely fine. The second line takes the pressure out of the night — guests fighting 1 bar of signal otherwise give up, and their photos never come.
When a guest has no smartphone
Some of the best frames at a party come off a compact camera owned by somebody who has had it for 15 years. There are 3 routes into the album for that guest, and none of them involves buying a phone.
The first is a computer: the album opens at the same web address in a desktop browser, and files can be dragged in from a folder or straight from a card reader. The second is the person sitting next to them, who can upload the card that week. The third is you — anything handed over on a memory card can be added from the host dashboard after the event, carrying whatever name you give it, so the credit is not lost.
Print the album web address next to the code for exactly this reason. A code is no use to somebody who will upload from a laptop 3 days later, and a short line of readable text costs nothing on the card. Say by when the album closes, too: getting photographs off a camera takes a few days longer than sending them from a pocket.
Common questions
Can several guests upload at the same time?
Yes. Each guest uploads in their own session, independently of everybody else. If 30 people scan at once after the speeches, no queue forms in the album.
Do guests have to give their name or an email address?
No. Leaving a name is optional and there is no email field at all. A guest who adds a name has it shown beside their photos, which makes it easier for the host to say thank you.
Can a guest delete a photo again?
While the same browser session is open, a guest can remove their own uploads. After that the host does it from the dashboard. A guest can never delete somebody else's photograph.
Can guests still upload the day after the party?
Yes, for as long as the album stays open. Many guests upload the next morning, once they've looked through their photos properly. The host decides when uploading ends.
A guest cannot scan the code
Paper, size and light — what to check before you reprint.
How guests upload videos
The same route, only longer, with a ceiling that depends on the plan.
An upload is missing
Processing, approval or an abandoned transfer: telling the 3 apart.
Do guests need an account?
The same question from the guest's side, with what they see on screen.
A guest cannot get into the album
Forward us the album name, the date of the event, and the guest's phone model. That lets us reproduce the case without writing back first.