Running the set
The wedding guest picture collection, run like a small project
A wedding guest picture collection has a beginning, a watching period and one deadline that matters: where it lives, who keeps an eye on it, and when the download gets taken are three decisions, and they are all made long before the first dance.
The first half of this story is mechanical: open a page, print a card, let the room photograph at you. The second half is a small project with owners, a review routine and a deadline, and it is the half that decides whether anything survives. A collection that is merely full is a storage accident. A collection that is run produces an archive, in the right week, on drives in more than one house.
Where the collection actually lives
One event, one collection, one account. Everything about the workflow gets simpler once you stop planning around a different shape.
- The container
- A wedding is a single occasion, and it gets one collection holding the morning, the ceremony, the speeches and the last dance, in the order the evening produced them. Splitting the day into pieces is how the middle of it goes missing.
- The owner
- The collection sits in whichever account opened it: the settings, the review queue and the download all live there. This is why the couple should open it rather than a parent, a venue or the planner whose contract ends in September.
- The address
- Every collection has a short web address and a matching QR code, and both exist from the moment you create it. The slideshow runs from its own token-gated address, so the room screen and the guest page are separate doors into one collection.
- The paper
- Four table stands print on one A4 sheet from the dashboard, on an ordinary printer. The workflow reaches the room through printed cards, not through anybody remembering a speech.
- The shelf life
- The collection lives online for the period stated by the plan, counted from the event date, and then warning mail arrives before it ends. Everything in the rest of this page hangs off that date.
Weeks before the day, the setup pass
The pleasant secret of the workflow is that almost all of it happens in a kitchen, months out, while there is nobody to disappoint. Two months before the date is the ordinary moment couples wish they had known about; anything later starts to collide with the seating plan.
Open the collection, name it properly
Choose wedding as the occasion, put your names and the date on it, and write the welcome line the guest reads before uploading. It exists from this moment; nothing about the day has to be settled first.
Decide the three switches in one sitting
Whether submissions wait for you before they show, whether the room can browse, and whether the guestbook is open. Calm decisions in a kitchen beat frantic ones between the fish and the speeches.
Check the capacity against the guest list
The plan says how many photographs and clips the collection holds and how long it stays up. A hundred and twenty people asked for a handful each is arithmetic you can do in advance rather than discover at midnight.
Print the stands and the fallback text
Code plus typed address on every table, the bar, the cloakroom and wherever guests queue. Order the paper before the invitations go to print so the venue card and the collection say the same thing.
Test the address at the venue
Walk into the room with one phone, scan one card, send one photograph. Ten minutes that tell you whether the connection will carry the evening, while there is still time to change the plan.
Write the closing date on a calendar
Not a reminder you will delete in March: a calendar you actually look at. The download discipline depends entirely on this date being visible.
The three switches, chosen once and rarely changed
- Approval
- A control the host turns on; it starts off. On, every submission waits invisibly until you accept it and anything refused stays out of the gallery, the room screen and the archive. Couples switch it on when the room contains people they have not met, which at most weddings means the plus-ones.
- Public gallery
- On, guests browse what has arrived; off, the page is upload-only. Nothing else changes about sending, so the switch can move mid-evening without confusing a single contributor.
- Guestbook
- Its own switch, separate from photographs. Written messages are included from Gather upward; recorded video messages come with Celebrate and Keepsake, or as a one-off add-on to Gather.
The reason to settle these before the invitations print is not tidiness. It is that during the event you will have no attention left for settings at all, and changing the review arrangement halfway through means a guest who uploaded at seven expects one thing and a guest who uploads at ten meets another.
Who watches it, and how often that really needs to be
Watching the collection is the job that quietly decides the quality of the archive, and the honest answer is that it is smaller than hosts fear: minutes, not hours, and in fixed places on the clock.
- Before the main course: one pass through everything waiting, with blur, floors and somebody's elbow refused and anything a person would be pleased about kept.
- Before the last dance: a second pass, and one line said out loud to the room about how full the collection is, because a number is an invitation.
- Sunday morning: the proper sit-down review while the day still runs in order in your memory.
- Then one short look every second day until the gaps stop filling, because the chosen late uploads are often the best frames of the whole set.
Two people sharing the passes works better than one doing them perfectly. On Keepsake two extra helpers can be added to the account itself; on every other plan the second pair of eyes is a person reading a screen over your shoulder.
The collection does not need your attention all evening. It needs it at three fixed moments you can name in advance.
Catching the tail without becoming the couple who nags
The tail is real: guests who never saw the card, guests whose clips only move off the venue's wifi, guests who looked at their frames three days later and thought better of sending them. The workflow catches most of the tail with one message, sent once, and then accepts the rest.
Day two
The single reminder
One message, the address as text rather than a picture of a code, and a named gap: nothing from the ceremony, nothing of the readings. A specific hole gets filled; a general request gets a nice reply and no files.
Days three to ten
Answer, do not chase
Late uploads land, you run a short review pass over each batch, and that is the whole ask. The people shooting on real cameras get one private message asking for everything rather than a selection.
Week two
Close the ledger
Whatever has arrived is the day as your guests chose to give it. Chasing stragglers past this point converts a favour into a chore, and the photographs it might recover are not worth the room's temperature.
Taking the download, and when to take it
The download is the moment the collection stops being a page and becomes yours, and the entire timing argument fits in one rule: take it in the first week, and take it whole. The archive is one streamed file containing everything that stayed in the collection; individual frames can also come down when one person wants one picture, and files you refused are excluded from the result.
- Finish the review passes first, so what comes down is the set you accepted rather than the pile as sent.
- Pull the whole archive once, in week one, instead of saving frames out of the gallery every time you find one you like.
- Keep the contributor names: the gallery credits every frame to its sender, which is the difference between a photograph and a person you can ask for the rest.
- Copy it to a drive or a photo library that is not the online collection, ideally twice in two houses.
- Take the final download again shortly before the closing date, since late arrivals will have come after the first copy.
- Treat the warning mail as the last nudge you will ever get, because after the page comes down the download is the only copy.
Handing copies to the families without handing over the keys
Everybody wants the photographs, which is the nicest problem in the workflow and still a problem. The shape that works is handing out copies rather than access: the account that owns the collection keeps the settings, the review queue and the one streamed archive, and everyone else receives what the archive can be cut into.
Both sets of parents
A folder of the ceremony and the formalities, sent once, settles the request permanently. Access to the live collection does not: it invites opinions about the review decisions and confuses the closing date into a mystery.
The guest who shot the whole day
They get their own frames back, which takes two minutes with the contributor names and is the politest thank-you available for two hundred photographs.
Your photographer or the book you eventually make
The archive hands cleanly to whoever prints or edits next: one streamed file, originals kept as they arrived on Celebrate and Keepsake, standard downloads on Gather.
Each other
Two accounts can share a laptop in June and disagree about nothing, because the download is the same set. Keepsake is the only plan with two extra named managers, and it exists for the wedding where a helper genuinely runs part of the account.
Capacity, add-ons and the number you watch
The workflow needs a plan chosen against arithmetic rather than optimism. Contributors are unlimited on every paid plan, so the guest list is never the ceiling; the file count is, and a full collection simply stops accepting uploads.
- Preview · free
- 20 photographs, 10 contributing guests, 7 days online, no video and no downloads. Useful as a dry run of the whole workflow on an engagement dinner; not a wedding's plan.
- Gather · $19
- 200 photographs, 30 clips, unlimited contributors, written guestbook, standard downloads, six months online. The honest size of an elopement or a courthouse day.
- Celebrate · $39
- 750 photographs, 100 clips, video guestbook and live slideshow included, original-quality downloads, twelve months. The starting point for a normal wedding room that is photographing.
- Keepsake · $69
- 2,000 photographs, 300 clips, premium themes, two extra managers, 24 months online. For a large or multi-day wedding where the count will be high and the set will be handed down.
- Add-ons
- Extra uploads: 100 photographs for $5 or 250 for $10, 50 clips for $9 or 100 for $15. Longer retention adds six months for $9 or twelve for $15, starting when the included period ends.
Buy the headroom before the room goes home
A collection that fills stops taking uploads mid-evening, and there is no graceful way to announce that to a table that is still photographing. If the count is climbing fast, add upload room then, not in the taxi; the cheap version of this decision is always the early one.
The workflow, in the questions people actually ask
Does a guest picture collection need daily watching after the wedding?
No. Two passes on the day, one proper sit-down on Sunday, and a short look every second day until the uploads thin out. The routine is measured in minutes, and the archive deadline matters more than the frequency.
Who should own the account behind the collection?
The couple, or whichever partner opened it, because settings, review and downloads all live in that one account. A planner's or parent's account can run the day, but the handover afterwards is cleaner if the collection was never theirs.
When exactly should the download be taken?
Once the review passes are finished in week one, and again shortly before the closing date to catch anything that arrived late. Warning mail comes before the page ends, and after that the downloads you took are the only copies that exist.
Can both families get access to the collection?
They can get the photographs, which is what they actually want: cut folders from the archive and send them. Only Keepsake adds extra named managers, and access to the live settings tends to create more questions than it answers.
What happens to the collection when its period runs out?
It comes down on the date the plan states, following warning mail to the host. Extensions add six or twelve months to a collection that is still open, counted from the end of the included period.
Is one collection really enough for a whole wedding?
Yes, and it is the design: one event is one collection, so the preparations, the ceremony, the speeches and the afterparty all land in the same place with the sender's name on each submission. The ordering problem is solved at the desk, from the download, not by opening two pages.
Run the collection from a calendar, not from a panic
Settle the switches months out, put three review moments on the day itself, and let the closing date do the pushing. The workflow takes an afternoon once and minutes on the night.
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.