Transcript vs Transcription: The Difference, and Why It Matters for Churches

# Transcript vs Transcription

The short answer: a transcript is a thing, and transcription is what you do to get it. One is the output, the other is the process.

That distinction takes one sentence. The reason this page is longer is that the neighbouring words (captions, subtitles, verbatim, clean read) are where churches actually get confused, and where the confusion costs something: buying the wrong service, or failing an accessibility requirement while believing you have met it.

What is the difference between a transcript and transcribing?

Transcription is the process of converting recorded speech into written text. It is a verb turned into a noun. "We use AI transcription" describes a method. "Transcription takes four hours per audio hour by hand" describes the work.

A transcript is the document that process produces. It is a countable noun. You can email a transcript, post one on a web page, or search across a hundred of them.

Transcribing is the same act as transcription, in verb form. There is no meaningful difference between "transcribing a sermon" and "the transcription of a sermon" other than grammar.

So all of these are correct:

• "Transcription of Sunday's sermon takes about ten minutes." (the process)
• "Sunday's sermon transcript is on the website." (the document)
• "Who is transcribing the guest speaker?" (the act)

And this common phrasing is technically wrong, though everyone will understand you: "Send me the transcription." What you want is the transcript.

One more term worth having, since it appears on invoices: a transcriptionist is a person who transcribes professionally. If a vendor's pricing page mentions transcriptionists, humans are doing the work, and the price and the turnaround will both reflect that.

Our glossary covers the rest of the vocabulary a church runs into: diarization, timecodes, SRT, and the others.

Is a transcript the same as captions?

No, and this is the distinction that actually matters, because a church can satisfy one requirement and believe it has satisfied the other.

A transcript is a document. It is prose, meant to be read on its own without the audio or video. It has paragraphs, headings, and usually speaker labels. Time information is optional and usually sparse.

Captions are timed text. They exist to be displayed on top of a video, in sync with it, in short chunks of a line or two. Every caption carries a start and end time. Captions are meant to be read alongside the video, never instead of it.

The practical differences that follow from that:

• Captions are hard to read as prose. Pulled out of a video, a caption file is hundreds of fragments broken at display width rather than at sentence ends.
• A transcript is useless for video display without timing information added.
• Search engines index a page's text. A transcript published on a page is indexable content; captions inside a video player generally are not indexed in the same way, which is the main SEO argument for publishing transcripts.
• Accessibility requirements often name both. Captions serve someone watching the video who cannot hear it. A transcript serves someone using a screen reader, someone on a slow connection, and anyone who would rather skim than watch. Meeting one is not meeting the other.

You can convert between the two, and churches do this constantly. Stripping timings out of a caption file gives you raw text, which then needs sentence repair, paragraphing and formatting to become a readable transcript. Our transcript cleaner does the mechanical half of that conversion: it removes caption timecodes, index numbers and filler so you can start editing prose rather than untangling a caption file.

What are subtitles vs captions?

These two are genuinely mixed up even in the industry, and the distinction is worth two paragraphs.

Subtitles assume you can hear. They were built for translation: the dialogue rendered in another language for a viewer who can hear the audio but does not understand it. Subtitles carry speech only.

Captions assume you cannot hear. They carry speech plus the non-speech information a hearing viewer would get from the soundtrack: [music playing], [congregation laughing], [door slams], and speaker identification when it is not obvious on screen.

Two further terms you will meet on a video platform:

• Closed captions can be turned on and off by the viewer. This is the normal case and the accessible one, because it also means the text can be styled, resized, and read by assistive technology.
• Open captions are burned into the video image permanently. Nobody can turn them off, they cannot be resized, and they are not machine-readable. Useful for social media feeds that autoplay muted; a poor choice for your sermon archive.

For a church, the practical guidance is short. Use closed captions on your sermon videos, include the non-speech cues that carry meaning, and publish a transcript on the page as well. If you produce a Spanish version of the message, that is subtitling, and it is a translation job rather than a transcription job.

What is a verbatim transcript?

A verbatim transcript records what was said exactly as it was said: every "um," every false start, every repeated word, every stammer, and often non-speech events such as laughter and pauses. Nothing is tidied.

Its opposite is variously called clean read, intelligent verbatim, or edited transcript. It removes filler and false starts, repairs obvious grammatical slips, and produces text that reads as prose while preserving every substantive word.

Which one you want depends entirely on the use:

Choose verbatim when the transcript is evidence, when it is the object of study (a linguistics or homiletics analysis of delivery), when a legal or archival requirement demands it, or when the exact wording matters more than readability.

Choose clean read when the transcript is going on your website, into a newsletter, into a blog post, or into a book. Spoken English is full of repairs that a listener never notices and a reader trips over on every line. Publishing raw verbatim sermon text makes a competent preacher look inarticulate, which is unfair to them and unhelpful to the reader.

Almost every church wants clean read and some ask for verbatim because it sounds more accurate. It is more faithful to the audio and less faithful to the meaning. The full trade-off, with side-by-side examples of the same paragraph in both styles, is in verbatim vs clean transcription, and if you want to see what a finished, formatted sermon transcript looks like, our annotated example marks up each decision on a real one.

Why the vocabulary matters when you are buying

Three concrete places this costs churches money or time:

Ordering the wrong deliverable. A vendor who quotes for captions delivers an SRT file. If what you needed was a page of readable text for your website, you have bought a conversion job on top of the transcription.

Assuming captions covered accessibility. They cover part of it. A screen-reader user on your sermon page benefits from a transcript on the page, not from captions inside a player.

Assuming a transcript is publish-ready. A raw transcript, human or machine, is not a web page. Somebody still has to add headings, paragraph it, format Scripture references and write a summary. Budget for that step; it is where the value gets added and it is the step everybody forgets.

If you want the finished article rather than the raw output, that is the distinction to keep in mind when you compare services: some sell you transcription, and what you actually need is a transcript you can publish.