QR Code for Wedding Photos: The Complete 2026 Guide

You want every guest's photos in one place, and you've heard a QR code does that. A QR code for wedding photos is a printed link: guests scan it, a page opens on their phone, and they add photos to a shared album, upload folder, or event camera. The code itself is free and does very little. What decides whether it works is where it points, whether guests must sign in, and whether you tested it from a guest's phone before printing.

The code is the easy part. The destination is the decision.

A QR code holds a web address and nothing else. It stores no photos. So "which QR code should I use?" is really three questions:

1. Where will the photos live?
2. What does a guest have to do once the page opens?
3. What happens to the link and the photos after the wedding?

Generating the code takes about a minute. You can paste any link into our free wedding photo QR code sign maker, pick a template, and download a print-ready 8x10 sign with no signup. A pretty sign that leads to a sign-in screen will collect very little, so the rest of this post is about that link.

Where the QR code can point, and what each option costs your guests

Details below were checked in November 2026 on each provider's own pages unless noted. These services change often, so confirm anything that matters before you print.

Destination	Guest needs an account?	Camera roll photos?	Free limit	Main catch
Google Photos shared album	Assume yes to add photos	Yes	None listed on Google's help pages	Sign-in step, link can be passed on
iCloud shared album (version 27)	No, per Apple	Yes	Your iCloud storage	100 participants, storage counts against you
iCloud album (version 26 or older)	Yes to contribute	Yes	5,000 items per album	Photos reduced to 2,048 pixels
Dropbox file request	No	Yes	2 GB on Basic	Guests can't browse an album, you run out of space fast
Dedicated upload service	Usually no	Usually yes	Varies, often small	Limits, expiry, cost
Shared event camera, such as Revel	No	Yes, if taken during the Moment	Up to 10 participants on Revel	Photos from before the Moment can't be added

Google Photos shared albums

Google Photos is the default answer, and it's a decent one if most of your guests already use Google. Its app can even make the code for you: open an album, tap Share, and choose Show QR Code. According to Google's help page, anyone who has the link can view the album and add to it, as long as the owner's Collaborate setting is on.

The open question is sign-in. Google's help pages say a link can go to people without a Google Account, but they don't say whether those people can add photos without signing in. InvitePix, a competing service, says they must sign in first. Plan on a sign-in step, then confirm it with the stranger test below.

For a guest already signed in to Gmail, that step may be trivial. For your uncle with a forgotten Google password, it's the end of the road.

iCloud shared albums, which changed with version 27

Older guides call iCloud useless for mixed Apple and Android crowds. That's now out of date, depending on which version created the album.

For albums created on iOS, iPadOS, or macOS 27 or later, Apple's shared album guide says friends and family can join and contribute on the web, even without an Apple Account or Apple device. The owner can let anyone with the link join without approval, and Copy Album Link gives you the address for your QR code. Apple's limits page adds that photos on these albums stay at full resolution.

Now the catches, all from that same limits page. A version 27 shared album has a maximum of 100 participants, including the owner. Say you have 120 guests. Not all will join, but Apple doesn't spell out how web guests count toward that cap, so check before relying on it. Everything guests add also counts against your iCloud storage. Temporary shared albums skip that storage hit, but they cap out at 5,000 photos and videos combined across all contributors, and an existing album you convert to temporary is deleted after 30 days.

Older albums work differently. If you create the album on version 26 or earlier, you invite people by contact, email, or phone number, and the Public Website option is for viewing rather than contributing. Those albums also hold 5,000 items and reduce shared photos to 2,048 pixels on the long edge. So update your phone first, then create the album.

Dropbox file requests

A Dropbox file request is the most underrated free option. It's an upload page and nothing more. Dropbox says anyone can send you files whether or not they have an account, and the destination folder stays private by default.

That privacy is also the drawback. Guests drop files in and leave, with no album to scroll. Every upload uses your storage, and if you run out, guests see an error. Dropbox Basic includes 2 GB. As a rough illustration, if you assume 4 MB per photo, 2,000 MB ÷ 4 MB = 500 photos in an otherwise empty account. A paid plan is safer for anything but a small wedding.

Dedicated wedding upload services

These exist for this exact job: guests scan, a browser page opens, and they pick photos from their camera roll, usually with no app or account. You trade money, or a tight free limit, for a smoother path. Examples, as listed by each company in November 2026:

• Wedibox: its pricing page lists a free plan with 50 guest uploads and one-time plans at $29, $49, and $79. Its help page says guests can upload photos and videos from their phones without an app or account.
• Yogile: its blog describes a free plan with no photo cap, but the album stays active for only 7 days. Its pricing page lists $44.99 for a year.
• GuestPix: its pricing page describes one-time packages, a gallery hosted for 12 months from the event date, and upload windows of 3 or 12 months depending on the package. That page lists no dollar amounts.
• Joy: Joy's wedding website tools are free, but guests need Joy's mobile app to upload to the shared gallery.

Read the expiry terms as closely as the price, especially if your honeymoon starts the next day.

Shared event cameras, including ours

An event camera works differently from everything above. We make one called Revel, so weigh this accordingly. Guests scan and shoot straight from their phone browser, with no app or account. Every picture lands in one gallery, you can pick a film look that applies to all of them, and you can hide photos until the event ends so everyone sees them at once.

The limit matters for this post: guests can upload from their camera roll, but only photos taken between when the Moment was created and when it ends. If your aunt shot the ceremony on her regular camera app and only found the sign at dinner, she can still add those photos, as long as the Moment was already running. Throwbacks and shots from before it started can't go in. If you want those, or guest video, an upload service will serve you better. Revel fits when you'd rather have everyone shooting together through the night. Our shared albums comparison covers that trade-off.

Static or dynamic: pick the code that can't die on you

A static QR code stores your link directly in its pattern. A dynamic code stores a short redirect address owned by the company that made it, and that company forwards guests to your link.

The difference shows up when something changes. QR Code Generator's guide to expiry says static codes don't expire and keep working with no subscription, as long as the printed code is readable and the page still exists. Dynamic codes can be edited after printing, but they stop working if a subscription lapses, a scan limit is reached, or a free trial ends.

So if a free generator quietly gives you a dynamic code on a trial, and the trial ends before the wedding, your printed table cards become decoration.

For most weddings, use a static code. The sign maker's code is generated straight from the link you paste in, with no redirect service in between, so there's no trial to lapse. A static code can still fail if the destination expires or the link had a typo, so check both before printing.

If you might change destination after printing, you have two options. Pay for a dynamic code and keep the plan until you're done. Or point a static code at a page you control, such as your wedding website, and put the album link there. You can then swap the link any time, at the cost of one more tap for guests.

Free options that actually work

The code and the sign are free, permanently, if the code is static. Don't pay for that part. Storage is where the bill appears: an iCloud or Dropbox album uses your space, and if it fills up on the night, guests get errors at the worst time.

A free setup for each situation:

• Mostly iPhones, under the participant cap: iCloud shared album on version 27, with the link pasted into a free sign.
• Mostly Android or Google users: Google Photos shared album with Collaborate on, plus a line on the sign warning about sign-in.
• You want no accounts and don't need an album: Dropbox file request with enough storage.
• Tiny wedding or elopement dinner: a free tier from a dedicated service. Wedibox's 50 uploads or Revel's 10 participants could cover it. Yogile's free album fits only if you'll download within the week.

With 100-plus guests, no free option is perfect. Each has a sign-in step, a storage ceiling, a short expiry, or a low cap. Pick the catch you can live with, or pay a one-time fee for one wedding.

How to set it up, start to finish

Step 1: Choose the destination using the table above. Many older relatives on the list means "no sign-in" matters more.

Step 2: Set permissions. On Google, confirm Collaborate is on. On iCloud version 27, allow joining by link and turn on Can Add Photos. On Dropbox, pick a dedicated folder.

Step 3: Add one photo. An empty page looks broken, so put an engagement photo in first.

Step 4: Test the guest link using the checks in the next section, before you make any code.

Step 5: Make the sign. Paste the link into the QR sign maker, add your names and a message, and download the PNG. The download is 8x10 inches at 300 dpi. Shorter links produce simpler codes, so use the shortest official link your service gives you.

Step 6: Print one copy and test that. Use the real paper, not the screen version.

Step 7: Assign a person. Ask a friend to know how it works and help anyone who looks stuck.

Test it before you print anything

The stranger test. Open the link in a private browser window, logged out of everything, on a phone that isn't yours. That shows you what a guest sees. Try the full action, including adding a photo. If a sign-in page appears, you've found out now instead of at the reception.

The device test. Try iPhone and Android, including the oldest phone you can borrow, with Wi-Fi off, at the venue if you can.

The print test. Scan the printed sign from where a guest will really stand, in the kind of light they'll really have. Nielsen Norman Group notes that codes should be larger in dim light.

The dark-template test. Our sign maker's Midnight and Navy templates print a light code on a dark background. If any phone hesitates on those, switch to a dark-on-light template such as Minimalist or Cream.

How big to print it

Nielsen Norman Group's guideline is the reference to use here: aim for at least 2 cm × 2 cm (0.8 in × 0.8 in), then add about 1 cm of width for every 10 cm of scanning distance. That's roughly a 10:1 ratio of distance to code width. It's a rule of thumb, not a standard, and it assumes decent light.

Where it is	Expected scan distance	Code width by 10:1
Table card, phone held close	30 cm (about 1 ft)	3 cm (about 1.2 in)
Sign on an easel or welcome table	100 cm (about 3.3 ft)	10 cm (about 3.9 in)
Sign across a small crowd	200 cm (about 6.6 ft)	20 cm (about 7.9 in)

For reference, the code on our 8x10 sign is 1,280 pixels wide at 300 dpi. That's 1,280 ÷ 300 = 4.27 inches, or about 10.8 cm, good for about 108 cm by the rule. Scale the sign down to fit a 4-inch width for a table card and the code halves to 5.4 cm, good for about 54 cm. The sign's shape is 4:5, so it won't exactly fill a 4x6 card. Expect a small border.

Leave clear space around the code. The QR standard's maker, Denso Wave, specifies a margin four modules wide on every side, a module being one of the small squares. If you drop the PNG into Canva, don't crop tight or crowd the code with flowers.

Keep the contrast high, and consider matte stock, since glossy surfaces can catch reflected light.

What to write on the sign

Nielsen Norman Group's advice is to say where the code leads and make that text as prominent as the code. "Share photos!" is thin. Here are versions to borrow. Pick by what your link actually does, because a sign that promises no app when guests need one is worse than no promise.

For an upload page or album with no sign-in:

Saw something we missed? Scan to add your photos to our wedding album. No app, no account. It takes a minute.

For Google Photos or anything with a sign-in step:

Help us see the day through your eyes. Scan to open our album, sign in with Google, then tap Add photos. Stuck? Find Priya at the bar.

For a shared camera where guests shoot live:

You're our photographer now. Scan to open the camera. No app needed. Take your shots, and we'll all see them after the party.

Five photos. Choose wisely. Scan to open tonight's camera. Your countdown starts now.

For a low-signal venue:

Signal's patchy out here. Scan at the welcome table or join the "Harbor House Guest" Wi-Fi. Photos can go up tomorrow too, the link stays open for a month.

For a table card, where space is tight:

Your table, your photos. Scan to share them with us.

Add a short web address under the code, as Nielsen Norman Group suggests, for anyone whose camera won't cooperate. If your link has a deadline, print that too: "Add your photos by June 30."

Where to put the signs

Put a code where people look, at moments when they have a free hand. Nielsen Norman Group's advice is that a code must be noticed before it's scanned, and that one tucked in a corner feels disconnected.

The welcome table is the best spot, because nearly everyone passes it. Use your largest sign there and give it its own space, away from the guest book and gift box.

Table cards come next. A small code at each place catches people at their most idle: between courses, during a long toast.

The bar works well because the line gives people time. Mention the code in the program too, and consider a line from the MC or DJ, which reaches guests who walked past every sign.

Guest photos fill the gaps around your photographer, so plan both together. Our wedding photo shot list helps you decide what the professional covers, so you can ask guests for the candid stuff.

When the venue has no signal

A barn, a vineyard, a stone church, or a basement ballroom can all defeat you. Any QR link needs a connection to open, and most upload pages need one to finish.

Visit at the same time of day as the wedding if you can, and test on more than one carrier. Then choose from these fixes:

• Ask about guest Wi-Fi and print the network name and password on the sign. Check that it holds up with a full room.
• Place signs where signal exists. If the parking lot has bars and the hall doesn't, put the sign at the door so guests scan on arrival.
• Make uploading a next-day job. Keep the upload window open for at least a week, and text everyone the link the morning after.
• Use a tool built for it. Revel lets guests keep shooting with no signal, and photos sync when they reconnect. The page still has to open, so have guests scan where there's a connection. Hosts need internet to create and manage the event, so set it up in advance.

Paper disposable cameras are also a fair choice for a remote venue. You'll give up instant sharing and pay for developing, but nobody needs a password.

Helping older guests and anyone who doesn't scan

Some of your favorite guests have never scanned a code. Treat that as a design requirement.

Most phones can do this from the regular camera. According to Asurion's walkthrough, on an iPhone you open Camera, frame the whole code, and tap the banner. If nothing appears, the Scan QR Codes setting under Settings > Camera may be off. On Android 8 or later, it's the Camera app, with Google Lens as the backup. Put "Open your phone camera and point it here" on the sign.

The rest comes down to removing steps. A destination with no sign-in matters most here, and a printed short link helps. So does a patient cousin assigned to go table to table during cocktail hour.

Privacy: your QR code is a public link

A QR code has no idea who's scanning it. Treat anything behind it as open to anyone who gets the link.

Google calls a shared link a URL "that people can't guess on their own," but the same page notes that a link can be shared by others once it exists. Its sharing help adds that anyone who scans the album's code can access the album. A photo of your sign posted to social media is enough to pass it along, and so is a screenshot in a group chat. If you remove a person but leave link sharing on, they can come back through the link.

Viewing is one risk. Adding is another: with Collaborate on, anyone with the link can add, and Google says you can't block individuals from adding.

Practical ways to reduce the risk:

• Prefer upload-only when privacy matters most. Dropbox describes a request's destination folder as private by default, so guests aren't handed a gallery of each other's photos.
• Use approval where it's offered. iCloud version 27 can admit only approved people, though someone has to process requests. Revel lets a host review and approve every photo before the gallery goes live.
• Put any no-post request on the sign. "Please keep photos in this album until we've shared ours" is enough.
• Think about children. If guests will photograph kids who aren't theirs, ask the parents or keep the gallery private.
• Keep the sign offline. Ask vendors to leave it out of social media shots.

Google says turning link sharing off and on resets the link. Read the next section before you touch that setting.

After the wedding: save everything before you close anything

Set an end date. Send a thank-you with the link and a deadline: "Add your photos by Sunday."

Download a full copy before doing anything else. Put the originals on your own drive, plus a second backup somewhere else.

On Google Photos, turn off Collaborate. Don't stop sharing yet. This is the big trap. Google's album settings help says that when you stop sharing an album, photos and comments other people added are removed. Turning off Collaborate only stops new additions, and photos already in the album stay. So download first, and copy guests' photos into your own library before you remove anything or anyone. Google's privacy page also says removing a person removes their photos.

On iCloud, watch storage and any temporary album. Guest additions to a version 27 album use your iCloud space, and a temporary album needs saving before it goes.

On Dropbox, close the request after the deadline. A closed request can't receive uploads until you reopen it.

Retire the link when you're done. A static code on old table cards keeps working as long as the link lives.

Common questions

Is a QR code for wedding photos free?

The code itself is free, and a static code has no expiry or subscription. Costs come from where the photos go: storage on Google, iCloud, or Dropbox, or a dedicated service with limits on its free tier. Avoid free generators that make dynamic codes on a trial, since those can stop working when the trial ends.

Do guests need an app to upload wedding photos with a QR code?

Not usually. Dedicated upload pages, Dropbox file requests, and Revel's camera all run in the phone browser. Joy is one exception, since its site says guests need its mobile app to upload to the shared gallery. With Google Photos, plan for a sign-in step and test what guests actually see.

Can Android guests add photos to an iCloud shared album?

On albums created with version 27 or later, Apple says people can join and contribute on the web without an Apple Account or Apple device. On older albums, they can view through Public Website but that isn't a contribution route. Create the album on updated software, and test from an Android phone before printing.

Do wedding QR codes expire?

Static codes don't expire, though the page they lead to might. Dynamic codes can stop working when a trial or subscription ends or when a scan limit is reached. Check both the code type and the terms of the album or service behind it.

Your next step

Do the stranger test tonight, before you've printed anything. Pick one destination, open it on a friend's logged-out phone, and add a photo. If it works, paste the link into the free sign maker. If you'd like to try the live camera route, create a free Moment in Revel for up to 10 participants and run the same test with a friend over dinner.