Resource Review11 min read

CP Sermons

4.6Editor rating

A polished, actively maintained WordPress sermon manager with a persistent player, deep filters, transcripts, podcasts, migrations, SermonAudio sync, and engagement analytics—one of the strongest self-hosted choices, provided your church can own WordPress security, media delivery, licensing, and accessibility.

Starting price
$14.99/month
Free tier
No
Platforms
Self-hosted WordPress · Modern themes · Full Site Editing · Page builders
Developer
Church Plugins / Mission Lab
Launched
2023 or earlier
Updated
Aug 9, 2026
1.6.2Current version
$14.99Monthly
$127Yearly
$379Lifetime
$24.99All Access monthly
30 daysRefund window
IncludedSermonAudio sync
IncludedPodcast feeds

The verdict

CP Sermons is unusually complete for a WordPress sermon plugin and has current documentation, recent releases, migration tooling, meaningful analytics, and a clear commercial owner. The $127 annual single-plugin license is the best starting value for most churches; the $379 lifetime option only makes sense after a year of compatibility and support experience, and the $249 annual bundle is attractive when at least two or three companion plugins replace real costs. Run the migration on staging, retain backups, test the player and filters with your theme, audit transcript and podcast output, and remember that self-hosting transfers security, performance, accessibility, media rights, and continuity to the church.

Try CP Sermons

Opens churchplugins.com

CP Sermons—also described in its documentation as CP Sermon Library—is a premium WordPress plugin for publishing, organizing, playing, filtering, and syndicating a church’s sermon archive. It creates structured content for messages, series, speakers, topics, seasons, Scripture, service types, and campuses; offers modern archive and detail layouts; and keeps audio or video playing while a visitor browses other parts of the site. The result feels more like a purpose-built media application while the church retains content inside its own WordPress installation.

The current product page identifies version 1.6.2 and shows active 2024–2026 maintenance. Recent documentation covers configurable labels and slugs, a template builder, Full Site Editing, transcript visibility, podcast feeds, service types, SermonAudio synchronization, analytics, import and migration, and role behavior. Changelog entries document Divi compatibility, mobile player work, migration refinements, template shortcodes, feed fixes, and continuing core updates. That evidence matters because a sermon plugin becomes part of the church’s public archive and must survive WordPress, PHP, theme, and browser changes.

Pricing is unusually flexible. CP Sermons alone costs $14.99 monthly, $127 annually, or $379 for a lifetime license. The All Access Pass costs $24.99 monthly, $249 annually, or $749 lifetime and includes CP Sermons, Groups, Live, Staff, Locations, Sync, and future products described by the vendor. Monthly and annual plans renew automatically for updates and support; lifetime plans do not renew. The vendor advertises a 30-day full money-back guarantee. License quantities can apparently be selected for one, five, or fifty sites, so confirm the displayed checkout amount for the exact quantity rather than assuming the headline price covers every installation.

We reviewed the current first-party product, demo references, price table, documentation, changelog, customer reviews, privacy policy, and terms. We did not buy a license, install version 1.6.2, migrate a production archive, connect SermonAudio, validate a podcast feed with Apple, benchmark a large library, inspect generated markup with assistive technology, test every supported theme, or audit source code. This is a researched review of the public product and operating model, not a claim that we ran the plugin on a live church website.

✓ The good

  • Modern visitor experience - search, filters, responsive layouts, and a persistent player make a large archive genuinely browsable
  • Structured sermon data - series, speakers, Scripture, topics, seasons, service types, and campuses avoid an unsearchable video wall
  • Active maintenance - version 1.6.2, recent changelog entries, documentation, and support responses show a living product
  • Migration tooling - automatic paths for Sermon Manager and Church Content plus CSV options reduce switching labor
  • SermonAudio integration - scheduled import and synchronization can prevent duplicate publishing
  • Transcript support - manual or YouTube-imported text improves discovery and accessibility when corrected
  • Podcast generation - the site can create a primary feed and feeds scoped to series or taxonomy archives
  • Transparent licensing - monthly, annual, lifetime, bundle, renewal, and 30-day refund information is public
  • Useful analytics - views, average play duration, and engaged plays provide more signal than raw page hits

✗ Watch out

  • WordPress responsibility - the church owns hosting, updates, backups, malware defense, caching, database health, and recovery
  • No free production tier - evaluation relies on the demo and refundable purchase rather than a permanent limited edition
  • Theme and plugin conflicts remain possible - a polished plugin still shares one runtime with builders, caches, security tools, and custom code
  • Lifetime is not risk-free - continued compatibility and support depend on a vendor remaining healthy without future renewal revenue
  • Media costs sit elsewhere - video and audio hosting, bandwidth, captions, storage, and stream production are not included
  • Analytics can be mistaken for impact - a 70% play threshold is useful behavior data, not a measure of discipleship or pastoral care
  • Generated and imported text needs review - YouTube transcripts can mishear names, theology, Scripture, and sensitive stories
  • Role model inherits WordPress defaults - Editors can manage broad sermon content, so church-specific permissions may need additional controls

Best for

  • Churches already committed to a maintained self-hosted WordPress website
  • Congregations with a growing archive that needs consistent Scripture, speaker, series, season, and topic discovery
  • SermonAudio broadcasters that want their church site to synchronize rather than duplicate uploads
  • Teams migrating from Sermon Manager or Church Content Plugin with a staging and backup process
  • Churches that want their own branded archive, podcast feed, transcripts, and engagement reporting
  • Agencies managing several church sites and willing to confirm multisite license economics

Avoid if

  • Nobody is accountable for WordPress core, theme, plugin, PHP, backup, security, and incident maintenance
  • Your hosted church website does not permit custom WordPress plugins
  • You want an all-in-one video host, encoder, mobile app, OTT distribution, livestream chat, or pastoral response platform
  • Your current sermon library already provides excellent search, transcripts, feeds, and stable embeds with less operational burden
  • You cannot stage and validate the full archive before changing URLs or replacing a legacy plugin

What CP Sermons is

CP Sermons turns sermon publishing into structured WordPress content rather than a collection of posts or embedded videos. Administrators can change the public label from “Messages” to “Sermons” or another term, control URL slugs, set default artwork, decide which taxonomies and filters appear, enable or disable series and speakers, configure service types, and choose archive layouts. Shortcodes and the template builder place collections in other pages, while theme overrides and CSS variables support deeper brand work.

Because it is self-hosted, the canonical metadata stays in the church’s WordPress database. That creates control and portability but not independence from every vendor: media may still live at YouTube, Vimeo, Facebook, or SermonAudio; the plugin license supplies updates; the host runs PHP and MySQL; the theme controls surrounding markup; and podcast apps cache the feed. Document every layer and preserve raw media, transcript masters, images, taxonomy exports, and redirect mappings outside the live site.

Why WordPress churches choose CP Sermons: a modern library without surrendering the church domain

Many hosted media products make publishing easy but place discovery, branding, URLs, and analytics inside a vendor-owned environment. Many older WordPress sermon plugins preserve ownership but look dated or require theme work. CP Sermons aims at the middle: the church controls its domain and data while visitors receive a persistent player, fast filtering, coherent taxonomies, transcripts, podcasts, and modern layouts. Recent migration tooling makes that promise more practical for existing archives.

The strongest advantage appears over years, not on launch day. Consistently tagged Scripture passages, topics, series, speakers, dates, and service types can make hundreds of sermons discoverable through search engines and useful to members. Establish a publishing taxonomy and editorial checklist before importing everything. A feature-rich filter cannot repair inconsistent names, missing dates, duplicate speakers, uncorrected transcripts, or vague titles after the archive grows.

Archive, filters, templates, and persistent player: design for listeners first

The public experience includes text search and filtering by topics, seasons, Scripture, speakers, series, service types, year, and other configured facets. A player can remain active while the visitor moves through the website, and sermon pages can expose audio, video, notes, downloads, timestamps, speakers, and related metadata. Template Builder shortcodes, Full Site Editing compatibility, theme copies, CSS variables, and component controls give implementers several levels of customization.

Test a realistic library, not five demo sermons. Load hundreds of items, long filter lists, multiple speakers, missing images, direct uploads, external embeds, and old mobile formats. Use keyboard-only navigation, VoiceOver or NVDA, 200% zoom, reduced motion, and a slow phone. Confirm the persistent player announces state without trapping focus, filters expose labels and results, transcripts are reachable, and pause position survives navigation. Measure Core Web Vitals with caching both enabled and cleared.

Migration, imports, and SermonAudio sync: preserve identifiers before changing the front door

The documented migration wizard detects Sermon Manager and Church Content records and imports sermons, series, speakers, topics, Scripture, media URLs, attachments, thumbnails, notes, bulletins, and supported images. The product page also mentions Series Engine and CSV imports. SermonAudio integration can run a full import and check for new material on a schedule, with controls for broadcaster ID, earliest date, minimum duration, service type, and batch behavior.

Clone production into staging, take database and file backups, inventory every legacy URL, and count content by type before migration. Compare counts and spot-check the oldest, newest, longest, multi-speaker, attachment-heavy, and unusual records. Preserve original IDs in an export. Build permanent redirects before switching archive slugs, verify canonical tags and sitemap entries, and prevent both the old and new importer from running simultaneously. Sync is not backup; an upstream deletion or bad update can propagate.

Transcripts, podcasts, and analytics: extend reach without overstating the numbers

CP Sermons supports manual transcripts and direct import from YouTube, with controls for displaying or truncating them. It generates a general podcast feed and can generate feeds for a series or taxonomy path, with artwork, title, subtitle, description, provider, copyright, email, category, clean marker, language, and migration URL settings. Current analytics advertise views, average play duration, and engaged plays defined as reaching 70% or more.

Correct every machine transcript against the recording, especially names, quotations, Scripture references, original-language terms, jokes, and pastoral stories. Confirm permission to republish music, video clips, artwork, and guest speakers in podcast and transcript forms. Validate feeds before submitting them, keep the feed URL stable, and retain audio masters. Define analytics consent and retention, filter staff and bots where possible, and read completion as product behavior. A listener reaching 70% does not prove agreement, understanding, conversion, or spiritual growth.

Pricing

CP Sermons monthly

$14.99/month

The lowest commitment and a good production pilot after the demo. The license auto-renews monthly for updates and support. Confirm site quantity, tax, cancellation timing, and whether an expired license disables only updates/support or any functionality.

Best value

CP Sermons yearly

$127/year

Equivalent to about $10.58 monthly and $52.88 less than twelve monthly payments. This is the strongest default after a staged migration and compatibility test.

CP Sermons lifetime

$379 once

Roughly three annual terms at current pricing. The license does not auto-renew. Ask whether lifetime covers the purchased site count, all future major versions, support for the life of the product, and license transfer after a redesign.

All Access Pass

$24.99/mo · $249/yr · $749 lifetime

Includes Sermons, Groups, Live, Staff, Locations, Sync, and advertised future products. The annual bundle costs $122 more than annual CP Sermons alone; justify that difference with companion plugins the church will actually operate.

Money-back guarantee

30 days

The vendor promises a full, hassle-free refund during the first 30 days if the product is unsuitable. Record the deadline and test migration, performance, theme compatibility, mobile playback, podcast output, and support before it passes.

The single-plugin monthly price totals $179.88 over twelve months. Annual billing at $127 saves $52.88 and is the sensible recurring term after the first month or staged evaluation. The $379 lifetime license breaks even just before the third annual renewal at unchanged prices.

Lifetime should not be treated as maintenance without risk. WordPress, PHP, databases, browsers, podcast specifications, video vendors, and accessibility expectations will continue changing. Ask what “lifetime” means, what support is included, whether major rewrites remain covered, and how the company funds continuing work.

The All Access annual pass is $249, $122 above CP Sermons alone. CP Live or CP Sync can easily justify the difference for the right church, while unused Groups, Staff, and Locations add attack surface and maintenance. Install only the modules that replace a documented workflow.

Hosting is not included. Add managed WordPress hosting, backups, security monitoring, development or agency support, media hosting, captioning or transcription review, podcast artwork, bandwidth, and migration labor. A $127 plugin can sit inside a several-thousand-dollar annual web operation.

Use the 30-day guarantee as an acceptance window rather than an invitation to rush production. Establish written tests, open support tickets early, and preserve the prior library until redirects, feeds, analytics, mobile playback, accessibility, backups, and rollback have passed.

Where CP Sermons falls behind

A permanent free tier. A limited noncommercial edition would make theme, accessibility, migration, and performance evaluation easier before checkout.

Published technical requirements. The sales page should prominently state supported WordPress and PHP versions, database expectations, browser support, multisite behavior, and tested builders and caches.

Enterprise trust material. Public security practices, vulnerability reporting, update policy, support targets, incident communication, accessibility conformance, and software bill-of-materials guidance would strengthen procurement.

Permission granularity. Inheriting standard WordPress post capabilities is understandable, but sermon-specific roles and approvals would help volunteer-heavy teams avoid overly broad Editor access.

Feed terminology. References to Google Podcasts are stale because that consumer service was discontinued; current documentation should emphasize valid RSS and the active directory ecosystem.

Migration matrix consistency. The product page and documentation should give one authoritative table for Sermon Manager, Church Content, Series Engine, CSV, SermonAudio, and exactly which fields each pathway preserves.

Public scale evidence. Benchmarks for libraries with thousands of sermons, large taxonomies, concurrent listeners, search indexing, and common caching stacks would help larger churches plan.

CP Sermons vs. Sermon Manager vs. SermonAudio vs. Subsplash

Sermon Manager and Church Content Plugin have historically offered WordPress-native sermon structures, often at a lower initial cost, but CP Sermons positions itself as the more modern and actively supported destination and supplies dedicated migration paths. Existing churches should compare current maintenance, markup, templates, player behavior, import completeness, support, and total redesign effort rather than assuming the familiar plugin remains safest.

SermonAudio is a specialized hosting, discovery, broadcasting, and distribution service. CP Sermons can synchronize from it, making the two complementary: SermonAudio handles the external media ecosystem while CP Sermons presents the branded archive on the church domain. Confirm ownership, deletion behavior, canonical pages, analytics definitions, and what happens to the site when the upstream API is unavailable.

Subsplash and similar church-platform suites combine media, apps, giving, messaging, websites, and engagement under one commercial relationship. They reduce WordPress operations but cost more and increase platform dependence. CP Sermons is compelling when the church already has good hosting and competent WordPress ownership and wants one excellent media component. Choose the operating model the team can sustain for ten years, not the most impressive launch demo.

The bottom line

CP Sermons earns a strong recommendation for WordPress churches because the public evidence matches the product promise: version 1.6.2 is current, documentation is detailed, recent changes address real compatibility and workflow issues, migration paths are explicit, and the $14.99 monthly, $127 annual, and $379 lifetime terms are understandable. The plugin’s greatest strength—living inside the church’s own website—is also its largest condition. Someone must own updates, backups, security, caching, accessibility, taxonomies, transcripts, feed health, redirects, and vendor continuity. Buy one month, clone the site, migrate and test a representative archive, open a real support request, and use the 30-day refund window deliberately. Move to annual when it passes; consider lifetime only after sustained compatibility; buy All Access only when companion plugins replace named systems and owners.

Alternatives to CP Sermons

Frequently asked questions

How much does CP Sermons cost?

Current single-plugin pricing is $14.99 monthly, $127 yearly, or $379 lifetime. The All Access Pass is $24.99 monthly, $249 yearly, or $749 lifetime. Confirm the selected number of sites at checkout.

Is there a free version of CP Sermons?

No permanent free tier is advertised. The vendor provides a demo and a 30-day money-back guarantee. Use staging and complete acceptance tests before the refund deadline.

Can CP Sermons migrate our existing library?

Documentation describes automatic migration for Sermon Manager and Church Content, while the product page also names Series Engine and CSV import. Field coverage differs by source, so test a cloned database and compare record counts, media, taxonomies, attachments, and URLs.

Does CP Sermons work with SermonAudio?

Yes. The integration can perform a full import and scheduled checks for new sermons using a SermonAudio API key and broadcaster ID, with date, duration, service-type, and batch controls.

Does it create a podcast feed?

Yes. It supports a primary sermon feed and feeds scoped to series or taxonomies, with podcast metadata settings. Validate the RSS, artwork, enclosures, duration, and stable URL before submitting it to directories.

What happens if the license expires?

The public page says recurring licenses provide continued software updates and support, but it does not clearly summarize every post-expiration behavior. Ask whether the installed plugin continues functioning and how security updates, downloads, and support access change.

Is the lifetime license the best value?

It breaks even at roughly three annual payments if price and use stay constant. First verify what lifetime covers, vendor sustainability, site count, major versions, support, transfers, and compatibility through at least one substantial WordPress or PHP update.

Sources & further reading

More Sermon Libraries

Try CP Sermons