How Church Media Kit turns a public YouTube sermon into a Sermon Kit

You have a public sermon link and a list of posts your church could use this week. It would be easy to paste the link, accept whatever appears, and call the job finished.

Church Media Kit is built around a different order of work. You paste the link of a public YouTube sermon your church is authorized to reuse. The product checks the source, asks what to make, and prepares editable draft designs for Facebook and Instagram posts and teaching carousels. A person at your church reviews each page against the sermon, so a misquoted line or a wrong date is caught before anything is exported.

The result is a Sermon Kit: a saved set of static social designs from one sermon, grouped by post type. Studio is the editor where your team corrects them. Church Media Kit does not post for you. It exports JPG or PNG files, and your team adds the caption and posts them through its own process.

A free account needs no card, and your first sermon is free. After that, plans start at US$29.95 a month for Starter, which covers five sermons a month and five Seats (a Seat is one person on your team). See pricing for the larger plans. This tour follows the full path, including the places where the work should stop.

Start with a supported public YouTube sermon

The process begins with a public YouTube watch URL. The system validates the address and rebuilds a canonical YouTube link before it uses the source.

Next comes a rights confirmation. The person submitting the sermon states that the video was produced by or licensed to the church and that they are authorized to repurpose it.

That statement matters, but it is still a statement. Church Media Kit does not investigate ownership, grant a licence, or obtain permission from YouTube. Your church must know whether it may reuse the sermon, speaker image, music, scripture translation, testimony, photography, and any other material that could appear in a post.

Stop here if the person submitting the source cannot responsibly make that decision for the church.

Read the caption result before choosing content

Church Media Kit checks the video for English captions after the rights confirmation. Captions the church uploaded and YouTube's automatic captions both count. The result can take one of several forms.

• Captions are available.
• No captions were found.
• The source is invalid.
• The caption check is temporarily unavailable.

An invalid source cannot become a Sermon Kit. A temporary failure calls for a retry. It is not evidence that captions are missing.

Available captions give the workflow sermon text to work with. They do not prove that every word is right. Proper names, scripture references, uncommon theological terms, accents, overlapping speech, and poor audio can all cause errors.

YouTube says a transcript is available only when a video has captions. Viewers can jump from a transcript line to the matching moment in the video. That makes YouTube's transcript view useful for spot checks.

If no captions are found, Church Media Kit does not transcribe the sermon audio. It can instead use a manually supplied transcript, manuscript, or notes with at least 40 words. Check that text against the recording before relying on it. If no suitable text is available, add or repair the video’s captions in YouTube, or use another verified source. YouTube documents caption file, manual-entry, and automatic-caption options.

Choose a direction and the content set

Once you have usable source text, the setup asks how the drafts should sound. The setup offers four directions: Warm and Pastoral, Bold and Convicting, Reflective and Quiet, and Uplifting and Joyful.

These controls guide the draft. They do not teach the system your church's voice. A warm selection cannot know how your pastor speaks to a grieving family. A bold selection cannot decide whether a sharp line preserves the sermon's invitation or strips away its care.

The next choice is the content set. You can select counts for Quote, Big Idea, Teaching, Announcement, Prayer, Question, Devotion, Testimony, Sermon Recap, and Stat Impact posts. A Stat Impact post is built around a number the sermon states.

Choose what the source can support, not the largest possible set. A sermon with no event details should not be forced into an announcement. A private story should not become a testimony card because the format is available. A number should not become a Stat Impact post unless the sermon states it and a reviewer can verify what it means.

The useful question is not "How many posts can we get?" It is "Which posts help our people understand or act on this message without changing it?"

Generation becomes a saved job

Starting generation creates a saved job, so a browser refresh does not lose the work. The job can be queued, running, succeeded, failed, marked as needing attention, or held for reconciliation. Each selected content section is tracked separately. A section that is ready stays ready when another one fails, and some failed sections can be retried on their own.

These are recovery controls, not a guarantee. They do not prove that every attempt finishes or that generation will take a particular amount of time. "Needs attention" means a person decides what to retry or abandon. "Reconciliation" means the system could not tell whether an attempt worked, so it holds the result for review instead of repeating it blindly.

Your decision is simple. Do not start a second unrelated run because the first looks slow. Check the saved job first, and treat a request for manual review as a real stop.

The system builds evidence, then applies narrow checks

When captions are available, the workflow turns caption segments into bounded excerpts with timestamps. It uses those excerpts to prepare a short summary of the sermon and a plan for each selected content section.

The system applies several automatic checks. In plain terms, each planned post must draw on excerpts from the sermon, generated evidence outside the plan is rejected, required design fields must be filled, text must fit its design slot, and the preview must have the expected pages. The generation instructions also distinguish exact quotes from paraphrases and tell the system not to invent names, event details, addresses, or scripture references.

These checks catch specific structural problems. They do not prove that a post is true, wise, kind, accessible, or faithful to the sermon's purpose.

An exact line can still be misleading when removed from its surrounding argument. A paraphrase can pass a character limit while making the pastor sound more certain than the sermon was. A scripture reference can appear in the captions and still be misheard. An announcement can be complete in shape and out of date in fact.

The source evidence helps a reviewer find what to check. It does not replace the check.

Review the generated Sermon Kit

After the selected sections are ready, the Sermon Kit groups the generated static designs by content type. A design may have alternatives. The overview can mark a design as needing review and can block download when the selected pages are not ready.

"Ready" has a narrow meaning. It means the product's current structural checks have not found a blocking issue. It does not mean that a pastor approved the theology, a communications lead approved the voice, a ministry owner confirmed the facts, or an accessibility reviewer approved the page.

Opens a free sign-up for Church Media Kit.

Review each design against the source before choosing an alternative. Use this order:

1. Confirm that every quotation is word-for-word. Remove quotation marks from a paraphrase.
2. Read enough of the surrounding transcript to recover the sermon's actual point.
3. Verify names, dates, locations, service times, statistics, scripture references, and calls to action from a current source.
4. Remove prayer requests, safeguarding details, testimonies, or personal stories that do not have the right consent for a social post. Check any student or minor who is named or pictured yourself.
5. Check whether the image has the right subject and permission.
6. Read the page at phone size. Check type size, contrast, and whether the important words survive the design.
7. Write or correct the image alternative so it describes what the image contributes.

For step 7, the W3C images tutorial explains how to write a useful alternative. WCAG 2.2 asks for a 4.5:1 contrast ratio for ordinary text.

Edit the static pages in Studio

Studio is where the team corrects the draft. It supports changes to text, images, shapes, backgrounds, page order, and layers, with undo and redo. The point is not to decorate every page. It is to make the smallest changes that bring the post back to the source, the church's voice, and the intended reader.

Your church's saved Brand Kit is never applied during generation. A person adds it in Studio: colors from the swatches, and fonts through Apply Brand Kit. Studio is a static-design editor and does not claim parity with a general-purpose design platform.

Delete weak work. A Sermon Kit is not better because every generated idea survives. If a design needs too much explanation, uses a thin source fragment, repeats another post, or creates a pastoral problem, removing it is often the best edit.

Export only the pages the church approves

The export flow lets the user choose all pages, the current page, individual pages, or a page range. A selected page that still needs review blocks the export action. One approved page can be downloaded as a JPG or PNG image. Several approved pages can be collected in a ZIP.

Export is not approval, and it is not publication. It creates files that your church can move into its own approved publishing process. Church Media Kit does not post these files for you.

Keep the approved copy, image permissions, alt text, destination, and publication time together. If a fact changes after export, update the design before anyone posts it.

Compare the job, not the feature count

Other sermon-repurposing products advertise broader workflows. Sermon Shots claims transcription, video clips, images, templates, and direct social sharing. ChurchSocial Sermon Studio claims clips, written content, scheduling, and team collaboration. Pulpit AI claims audio, video, and document uploads with a larger set of ministry resources.

These are the vendors' own descriptions, and they point to different buying decisions. Our side-by-side pages for Sermon Shots, ChurchSocial.ai, and Pulpit AI go further. If your church needs captionless audio transcription or a particular publishing workflow, compare a product that can demonstrate that job now. External publishing is not included in the current Church Media Kit subscription.

Church Media Kit is narrower. It starts with a public YouTube sermon, depends on source evidence, prepares static drafts, and keeps a human review between generation and export.

Use one ordinary sermon to verify the product

A polished sample tells you very little. Use your free first sermon as the test, and pick an ordinary authorized one. Choose one with a proper name, a scripture reference, a paraphrase, an announcement, and at least one section that should not become a post.

Walk the whole path:

• Submit the real public URL and show the rights confirmation.
• Open the captions and compare one line with the video.
• If the sermon has no captions, test the manual-text fallback: supply a verified transcript, manuscript, or notes of at least 40 words and compare it with the recording. If no verified text is available, add or repair captions before retrying.
• Select a small content mix instead of every format.
• Refresh the page while drafts are being made, and confirm the saved job is still there.
• Trace one exact quote and one paraphrase back to their evidence.
• Correct a factual detail and replace one unsuitable image.
• Leave one page unresolved and confirm that export stays blocked.
• Approve a different page and export only that page.

A good test shows the failure state, the correction, and the final handoff, not only the clean result. Review time per sermon is not a published figure, so time your own reviewer during the test.

Is it a fit?

Church Media Kit may fit if your church:

• has an authorized public YouTube sermon with captions, or a verified transcript, manuscript, or notes of at least 40 words;
• wants editable static social drafts (short captioned clips come from a separate app, Sermon Clips, which works from an uploaded recording);
• has a named person who can review the source and approve each page;
• is comfortable publishing the exported images itself.

It does not fit if your church needs:

• audio transcription for a sermon with no captions and no verified text;
• branding applied automatically, or automatic approval;
• external publishing from the subscription;
• guaranteed outcomes.

To try it, create a free account and run your first sermon. See the current Sermon to Social feature and pricing. The product can prepare material and expose checkpoints. Your church still decides what the sermon means, what the public should see, and whether a page is ready to carry the church's name.