- Starting price
- $9/month
- Free tier
- No
- Platforms
- Embeddable web widget · WordPress · Squarespace · Wix · church website builders
- Developer
- Cowntdown / David Crowson
- Launched
- 2022 or earlier
- Updated
- Aug 9, 2026
The verdict
Cowntdown solves an oddly persistent church-website problem for a modest price: configure recurring service times once, style the timer, paste the embed, and send visitors to the stream when the clock reaches zero. It is not a streaming host, chat room, video player, schedule database, or outage-proof service. The best buyer is a small communications team that values the automatic reset more than the $97 annual fee and will verify timezone, daylight-saving behavior, mobile layout, screen-reader output, cancellation, and a plain-link fallback before relying on it.
Try Cowntdown ↗Opens countdown.church
Cowntdown—with the deliberate “Cow” spelling—is a hosted countdown generator made for churches that livestream on a recurring weekly schedule. A church chooses one or many service times, sets the expected duration, controls text and visual styling, supplies the destination link, and pastes two lines of embed code into its website. The public timer counts down to the next service, changes its message or link during the live window, and then moves automatically to the next scheduled service. Staff do not have to reset a generic countdown every Sunday night.
The product comes from David Crowson, a worship pastor and church-focused designer who also created Churchly before selling that platform to Ministry Pass in late 2023. The origin story is credible and narrow: churches repeatedly asked for a timer that understood weekly recurrence and multiple services, and ordinary event countdowns did not. Cowntdown now advertises compatibility with WordPress, ChurchCo, Subsplash, Nucleus, Churchly, Squarespace, Wix, and other sites that accept the supplied embed.
Current public pricing is $9 per month or $97 paid annually. The annual option saves $11 against twelve monthly payments. Both begin with a seven-day free trial that the pricing page says requires no credit card. Cowntdown is therefore inexpensive but not free. It should be compared with a small custom script, a timer included in a church website or livestream product, and the labor cost of remembering to update a manual banner—not with the price of a complete streaming platform.
We reviewed the current official marketing, price, support, about, privacy, and terms pages and inspected the public site and example behavior. We did not create an account, paste the production embed into a church website, alter a live schedule, simulate a daylight-saving transition, inspect authenticated code, measure uptime, test assistive technology, or receive a security response. Claims that churches with a countdown average twice the livestream audience were not accompanied by a visible study design, sample, or independently auditable evidence, so we treat that as marketing rather than a forecast.
✓ The good
- Purpose-built recurrence - weekly service schedules reset without a staff member editing the website after every broadcast
- Multiple services - one timer can move through many times on one day or across several days
- Low price - $9 monthly or $97 annually is accessible for churches that genuinely save recurring labor
- No-card trial - seven days is enough to stage the widget on a hidden page and test its basic cycle
- Broad embed compatibility - the product only needs a host that permits the supplied code
- Visual customization - font, size, colors, messages, and links can be aligned with the church website
- Simple publishing - two lines of code keep the website integration lighter than a full plugin or theme migration
- Clear scope - the FAQ explicitly says Cowntdown is not the livestream platform, reducing category confusion
✗ Watch out
- Single-purpose subscription - some website, video, or church-online platforms already include a schedule and countdown
- Hosted dependency - an unavailable script, changed domain, or slow third party can leave a blank or delayed website element
- No public status or service-level page - availability, monitoring, incident communication, and recovery targets are unclear
- Timezone and exceptions need proof - holidays, special services, daylight-saving changes, and canceled broadcasts can defeat a recurring schedule
- Accessibility is undocumented - color contrast, keyboard behavior, screen-reader announcements, reduced motion, and zero-state semantics need testing
- Audience-growth claim is unsupported - a timer may help visitors, but it cannot guarantee twice the attendance
- Legal copy looks generic - the terms include unrelated child-account, messaging, and Cowntdown.io language that weakens confidence in maintenance
- Privacy detail is limited - analytics, remarketing, cookies, transfers, retention, subprocessors, and account-data handling deserve a clearer current notice
Best for
- Churches with one or several predictable weekly livestream times and an existing video destination
- Small teams that repeatedly forget to update a manual homepage countdown or live banner
- Sites built on a platform that accepts custom embed code but lacks a reliable recurring timer
- Churches willing to test the complete schedule cycle on a staging page before public launch
- Teams that want a branded handoff to YouTube, Facebook, Vimeo, or another existing stream
Avoid if
- Your website or livestream platform already provides an accurate schedule-aware timer at no added cost
- Service times change often, are announced at short notice, or depend on manual go-live confirmation
- Your site builder blocks third-party scripts or your security policy requires a documented vendor review
- You need video hosting, encoding, simulcasting, chat, prayer, moderation, analytics, or on-demand media
- You cannot provide a visible text link and schedule when the embed fails or JavaScript is unavailable
What Cowntdown is
Cowntdown is schedule logic wrapped in a branded web widget. Its dashboard stores a repeating weekly pattern rather than a one-time date. The public embed asks which occurrence comes next, counts toward it, recognizes the defined service window, and then advances. That distinction is the product. A generic “days until Christmas” script can display numbers; Cowntdown is intended to understand Sunday at 9:00 and 11:00, Wednesday at 7:00, and the reset after each one.
The widget sits between the church website and the actual broadcast. It does not know whether the encoder started successfully unless the product has an integration not documented on the public pages. A schedule can say “live” while the platform is offline, or it can send people to an old link if staff forget to update the destination. Treat its state as scheduled availability, not positive technical confirmation, and phrase messages accordingly: “Service is scheduled now” is more honest than “We are live” when no health check exists.
Why churches use Cowntdown: the timer survives Sunday without a Monday reset
The recurring reset is a tiny automation with visible consequences. A stale banner tells a Monday visitor that church is still live, a one-off counter reaches zero and stays there, and a volunteer has to remember another weekly website task. Cowntdown preserves one consistent homepage location and advances through the schedule. Multiple service times are especially useful because the same element can guide a visitor from one occurrence to the next without separate edits.
That benefit is worth paying for only when the schedule is stable and the embed removes real work. Assign one communications owner, record the timezone and all service windows, add a monthly check, and create an exception checklist for holidays, weather closures, conferences, and daylight-saving changes. A recurring automation is reliable when exceptions are deliberately handled—not when everyone assumes the schedule is self-aware.
Recurring and multi-service scheduling: test the edges, not just Sunday morning
Cowntdown lets a church add multiple services to one countdown and spread them across more than one day. The service duration tells the widget when to stop counting and when to begin looking for the next occurrence. This can cover repeated Sunday gatherings, a midweek stream, or another predictable broadcast without building several timers. Dashboard edits remain possible after publication, so the embed need not be replaced for ordinary schedule changes.
During the trial, set the production timezone explicitly if the interface allows it, then test from a device in another timezone. Observe the instant before zero, the full service duration, simultaneous or closely spaced services, midnight boundaries, and the next occurrence. Ask support how daylight-saving transitions are calculated. Document who edits holiday exceptions and how quickly cached changes appear. Never learn the answer while visitors are arriving for a real service.
Styling and messages: keep the timer clear, responsive, and truthful
The product advertises controls for font family, text size, colors, messages, links, and other visual details. That is enough to make a small embed feel native to most church sites. Customize the label so people know what is approaching, include the day and time outside the changing digits, and make the destination action explicit. Preserve sufficient contrast and a usable tap target rather than treating the timer as decoration.
A moving counter can be noisy for screen readers if every second is announced. Test with VoiceOver or another assistive technology and ask Cowntdown how the numbers are exposed. The surrounding page should state the next service in static text, expose the live link without requiring the timer, and remain understandable when scripts or styles fail. Do not rely on color alone to indicate live status. Respect reduced-motion preferences and test at narrow mobile widths and large text zoom.
Two-line embed and livestream handoff: simple integration still needs a fallback
Publishing is intentionally lightweight: copy two lines from Cowntdown and paste them into a website area that permits custom code. The site lists WordPress, ChurchCo, Subsplash, Nucleus, Churchly, Squarespace, Wix, and more as examples. When the timer reaches the configured state, a custom link can send the visitor to the church’s video destination. The church remains responsible for the stream itself.
Third-party code affects privacy, performance, content security policy, and availability. Inspect the requested domains, load the page with common privacy protections, measure the impact on mobile performance, and place the embed below critical service information if it blocks rendering. Keep the normal watch link and service schedule in native HTML. If Cowntdown fails, remove or disable its snippet without losing the path to worship. Never paste production code into a page builder without recording where it lives and who can change it.
Pricing
Free trial
7 days
The current pricing page says no credit card is required. Use the trial on a hidden or staging page, enter every regular service, and watch at least one complete pre-live, live, and post-live transition before buying.
Monthly
$9/month
Pay month to month and cancel when the widget no longer earns its place. This is only $11 more across a full year than the annual price and is the safer first paid term.
Annual
$97/year
Paid annually, equivalent to about $8.08 per month. Choose it after the timer has survived schedule changes, daylight-saving behavior, mobile and accessibility tests, and a normal cancellation or renewal review.
Livestream platform
Not included
Cowntdown links visitors to an external destination. You still need YouTube, Facebook, Vimeo, Resi, Subsplash, another host, or an embedded player, plus the camera, encoder, connectivity, moderation, and archive workflow.
Implementation and fallback
Church-managed
Budget staff or web-provider time for embed approval, branding, responsive layout, consent review, accessibility verification, schedule ownership, exception handling, and a native text link that remains useful during an outage.
Cowntdown costs $9 monthly or $97 annually. Twelve monthly payments total $108, so the annual commitment saves $11—not enough to justify prepaying before the widget has proved reliable in the church’s actual environment.
The seven-day no-card trial is valuable because the product’s core behavior can be observed quickly. Stage it before a service, watch the live window and reset, change a time, inspect mobile layout, and disable JavaScript. Ask support about timezone, daylight saving, caching, outages, cancellation, refunds after the trial, data export, and deletion.
The real alternative cost is staff attention. If a communications coordinator spends ten minutes each week correcting a manual timer, the subscription is easy to defend. If the church’s site already reads upcoming events from a calendar or its video platform supplies a live-aware player, Cowntdown may duplicate existing capability.
Annual cost should include the surrounding workflow. A reliable timer still needs accurate stream links, exception updates, visual review, accessibility, monitoring, and a fallback. It does not remove production labor, encoding fees, platform costs, music licensing, captioning, or online-host responsibilities.
Do not buy based on the “2x audience” claim. Measure your own baseline: clicks to the watch destination, arrival timing, error reports, and staff minutes spent maintaining the homepage. The purchase succeeds if visitors find the right service and the church eliminates a fragile task, even if total attendance does not double.
Where Cowntdown falls behind
Live awareness. The public description is schedule-driven and does not establish that Cowntdown verifies an encoder or platform is actually broadcasting.
Exception management. Public material should explain one-off cancellations, holiday overrides, timezone choice, daylight-saving transitions, overlapping windows, and emergency edits in detail.
Accessibility evidence. The site does not publish keyboard, screen-reader, contrast, reduced-motion, or WCAG information for the embedded widget.
Operational transparency. A public status page, uptime history, incident channel, support target, backup behavior, and service dependency list would reduce the risk of a homepage embed.
Privacy and security detail. The policy mentions cookies, statistics, Google advertising remarketing, affiliate links, and data transfers but does not provide the depth many organizations expect from a current SaaS vendor.
Legal maintenance. The terms contain generic provisions about child/family accounts, message boards, email, instant messaging, downloadable programs, and Cowntdown.io that do not fit the visible product and should be refreshed.
Evidence for growth claims. A definition of “join,” cohort, sample size, comparison period, and methodology is needed before the advertised average doubling can guide a decision.
Cowntdown vs. a custom timer vs. CP Live vs. a church-online platform
A custom JavaScript timer can be nearly free and fully controlled, but someone must correctly implement recurrence, timezone, daylight-saving behavior, exceptions, accessibility, and maintenance. Cowntdown converts that responsibility into a small subscription and a dashboard. It is the better choice when the church lacks a dependable developer; custom code can be better when the site team already maintains tested schedule components.
CP Live is a WordPress plugin that advertises automatic detection and embedding for YouTube and Resi, including a countdown to the next scheduled broadcast. It can be more integrated and live-aware for a WordPress church already buying Church Plugins. Cowntdown is much lighter, platform-agnostic, and appropriate when the video player already exists. Compare whether each product knows the actual broadcast state or merely the planned time.
Church Online Platform and paid church-streaming suites add chat, hosts, prayer, response tools, video destinations, analytics, and production workflows. They solve a far larger problem. Cowntdown belongs on a normal church website that needs only the front-door clock and link. Use the smallest system that meets the ministry need, and keep a native schedule and watch link regardless of which automation wins.
The bottom line
Cowntdown is a good example of narrowly useful church software. It does not promise to produce the stream or replace the website; it remembers recurring service times and keeps one countdown from becoming stale. The $9 monthly price is reasonable when that automation removes a real weekly failure point. Start with the no-card trial, stage the widget through a complete service cycle, test timezone and daylight-saving behavior, inspect assistive technology and mobile layout, and keep the schedule and watch link visible without it. Use truthful scheduled-language unless the timer actually verifies the broadcast. Stay monthly until the church has handled a holiday exception and confirmed cancellation, support, privacy, and fallback behavior; then the modest $11 annual saving is sensible.
Alternatives to Cowntdown
Church Online PlatformLife.Church’s free hosted online-service experience with chat, prayer, hosts, and response tools.YouTube scheduled livestreamA native watch destination and reminder workflow that may be enough without a separate homepage timer.ResiA full church streaming and delivery platform for organizations solving reliability and distribution, not just countdown display.Custom recurring timerLow recurring cost and full control when a capable developer owns timezone logic, accessibility, testing, and maintenance.Frequently asked questions
Why is Cowntdown spelled with a “w”?
Cowntdown is the product’s official stylized name. Its website and domain use countdown.church, but the brand shown in current product and legal copy is Cowntdown.
How much does Cowntdown cost?
The current pricing page lists $9 per month or $97 per year, with a seven-day trial that says no credit card is required. Twelve monthly payments cost $108.
Does Cowntdown host a church livestream?
No. It is a recurring timer and link for an existing livestream. The church still needs YouTube, Facebook, Vimeo, Resi, Subsplash, or another broadcast and viewing platform.
Can one Cowntdown widget handle several services?
Yes. The official site says one countdown can follow multiple service times, including times on multiple days, and automatically move to the next occurrence.
Will Cowntdown work on our church website?
It should work where the site allows the supplied two-line custom embed. The vendor names WordPress, ChurchCo, Subsplash, Nucleus, Churchly, Squarespace, and Wix, among others. Test on a staging page because some builders and security policies block scripts.
Does it know whether our stream is actually live?
The public materials describe a schedule and service-duration workflow, not a verified health check against the encoder or video platform. Ask the vendor directly and word the status as scheduled unless actual detection is demonstrated.
What fallback should a church provide?
Keep the next service day and time, timezone, and direct watch link in ordinary page content. The path should remain usable when JavaScript is disabled, the vendor is unavailable, or the timer displays the wrong state.
Sources & further reading
More Christian Streaming Apps
Good Feed MediaGood Feed Media streams complete discipleship series, Bible study tools and all six volumes of 33 The Series without a subscription—an unusually generous library whose optional books, mature themes and Subsplash data layers need clear group leadership.
Olive Christian RadioOlive Christian Radio offers a free stream of current worship, inspirational songs, timeless selections and short biblical encouragement with favorites and a sleep timer—but its app-store privacy label omits data the official policy describes.
ZipWave TVA free live-channel bundle mixing faith, international news and family programming without a required iOS account—more convenient than channel-hopping, but neither ad-free nor uniformly child-safe.
Every Man MinistriesEvery Man Ministries packages Kenny Luck’s evangelical men’s teaching, video studies, daily devotions, Bible plans, livestreams, prayer, and group discussion into a polished subscription app—but a narrowly gendered library, tiny store sample, identifier tracking, broad Vimeo-powered data collection, and a yearly plan that saves almost nothing deserve a clear-eyed trial.
BCC MediaA Norwegian nonprofit streams polished, ad-free Bible animation, children’s series, studies, sermons, shorts, and interactive lessons across mobile, TV, and web—but the library represents Brunstad Christian Church’s teaching, account history is retained broadly, and families still need to preview.
MyTRIBE.watchA homegrown, funny, chronological Bible-video subscription with printable family activities and real creative personality—promising for elementary-age engagement, but expensive and undermined by contradictory prices, age terms, and stale privacy documents.