If you’re a pastor who has ever stood at the office computer on a Saturday afternoon, scrolling through a folder called “Photos” looking for that one good shot from the fall picnic, and finally given up and used a stock image of people you’ve never met, this post is for you.
Your church almost certainly has the photos. Someone took them. They’re on a phone, in a text thread, in three different Google accounts, on a volunteer’s laptop, or in a folder named “IMG_2847 through IMG_3112.” They exist. They’re just not findable, which for practical purposes means they don’t exist. This post is about the simplest system that fixes that: one shared place, one naming convention, and a little tagging. Nothing to buy, and no software your volunteers don’t already know.
The short version
- Photos you can’t find are photos you don’t have. The problem is organization, not quantity.
- Use one shared drive, one folder structure, and one owner.
- Name folders by date and event:
2026-09-13 Fall Kickoff. That one habit does most of the work. - Pull a handful of the best shots from each event into a “Favorites” folder, so the good ones are one click away.
- Make it easy for volunteers to drop photos in, and make it someone’s job to sort them monthly.
Why this keeps happening
Photos pile up faster than any other kind of church content. Every event produces dozens or hundreds of them, from multiple phones, and nobody has a plan for what happens next. The person who took them means to send them along. Sometimes they do, in a text with fourteen images attached. The office downloads them somewhere. Six months later, no one remembers where.
The result is that the church’s visual story, its actual people doing actual ministry, sits unused, while the newsletter and website fall back on stock photos or the same five images from 2019. Visitors notice. Your own people notice, too. Seeing themselves and their friends in the church’s materials is one of the quiet ways people feel they belong.
The fix doesn’t require a photographer, a budget, or a digital asset management system. Those are real tools for large organizations, but most churches need something much smaller: agreement on where photos go and what they’re called.
Step one: one shared place, one owner
Pick a single cloud drive and commit to it. Google Drive, Dropbox, OneDrive, iCloud shared folders. It doesn’t much matter which, as long as it meets three tests: the church owns the account (not a volunteer’s personal login), it has enough storage, and the people who make things can get to it from their own computers.
For most churches, that means Google Drive on the church’s Google Workspace account, because the office is already there. If the church doesn’t have its own account, set one up now, because photos stored under a volunteer’s personal account walk out the door when the volunteer does.
Inside the drive, create one top-level folder: Church Photos. Everything goes under it. Resist creating a second one for “Youth Photos” or “Special Events.” One tree, so there’s only one place to look.
Give the folder one owner. Not a committee, one person: the administrator, a communications volunteer, whoever is most likely to actually do it. Their job is not to take photos. It’s to keep the folder tidy, which takes about thirty minutes a month once the system is running.
Step two: the naming convention
This is the heart of the system, and it’s almost embarrassingly simple. Inside Church Photos, create one folder per year. Inside each year, one folder per event or occasion, named like this:
2026-09-13 Fall Kickoff Sunday
2026-09-20 Youth Lock-In
2026-10-04 Blessing of the Animals
2026-10-11 Worship
Date first, in year-month-day order, then a plain description. That’s the whole convention. Three things make it work.
Date first means everything sorts itself. Your computer will list these folders in chronological order automatically. You never have to remember whether the picnic was in September or October; you just scroll to the right part of the year.
Plain words mean anyone can find it. “Fall Kickoff Sunday” is what people call it, so that’s what the folder is called. Not “FKS26” or “Event_Sept.” If two people would describe the event differently, use both words: “Trunk or Treat (Fall Festival).”
One folder per event means you don’t have to name individual photos. Leave the files as IMG_2847.jpg. Renaming hundreds of photos is the step that kills every well-intentioned system. The folder does the work.
For recurring things like Sunday worship, one folder per Sunday is fine. If you only take photos a few Sundays a year, a single “2026 Worship” folder with photos inside is also fine. Don’t overthink it. The goal is that six months from now, anyone can open the drive and find the Blessing of the Animals in under a minute.
Step three: the Favorites folder
Here’s the part that saves you on Saturday afternoon. Most event folders will hold fifty or a hundred photos, and most of those are duplicates, blurry, or of the back of someone’s head. Scrolling through them every time you need one is what makes people give up.
So each time photos come in, the folder owner (or whoever took them) spends five minutes picking the three to ten best shots and copying them into a folder called Favorites, organized by year. Look for the ones that show faces, show people doing something (serving, singing, laughing, praying), and are sharp and well lit. Skip the group shot of everyone squinting at the camera.
Now, when you need a photo for the slide, the newsletter, or the website, you open Favorites and pick from a few dozen good ones instead of four thousand mixed ones. The full set is still there if you need it. But ninety percent of the time, Favorites is all you’ll open.
Step four: light tagging, if you want it
The naming convention handles “when” and “what.” Sometimes you also need “who” or “which ministry.” Google Drive and most cloud services let you search file descriptions, and Google Photos (if you use it alongside Drive) will recognize faces and objects automatically.
The lightest version: in the Favorites folder, add a word or two to the filename of the very best shots. 2026-09-13-kickoff-kids-craft-table.jpg. 2026-10-04-animals-dog-blessing.jpg. You’re only doing this for the favorites, so it’s a handful of files per event, not hundreds. Search for “kids” or “choir” and they come up.
If that feels like too much, skip it. A good folder structure with a Favorites folder is already more than most churches have. Tagging is a nice extra, not a requirement.
Step five: make it easy to get photos in
None of this matters if the photos stay on people’s phones. So make the drop-off point obvious.
Create a folder called Inbox (drop photos here) at the top of Church Photos, and share the link with anyone who takes photos at church: the youth leader, the person who always has their phone out at events, the staff. Anyone can upload to it from a phone in about ten seconds. They don’t have to name anything or sort anything. Just get the photos in.
Then the folder owner, once a month or after big events, moves things from Inbox into the right dated folder and pulls a few into Favorites. That’s the whole maintenance job.
Two other things help. Mention it from the front occasionally: “If you took photos today, drop them in the church folder, the link’s in the bulletin.” And include a line in your volunteer onboarding or event planning checklist: “Who’s taking photos, and do they have the Inbox link?”
What to watch out for
Ask before you post faces. Especially children. Most churches include a photo consent line on registration forms for kids’ programs; if yours doesn’t, add one. For adults, a general announcement that photos may be used in church communications is usually enough, along with a simple way to opt out. Keep a short note in the drive about who has asked not to be photographed.
Don’t let the phone be the archive. Photos on the youth leader’s phone are one dropped phone from gone. The drive is the archive. Phones are the camera.
Keep the originals. When you edit a photo for a slide or crop it for Instagram, save the edited version somewhere else (a folder called “Edited for Social” is fine). The original in the event folder stays untouched, so you can use it again differently later.
Check storage once a year. Photos add up. If the church’s free storage fills, the small monthly fee for more is far cheaper than losing your visual history. Put it in the communications budget.
A small next step
This week, create the Church Photos folder on the church’s own account, with one year folder and an Inbox inside. Share the Inbox link with the two or three people who take the most photos. That’s it. Next month, spend thirty minutes sorting what came in and pulling ten favorites. Next Saturday, when you need a photo for the slide, you’ll know exactly where to look.
If posts like this are useful, you can get them in your inbox — subscribe to the Faithlab blog. No sales pitches, just practical help for church and nonprofit communicators.