Wedding venue wifi is bad. Plan for it.

The objection that kills photo collecting on the night is never the software. It is that a hundred and twenty people are standing in a stone building on a hill and nothing will send.

This is worth planning around rather than hoping about, because it is predictable. The failure has a shape, it happens at a known hour, and almost all of the damage comes from guests not knowing what to do when it happens.

Test the wedding venue wifi at the hour it matters

Whatever the venue told you, and whatever it did on the site visit, means very little. You went at eleven in the morning with four people in the building. The condition you care about is a full room at half past ten at night.

Two things change between those. The first is the number of devices. A cheap access point handles a couple of dozen clients and then falls over, and a wedding puts one phone per guest into the room, all of them awake, all of them holding a connection whether anybody is using it or not. The second is that the venue is often running another event, or the kitchen, or a card terminal on the same line.

If you can, test during another wedding. Ask the venue whether you can come by for twenty minutes on a Saturday night, stand where your guests will stand, and try to send a photograph and a short video. That single test tells you more than any answer the venue gives you, and it takes an evening.

If you cannot, ask a narrower question than does the wifi work. Ask how many people it has had on it at once, and whether it is the same connection the till uses. The answers are usually revealing and the venue is usually honest about it.

Mobile data is usually the better bet

At most weddings the phone network beats the venue wifi, because it was not built for one room. The exception is the case that matters here, which is a thick-walled building somewhere rural or coastal, and that is exactly the kind of place people get married.

The practical thing this changes is where you put the card. If reception is good outside and poor inside, uploads will happen on the terrace, at the smoking spot and in the car park. A card on the tables is still right, and a second one wherever people naturally step outside is worth printing.

It also changes what you ask for on the night. Photographs go over a weak connection. Video mostly does not, and a guest watching a bar crawl slowly across the screen will give up and never come back to it. If the venue is bad, ask for photographs during the evening and video whenever they get home.

What to put on the card

Put the wifi name and password on the same card as the code. This is the single highest-value thing on this page and it costs one line.

Guests ask for the wifi password at every wedding anyway, usually by interrupting somebody in the wedding party during dinner. Printing it means they never have to ask, and it means the guest who was about to give up on a slow upload has an alternative already in front of them rather than a reason to stop.

Write the password exactly as it is typed, in a font where a one and an l are not the same shape, and put it below the code rather than above it. Above the code belongs to the sentence that says what the code is for, and that line is the one doing the real work.

Nothing is lost when it drops

This is the part guests do not know and the reason most photographs go missing on a bad night. A guest whose upload stalls assumes it failed, closes the tab and moves on, and those photographs are gone for good even though the network came back twenty minutes later.

So it is worth knowing what actually happens. A stalled upload retries with a widening gap between attempts rather than hammering a connection that is already struggling. A batch is uploaded a few files at a time rather than all at once, because forty parallel transfers over one weak link is slower than four. If the server is under pressure it says so and the phone waits, instead of both sides fighting.

The phone screen is held awake while a batch is running, because a locked screen used to be the most common way an upload died halfway. And if the tab is closed or the browser evicts it, the list of what was sent is written down locally and checked against the gallery when the guest comes back, so they are told which photographs did not make it by name rather than being asked to guess. A part-sent video does not start again from zero either. It sends the gap.

None of that helps somebody who has already given up, which is why it belongs in this article rather than in a feature list. The mechanics are covered properly in the guide if you want them.

The one thing to tell guests

Say, out loud, that it does not have to happen tonight. That single sentence removes the whole problem for the majority of the room, because the people who fail on venue wifi are not people who cannot send photographs. They are people who tried once, at the worst possible moment, and concluded it was broken.

The upload window is weeks, not hours, and it exists for exactly this. The gallery stays open long after the wedding and nothing is deleted on a timer, so a guest who sends everything from their sofa on Sunday afternoon is not late. Which plan you are on decides how many weeks that is, and the plans are all sized in storage rather than in photographs.

It also has to be said at the right moment by the right person to land at all, which is a separate and slightly counterintuitive problem.