Every photo from the reunion.In your Drive.
The simplest way to collect photos from a family reunion is a QR code that opens an upload page in the browser relatives already have: they scan, choose pictures from the camera roll, and the files land in a folder in your own Google Drive. No app for anyone to install, no account for anyone to create, and no group chat where the good photographs sink under three days of replies.
A reunion is the one weekend where four generations are in the same place, and it is also the weekend where the photographs are most likely to scatter and never come back together.
Everyone takes pictures. Almost nobody sends them. The ones that do arrive come through four different channels: a few in the family group chat, a few by text to whoever asked, a shared album that half the family cannot open because it is the wrong ecosystem, and a cousin who says he will get them to you and means it sincerely. Six months later the group chat has rolled over, the shared album has quietly stopped being maintained, and the photographs of the oldest people in the room are on a phone that has since been replaced.
The organiser feels this most sharply, because the organiser is the person everyone assumes is keeping the record. You booked the hall, collected the money and made the name badges, and now you are also the unofficial archivist of a day you were too busy to photograph yourself.
None of these are bad tools. They are just tools built for a group that already shares an ecosystem, being asked to serve a group that emphatically does not.
| Method | Where it strains at a reunion |
|---|---|
| Family group chat | Works for everyone, which is its real strength. But photos arrive compressed, and they sink under conversation within days. Retrieving forty pictures a year later means scrolling a year of messages. |
| Shared album | Excellent inside one ecosystem. Half the family is on the other one, and the half that cannot open it is not evenly distributed by age. |
| Ask people to send them | Relies on everyone remembering and on you chasing. The people least likely to follow through are often the ones holding the photographs you most want. |
| A QR upload page | Scan and upload, no app and no account, originals into one folder you own. The cost is that somebody has to print a code and mention it twice. |
Most photo tools are built for a group of people who all have the same phone, the same account and roughly the same tolerance for setup. A reunion is the opposite of that. It runs from an eight-year-old with a hand-me-down tablet to an eighty-year-old who has one app on the home screen and did not put it there.
So the constraint that matters is not features. It is the number of steps between a relative wanting to help and actually helping. Point the camera at a code, tap the link, choose the photos, done. Nothing to install. Nothing to remember. No moment where a great-aunt is asked to create a password and decides this is a job for somebody younger, and then forgets.
Every upload goes into a folder in your own Google Drive, under your own account, from the moment it arrives. We keep a record of what came in and who sent it so your dashboard can show you the feed as it happens. We do not keep the files. There is no Glint library holding your family’s photographs, which means there is no version of the future where a company you signed up with once decides what happens to them.
That distinction is easy to skim past and it is the whole reason this page exists. Most tools in this category host your gallery and give it an expiry date: seven days on a free plan, a few months on a paid one, a year if you pay the most. That is a reasonable trade for a single event you will have finished with by Christmas. It is a bad trade for something you are building on purpose, year after year, and intend to still have when the youngest person in the photographs is old enough to want them.
To be precise about what does and does not have a clock on it: the files in your Drive are yours and stay there, and we never remove them. A paid event keeps its upload page open for 12 months from the day you create it, after which relatives can no longer add new photographs to that event. Your folder, your gallery and everything already collected are untouched by that. See what an event includes.
A single reunion produces a folder. Three of them produce something else entirely: the same faces at three points in time, the children visibly growing, the people who were there in the first year and not the third. Nobody sets out to build that. It accumulates, provided each year lands somewhere that the previous year is still sitting.
Each gathering gets its own event, its own code and its own folder, so one year never writes over another. If yours is an annual fixture, the Event Bundle covers three events and the slots do not expire, so you can buy them once and use the last one several years from now. That is the shape that fits a thing you do once a year: not a subscription that bills you for eleven months of nothing, and not a fresh decision every single time.
This is the part no photo tool is designed for, and it is the part that makes reunions worth the trouble. An aunt arrives with an album. Someone produces an envelope of prints from a caravan holiday in 1987. They get passed round the table for an hour, four people take pictures of the same page on their phones, and then they go home in the album they came in.
The upload page does not care whether a photograph was taken twenty minutes ago or forty years ago. If someone snaps a picture of a print and uploads it, it lands in the same folder as everything else from the weekend. It is not archival digitising and nobody should pretend it is, but a phone photograph of a print is enormously better than the print staying in one house where nobody else can see it.
If you want this to happen, put the code on the table where the albums end up and say so. Left to chance it does not occur to anyone, and the pictures with the most people alive in them are the ones that stay in the shoebox.
This is where a reunion differs most from the events these tools are usually built for. At most gatherings one person keeps the photographs. At a reunion everybody wants a copy, and the request arrives in ones and twos for months afterwards, usually by phone, usually to you.
You can turn on a share page for the event, which gives you a single tidy link to send round: the family lands on a page for your gathering with a button through to the folder itself. It is off by default and never indexed by search engines, so it exists only for the people you send it to.
One honest caveat, because it is the sort of thing that is annoying to discover later: the folder is in your Drive, so who can open it is governed by your own Google sharing settings, not by us. Set the folder to anyone-with-the-link before you send it round, or you will spend a fortnight approving access requests one relative at a time.
Print the code larger than feels necessary and put it where people already stop moving: the food table, the bar, the table where badges are handed out. A code at eye level next to the buffet gets scanned. A code on a wall at the far end of the room does not.
Say it out loud once, early, while everyone is still in one place and nobody has wandered off. One sentence is enough, and it works better coming from whoever the family actually listens to rather than from whoever set the thing up.
Then say it again afterwards. The best photographs from a reunion almost never arrive on the day. They arrive the following week, when someone is back home on a decent connection and going through their camera roll properly. Put the link in the thank-you message and mention that it still works, because it does. See how the upload page behaves.
