
Wedding photo collection
A wedding photo collection website built around your guests
One web address, shared before the wedding. A gallery that fills as the day progresses. An archive you download when it is over. The whole structure of collecting guest photographs is here.
A wedding photo collection website is a specific thing: a page at a stable address where guests can send photographs without registering, where the event owner controls what appears and who can browse, and where the full set of files can be downloaded as an archive at the end. The word 'website' here means something built to work in a browser without installation, designed around the fact that the people contributing to it are at a wedding, not in front of a computer.
The alternative most couples try first is a shared folder in a cloud service. Those fail for two predictable reasons. The first is authentication: the folder requires a login, and not every guest has the right account. The second is friction: attaching files to a folder is not an action most people do from a phone at a party, and the ones who would do it after the event have usually lost track of the link.
What a wedding photo collection website needs to do
Open without installation
The page has to work in a mobile browser from a QR code scan. Installing anything is a step too many at a wedding, and the design cannot assume every guest is using the same operating system or the same version of anything.
Accept contributions without accounts
A guest provides a name, selects photographs, and sends. No email, no password, no registration. The barrier is the same whether the guest is twenty-three or seventy-eight.
Collect video and photographs together
A wedding produces both, in the same camera roll, taken by the same guest. A collection page that accepts only images forces a choice the guest should not have to make.
Give the event owner control
Who can browse the gallery, whether submissions need approval, and when the collection closes are decisions for the couple, not the guests. Each setting is accessible from the dashboard without changing the guest experience.
Produce a downloadable archive
The collection is not permanent by design. The plan has a duration, and at the end of it the owner downloads an archive of everything. The archive is the copy that belongs to the couple; the platform is the mechanism for collecting it.
The gallery: private by default, controlled by the couple
A wedding photo collection involves two distinct groups: the guests contributing photographs and the people the couple wants to share the finished gallery with. These may overlap or not, and the settings exist to handle both.
- Guest browsing
- Switched on, guests can see each other's contributions while they upload. Switched off, the page becomes an upload form: guests send photographs without seeing what anyone else submitted. Most couples keep it off during the event and switch it on the week after, when the collection has been reviewed.
- Approval
- With approval on, every submission waits in a queue until the event owner accepts it. Accepted submissions appear in the gallery and in the room slideshow. Rejected ones are excluded from the gallery and from the downloadable archive. This is the right setting for a room containing people you have not met, or a couple who wants to review before anything is public even within the collection.
- The collection address
- The address is not listed anywhere. Guest pages are excluded from search indexes. The couple shares the address themselves — in invitations, in messages, on printed cards — and nobody else can find it without it.
- The room screen
- A separate slideshow address, gated by a token, plays accepted photographs on a venue screen or projector. This is a different address from the guest upload page, so showing the room its own photographs does not expose the collection to everyone in the building.

How a collection fills during a wedding day
Understanding how a wedding collection accumulates is useful for thinking about where to place the printed codes and when to make the announcement.
How contributions arrive across a wedding day
Before the ceremony
The early arrivals and the getting-ready photographs
These are mostly taken by the wedding party and by photographers hired for the morning. If the collection address is in the pre-event message, some of these arrive during the day. They are usually the photographs the couple did not know existed.
During the reception
The main wave, driven by the printed cards
The table cards drive the majority of contributions. A guest who scans the code at the table is at their most available: seated, with a phone in hand, and not yet on the dance floor. This is the two-hour window that fills the collection.
Evening and after
The dance floor, the bar, the moments the photographer missed
These arrive in smaller numbers but are often the most candid: unposed, unlit by flash, taken by people who were not trying to take a good photograph. They tend to be what the couple remembers most distinctly a year later.
The next two days
Late submissions from guests who took their time
A guest who had one hundred photographs to look through sends three good ones the next morning. These tend to be chosen rather than grabbed, and they represent a kind of curation the couple cannot do themselves.
Downloading the collection and keeping it
The archive is the most important part of a wedding photo collection website, and it is the part couples most often leave too late. When the plan period ends, the files are removed from the platform. The archive you have downloaded is the only copy that remains.
Three things to do in the first week
- Work through the approval queue while you can still name every face in the submissions.
- Download the full archive and store it in at least two places: one you access often and one that is a genuine backup.
- Note the closing date in a calendar, because warning mail arrives before the closure but it is easy to miss.
The plan period starts from the event date, not the date you created the collection. Keepsake keeps a collection open for six months; Celebrate for three; Gather for one. Add a retention period from the dashboard if you need longer.
Questions about wedding photo collection websites
Is a wedding photo collection website different from a shared album?
In one important way: a shared album requires accounts, and a wedding photo collection website does not. Guests upload from a browser with just a name. The couple controls who can browse, whether submissions need approval, and when the collection closes — none of which is typically available in a shared album.
How many photographs can the collection hold?
It depends on the plan. Gather holds two hundred photographs and thirty clips, Celebrate holds seven hundred and fifty photographs and one hundred clips, and Keepsake holds two thousand photographs and three hundred clips. Extra upload capacity is available as an add-on to any paid plan.
Can we share the gallery with family after the wedding?
Yes. The collection address is the gallery address. Sharing it with people who were not at the wedding — a grandparent who could not come, friends abroad — works the same way as sharing it with guests: they open the same link, can browse if the gallery is on, and can even add their own photographs if the collection is still accepting uploads.
What happens if we run out of capacity during the event?
New submissions stop arriving when the collection is full, and the event owner is notified. Additional upload capacity can be purchased as an add-on and applies immediately, without affecting what has already been collected.
Open the collection before you need it
Your wedding photo collection website is ready the moment you create the event. The address goes on the stationery; the QR code goes on the table cards; the archive comes home with you.
Wedding photo sharing
Put one link on the tables and let everyone contribute.
Create a collection, print the table stands, and the photographs your guests took are waiting for you the morning after. Guests never install anything and never make an account.