Gathering what the room has
Collecting event memories online when the day is split across forty phones
Collecting event memories online means asking each guest for what they captured, once, through one address, so the photographs, the clips and the written notes land in a single pile you can actually hand to somebody a year later. Here is how that pile is built, what it takes from you on the day, and where it comes back out again.
Ask around a room a month after any occasion and the same shape of answer comes back: somebody has the speeches, somebody else has the dance floor, a cousin has forty photographs of the food and none of the ceremony, and the clip everybody says is the best one exists on one phone that has not been backed up since. The material for a complete record of a day is almost never missing. It is distributed, which is a different problem and a harder one, because distribution cannot be fixed by asking one person to be more organised. It is fixed by giving everybody the same small place to put what they have, at the moment they have it, and by making that place openable on a phone that is already holding a photograph.
What online collection has to beat
Four routes already carry the memories of most events. None of them survives being the archive, which is why the pile still ends up incomplete.
- The group chat
- It is the route everybody actually uses, and it is the worst storage medium in the house. Files sit inside a scroll, get pulled off the phone for space, and lose the name of who took them. Searching a chat for a specific photograph at a specific moment returns almost nothing, and a chat with a hundred people in it eventually silences itself into unread.
- One shared album on somebody's phone
- It requires every contributor to be on the same service, to have an account on it, and to accept an invitation that half the older relatives will not find in their mail. The host then cannot see what the album holds without opening that phone, and when the account gets reclaimed, the album goes with it.
- A folder of files sent to the host
- Technically a collection, practically a chore. Thirty attachments arrive over two weeks, several of them the same shot from the same angle, all of them named IMG_4471. The work of ordering, deduplicating and identifying who sent what lands on one person, usually the one with the least time.
- Nobody collecting at all
- This is the most common outcome and the one nobody plans for. The photographs stay where they are, the good clip stays on a cousin's phone, and the day is eventually remembered through the two or three images the host happens to have taken themselves.
The address that replaces all four
A collection is one web address belonging to one event. It carries a page for the photographs and clips people want to send, a page for the notes people want to write, and a page that shows what has arrived so far. Everyone who has the address can use it. Nobody who uses it has to register, install anything, or tell you which service they normally use, because the pages are ordinary web pages and a phone opens them the way it opens a weather site. This is the whole trick behind collecting from a room: the moment the ask involves an installation, the response collapses to the people who were going to help anyway.
The address is printed as well as typed. A table stand at the reception carries a code that opens the upload page directly, which matters more than it sounds: a guest who has just photographed something is on their feet with a drink in one hand, and a code they can point a camera at is the only ask that reaches them at the moment the memory is still on their person rather than buried in a drawer at home. The printed code and the typed link open the same page, so there is one pile regardless of how somebody found it.
Name the event and set the date
The name appears at the top of every page a guest opens, which is what makes a year-old photograph identifiable later. The date decides when collecting closes; a deadline is worth setting earlier than your patience, because the slow arrivals come in the week after.
Choose what the collection accepts
Photographs, films, written notes, or any combination. A funeral wake and a birthday do not want the same set of boxes open, and a page that refuses what nobody asked for is clearer than one that accepts everything.
Send one line to one group
The link travels in the same message that carries the address of the venue, or in the follow-up the morning after. It does not need an explanation, because the first thing a guest sees is their own name being asked for and a large area to drop files into.
Put the code where people are standing
The printable stand is generated from the collection, not typed out by hand, so the code on the table cannot point at a draft or at the wrong occasion. One per table is enough; guests photograph the stand itself and pass the link along.
Take the download before the hosted period ends
This is the only step with a deadline behind it, and it is described in full below, because a collection you have not downloaded is a collection that eventually stops existing in a form you can use.
What a guest is asked to do, and what they are not
A guest gives a name and, on the page that takes files, chooses photographs from their own library. There is no password, no confirmation mail, no app store, no agreement to a service's terms, and no request to grant a phone's whole camera roll to anything. The name is asked because an unattributed pile is nearly useless a year later: thirty frames of a first dance tell you nothing about who was holding the phone, and the person who took the photograph is usually the one you want to thank. The name is typed once and remembered on that device for a few hours, so a guest sending a second batch the same evening does not type it again.
- No account. The upload page has no sign-up screen anywhere on it.
- No app, no plugin, no converter. Files are chosen from the phone's own picker and sent as they are.
- No payment. A guest never sees a price; the event is paid for once, by the person who created it.
- No re-encoding, renaming or resizing before sending. A file that is too large to accept is refused with the limit stated, not quietly shrunk.
- No instruction booklet. The page holds a name box and a drop area, which is the whole of what has to be understood.
What arrives, and in what shape
A photograph arrives as the file the camera made, at the size it left the phone, and a smaller preview is drawn separately so a gallery of a thousand images can be scrolled on a mobile connection. A clip arrives as its own file rather than as a stream inside somebody else's player. A written note arrives with the name attached and stays readable as text rather than as a screenshot. Everything lands in one sequence ordered by arrival, which is the only ordering that a mixed pile from strangers can support without a person making decisions; anything cleverer than that, like sorting by who is standing in a picture, is not a feature here and no page should have implied it was.
- What one photograph may weigh
- Fifteen megabytes. That covers a full-resolution frame from any recent phone and a raw export from a camera, and it refuses the genuinely enormous files that break an upload on a bad signal.
- What one clip may weigh
- One hundred megabytes, which is a speech, a dance or a goal rather than a whole service. Footage that long belongs on the drive where it was shot, not in a collection of a day.
- How much a collection holds
- A free collection takes twenty photographs and no footage. The paid levels run from two hundred photographs and thirty clips to two thousand photographs and three hundred, and going past an allowance is a one-off purchase rather than a bigger plan.
- How long anything is kept
- A week on a free collection; six, twelve or twenty-four months on a paid one, counted from the event. Nothing is kept indefinitely on any plan, and the download below is what solves that honestly.
One event, one collection
A collection is not subdivided. Two occasions need two collections and two addresses; the files of one occasion stay in one pile rather than being sorted into smaller books inside it, and nothing here offers a further division of a single event, so a plan page or a brochure promising one is describing a feature which does not exist.
What each level includesThe moment the pile becomes useful
A collection earns its keep twice. The first time is on the night, when what guests have sent is already being watched by the rest of the room; a screen in the corner drawing from the same pile turns private phone libraries into one shared thing, and it visibly encourages the people who had not sent anything yet. The second time is a month later, when the person who organised the day wants the photograph of a specific moment and can search one place rather than messaging eleven people. Both of those depend on something having actually been collected, which is why the ask goes out at the event rather than in a later, guiltier week.
The room screen is its own address rather than the gallery dressed up, because a projector should not be handed the settings of somebody's event. It plays oldest first at a pace chosen before guests arrive, with a handful of keyboard keys for the person who ends up near a laptop: full screen, step back, step on, hold. Clips can be left out of the wall while staying in the collection, which is nearly always what a room that is talking wants.
What collecting does not do
- It does not gather what people refuse to send. A collection lowers the cost of contributing to almost nothing; it does not reach a guest who took the photographs and never shared them.
- It does not repair a poor original. Nothing here brightens, crops, steadies or colour-corrects a file, and a bad photograph arrives exactly as bad as it was taken.
- It does not edit. There is no montage, no automatic film, no captions burned in, no trimming of a clip and no titles anywhere.
- It does not find people. There is no sorting by face, no automatic album per guest, no assistant writing captions, and no scan of what is inside a frame.
- It does not publish. A collection is opened by an address you gave somebody; it is not a public feed, a profile, or a page that appears in a search result.
- It does not stream. There is no live feed to a second room, and a screen shows what has already arrived rather than what is happening now.
The part people forget until it is urgent
Everything collected is eventually somebody's own files again, and the only mechanism for that is the download. It is one action in the dashboard and it produces an archive containing the originals: photographs at the size they arrived, clips as their own files with the camera's name and a number in front, written notes as text rather than as pictures of text. Nothing is re-compressed on the way out, which is what allows the archive to go into an ordinary photo application, onto a drive, or into the hands of whoever ends up cutting the anniversary film.
Take it before the hosted period ends rather than after. A free collection closes seven days after the event, which is a genuinely tight window for anything a guest sends late; a paid one closes at its own date, and an extension bought before it closes restarts the clock from where it stopped. After closure there is no page left to download from, which makes the download the most important minute of the whole arrangement rather than a housekeeping chore.
The questions that come up while you are asking people
How do I get guests to send what they already took?
Ask while the day is still on them. The link goes out in the message that carries the venue, the code stands on the tables, and a short reminder the next morning catches the people who meant to send something and did not. A general request produces a general pile, so name two or three specific things worth having.
Do the guests need an account or the app?
Neither. They open the address, type their name, choose files and send. There is nothing to install and nobody else needs to be signed up for the page to work.
Can I see who has sent what?
Yes. Every item carries the name the guest typed, and a guest can look at their own contributions rather than the whole event, which is what lets somebody find the photographs they took.
What stops a stranger finding our collection?
The address is not listed anywhere and there is no directory of events. Anyone who has it, however, can open it, so a collection gets sent to people you invited rather than posted in public. Where an occasion needs more than that, a password in front of the collection is an option, and the people who need it are told the password by you.
What happens to the photographs after a year?
The hosted period ends at the length your plan states and the pages come down. The download hands the files back before that happens, and after it they live where you put them rather than on anybody's hosting.
Can relatives in another country contribute?
They can, and this is usually where the route beats a chat. They need the link, a browser and their own photographs; the time difference is irrelevant, because the upload page does not care when it is opened.
Is there a free way to try collecting?
There is a free collection holding twenty photographs for a week, which is enough to see whether a real group of guests will actually use it. It takes photographs only, with no footage and no written book, and a paid plan is what most people choose once they have watched it work.
Put one address in front of the whole room
Start a collection, print the stand, and let the photographs, clips and notes arrive where they can be found again. Then take the download while the pages are still up, so the day outlives the hosting.
How it works
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.