By the end of your wedding night there will be more photos of you on other people's phones than on your photographer's memory card. Almost none of them will ever reach you. The group chat gets a dozen compressed images from the most organised friend, the shared Drive folder dies at the "sign in with Google" screen, and everything else sits in camera rolls until it gets deleted to free up space.
The fix is boring and reliable: one upload page with a link, and a QR code pointing at it. A guest scans the code with their phone camera, a web page opens, they pick photos from the camera roll, tap upload, done. No app store, no account, no password - which matters when your guest list runs from teenagers to a grandmother with a five-year-old Android.
This guide covers the setup, but mostly the parts other guides skip: the page-lifetime trap, the settings that silently eat guest videos, and what a realistic collection window looks like.
The setup
Create an upload page at getfiles.app - type a title like "Nora & David - Wedding Photos", create, and you get a short link plus a private dashboard where uploads land. Uploaders never need an account; you don't need one either, though signing in keeps the page attached to something you can find again later.
Turn the link into a QR code with any generator (qree.app is free and shows scan counts, so after the wedding you can tell whether the table cards were actually used). Print it on cards for the tables and you have the whole mechanism.
One optional field is worth filling while you're there: the notification email. New uploads are announced in a batched email about an hour after they land, so the week-after trickle shows up in your inbox instead of needing a dashboard check.
Before you print anything, though, read the next section.
The timing trap: page expiry vs your stationery timeline
Upload pages here are deliberately temporary - this is a collection window, not a photo album. A new page starts at 7 days and can be given at most 7 days at creation. After that you can extend it in 7-day steps, up to 14 days of total lifetime.
Don't print the QR code on invitations that go out two months early and assume the page will quietly wait. Extensions only become available in the last 7 days of a page's life, and once a page has been expired past its short grace window it can't be revived - so keeping an early page alive means extending it every week or so, every time, until the wedding. Create the page during wedding week instead, and put the QR on table cards, not invitations. An expired link on a beautifully printed card collects nothing.
The practical schedule that works:
- A few days before the wedding: create the page, print the table cards, drop the link in the wedding group chat.
- Wedding day: cards on tables, one verbal announcement (more on that below).
- The week after: send one reminder message, extend the page if uploads are still trickling in.
- Before expiry: download everything as a ZIP. Files stay downloadable for 3 more days after the page expires, then they're gone for real.
Settings that actually matter for a wedding
The defaults are tuned for small file requests, not a hundred guests. Three of them are worth changing before the day:
Raise the file cap. A page accepts 50 files by default. One enthusiastic table can burn through that during cocktail hour. Raise it to the maximum of 2000 - there's no cost to headroom.
Raise the per-file size for video. The default is 100 MB per file, which covers photos with room to spare but rejects the ceremony video someone shot in 4K. The maximum is 200 MB. Uploads over a few megabytes are chunked and resumable, so a large clip on flaky venue Wi-Fi picks up where it dropped instead of starting over.
Watch the total, not just the per-file size. A page holds 5 GB of uploads all together, and no setting moves that ceiling. Photos won't get near it - a few hundred phone shots is a gigabyte or two. Video is how you fill a page: at the 200 MB per-file maximum, two dozen long clips and the page is done, whatever the file counters say. The dashboard shows the running total - glance at it during the week after rather than discovering a full page on the last day of the grace window.
Leave file types unrestricted. The page offers type presets like "images only". Skip them for a wedding: the presets are strict allowlists, and none of them include video formats - an images-only page silently rejects every first-dance clip.
The upload form has an optional name field. Put "sign your photos!" on the table card - three weeks later, "who took this incredible shot of the vows?" is answerable, and you know who to thank.
A few settings are situational. Gallery mode lets guests see what others have uploaded - at the reception this turns into entertainment on its own, phones passed around the table. Switching it on also puts a slideshow link on your dashboard: open it on a laptop feeding the venue's screen and approved photos play as they arrive - the live slideshow dedicated wedding apps headline with, running off the same QR card. Moderation holds each upload out of the gallery until you approve it; sensible if the QR code ends up somewhere semi-public, unnecessary for a private guest list. A password adds protection but also friction - for a code that only exists on your reception tables, most couples skip it.
Getting people to actually scan the card
The card itself needs three things: a short line ("Share your photos with us"), the QR code printed large, and the URL written out underneath for whoever prefers typing. Match it to your stationery and it doubles as table decor.
Distribution is the part that decides how much you collect, and it's social, not technical. A silent QR card gets scanned by the diligent few. What moves the rest:
- One announcement from the MC or DJ, timed when phones are already out - right after the first dance works well.
- Cards where people idle, not just dining tables: the bar queue and the photo-booth line are where guests stand still with a phone in hand.
- A next-morning message in the group chat. Plenty of the best photos are taken late and uploaded never; one "we'd love everything from last night" catches them while the link is still alive.
Delegate the nudging. One bridesmaid and one groomsman who each remind their own circle will out-collect any sign. Personal asks beat announcements.
After the wedding
Everything lands in one dashboard with thumbnails, uploader names, and a one-click ZIP of the lot. Download it before the page (plus its 3-day grace window) closes, and back it up like the irreplaceable thing it is.
What this tool deliberately doesn't do is permanent hosting. If you want guests to browse the full collection forever, curate the best into a shared album afterwards - Google Photos is fine for that job, since now it's you managing one album rather than eighty guests being asked to sign in. Collection and long-term sharing are different problems; use the upload page for the first and anything you like for the second.
If you're weighing this approach against dedicated wedding-photo apps like WedUploader or GuestPix - some of which add galleries and slideshows as headline features - the trade-offs are covered in our comparison of wedding photo sharing apps.