Wedding photos in a group chat get lost

Somebody makes a group two days before the wedding. It fills up that night, everyone laughs at the same four pictures, and by the following weekend it is a conversation about who left a jacket at the venue. Six months later the couple goes looking for a photograph they remember and cannot find it, and when they do find it, it is four hundred pixels wide.

This is the most common way wedding photographs are collected, in a lot of places it is the only way anyone has ever tried, and it is worth being precise about what it costs, because the cost is invisible while it is happening.

Why wedding photos in a group chat feel like they work

It works on the night, and that is not nothing. Everybody already has the app, nobody has to be told what to do, and photographs start arriving within minutes of the first person posting one. Compared to a service that asks for an install or an account, it wins on the only metric that matters at eleven in the evening, which is how little it asks.

It is also social in a way a gallery is not. People react, they reply, somebody posts the terrible one of the groom and there are forty responses. That is a genuine part of the wedding and no shared folder reproduces it. Nothing below is an argument for killing the group.

The problem is that the group is doing two jobs at once and it is only good at one of them. It is a conversation, and it is being used as an archive. Conversations are supposed to scroll away.

What the chat does to the photographs

Every messaging app compresses images before sending them. It has to: it is moving billions of files a day and the original off a modern phone is several megabytes. What arrives at the other end is a smaller, re-encoded copy, and the difference is not visible on a phone screen, which is exactly why nobody notices.

It becomes visible the first time you try to print one, or crop into one, or put it in a photo book. A compressed copy that looked fine at the size of your hand falls apart at the size of a page. The original still exists, on the phone of whoever took it, and you will not be asking a hundred and twenty people to go and find it eight months later.

Video is worse. Compression that is merely lossy on a photograph is brutal on a dark moving scene, which is what a reception is. Most apps also refuse anything over a size limit outright, so the speeches, which are the longest clips anybody records, are the material most likely never to be sent at all.

The half of the room that is not in the group

Somebody has to add each person by number. In practice that means the group contains whoever the organiser already had saved, which is one side of the family, one circle of friends, and not much else. Your partner's colleagues are not in it. Your parents' friends are not in it. The two people who drove four hours and left early are not in it.

Those are not marginal guests. They are frequently the ones who photographed the parts of the evening you were not at, precisely because they were not in the middle of it with you. A collection method that only reaches the people you talk to every week reaches the people whose photographs you already have.

There is also the guest who does not want to be added to a group of ninety strangers, which is a completely reasonable position and one that costs you every photograph they took.

What to do instead, without banning the group

Keep the group. Let it be the conversation, because that is what it is good at. What you add is one place where the actual files go, and the whole trick is that it has to ask the guest for less than the group does, not more. A code on the table that opens a page in the browser clears that bar: no app, no account, no being added to anything. How a shared gallery works is the shortest version of it.

Then say it out loud during the evening, once, and say both halves: post whatever you like in the group, and put the originals on the code so we get them properly. People do both when they are asked to do both. The comparison with a wedding hashtag covers the other version of this problem, which fails for a related reason: it only collects from people willing to post publicly.

One extra sentence in the group itself, pinned, does more work than anything else. Put the link in it on the night. The people who were never going to scan a card will tap a link that is already in front of them.

If the wedding already happened

It is late but it is not hopeless, and the thing that works is being specific. A general request in the group for everyone to send their photos produces two replies. A request naming a moment produces files, because it turns an open-ended chore into a search somebody can actually run.

Ask for the speeches, or the dancing after midnight, or anything from before the ceremony, one at a time, a week apart. Ask for the originals rather than a forward of what is already in the chat. And expect fewer than you would have got on the night, by a lot: the number guests actually take is much larger than the number that ever reaches the couple, and the gap is almost entirely down to when you asked.