Distributing Sermons and Lectures: The Weekly MP3 Workflow

A weekly sermon or lecture series is a publishing operation whether anyone calls it that or not: record Sunday, publish Monday, repeat fifty times a year. The organizations that keep it running smoothly are not the ones with the best equipment — they are the ones with a written, repeatable routine that any volunteer can execute in fifteen minutes. This guide lays out that routine: capture settings, the trim-normalize-convert-compress chain, and the file conventions that keep a five-year archive findable.

The weekly reality

The job has fixed constraints. The talk happens on a schedule; the person doing the audio changes over time; listeners expect the recording promptly; and storage and bandwidth are budgeted, not infinite. A 45-minute talk captured as WAV is roughly 450 MB — multiply by 50 weeks and you are warehousing 22 GB a year of mostly silence and speech. The entire workflow below exists to turn that into ~30 MB per week of clean, consistent, published MP3 without requiring anyone to make judgment calls under time pressure.

Capture: get this right and everything downstream is easy

• Record from the mixing board, not the room. A feed from the sound desk captures the speaker's mic directly; a recorder at the back of the hall captures the hall. If a board feed is impossible, put the recorder as close to the speaker as you can.
• Record WAV. Capture lossless, publish lossy. Recording straight to low-bitrate MP3 saves a conversion step but permanently bakes in any problems; the WAV gives you room to fix mistakes. (Why editing lossy files is a bad habit is covered in lossy vs lossless explained.)
• Set gain once, tape the knob. Aim for speech peaking around -12 dB. Level consistency week to week is worth more than perfection any single week.
• Start recording early, stop late. Disk space is cheaper than a clipped opening line. You will trim anyway.

The Monday chain: four steps, same order, every week

1. Trim

Cut the pre-roll (setup noise, announcements if you don't publish them) and the post-roll. Use an online MP3 trimmer or your recorder's software — either way, the published file should start within a couple of seconds of the first intended word. This is also the moment to cut any segment that should not be published, such as congregational prayer requests with personal details.

2. Normalize

Speakers vary: this week's guest whispers, next week's preacher peaks the meters. Listeners notice immediately when they have to change volume between episodes. A weekly pass through an audio normalizer brings every talk to the same loudness target so the series sounds like a series. The reasoning behind loudness normalization is explained in this normalization guide — the practical takeaway is: normalize every week, with the same settings, no exceptions.

3. Convert

Turn the edited WAV into MP3 with a WAV to MP3 converter. MP3 remains the right publishing format for this use case because every listener device — from a granddaughter's phone to a shut-in member's decade-old player — handles it without help.

4. Compress to the target size

Speech does not need music bitrates. For a single voice, 64 kbps mono is the workhorse setting: clear, natural, and about 21 MB for a 45-minute talk. If there is congregational singing or live music you want to keep listenable, 96–128 kbps is safer. An MP3 compressor gets the file to target, and converting to mono via a stereo to mono converter halves the size of a board feed that was recorded in stereo for no reason — a single lectern mic is mono content regardless of the channel count. The trade-offs are laid out in this bitrate guide for speech and mono vs stereo.

Naming and archiving: the part everyone regrets skipping

• Name by date first: 2026-07-19-title-of-talk.mp3. Date-first names sort chronologically in every file browser forever. "final_v2_USE_THIS.mp3" does not.
• Fill in the ID3 tags: title, speaker in the artist field, series name as the album. Car stereos and phone players display tags, not filenames; a feed full of "Unknown Artist" looks abandoned. (What these tags are: ID3 metadata explained.)
• Keep two copies: the published MP3, and the trimmed WAV master if storage allows — or at minimum a 192 kbps MP3 mezzanine. When someone requests a compilation or a re-edit in three years, you will need better than 64 kbps source.

Distribution: meet listeners where they are

Once the MP3 exists, publish it in more than one place, because your audience spans more technology generations than almost any other. A simple website page with a download link serves the members who want to save files; a podcast feed serves the ones who live in apps — a sermon or lecture series is structurally identical to a podcast, and every podcast host will accept your weekly MP3 without modification. Keep the audio settings identical across channels so you only produce one file, and keep old recordings up: series archives get a surprising long tail of listeners working through them from the beginning, which is exactly why the consistent naming and tagging above pays off years later.

The fifteen-minute checklist

• Pull the WAV off the recorder or board.
• Trim head and tail; cut anything not for publication.
• Normalize with the standard settings.
• Convert to MP3; compress to 64 kbps mono (96+ if music matters).
• Rename date-first; fill in tags; upload; archive the master.

Write these steps down with your exact settings, keep the document with the equipment, and the workflow survives volunteer turnover — which, for a weekly series, is the difference between an archive and a pile of files.