Website Live Streaming for Churches, News Desks, and Events
Three complete setups for putting a live channel on your own website: a church watch-live page, a 24/7 news desk with cut-ins, and an event site with a domain-locked player.
The Same Player, Three Very Different Jobs
The embedded player is one feature, but what it's for depends entirely on who you are. Here are three complete setups we expect to be the most common, each combining the embed with the calendar, studio, and multistreaming pieces you may already run. All three assume a Business workspace ($119/mo billed annually), which includes website embedding.
Setup 1: the Church Watch-Live Page
The goal: members type your church's address, not YouTube's, and the service is just there on Sunday.
The page. A permanent
/watch-livepage with the embed at the top and the service schedule underneath. The iframe goes into your site once; everything else is operated from playout.video.The schedule. Program services on the Calendar with auto-start and auto-stop: the stream signs on ten minutes before the 11am service and off after the postlude, every week, unattended.
DVR rewind: on (1 hour). The family that arrives at 11:20 scrubs back to the processional. This single setting absorbs every "we missed the beginning" email.
Viewer count: your call. Big congregation, turn it on; small chapel, leave it off.
Keep multistreaming. The same service still goes to YouTube and Facebook for discovery; the embed serves the people who are already yours. And with multiple speakers, run the service through Live Studio.
Setup 2: the 24/7 News Desk
The goal: a live desk on your masthead, platform-independent, running around the clock.
The channel. A 24/7 programmed stream: fixed daily shows, looped bulletins between them, live cut-ins when news breaks. The full pattern is in How to Run a 24/7 News Desk With Live Cut-Ins.
The embed. Pinned player on the homepage. Adaptive quality matters most here: news audiences arrive on every device and network imaginable, and ABR keeps the phone-on-the-bus viewer watching instead of buffering.
DVR rewind: on (4 hours). "As we reported earlier this hour" becomes something viewers can actually check.
Viewer count: on. A visible audience is credibility for a news product.
Access mode: domain-restricted, listing your main and mobile domains, so aggregator sites can't rehost your desk player.
Setup 3: the Event and Conference Site
The goal: ticket-holders watch on the event page; the stream doesn't leak.
The embed. Player on the agenda page, domain-restricted to the event site. For paid-access events, go one further: signed mode puts playback behind your own login, with tokens minted by your server.
The programming. Each stage day is a calendar of sessions; between talks, a holding loop with sponsors and the schedule. Play Now covers the inevitable moment a session starts late.
Rotate at the end. When the event's over, rotate or disable the player link. Next year's event gets a fresh one; last year's embed codes floating around the internet play nothing.
After live: the recording lands in your library (Business includes recording), ready to be cut into session videos.
The Pattern Underneath
Notice what all three have in common: the website is where the committed audience watches, and the settings differ only in trust. Public and rewindable for the church, domain-locked for the newsroom, signed for the ticket-holders. One channel, one player, tuned by three switches.
If you're starting from zero, do it in this order: get the channel itself running, then the schedule, then the embed. Each piece works without the next, and the embed is the finishing move, not the foundation.