Collection by event type
Church event photo sharing, kept for the people who could not come
Church event photo sharing has a different audience from a party: a congregation that includes people who were not in the room. One address on the noticeboard and in the order of service collects the day, and the recording of it goes to whoever was at home.
Conferences, corporate days, schools, churches, sport and community.
A church photographs its own life constantly and keeps almost none of it. The anniversary lunch, the harvest service, the retirement of a minister who served thirty years, the new building, the camp photos a teenager took: all of it gets taken and then scattered into family phones and a WhatsApp group that nobody can search two years later. Congregations are also the audience with the least patience for software, and the most need for the record, because a church's memory is made of people who have moved away, people who are housebound, and people who were there in 1994 and did not have a camera. The useful version of church event photo sharing is therefore not an application. It is one printed address that opens a page in whatever browser an elderly relative already has.
Naming the occasion, since church is not on the list
A collection is created against an occasion, and the named ones are wedding, birthday, graduation, baby shower, anniversary, corporate event, conference, family reunion and anything else you type. For a church that means two ordinary choices. A dedicated day, an anniversary, a jubilee or a rededication service, can use the named anniversary option, which puts a celebratory line and the people's names on the opening card of the room display. Everything else, a harvest festival, a community lunch, a camp, a funeral lunch, is created as one of the remaining occasions with the name typed in, and the typed name is what appears on the guest page, on the screen, and on the archive the church keeps.
- An anniversary or a jubilee
- The one where a collection earns its keep. Created with the anniversary occasion, run on the hall screen through the lunch, and closed on a stated Sunday so the archive can be given to the church's own storage and the book can be bound later.
- A funeral lunch or a celebration of a life
- Small, tender, and the single case where the record is the point. The address goes to the family rather than to a room, and the download becomes the gift: every photograph the family could not take because they were the ones being hugged.
- Harvest, nativity, camp and youth weekends
- Material with children in it, which is where the two settings that matter are switched on: the gallery set so contributors upload without browsing, and arriving photographs looked at before they appear anywhere.
- A retirement, an installation, a new building
- A once-in-a-generation afternoon with a large room and a screen. The written book is worth opening alongside the photographs here, because the sentences a congregation writes on a day like that are the part nobody else can supply.
How the address gets into hands, in a building with no IT department
The noticeboard, in large print
A code big enough to scan at arm's length, one line saying what happens to the photographs, and the date the page closes. This is the cheapest channel in a church and the most reliably ignored, so it needs the sentence said aloud as well.
The order of service or the bulletin
Paper that is already printed and already in every seat. One square and one line costs nothing on a sheet that exists regardless, which is the whole argument for printing the code rather than announcing it.
Read out once, by name, with the screen showing it
One sentence at the notices: photographs taken today go on this page, and they will be on the hall screen after the service. A congregation that can see the wall filling uploads at several times the rate of one that has been told a link exists.
The Sunday group message, sent once
Every church has three people who forward everything. Give them the address as text with the sentence already written and they will do the distribution better than the office can.
Somebody's daughter, on her own phone
The honest answer for the members who will never scan anything. A relative photographs the service, uploads from their own device, and gives the name of the person the photographs are for. Nothing about the flow changes, and it is worth saying from the mic that this is allowed.
What an elderly contributor has to do
This is the question the office should ask before anything else, because the congregation's age profile decides whether a collection fills. The answer is: open the page, choose the photographs, type a name, press send. There is no application to install, which matters enormously on a phone nobody configured, and no account to create, which matters on a device somebody shares with a grandchild. A contributor gives their name once and is not asked again for twelve hours, so the aunt who sends four separate batches types once. The page is not indexed and is not listed anywhere, so the only people who find it are the people who were told about it, which is what a church means by private.
The screen after the service
A church hall has a trestle table, a screen that belongs to somebody's laptop, and an hour where everybody is standing. That is the best room display in any setting, and it is worth the ten minutes it takes to arrange. The wall runs at its own address, which is separate from the upload page and separate from the account that owns the collection, so handing it to the person who sets up the tea urn does not hand them anything else. It plays the photographs while the room is still sending them, can show the sender's name beside each frame, and keeps an order chosen once at creation from twelve arrangements, of which the mosaic and the printed-photograph layouts suit a standing room better than a slow single-frame film.
What the screen cannot do, so the plan is honest
There is no live stream, no telephone dial-in, and no way to broadcast to a venue's own television from a phone. The wall is a browser on a machine connected to a panel. For the members watching from a bed upstairs, the answer is not the screen: it is the same address opened by a relative, or the download that arrives in the family's hands a week later.
What the room display isGetting the day to the members who were at home
A congregation asks for the record more often than it asks for the photographs, and there are three honest ways to reach somebody who was not in the room. The first is the address itself: a member with a tablet, or a relative with a phone, can open the gallery and watch the day arrive, provided the office leaves browsing switched on, since the other setting turns the page into somewhere to send rather than somewhere to look. The second is the screen, which reaches a room rather than a bedroom; a hall running the wall through a tea club is as close to a broadcast as this ever gets. The third, and the one that genuinely travels, is the archive: whoever downloads the collection can put the memorial lunch onto a drive, print four pages for somebody's front door, or message the photographs to the member who moved to a care home two counties away. There is no live feed, and no way to push the day to somebody who has not been given the address, which is why the printed order of service and the relative with a phone matter more than anything else in this section.
The book that sits beside the photographs
A collection can carry written messages as well as files, which is worth knowing on the occasions where the sentences matter more than the images: a retirement after thirty years, a minister's installation, an anniversary of a church that lost somebody, a funeral lunch. The same address that takes a photograph takes a note, the contributor gives their name once, and the entries keep the date they arrived. The practical limit is worth stating plainly, because it surprises committees: the download archive holds the photographs and the clips, while the written entries stay in the book on the collection page. So the entries are read out of the page and copied into whatever the church keeps, whether that is a printed book, a folder on the parish computer, or the yearbook, and that is done before the page closes rather than after.
- Which occasion it is created as, because that decides the wording on the screen and on the page.
- Whether arriving photographs are looked at before they appear, which is a switch on the collection settings and off by default, and the right answer whenever children are in the pile.
- Whether the gallery may be browsed by contributors or only uploaded to, which is the other switch worth deciding in advance rather than in front of a room.
- The closing date, said aloud and printed, so the archive is taken while the material is still arriving rather than in the last week.
- Who downloads it and where the copy goes, because a hosted collection is the temporary half of the arrangement and the church's own storage is the permanent one.
- One named person who holds the screen address, so nobody has to find the vicar when the laptop needs waking.
Nothing in the collection is indexed or listed. Access is the address, which is why it can go in a printed order of service and why it should not go on a public webpage.
What the person who files the archive is actually handed
- The download is a folder, not a book
- Every photograph and clip the collection kept, numbered in the order they arrived and carrying the file names they came in with. It is four hundred files sorted by when the sender pressed send, not by who is standing in the frame.
- The names are on the page instead
- Who sent which photograph lives in the gallery and, if the organiser chooses, beside each frame on the screen. That list is copied out of the page while the collection is open, because it is not in the folder and the page does not stay up forever.
- Somebody has to sit down with it for an hour
- Renaming, sorting into the church's own categories, and putting one copy on the parish machine and a second somewhere else. This is the part a committee assumes the software does, and it is the part that decides whether the anniversary of 2031 has photographs of the people in the 1994 ones.
- The window is the hosted period, not the archive
- Six, twelve or twenty-four months from the event depending on what was chosen, with one-off extensions of a further six or twelve, and warning beforehand when it ends. Once the download is taken, the hosted page stops being the church's dependency.
Two occasions in one church year means two collections
A collection is one occasion: one name, one date, one address, one closing date, one download. A church that has an anniversary lunch in June and a harvest service in September creates two, and pays for them separately, which is the shape a parish's records want anyway. The habit to avoid is the running parish page that holds the whole church year in one collection. Its closing date has to be the same date for the lunch and for the nativity, its download merges two entirely different sets of people, and its gallery gives next year's archivist no way to tell one service from the other. Two collections, two addresses on two pieces of paper, and two folders on the church's own storage is more work for exactly one afternoon and is the difference between records and a pile.
What a congregation asks before it agrees
Does anybody need an account, a password or an application?
Nobody who is contributing. The page opens in the browser already on the phone, a name is typed once, and files are chosen from the device. There is nothing to install, and the account that owns the collection is the office's business rather than the congregation's.
Can we see who sent which photograph?
Yes, in the gallery and on the screen: each frame can carry the name the sender typed. It is a name they gave rather than a verified identity, which is usually exactly what a church wants and never what an audit wants.
What stops a stranger finding the photographs of our children?
Three things working together: the address is not listed or indexed anywhere, the gallery can be set so contributors cannot browse what other people sent, and arriving photographs can be held until the organiser accepts them, with anything refused never appearing in the gallery, on the screen or in the download. The rest is the church's own judgment about who is handed the address.
Is there a cost for the members who send photographs?
No, and no price is ever shown to a contributor. The church pays once for the event: nineteen dollars for 200 photographs and thirty clips kept six months, thirty-nine for 750 and a hundred over twelve months, sixty-nine for 2,000 and three hundred over two years.
How long will the photographs stay available?
Six, twelve or twenty-four months from the event date depending on what was chosen, with a further six or twelve months available as a one-off, and warning beforehand when it is ending. The download is the copy that outlasts all of that.
Two of our people need to run it. Is that possible?
One account owns the collection. The screen has its own address that can be given to whoever sets up the hall, and it reaches the display and nothing else, but there is no second organiser seat, no shared admin login and no departmental view.
Can the family have everything from the memorial lunch?
Yes, and it is the best use of this in a church. Take the archive, which holds every photograph and clip the collection kept, in the order they arrived, and hand it over as a folder or on a drive. Written entries are copied out of the book separately, because they live on the page rather than in the archive.
Print it on the paper that is being printed anyway
Open the collection, name the day the way the bulletin names it, and put one square and one sentence in the order of service. The anniversary photographs will find their own way there; the ones from the back pew need to be told where to go.
Photo collection by event type
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.