---
title: "Do wedding guests need to download an app to share photos?"
description: "No. Guests scan the QR code, the album opens in their phone's browser, and they upload from their camera roll. There is no app to install, no account to create, and no password to remember."
source: https://www.wedding.studio/faq/do-guests-need-an-app-to-share-wedding-photos
---

# Do wedding guests need to download an app to share photos?

No. Guests scan the QR code, the album opens in their phone's browser, and they upload from their camera roll. There is no app to install, no account to create, and no password to remember.

No. A guest points their phone camera at the printed QR code, taps the notification that appears, and the album opens in Safari or Chrome. From there they choose photos and videos from their camera roll and upload. The whole thing takes under thirty seconds and leaves nothing installed on their phone.

That's the answer that matters for the guests you'd never talk into a download: your aunt holding the only photo of the toast, the friend whose phone storage has been full since 2019.

**Why this matters more than it sounds.** Every step between "I should share these" and "done" loses people, and installing an app is the most expensive step you can put in the way. It means opening a store, signing in to that store, waiting on a download, granting permissions, and often creating yet another account. At a wedding, where a guest is holding a drink and half-listening to a speech, that sequence doesn't survive. A browser upload survives because it's one tap away from a camera the guest already has open.

<VerifiedClaim date="2026-07">QR scanning is built into the stock camera app on every iPhone running iOS 11 or later and on Android 9 or later, which covers effectively every phone at a modern wedding.</VerifiedClaim>

Guests with much older handsets, or with a camera app that has scanning disabled, can type the album's short link instead. That link belongs on the [printed QR card](/guides/printed-qr-cards) underneath the code.

**What the guest actually experiences.** They scan a code you've [placed where guests are already sitting](/guides/qr-code-placement), and the album loads with your names on it. If you've asked for names, they type theirs once; otherwise they go straight to the upload button. They select from their camera roll, watch a progress bar, and see their photos land in the feed alongside everyone else's. If the album is set to reveal later, they see a confirmation instead of the feed, which is the point.

Nothing is stored on their device, nothing asks for their email, and no login is created. If they come back an hour later and scan again, the album remembers them on that phone and they can add more.

**The trade you're making.** A browser-based album gives up one thing an installed app genuinely does better: background upload. An app can keep pushing large video files while the phone is locked and the guest is dancing. A browser tab can't, so a guest uploading a two-minute 4K video needs to leave the tab open until it finishes. In practice this is why a real share of every album arrives in the days after the wedding rather than on the night. People start the big files at home instead.

That's a genuine loss on the night, and it's the trade we'd still make. Background upload only beats a browser for the guests who install the app first, which is the step this whole page exists to remove.

<ComparisonTable
  caption="What the guest has to do, by method"
  columns={["Method", "Steps before the first upload", "Account required", "Photo quality"]}
  rows={[
    ["QR code to a browser album", "Scan, tap, select", "No", "Original resolution"],
    ["Dedicated guest app", "Store, download, permissions, sign-up, then upload", "Usually", "Original resolution"],
    ["Shared cloud folder", "Sign in to a cloud account, accept the invite, upload", "Yes", "Original resolution"],
    ["Messaging app or social feed", "Send", "Already signed in", "Compressed"],
  ]}
/>

**Does no app mean lower quality?** No, and this is the confusion worth clearing up. The compression people associate with guest photos comes from messaging apps and social feeds, not from the browser. Files uploaded through the album keep their original resolution, which is what makes them big enough for a [photobook built from the guest album](/guides/photobook-from-guest-photos). A photo that reached you through a group chat generally isn't.

**What about guests who refuse on principle.** Some will, and you're better off planning for it than arguing with it. The answer is the same one that works for the guests who simply forget: ask a specific person for a specific thing afterwards. "You filmed the first dance. Can you drop it in the album?" gets a response that a general appeal doesn't. Anyone who'd rather not use it at all can still send you the files directly, and you can add them yourself as a co-host.

Across the <Stat name="weddingsCount" /> weddings that have run an album this way, the objection we expected (that guests would find a browser upload confusing) hasn't materialised. The friction that actually costs photos is social: nobody told the room the album existed, which is the gap our [guide to setting up a wedding QR code](/wedding-qr-code) walks through end to end.