Recording, archiving and finding your sermons again
Most churches record every service and can find almost none of them. The recording is the easy part; keeping it and being able to find it again is where the value actually is.
Recording reliably
Record audio separately. Whatever else you do, run a dedicated audio recording from the sound desk. It is small, it almost never fails, and it is what gets reused — for the podcast, the transcript, the archive. Video is a bonus.
Do not depend on the stream recording. Streaming software will save a copy, and that copy is subject to everything that can go wrong with the stream. It is a second copy, not the primary.
Start it before you need it. Roll the recording from the beginning of the service rather than at the start of the sermon. Storage is cheap; the first minute of a reading is not recoverable.
Check it afterwards, every week. Open the file, scrub to the middle, listen for ten seconds. The most demoralising discovery in church media is a month of silent recordings because a fader moved.
The failure that catches everyone: recording the wrong source. A desk feed with the preacher's microphone routed elsewhere gives you a perfect recording of the room and nothing else. Check the routing when you set it up, then check the file weekly.
Storing it so it survives
The standard rule, and it is a good one: three copies, two kinds of storage, one off-site.
For a church, that usually means:
- The recording computer.
- An external drive, connected only when copying.
- A cloud service — the off-site copy.
Two copies in the same building is one copy. Fire, theft, flood and a failed power supply take both.
Automate it or it will not happen. A sync tool that copies a folder to the cloud when files appear is far more reliable than a volunteer remembering on a Monday.
Test a restore once a year. A backup nobody has restored from is an assumption. Pick a random service from two years ago and try to open it.
Making it an archive rather than a folder
This is where most churches stop, and it is what determines whether any of the recording was worth doing.
Name consistently
One scheme, used every time. Something like:
2026-09-07 — Romans 8:28-39 — Nothing Can Separate Us — J Smith
Date first, in a sortable format. Passage, so the archive can be browsed by scripture. Title. Speaker. That single decision does more for findability than any software.
Store the transcript beside it
A recording can only be searched by whatever is in its filename. A transcript can be searched by anything that was said — which is the difference between "I know we covered this once" and finding it in ten seconds.
This is the strongest practical argument for transcribing every service, and it compounds: an archive of five years of searchable text is genuinely valuable to whoever is preparing next month's series.
One place, and only one
Recordings scattered across a booth computer, a shared drive, someone's laptop and a YouTube channel are not an archive. Pick the place, and make everything go there.
How long to keep things
Decide deliberately rather than when a drive fills.
- Audio and transcripts: keep permanently. They are small, and they are what people come back to.
- Video: decide. It is large. Many churches keep two years of video and keep audio forever, which is a reasonable balance.
- Raw camera files: rarely worth keeping once the edit exists.
Write the policy down. Otherwise it is made in a hurry by whoever is looking at the full drive.
A note on permission
A recording of a service includes people who did not choose to be recorded. Some sensible habits:
- Say that services are recorded and streamed, somewhere people will see it.
- Be careful with recordings of testimonies, prayer requests and anything shared from the floor. Ask before publishing.
- If someone asks not to be in a recording, honour it — with the camera framing, not by editing afterwards.
The takeaway
- Record audio from the desk, independently of the stream, and check the file weekly.
- Three copies, one off-site, automated. Two copies in one building is one copy.
- Consistent names plus transcripts are what turn recordings into an archive anyone can use.
Have every service transcribed and saved as it happens. Free, and it runs on your own machine.
Download TajiCast, freeRelated: Transcribing sermons · One sermon, a week of content
Frequently asked questions
- What is the best way to record a sermon?
- A dedicated audio recording taken from the sound desk, running independently of anything else. Video recording from the streaming software is a useful second copy, but audio from the desk is the one that reliably works and is what gets reused.
- How should churches back up sermon recordings?
- Three copies, two kinds of storage, one off-site. In practice: the recording computer, an external drive, and a cloud service. Two copies in the same building is one copy, because fire, theft and flood take both.
- How do I make our sermon archive searchable?
- Transcribe each service and store the text alongside the recording, with a consistent naming scheme including the date, the passage and the title. Searching text is what makes an archive usable; searching filenames is what makes it a folder.
- How long should churches keep sermon recordings?
- Indefinitely for audio and transcripts, which are small. Video is large, so many churches keep video for a year or two and keep audio and transcripts permanently. Decide deliberately rather than discovering the policy when a drive fills.
Keep reading
One sermon, a week of content: clips, posts, emails, podcasts
A repeatable route from one service to clips, a post, an email and a podcast — without a second job for anyone.
Read the guide →SetupRun sheets, checklists and the booth itself
A run sheet the team can use, start-up and shut-down checklists, signal flow, and the big services.
Read the guide →ContentTranscribing sermons: methods, accuracy, and uses
Ways to turn a sermon into text, what drives accuracy, local versus cloud, and what the text is good for.
Read the guide →