What to check before choosing sermon-repurposing software

Church Media Kit turns one sermon into editable social-post drafts: designs, captions, and alternative text that your team reviews, edits, and downloads. It does not post for you. External publishing is not included in the subscription, so your team posts through its own process. Plans start at US$29.95 per month, and a free account needs no card.

This guide helps you decide whether any sermon-repurposing tool, ours included, fits your church. Church Media Kit team makes Church Media Kit and has a commercial interest in this guide. It is a maker-authored checklist, not an independent review.

Before comparing software, define what your church needs to finish. A generated draft is not a reviewed asset. An export is not a scheduled item. A provider receipt is not proof that the right post is visible on the right account.

Without a shared finish line, a feature comparison rewards breadth. It hides the work that determines whether a post is accurate, approved, accessible, and recoverable.

Then test one ordinary sermon that your church has permission to use. Follow it through the whole route. Note the setup, the fixes to the source, the decisions people make, the editing, the handoffs, anything that fails, the checks on the destination account, and the records you keep for a later correction.

Public product pages describe a vendor's offer. They cannot tell you what your church will have to repair, review, or wait for. For Church Media Kit's current workflow and product boundaries, compare the actual offer with your finish line; review current pricing only if the workflow fits.

We rechecked Church Media Kit's live pricing and published terms on October 12, 2026. Our research on other vendors dates from 29 August 2026. Their details remain attributed to their public pages and may change. We did not create vendor accounts, run vendor outputs, or perform a side-by-side test. A feature missing from one public page is not proof that the product lacks it.

Start with the completion definition

Write one sentence that describes what "done" means for your church. For example:

One approved static teaching post is visible on the intended account with the final wording, crop, link, audience, and alternative text checked, and the source and approval record retained.

Your finish line may stop at an approved local export. That is valid. Just do not compare it with another route whose finish line includes provider delivery and native inspection.

Compare software against the last state your church actually requires, not the first state a product can create. If your church only needs drafts to download and post by hand, the table stops at the second or third row.

Check the source and rights path

Start with what the product can accept under the exact plan you would buy. Products in this category describe different combinations of public links, private links, files, documents, slides, audio, and recorded messages. Do not assume the category name means every product supports the same sources.

Ask these questions:

• Which source types are accepted, and which require public access?
• Does the product retrieve existing captions, transcribe an audio track, read a supplied document, or use another method?
• Which languages and caption tracks are supported?
• Can a reviewer trace a candidate back to source words and a useful time range?
• Are exact quotations, paraphrases, and summaries labelled differently?
• What happens when captions are missing, incomplete, or wrong?
• What happens when the source cannot be reached temporarily?
• Can a reviewer replace or correct the source without losing the decision record?
• Who confirms that the church may process and republish the sermon and every included work?
• Does the church have consent to use footage or images of children, teens, or other identifiable people, and how quickly can a family ask for a post to be removed?
• Does the vendor verify rights, or merely record the user's statement?

YouTube says a transcript is available when an item has captions. A public YouTube URL therefore does not prove that useful transcript evidence exists. A saved URL with no sermon words is a source reference, not a transcript.

Availability also does not settle permission. YouTube's copyright overview and licence guidance make clear that material appearing on YouTube does not grant another party the right to reuse it.

A church may own its recording while still needing to consider music, Scripture editions, guest speakers, photographs, identifiable stories, and other included material.

A rights checkbox in a product only records what the church says. It cannot investigate or grant rights.

Match the output to the actual job

Name the required output without relying on a product label.

Representative vendor pages show how far the category spreads.

Sermon Shots currently advertises transcription, static graphics, moving-image excerpts, templates, written resources, languages, and direct publishing on named plans. Pulpit AI currently advertises document, slide, audio, and recorded-message inputs with several written and visual outputs.

ChurchSocial describes a broader social-planning product with a sermon add-on, publishing, design, and team functions. Modulus describes a narrower source-and-writing job while leaving visual production elsewhere.

These are different workflows. None of those public pages proves output quality, source accuracy, suitability for your church, or parity with another product.

If your weekly need extends beyond editable static sermon-derived drafts, do not score a static-draft product against work it does not claim to perform. Exclude it. The same rule applies in the other direction. A broad output list should not receive credit for source fidelity, approval, or recovery until the route proves those duties.

Inspect fidelity and human review

Ask the vendor to show where one exact draft came from in the sermon. Then have your own reviewer check the result.

The reviewer should be able to answer:

• Does every exact quotation match the authorized source?
• Does a paraphrase stay labelled as a paraphrase?
• Does the short version preserve the qualification that controls the point?
• Are Scripture references, names, dates, locations, and factual claims correct?
• Does the wording represent the church's teaching?
• Does the source include a pastoral story, prayer request, child, vulnerable person, health detail, or other sensitive material that should not be republished?
• Does the church have permission and consent for the planned use and destinations?
• Does the copy sound like this church without inventing a voice-matching result?
• Does the final design fit the church's visual rules?
• Do the exported pixels remain readable and complete?
• Does the alternative text describe the final image in its posting context?
• Who has authority to approve the exact version?
• What evidence identifies the source, corrections, approver, final asset, and later destination state?

Automated checks can catch missing fields, placeholders, structural defects, or some source mismatches. They do not make a pastoral, theological, legal, safeguarding, or publication decision.

Accessibility also belongs to the final version. The W3C Images Tutorial says informative images need a concise text alternative that conveys their essential information. WCAG contrast guidance also applies to words rendered into an image.

A draft alternative-text field and a structural readiness label do not prove that the crop, contrast, text size, or description works after export and destination processing.

Test editing, brand control, and export

Open a draft and correct it yourself. Do not settle for watching a polished demo.

Check whether a person can edit the exact words, images, shapes, backgrounds, crop, page order, layers, and layout properties needed for the result. Test design alternatives, undo and redo, asset replacement, multi-page handling, and whether a correction survives reopening or regeneration.

Ask how the product handles brand inputs. A logo upload is not automatic branding. A template is not proof that church colors, fonts, imagery, logo use, and writing choices are applied to every output. If people must apply those rules manually, put that work in the comparison.

Export the exact approved version. Check:

• all pages selected and in the intended order;
• supported file formats and dimensions;
• filenames that another person can identify;
• opened files, not only a success message;
• text fit, crop, color, transparency, and image quality;
• caption, link, alternative text, credit, and notice files;
• metadata or a manifest when the handoff needs one; and
• a record that ties the export to the approved version.

An editor with common static controls is not automatically a replacement for a general design product. An export button is not proof that every browser, page, and file path works in normal use.

Map the people and the handoffs

One person can carry several duties. The duties still need names.

Then inspect the product's account model. Ask about owners, seats, invitations, roles, concurrent editing, comments, approvals, transfer, and what happens when the only account holder leaves. A documented ownership transfer is not the same as shared seats. A comment is not approval. An approval control is not proof that the reviewer had ministry authority.

An owner-only offer is a non-fit when several people need separate accounts, concurrent editing, or approval inside one shared workspace. Church Media Kit plans include role-based Seats; confirm the needed count against pricing. Outside review can work, but the owner must preserve the exact version and bring the decision back into the handoff.

Demand destination and recovery evidence

If the purchase depends on publishing, require a current demonstration with the same account type and destination your church will use.

For Facebook and Instagram, ask separately about:

• eligible account types and connection permissions;
• supported asset shapes and caption differences;
• alternative-text transport and destination editing;
• previews and what they do not reproduce;
• scheduling and immediate handoff;
• provider identifiers and native-result links;
• correct handling when some destinations succeed and others fail;
• ambiguous responses where the provider may have accepted the post;
• duplicate prevention before retry;
• credential repair, retry, rescheduling, and final verification;
• local archive or hide controls compared with remote deletion; and
• the record retained for later correction or removal.

Do not let a local "scheduled," "sent," or "published" label replace provider proof. The final publisher should inspect the native result for the correct account, asset, caption, links, crop, audience, and accessibility treatment.

An ambiguous provider response is not permission to send again blindly. Check the destination first. A retry that creates a duplicate is a new failure.

Deleting or hiding a local record also does not prove that a provider-held post changed. Ask which removals happen inside the product and which require the provider's own controls.

Read the commercial terms as a workflow

The headline monthly number is only one input. Record:

• market and currency;
• monthly or annual billing;
• taxes and invoice information;
• what the allowance counts;
• when work reserves capacity;
• what the visible usage meter omits;
• treatment of terminal failures and uncertain jobs;
• overages, credit packs, or extra-work purchases;
• trial terms and conversion;
• team plans and seat charges;
• live Checkout amount, interval, and currency;
• receipts and payment-failure handling;
• refund terms;
• cancellation controls and effective date;
• access, editing, export, retention, and deletion after cancellation;
• support route and response terms;
• service levels, eligibility geography, and regional restrictions; and
• what happens when normal demand exceeds the allowance.

Do not compare plans whose allowance units differ as if the numbers were equivalent. A file upload, recorded hour, generated kit, connected account, and owner seat are different units. The output and retained work can differ too.

Check the current Church Media Kit offer

A generation is one Sermon Kit: one saved set of editable designs, captions, and posting guidance made from one YouTube sermon. A Seat is one person's login on your church's account. As of October 12, 2026, the live pricing page lists:

A free account needs no card. Sermon to Social, Sermon Clips and Sermon Slides each give one free use (one sermon, one upload up to two hours, one AI deck). A Church Page is live free for 14 days from first publish, and Design and Verse of the Day are free with any account. The pricing page also states the video-upload allowances; use it for those limits and do not infer other video outputs. The published terms cover cancellation, refunds, taxes, and access after cancellation. External publishing is excluded from the current subscription.

An allowance is a limit, not a promise of completed or usable generations. The account may show usage differently from work that is still in progress; ask how active and uncertain jobs affect the allowance before relying on a workflow. Compare the pricing page and terms with the Checkout total and the exact workflow you need.

Audit privacy and operations separately

Ask what happens to the source and generated material at every step:

• Which AI providers receive sermon words, prompts, settings, or generated content?
• Does the vendor use customer material for training, evaluation, product improvement, or marketing?
• Which settings, plan terms, and contracts govern that use?
• How long do source files, transcripts, prompts, drafts, exports, and provider records remain?
• How does account deletion differ from content deletion?
• What remains in backups, logs, billing records, support records, or legal holds?
• Which subprocessors receive data, and in which regions?
• What happens to copies already sent to a destination provider?
• Can the church export its data in a usable form before cancellation or deletion?
• Which incident, support, uptime, backup, restore, and recovery promises are contractual and currently operated?
• What current deployed evidence supports those promises?

A marketing privacy statement is not a security audit. A documented deletion path is not proof that a deletion job ran. A provider setting is not proof that all copies disappeared.

The published Privacy Policy explains how sermon context, transcript excerpts, prompts, and generation settings are handled, including the limits of the provider setting that asks AI providers not to store requests. It also states the rule against using your sermon material for training, evaluation, or product improvement without separate consent. Read it for current subprocessors, retention, deletion, and cross-border terms. A public policy is not an independent security audit or proof that every operational deletion or recovery step has been tested.

What Church Media Kit can and cannot support in this check

For the public YouTube sermon workflow, the current marketing describes source-based editable drafts for review and export; it does not include external publishing. Paid plans include role-based Seats. These boundaries do not establish rights verification, audio transcription for YouTube intake, automatic branding, in-product approvals, universal alternative-text delivery, privacy operations, reliability, service levels, or buyer outcomes.

The public Sermon Content workflow is a non-fit for a church that needs:

• a source other than a public YouTube sermon or supplied text;
• a workflow without usable captions or verified text and a clear rights decision;
• outputs beyond editable static drafts;
• automatic church-brand application;
• more active Team Members and pending invitations than the plan’s included Seats allow, concurrent editing, comments, or in-product approval;
• external publishing included in the subscription;
• one alternative-text method guaranteed across destinations;
• a generation allowance above the highest listed Volume plan, or an overage path;
• terms the church cannot accept, or a need for an independent security audit or operational proof that the seller has not provided;
• service in a geography that has not been confirmed; or
• a workflow with no accountable human reviewer.

Other Church Media Kit workspaces have separate scopes. Evaluate each only against its published offer and a current demonstration.

Run one representative-source trial

Use one ordinary sermon your church may repurpose. Make sure it has usable captions and keep a stronger approved transcript or manuscript for checking.

Give every product the same:

• source and source words;
• brief for one required static result;
• dimensions and destination fields;
• church assets and wording rules;
• source and ministry reviewer;
• final publisher;
• intended destination and account; and
• completion definition.

Record the whole route:

1. List setup, access, plan, permissions, source preparation, templates, church assets, and training.
2. Keep every candidate and trace it to the source.
3. Record corrections to quotation, context, doctrine, facts, rights, consent, safeguarding, church voice, design, and accessibility.
4. Separate active work, waiting, and blocked time.
5. Open every export and destination preview.
6. Record handoffs, approval, provider responses, native checks, partial results, ambiguous results, duplicate checks, and recovery.
7. Preserve the source, candidates, exact approved asset, screenshots, errors, decisions, and final state.

One run may expose a broken source path, missing control, or unreliable handoff. It cannot prove what every church will experience.

Public manuals, similar products, anecdotes, and one person's impression do not support broad claims about speed, quality, accuracy, savings, reliability, or outcomes. That is why this guide gives no time-saved figures.

A decision rule for your trial

After one trial, record one of three results for each requirement: fit, hold, or non-fit.

Suppose the source is one authorized public YouTube sermon, the required result is one editable draft, and the church has people assigned to source, ministry, design, accessibility, and publication decisions. The plan has enough Seats for everyone who needs access. The workflow may fit that draft-preparation task, but nothing is proven until you generate and export one draft yourself. Until then, the result is hold.

If a requirement is not included, such as publishing from the product, or needs more Seats than the plan provides, record non-fit for that requirement. A public pricing page is not proof of product performance.

What we checked

We checked this guide on 29 August 2026. Sources included Google Search guidance, official YouTube and W3C pages, public vendor product, plan, terms, privacy, and help pages, current practitioner discussions, and Church Media Kit product, commercial, legal, privacy, and deployment records.

We did not create vendor accounts, accept free access, buy a plan, contact sales, inspect authenticated controls, run a vendor output, test support, or complete a side-by-side trial. We did not audit a vendor's security, privacy, retention, deletion, training, reliability, or service operations. Missing public detail proves only that we could not verify it on the pages checked.

Google's people-first guidance, generative search guide, and review guidance support clear sourcing, honest creation context, useful original decision work, and first-hand evidence for performance conclusions. They do not promise that this page will rank, appear in a generated answer, or receive a citation.

To report a factual error or changed vendor fact, use the correction route on our editorial standards page.

Frequently asked questions

What is the first question to ask a sermon-software vendor?

Ask the vendor to show how your required result reaches your definition of done. Name the source, output, reviewer, approval, destination, and retained evidence. A general feature tour cannot answer that question.

Is a generated sermon post ready to publish?

Generation creates a candidate. A person still needs to check source wording, context, doctrine, facts, rights, consent, safeguarding, church voice, design, accessibility, destination fields, and the exact version being approved.

Should we choose the product with the most output types?

No general conclusion follows from output count. First exclude products that cannot accept the required source or produce the required result. Then compare review, correction, handoff, commercial terms, privacy, provider proof, and recovery for the work that remains.

Does a rights confirmation prove we may repurpose the sermon?

No. It records the user's statement. The church still needs a defensible rights and consent decision for the recording and every included work or person. Seek qualified advice when the answer is uncertain.

Does a scheduling status prove the post is live?

No. A scheduled item is an instruction. A provider receipt is a later state. The final publisher should inspect the native result on the intended account and record partial, ambiguous, failed, or corrected outcomes.

How should a church compare allowances?

Compare the unit, reservation point, visible meter, failed and uncertain work, reset boundary, overage path, and required output. File uploads, recorded hours, completed kits, destination accounts, and seats are not interchangeable.

Is Church Media Kit a fit today?

It may, if your church wants editable drafts from a sermon, has someone to review them, and is content to post them through its own process. Church Media Kit does not publish for you. Run the one-sermon trial above with a free account, which needs no card, and read the current pricing and terms before you pay.