QR Photography: Add a QR Code to Photo Albums and Sharing
How do you get 120 wedding guests to put their photos in one place, instead of 120 camera rolls?
That’s what QR photography usually means in practice: a QR code that opens a photo album, an upload page or a client gallery. Guests scan a card on the table and the photos flow into one album. Photographers print one on the back of a print and the client lands in their gallery. (If you came here for photographing QR codes, that’s a different problem: here’s how to scan a QR code from an image.)
I build QR code tooling at linkutm, so I care about the boring parts. Which album service lets guests add photos without an account? How big does the code have to be? And what breaks a year later? I tested the size question myself. You’ll get a service comparison, the steps, measured print sizes, and the trade-offs nobody puts on the table card.
What Is QR Photography?
QR photography is the use of QR codes to connect printed material to photos online: event albums, guest uploads and client galleries. The core object is a QR code for photo sharing, a QR code that stores a link to an online album, upload page or gallery. It never holds the photos. A QR code tops out at about 3 KB of data, so every “photo QR code” is really a link to photos hosted somewhere else.
That one fact sets up the whole system. There are three parts, and each one can fail on its own:
- The printed code. Black and white modules on paper. It only knows a URL.
- The link. Either the album service’s own share link, or a short link you control that redirects to it.
- The album service. Google Photos, iCloud, Dropbox, Google Drive or a photographer’s gallery. The service decides who can view, who can add, and at what quality.
Here’s the thing: most people choose the code design first. The album service matters far more. It decides whether guests without an account can upload, and whether you get full-resolution files back.
The limitation is plain. A QR code can’t fix a bad album choice. If the service needs an account your guests don’t have, the code just opens a sign-in screen.
Which Photo Album Service Should the QR Code Open?
In QR photography, the album service matters more than the code. Pick it by what guests need to do. Viewing is easy everywhere. Uploading without an account is where the services split.
| Service | Guests view by link | Guests add photos without an account | Built-in QR code | Quality you get back |
|---|---|---|---|---|
| Google Photos shared album | Yes | Link holders can add; account need not documented | Yes (Share > Show QR Code) | Not documented |
| iCloud Shared Albums (iOS 27 and web) | Yes | Yes, on the web, per Apple | Not documented | Full resolution (iOS 27 albums) |
| iCloud Shared Albums (made in iOS 26 or earlier) | Yes, with Public Website on | No | Not documented | 2048 px long edge, 720p video |
| Dropbox file request | No, upload only | Yes | No | Original files, up to 2 GB each on Basic |
| Google Drive folder | Yes, without signing in | Not documented when signed out | No | Original files |
| Pixieset client gallery | Yes, optional password or email | No (photographer delivery) | Yes (Get QR code) | Set by photographer |
I checked every cell against the vendor’s own help pages on October 27, 2026. “Not documented” means exactly that: I couldn’t find an official answer, so I won’t guess.
My pick for events is a Dropbox file request when you mainly want to collect photos. When guests should also see each other’s shots, use an iCloud Shared Album made on iOS 27. Google Photos is the easy default if most guests already have Google accounts.
The trade-off: Dropbox uploads count against your own storage, and the request link opens an upload form, not the album. People like seeing the album grow. An upload form feels like sending files into a void.
Google Photos QR code: built into every album
Google Photos already makes a QR code for an album. Open the album, tap Share, then Show QR Code. Google’s help page says anyone with the shared link “can view the photos and add to the album.” Turn off Collaborate under Options to stop people adding.
Google also lets you reset the link at any time. That’s a feature and a trap. Reset it after printing and every table card dies.
One more wrinkle. Google Photos links use the photos.app.goo.gl domain, and Google shut down most goo.gl links in August 2025. Google says goo.gl links “generated via Google apps (such as Maps sharing) will continue to function.” Photos isn’t named in that statement. I’d still print a link I control in front of it.
iCloud Shared Albums: changed in iOS 27
Apple rewrote Shared Albums in iOS 27. Apple’s support page says friends and family “will be able to join and contribute their own photos on the web, even without an Apple Account or Apple device.” Shared photos now keep full resolution and count against the owner’s iCloud storage.
To get the link on iOS 27, open the album, go to Participants, and tap Copy Album Link. You can let anyone with the link join without approval. An album holds up to 100 participants, including you.
Older albums still follow the old rules. Per Apple’s limits page, albums made in iOS 26 or earlier cap at 5,000 photos and videos. Photos shrink to 2048 pixels on the long edge, and video stops at 720p. If your album predates iOS 27, make a new one before printing.
Dropbox file requests: upload without an account
A file request is a Dropbox upload page that drops files into a folder you own. Dropbox’s help page is blunt: “You don’t need a Dropbox account, or need to be signed into one, to respond to a file request.” Guests may be asked for a name and email.
Files arrive as originals. Dropbox Basic, Plus and Family accept files up to 2 GB each, and business plans up to 250 GB. Make sure you have the storage before 300 guests start uploading 4K video.
Photographer client galleries
For photographers, the album is the delivery gallery. Pixieset gives each collection a direct link and a Get QR code download, plus passwords, download PINs and email registration. Pixieset itself notes that email registration “is not a security feature.”
Pic-Time uses access codes, and its QR codes cover guest pre-registration. ShootProof galleries are private behind a direct URL and a password, and I found no built-in QR code in its help center. So for ShootProof, you’d generate the code yourself.
How to Add a QR Code to a Shared Photo Album (Step by Step)
Okay, so here’s the process I’d follow for any event or client delivery. It takes about 15 minutes, most of it testing.
- Pick the service by the job. Use the table above: upload-only, shared viewing, or client delivery.
- Set permissions before you copy anything. Turn on adding (Collaborate in Google Photos, Can Add Photos in iCloud) or create the file request. Changing permissions later can change or reset the link.
- Copy the share link. Paste it in a private browser window while signed out. If it asks you to sign in, your guests will see the same wall.
- Put a short link in front of it. Create a dynamic QR code or a short link that redirects to the album. If the album moves, you update one redirect instead of reprinting.
- Generate the code. A wedding photo QR code or party table card needs nothing fancy. Use level M error correction unless you add a logo. The wedding QR code generator is built for exactly this card.
- Size it for the distance. See the next section. A table card needs about 3 to 4 cm for a typical album link.
- Test on three phones before printing. At least one iPhone and one Android, from the real distance, in the room’s light.
- Print the instruction next to the code. “Scan to add your photos” beats a bare code every time.
The limitation: step 4 adds a dependency. The short link service now sits between the code and the album. Pick one you trust to be around as long as the prints.
How Big Should a Photo Album QR Code Be? (My Test)
For QR photography at events, a QR code for a typical album link needs to be about 3.3 cm wide on a table card read at 40 cm. A short link gets that down to 1.8 cm. A long Google Drive folder link needs 4 cm.
I measured this rather than quoting a rule of thumb. The test script turns each share-link format into a QR code and simulates a phone camera reading it at increasing distances. Each setting got 40 simulated scans with two decoders (zxing-cpp and OpenCV), with blur, noise and slight rotation. A size “passes” only when both decoders read at least 38 of 40 at that distance and every closer one.
| Link pointing to the album | Characters | QR version (level M) | Reliable distance | Table card, 40 cm | Easel sign, 1.5 m | Poster, 3 m |
|---|---|---|---|---|---|---|
| Short link | 26 | 2 (25×25 modules) | 22x code width | 1.8 cm | 6.8 cm | 13.6 cm |
| Typical album share link (Google Photos, iCloud, Dropbox request, Pixieset) | 43 to 52 | 4 (33×33) | 12x | 3.3 cm | 12.5 cm | 25.0 cm |
| Google Drive folder link | 84 | 5 (37×37) | 10x | 4.0 cm | 15.0 cm | 30.0 cm |
| Drive folder link + UTM tags | 150 | 8 (49×49) | 10x | 4.0 cm | 15.0 cm | 30.0 cm |
Widths are the code itself. Add the quiet zone, a white margin of four modules on every side, around it.
Two results surprised me. First, every common album link landed on the same QR version. At level M, anything from 43 to 62 characters is version 4. Count the characters in your own link: up to 26 is version 2, up to 42 is version 3, up to 62 is version 4, and up to 84 is version 5.
Second, the UTM-tagged Drive link tied with the plain one on my strict pass rule, but it wasn’t really equal. At 12 times its width away, the version 8 code read 24 of 40 times. The version 5 code read 35 of 40. Long links fail sooner and harder.
The honest caveat: this is a simulation, not a phone in a dim reception hall. It has no focus hunting, glare, motion or curved paper. Real phones usually do better close up and worse in bad light. Treat the table as a minimum, then test. The full mechanism behind link length and size is in my guide to the smallest QR code size, and the camera side is explained under QR code scanning distance.
Where QR Photography Codes Work Best
Put the code where people already have their phones out and a free minute. At events, that’s the table, the bar queue and the photo booth.
- Table cards. The highest-value spot at a wedding or party. Guests sit for an hour with phones in hand. Print 3.5 to 4 cm codes for a typical album link.
- Photo booth prints. A code in the corner of each strip sends people to the full gallery. Booth strips are about 5 cm wide, so a short link matters here. A version 4 code eats most of the strip width.
- The back of physical prints. Photographers can print the gallery code on the back of a proof or album page. The client finds the digital set years later.
- Welcome signs and easels. Read from 1.5 m or more, so go big: 12.5 cm or more for a typical album link.
- The slideshow screen. A code on the reception screen gets scanned from across the room. Make it fill a large part of the slide.
- Client delivery emails and thank-you cards. A printed thank-you card with the gallery code gets a second wave of visits.
For event-wide signage beyond photos, the event QR code generator covers schedules and maps. Wedding-specific uses like RSVP and registry live on the wedding tool page.
The limitation: not every guest will scan. Print a short typed URL under the code as a fallback. Some guests would rather type a short address than open the camera.
Will the Photo QR Code Still Work Next Year?
A photo album QR code keeps working only as long as the link inside it keeps working. The code itself never expires. The album link often does: albums get deleted, links get reset, and services change their rules.
That’s the real argument for a dynamic QR code. A dynamic code stores a short link, and you can change where it points after printing. A static QR code stores the album link directly and can never be updated.
Three things break printed photo codes:
- The owner resets the share link. Google Photos and iCloud both let you invalidate a link. Great for privacy, fatal for printed cards.
- The album moves. Someone migrates from Google Photos to iCloud, or from a free gallery to a paid one.
- The plan lapses. Photographer galleries often expire with the subscription.
With a dynamic code, each of those is a 30-second redirect change. I wrote up how long each type actually lasts in do QR codes expire.
The trade-off: a dynamic code depends on its provider staying in business. If you never expect the album to move, a static code with the service’s own link has one less moving part.
Privacy: Who Can See a Photo Album Behind a QR Code?
Anyone who scans the code can open the album, and so can anyone who photographs your table card. That’s the privacy cost of QR photography. A printed QR code is a public link. Treat the album as semi-public, even if it’s “unlisted.”
What I’d do:
- Use an upload form for collection. A Dropbox file request link opens an upload page rather than the album itself.
- Turn off adding after the event. Switch off Collaborate in Google Photos, or stop the file request, so strangers can’t add later.
- Use a password for client galleries. Pixieset, Pic-Time and ShootProof all support passwords or access codes. Print the code; send the password separately.
- Keep children’s photos out of public albums. Use a password-protected gallery instead of an open shared album.
The limitation: none of this stops someone sharing a photo they downloaded. A QR code controls the door, not what people do once inside.
How to Know If Guests Actually Scanned It
Album services tell you who uploaded, not who scanned and gave up. A dynamic QR code with scan analytics shows the gap: how many people scanned versus how many photos arrived.
On one table card, that tells you whether the problem is the code (few scans) or the album (many scans, few uploads). If scans are high and uploads low, the album probably asked for a sign-in. If you tag the destination with UTM parameters, QR code tracking in GA4 shows the sessions too, though album services rarely run your analytics.
The limitation: scan counts include repeat scans and curious staff. Use them as a trend, not an exact guest count.
Frequently Asked Questions
How do I make a QR code for a shared photo album?
Create the shared album, turn on link sharing and adding, and copy the link. Paste the link into a QR code generator, preferably as a dynamic QR code so you can change the album later. Test the code on an iPhone and an Android phone before printing.
Can guests upload photos with a QR code without an app?
Yes. A Dropbox file request opens in the phone’s browser and needs no Dropbox account. iCloud Shared Albums made on iOS 27 also let people contribute on the web without an Apple Account, according to Apple. Google Photos lets link holders add photos, but Google doesn’t document whether that needs a Google account.
Does Google Photos have a QR code for albums?
Yes. Open the album, tap Share, then Show QR Code. Anyone with the link can view the album, and they can add photos if Collaborate is on. The QR code holds the album’s share link, so resetting that link breaks the code.
What size should a photo QR code be on a table card?
About 3.3 cm wide for a typical album share link read from 40 cm, based on my simulated test. A short link can go down to about 1.8 cm, and a long Google Drive link needs about 4 cm. Always add a four-module white margin and test with real phones.
Do photo album QR codes expire?
The QR code itself doesn’t expire. It stops working when the album link does: the album is deleted, the link is reset, or the service plan ends. A dynamic QR code lets you point the same printed code at a new album.
Is QR photography safe for private photos?
Only with a password or upload-only setup. Anyone who scans or photographs the code can open an open shared album. For private photos, use a password-protected gallery or a file request, and turn off adding after the event.
Start With the Album, Then the Code
QR photography is simple once you get the order right. The album service decides almost everything. The code only opens the door.
What to remember:
- Choose the service by the job. Dropbox file requests for collecting, iOS 27 iCloud albums for shared viewing, client galleries for delivery.
- Check sign-in walls. Open the link signed out before you print.
- Size it right. About 3.3 cm for a table card with a typical album link, 1.8 cm with a short link.
- Plan for the album moving. A dynamic code turns a dead card into a 30-second fix.
- Close the album after the event. Turn off adding, or close the file request.
Make the code itself with the free image QR code generator, or point a Google Drive folder QR code at a folder you control. If you want an editable code with scan counts, create a dynamic QR code with linkutm. It’s free to start, and you can repoint every printed card when the album moves.
