After every event the same thing happens: dozens of phones full of photos, a half-hearted "share them in the group chat", a handful of compressed WhatsApp uploads from the most diligent attendees, and everything else quietly deleted months later to free up storage. The photos exist; the collection mechanism doesn't.
The mechanism that works is a QR code pointing at an upload page. Attendees scan with the phone camera, an upload page opens, they pick photos, done - no app, no account, no explaining a shared folder to a relative. The rest of this guide is about the part tools don't solve: getting people to actually scan it.
Setup, briefly
Create an upload page titled after the event (getfiles.app - free, no accounts for uploaders), generate a QR code from the link - any generator works; qree.app is free and adds scan analytics, so you can see how many people actually scanned - and print it big. Everything after this point is social engineering, not software.
Placement: where people idle, not where they pass
A QR code works when someone is standing still with their phone already out. Put it where people wait or linger - registration desk, bar, food table, seats - not on a wall they walk past. Size matters more than design: a poster-sized code readable from a couple of meters beats an elegant card nobody notices.
By event type, the spots that earn their keep:
- Conferences and corporate: registration queue (captive, phone in hand), every table at lunch, a slide between sessions, the exit sign ("share your photos before you go").
- Parties, birthdays, showers: near the cake or food - the two places everyone photographs anyway - plus the group chat, because half the guests respond to messages and the other half to physical signs.
- School events and tournaments: the program handout and the entrance; aim at parents - they take the most photos and share the most willingly.
- Fundraisers and galas: every table, the photo backdrop, the auction display.
One verbal announcement beats ten printed signs. Have the MC or host say it once, mid-event: "If you've taken photos today, scan the code on your table to share them." Passive QR codes collect from the observant; the announcement collects from everyone else.
Timing: the follow-up catches what the event missed
People forget mid-event and remember on the couch. Send the upload link to the group afterwards - the event chat, the recap email, the thank-you note - with a soft deadline: "upload by Friday, the page closes after that."
The page's expiration is your deadline mechanism: a new page runs up to 10 days, which comfortably covers event day plus a follow-up window. When it expires, uploads stop by themselves - no lingering link accumulating strangers' photos a month later.
What lands in your dashboard
Photos and videos with uploader names and timestamps, previews in place, one ZIP download. Two settings worth touching at creation: raise the per-file size limit toward 200 MB if you expect videos (the default is 100 MB), and leave file types unrestricted - the "images only" preset would reject every video, and phones ship MP4, MOV and whatever format arrives next year.
Why the usual tools underperform here
| Method | Failure mode |
|---|---|
| WhatsApp / Telegram group | Compresses photos, buries them between messages |
| Google Photos shared album | Requires a Google account - fails on exactly the relatives who take the best photos |
| Shared Drive folder | Permissions dialog kills the moment |
| Instagram hashtag | Public, compressed, excludes everyone not on Instagram |
| QR to upload page | Nothing to install or sign into - the only method that survives contact with a mixed-age crowd |
After the event
Attendees uploaded photos to share with the organizer - that is not consent to publish them. For public marketing use (social media, next year's landing page), ask before posting, especially for photos with children in them. School and family events deserve the strictest reading of this.
Download the ZIP, share a highlights album back to the group - people upload more readily next time when they saw the results last time - and let the page expire. For recurring events, a fresh page each time keeps collections scoped and links from leaking across years.
getfiles.app - the upload page half of this setup: free, branded if you want it, no accounts for anyone scanning.