Back to resources

Uploading sermons

How to Upload Sermons and Use the AI Processing Pipeline

The Upload Sermon page is built for both single recordings and weekly batches. It handles audio file drops, pulls in dates from file metadata when it can, runs each sermon through transcription and AI enrichment, and tracks pipeline status while you work. Knowing how the upload flow really behaves makes the difference between a 30-second weekly routine and an awkward Sunday-night scramble.

What this guide helps with

  • Upload one sermon or a full batch without losing track of any file.
  • Edit titles, dates, pastors, and tags while the AI processes audio in the background.
  • Recognize pipeline statuses, errors, and retry options without guessing.

Drag and drop accepts batches, not just one file

The Upload Area is a drop zone that also opens a file picker when you click it. You can drop multiple audio files at once and the page will queue every one of them under "Sermons in This Batch". Each accepted file is checked against the supported formats (MP3, WAV, M4A, OGG, WEBM) and the 500 MB-per-file size limit before it appears in the list.

Once a file is queued, you can keep dropping more files and editing earlier rows. The list is your batch, and pressing the big upload button at the bottom uploads every pending item in sequence.

Sermon Mind tries to pre-fill the date from the audio file itself

When you drop an MP3, Sermon Mind reads the ID3 tag and pulls the recording date if one is present. For M4A or MP4 files, it reads the standard creation atoms instead. If the file does not have an embedded date, the upload falls back to the file system "last modified" date, and if that is missing too, it defaults to today.

This is one of the easiest things to miss because it happens silently. If the auto-detected date is wrong, just edit it on the card before uploading — your edits stick even while AI is running in the background later.

  • ID3 date frames on MP3 (TDRC, TDRL, TDOR, TYER + TDAT)
  • MP4 / M4A creation atoms (mvhd, mdhd) and the iTunes day atom
  • File system last-modified timestamp as a fallback
  • Today's date if no other signal is present

Pick the pastor and tags before you press upload

Every sermon row in the batch is a full sermon card. You can set the title (defaults to the file name), confirm the date, assign a pastor from the dropdown (the list comes from members with the Pastor role), and add as many tags as you want before the file is processed. Tags you set here become the starting point for the AI — it will add more, but yours are preserved.

If only one pastor exists for the church, that pastor is selected automatically for every file in the batch. Adding new pastors happens on the Users page, not on the Upload page.

AI generates content while you keep working

When you press the upload button, each file goes through three states: Uploading (transferring to storage), Processing (running through the AI pipeline), and Completed. The Processing label updates with the current pipeline step — "queued for transcription", "transcribing", "summarizing", and so on — and the page polls the pipeline every few seconds so you do not have to refresh.

During Processing, you can still edit the title, date, pastor, and tags on the card. When the pipeline finishes, the AI-generated summary, full summary, transcript, scripture references, and additional topic tags appear automatically. If the pipeline fails, the card shows an error and a Retry button.

  • Transcript — full text from the audio
  • Short summary — used on the sermon card and search results
  • Full summary — longer narrative shown on the Full Summary tab
  • Scripture references — book, chapter, verse, and text where available
  • Topic tags — suggestions added on top of any tags you applied manually

Trial limits and overage warnings show up before you confirm

The "Upload allowance" card at the top of the page reflects your current plan or trial. Free trial accounts have a hard cap of 3 sermons during the 14-day window — uploads above that are blocked. Paid plans allow overage uploads, billed as line items on the next Stripe invoice.

Before a batch starts, the page warns you about any sermon that will push past the included amount and asks for confirmation. There is no surprise billing — every overage is shown in the confirmation dialog with the estimated charge.

Next step

See the workflow with your own sermon library.

Start with one recent sermon, then decide whether the library should stay private for your team or become public for members and guests.

Related guides

Keep reading

View all resources

Searchable sermon archive

How to Build a Searchable Sermon Archive for Your Church

A practical guide to turning weekly preaching into a sermon archive your staff, members, and guests can search by topic, phrase, and Scripture.

Organize old sermons

How to Organize Old Sermon Recordings Without Losing Context

A guide for churches that want to clean up older sermon recordings, recover missing context, and make past teaching easier to search and use.

Sermon transcripts

How Sermon Transcripts Help Churches During the Week

Why sermon transcripts matter beyond Sunday and how churches can use them for search, follow-up, study, and ministry conversations.