We analyzed 203 real weddings. Here is how many photos guests actually uploaded.
The single most common question we get from couples deciding on a QR photo album is whether guests will really use it. This is the answer, from our own platform's data.
Data pulled from real Pix Wedding events on 10 July 2026. Methodology, exclusions, and limitations stated in full below. Numbers are traced to internal aggregates, not survey data.
What counts as a qualifying wedding
Every number on this page comes from the same inclusion rule. Stating it plainly matters more than the numbers themselves.
The median is 149. A quarter of weddings finished under 70, a quarter finished above 253, and the largest single wedding in the dataset closed at 1,365 guest uploads, from just 3 guests.
The story is not the maximum. The story is that 197 photos on average is a stack of images a couple would not otherwise have. Their professional photographer took what they took. These 197 are the second angle.
Median 8. A quarter of weddings finished with 5 or fewer unique guest uploaders, a quarter with 13 or more. The maximum in our dataset was 60 unique uploaders at a single wedding.
The wedding with the most uploaders was not the wedding with the most photos.
The wedding at the top of our uploader-count list drew 60 unique guest uploaders and finished with 224 photos. The wedding at the top of the photo-count list drew just 3 unique uploaders and finished with 1,365 photos. Big volume in a wedding album is driven by a small number of enthusiastic guests, not by breadth of participation.
This changed how we think about our own product. Reducing friction for the marginal, hesitant guest earns a lot less album volume than reducing friction for the guest who is already uploading fifteen photos and would upload thirty if it were easier.
First dance
You guys!!
Start your own album, add to our dataset
Free to start. 20 guest uploads free, no card. When your wedding is done, your numbers count.
From Mom
Scan to join the album
No app, no account
UPLOADING
Saving your moment
THE ALBUM
Emma & Jack
June 21, 2026
647 photos · 95 guests
SCAN TO TRY
pix.wedding/
your-wedding
A guest who uploads at all uploads a lot. Average is around 26 photos per guest, median around 17. A quarter contribute fewer than 11, a quarter contribute more than 27. The heaviest single guest crossed 100 uploads.
The gap between p75 and the average tells the story of the long tail. The 75th percentile guest uploads 27 photos, but the average is 26. That is because a small number of guests upload dozens each and pull the mean above the middle. This is the exact pattern behind Finding 2.
Of 40,531 guest media items in the dataset, 2,078 were videos. Photos still dominate wedding uploads by a wide margin.
The HEIC share is worth flagging for anyone building around iPhone uploads. It is small at 1.5% because we transcode HEIC on the way in. In the raw guest camera roll it would be much higher; on the way to the album it looks like a normal JPG.
Audio guestbook is a Standard-plan feature that lets guests attach a voice message alongside a photo. Only 14 of the 203 qualifying weddings had at least one audio message attached. Across those 14 weddings, 130 total audio messages were recorded.
We shipped audio guestbook and roughly seven percent of eligible events used it.
We think the feature is beautiful when it lands. The barrier is discoverability: most couples on Standard and above do not realize the feature is included, and most guests do not think to look for a voice note button after selecting a photo. We are working on discoverability. As of this dataset it is one of the least-used features we ship.
Almost all our dataset is small-to-mid weddings
We do not capture headcount, so we bucket weddings by the only wedding-size proxy we have: unique guest uploaders. This is not the same as guest count and we do not pretend otherwise. Even so, the shape is clear.
| Wedding size bucket (by unique uploaders) | Weddings in bucket | Average photos | Median photos |
|---|---|---|---|
| Small (under 30 uploaders) | 200 of 203 | 193 | 148 |
| Mid (30 to 79 uploaders) | 3 of 203 | 451 | 554 |
| Large (80+ uploaders) | 0 of 203 | n/a | n/a |
Two important things follow from this. First, we cannot report anything about weddings with 80 or more unique uploaders because we have zero of them in the dataset. Second, the tiny mid-bucket (three events) is not enough to make strong claims about, so treat the mid-bucket averages as directional only.
What this data does not, and can not, show
A stats page is only trustworthy if the author names its own limits before a reader has to guess. Here are ours.
We do not ask couples how many people they invited or attended. Every number here counts uploads and unique uploaders. Nowhere do we report participation as a share of the guest list, because we do not have the denominator.
Every wedding in this dataset chose our product. Couples who used a different QR photo tool, or a shared Google Photos album, or no digital collection at all, are not represented. This dataset is descriptive of Pix Wedding users. It is not a claim about weddings in general.
200 of 203 events fall in the sub-30-uploader bucket. Only 3 events reach 30 or more uploaders. Zero events have 80 or more uploaders. Anything you take away from the wedding-size table should be treated with that in mind.
We count unique guest uploaders using the name a guest typed when they uploaded. A guest who uploads twice under two spellings of their name is counted twice. A group of guests sharing one phone is counted once. In practice this washes out in aggregate, but no unique-uploader count from a photo-sharing product is a true headcount.
This page is about upload counts, but our sister page on when guests upload uses UTC-based day buckets. Weddings in high-offset timezones can bleed some reception-night uploads into the day-after bucket. Read that page's methodology section for the details.
What to take away if you are still deciding
Stats pages are easy to nod at and hard to actually use. Three concrete moves come out of this dataset for anyone deciding whether to set up a QR photo album for their own wedding.
The realistic expectation is 149 guest photos, not 1,365. If your mental picture of a working album is more than a thousand images, most couples in our dataset would have felt disappointed. If your mental picture is a couple hundred images that would otherwise have never left phones, most couples land there.
The typical wedding gets uploads from 8 unique guests. Those 8 upload around 17 photos each. The volume comes from the top few, not the whole invite list. If your goal is a full album, invest in the guest who is already uploading (put the QR near them, make the flow one-tap), not the guest who was never going to.
5% video share is not zero, but it is not the point either. Guests are much more comfortable snapping photos than shooting video. If a video moment matters to you, ask someone directly. The QR album is not going to accidentally produce a great video reel.
Pages built on this dataset
The exact rules behind every number
So a careful reader (or a curious rater at Google) can trace each figure back to a real query rather than take our word for it.
Every event with isActive true, where eventUrl is not the marketing demo slug, and whose totalPhotos counter is at least 20. Result: 203 events.
Count of guest-upload photo documents per event (isGuestUpload true, seeded false). The distribution is skewed right, which is why we quote both the median and the average and treat them as two different signals.
Distinct uploaderName values across guest uploads for the event. We cross-checked this against distinct uploaderEmail and uploaderPhone and confirmed that name-based counting is not undercounting on our data: those fields are almost never set on guest uploads, so name-distinct is the only usable identity field, and it does not miss uploaders that other fields would have caught.
Documents whose mediaType is video, divided by all guest media in the qualifying event set. Legacy uploads without an explicit mediaType field are treated as images (they are almost always JPEG or HEIC on inspection).
Events in the qualifying set that have at least one photo document with an attached audioMessage.url. This measures adoption at the event level, not per-guest, so 6.9% is the share of couples for whom the audio feature ever appeared, not the share of guests who left one.
Reading this page as a couple
If you are trying to decide whether guests will really upload, the useful number to lock into is the median: 149 photos per wedding, from 8 unique guest uploaders. That is what most couples in our dataset saw. The average pulls higher because a small number of very large albums pull the mean up.
The most common mistake we see couples make when they read stats like these is treating one huge number as the promise. A single 1,365-photo wedding exists in this dataset, and it came from just 3 very active guests. Most weddings do not look like that. Plan for the median and treat everything above it as bonus.
Reading this page as a fellow builder
If you are working on any product that captures user-generated content at events, the shape here is worth studying. The volume comes from a long tail: a small share of guests contributes the bulk of the album. The median 8-uploader event with 17 uploads per uploader tells the same story as the 3-uploader event that produced 1,365 photos: a few enthusiastic people drive the archive.
The most useful thing this data changed for us is where we invest in friction reduction. Improving the flow for the marginal, hesitant guest yields much less than improving the flow for the guest who is already uploading twenty photos and might upload thirty.
Explore more free wedding tools
Everything you need to make your wedding day stress-free and unforgettable.
QR Sticker Designer
Design custom print-ready stickers.
Hashtag Generator
Create unique wedding hashtags.
How to Collect Guest Photos
5 methods ranked by participation rate and ease.
Get Photos After the Wedding
Message templates to gather guest photos post-wedding.
Share Wedding Photos with Guests
Compare every sharing platform by ease and participation.
Best Way to Get Guest Photos
The single method with the highest participation rate.
How to Make a Shared Wedding Album
Step-by-step setup for every platform.
Alternative to Disposable Cameras
Better, cheaper options than disposable cameras.
Frequently asked questions
Everything you need to know about our free tools and how they help your wedding day.
Across 203 real weddings on the Pix Wedding platform, the average was 197 photos per wedding, with a median of 149. A quarter of weddings collected 70 or fewer, and a quarter collected 253 or more. The biggest single wedding album in the dataset held 1,365 guest uploads, driven by just 3 guests.
On average, 9.8 unique guests uploaded at least one photo per wedding, with a median of 8. A quarter of weddings had 5 or fewer unique uploaders and a quarter had 13 or more. The busiest single wedding drew 60 distinct uploaders. Wedding photo participation is driven by a small handful of enthusiastic guests, not the whole room.
No. In our dataset, the wedding with 60 unique uploaders collected 224 photos. The wedding with the highest photo count, 1,365 photos, was driven by just 3 uploaders. Volume is driven by a few high-contribution guests, not by breadth of participation.
On average, each guest uploader added around 26 photos, with a median of about 17. A quarter of guest uploaders contributed fewer than 11 uploads, and a quarter contributed more than 27. The heaviest single guest uploader crossed 100.
Roughly 5.1% of guest media in our dataset was video, drawn from 2,078 video uploads across 40,531 guest media items. Photos still dominate wedding uploads by a wide margin.
It does not show total guest counts (we do not capture headcount), so we never report participation as a percentage of the guest list. It also skews to small and mid weddings; only three events crossed 30 unique uploaders and none crossed 80. The dataset is our own users, so it is not representative of every wedding sharing app, and it is not representative of couples who chose a different tool.