Skip to content
All articles

How many wedding photos from guests should you expect?

Nobody can give you an honest average. Here is what actually decides how many wedding photos from guests you end up with, and what they weigh.

August 26, 20265 min read

There is no honest average. Anybody quoting you a figure has measured one wedding, or made it up, and the spread between two weddings of the same size is wide enough that a single number would not help you plan anything.

What is worth knowing is which decisions move it, because you are making most of them already. This is how to arrive at a number for your wedding rather than for a wedding in general, and what that number costs you in storage.

They are not spread evenly across the day. If you plotted them on a timeline you would get four or five spikes with long flat stretches in between, and the spikes are always in the same places.

The arrival and the first hour, when everybody is dressed, sober and has nothing to do but look at each other. The ceremony, where the phones go up whether you asked for that or not. The toasts. The first dance. And then the late part of the night, which produces more frames than any other hour and almost none of them in focus.

The flat stretches matter as much. During dinner people put their phones down. During the speeches they are listening. A wedding with a long seated dinner and a short dancefloor produces a fraction of what a wedding with a short dinner and a band until two in the morning does, at the same guest count, on the same day.

The late part of the night produces more frames than any other hour, and almost none of them are sharp.

The four things that move the number

In rough order of how much difference each one makes.

  • Whether you asked. This is the largest single factor and it costs nothing. A wedding where nobody was told to send anything gets whatever happens to arrive in a group chat over the following week, which is a small and arbitrary slice. A wedding where the ask was made out loud and there was somewhere obvious to send them gets most of what was taken.
  • How long the party runs. Hours on the dancefloor, not hours at the venue. The number roughly tracks the length of the loud part of the night.
  • Guest count, but less than you would think. Photographs come from a minority of the room, and it is a fairly stable minority. Doubling the guest list does not double the photographs, because the extra guests are disproportionately the ones who take none.
  • Whether the phones are welcome. An unplugged ceremony cuts one of the spikes entirely, which is a legitimate choice and worth making deliberately rather than discovering afterwards.

There is a fifth that only shows up later. If people can see the photos going in, they add more. A gallery that visibly fills up during the evening turns into a small competition, and a folder that swallows uploads silently does not.

What it weighs

This is the part you can actually calculate, and it is the reason the question comes up at all. A photograph off a recent phone usually lands somewhere between two and five megabytes. Portrait mode and the higher resolution settings push it up, older phones and messaging apps push it down.

So a thousand guest photographs is somewhere around two to five gigabytes. Ten thousand would be twenty to fifty. That is the entire arithmetic, and it is why the smallest paid plan here is measured as fifty gigabytes rather than as a photo count. Counting photographs would be the wrong unit, because one guest sending four minutes of video costs more than two hundred stills.

Video is what actually moves the total. A minute of phone video is roughly sixty to a hundred megabytes at 1080p and several times that in 4K, so a handful of clips from the dancefloor weighs more than the whole ceremony. Apple's own camera guide says as much: faster frame rates and higher resolutions make larger files. If people are going to send video, plan for it rather than being surprised by it. The plans and their storage are all sized around that, with a per-file ceiling of twenty megabytes for a photo and ninety for a video.

Most of them will not be keepers

This is worth saying plainly, because the count is not the point. A large proportion of what guests take is blurred, badly lit, a duplicate of the shot next to it, or a photograph of the back of somebody's head. That is not a failure. It is what a phone at a party produces and it is the price of the twenty or thirty frames that are genuinely worth having.

Those twenty or thirty are also the ones your photographer could not have taken. They are from inside the group rather than outside it, at the table, in the car, at four in the morning. Nobody is paid to be there and that is exactly why they are different.

So do not go looking for a high number. Go looking for coverage of the moments the professional was not in the room for, and accept the noise around them as the cost of getting those at all.

What to do with the number

Pick a plan on the storage, not on a photo count, and pick it slightly higher than your estimate. The failure you are insuring against is an upload being refused at eleven at night at somebody else's wedding, which nobody will tell you about and which you cannot fix afterwards.

Then stop thinking about it. The number is not something you control on the day, and the two things that actually change it are both decided weeks earlier: whether there is somewhere obvious to send photographs, and whether anybody said so out loud.

The first of those is where you put the card. The second is what you say when you ask, which is one sentence and gets left out of almost every wedding.

Start your gallery

Create an event, print the card, and let your guests fill it in on the night.