sermon transcript

Edit the sermon transcript, then export it as Markdown

The transcript is not a by-product here. It is the document everything else points at, and it stays visible, numbered, and exportable.

You want the text itself: readable, paragraphed, and portable into whatever your church actually uses to publish or file it.

What HomilyForge actually does here

Transcript editor, numbered paragraphs, and Markdown export.

Numbered paragraphs

The transcript view shows every paragraph with its §number, which is the same identifier the outline points cite.

Markdown export

One download produces a Markdown file with the summary, themes, references, outline, discussion, applications, and key statements, each outline point carrying its source paragraph number.

Print-ready

A print stylesheet drops the navigation and controls so the browser's print dialog produces a clean handout without a separate export step.

A worked example

This is the real Markdown export for the demonstration study, produced by the same function the download button calls.

# Preparation, paragraph by paragraph

**Speaker:** Synthetic demonstration voice  
**Occasion:** Midweek teaching  
**Source:** HomilyForge demonstration transcript

## Summary

Preparation begins long before the room fills. Notes made in a hurry rarely survive the week. Listening well is slower than agreeing quickly.

## Themes

- Attention
- Preparation
- Review
- Argument

## Scripture references

- Philippians 4:6-7
- Psalm 34:18

## Outline

1. **Preparation begins long before the room fills**

   A message becomes useful when someone has already sat with it, argued with it, and written down the part they still do not understand. Philippians 4:6-7 keeps surfacing in this kind of preparation, because anxiety is usually the first thing that crowds out attention.

   _Source paragraph 1_

2. **Notes made in a hurry rarely survive the week**

   They record what was said without recording where it was said, so no later review can check a single claim. A paragraph number is a small thing, and it is what separates a quotation from a memory.

   _Source paragraph 2_

3. **Listening well is slower than agreeing quickly**

   A talk that moves fast invites us to keep the conclusions and quietly drop the reasoning that produced them. Psalm 34:18 was read twice here, and attention to that repetition changes how the middle of the argument should be weighed.

   _Source paragraph 3_

4. **Questions travel further than summaries**

   A summary tells a group what to think about the talk, while a question sends the group back to the paragraph that provoked it. The gap shows up the moment somebody disagrees in good faith, because a group can reopen the exact wording instead of arguing about a mood.

   _Source paragraph 4_

5. **Application should be smaller than the ambition that produced it**

   One repeatable practice, named out loud, outlasts a list of intentions nobody writes down. The aim of preparation is not to prove effort; the aim is to keep returning with attention intact.

   _Source paragraph 5_

6. **Review cannot be handed to a tool**

   A qualified person still has to check the wording, the permissions, and whether this room is the right place for this material at all. psalm 34:18 belongs to the argument of the talk, and review is where that judgement is made.

   _Source paragraph 6_

Demonstration material written for HomilyForge and processed by the same engine the product uses. No supplied recording or transcript is ever published as an example.

How the workflow works

Step 1

Supply the message

Paste a transcript or upload a supported audio file for transient transcription in a private workspace.

Step 2

Structure the source

Number paragraphs and derive summaries, outlines, explicit references, questions, and applications with visible source links.

Step 3

Review and export

Edit the material, verify interpretation and permissions with a qualified human, then export Markdown or a print-ready view.

Limits that apply before you start

Useful search results begin with an accurate promise. These are the current bounds on this job.

  • Transcripts must be between 250 and 30,000 characters and are split into a maximum of 24 numbered paragraphs.
  • Text uploads accept UTF-8 .txt and .md files up to 2 MB. Word documents, PDFs, and URLs are not imported.
  • Export is Markdown or print. There is no .docx, PDF writer, or publishing integration.

Questions about sermon transcript

What is in the Markdown export?

The title and message details, the summary, themes, extracted references, the full outline with a source paragraph line under each point, discussion questions, applications, and key statements as block quotes.

Can I edit the transcript after transcription?

Yes. The transcript is an ordinary editable field before you build a study, and the saved study keeps a snapshot of the source it was built from.

Where is my transcript stored?

Without an account it stays in your browser's local storage. Signed in, it is stored in an owner-scoped Firebase library that only server code reads.

Related sermon transcription and study preparation pages