Why HLS on WordPress scales — and what that means for you
Castio.live delivers video as HLS (HTTP Live Streaming). Unlike low-latency point-to-point technologies, HLS runs over plain HTTP and can be cached and served by ordinary web servers or CDNs. That means your live event can scale to thousands or more viewers so long as your hosting or CDN can deliver the required outbound bandwidth. There are no platform-imposed viewer caps — capacity is bounded only by your server, CDN, and bandwidth resources.
Pre-event checklist: technical and operational items
Before you promote a large live event, run through this checklist so viewers get a reliable experience and you keep moderation and access control under control.
- Confirm publishing browser support: Only Chrome/Edge on desktop and Chrome on Android can publish (go live) because the browser-side publisher requires MediaStreamTrackProcessor and a WebCodecs H.264 encoder. Any browser, including Firefox and Safari, can watch the stream. See the FAQ for details if you need to verify client compatibility.
- Estimate bandwidth needs: calculate outbound bandwidth and plan a CDN. We cover a simple calculation below.
- Use a CDN or object cache: HLS uses small media segments and playlist files that are well suited to CDN caching. Point your HLS origin to a CDN or configure your hosting to offload .m3u8 and segment requests to a CDN to avoid a single server bottleneck.
- Decide access controls: use password-protected streams for ticketed or private events — Castio.live issues a signed cookie granting access for 24 hours after a correct password is entered.
- Plan chat moderation: enable the built-in real-time chat sidebar and assign moderators. Admins and moderators can delete messages and ban users directly from the viewer list during the event.
- Record the event: enable recording so you can repurpose the stream as VOD after the event.
- Run rehearsals and load tests: schedule a dress rehearsal with a subset of real viewers and do a private load test via a CDN to validate playback and bandwidth.
Bandwidth planning: a practical example
Plan around an average bitrate per viewer. Real-world bitrates vary by resolution and encoder settings; here are conservative estimates you can adjust:
- 720p @ ~2.5 Mbps — good balance of quality and bandwidth
- 480p @ ~1.0–1.5 Mbps — acceptable for mobile viewers
- Audio-only or low-res — 128–256 kbps
Example: 10,000 concurrent viewers watching a 720p stream at 2.5 Mbps means 10,000 × 2.5 Mbps = 25,000 Mbps = 25 Gbps of outbound capacity. Delivering that quantity reliably requires a CDN or a hosting provider able to sustain that throughput. Without a CDN you’ll quickly hit bandwidth limits on cheap/shared hosting.
If you cannot provision or afford that outbound capacity, either reduce the published bitrate (lower resolution/frame rate) or require attendees to watch at lower-quality options.
Using a CDN with Castio.live
Because Castio.live outputs HLS over HTTP, it works with standard CDNs. Typical setup steps:
- Configure your web hosting or Castio origin URL as the CDN origin.
- Ensure the CDN caches .m3u8 playlists and media segments (common CDN defaults work, but verify TTLs for playlists).
- Allow the CDN to fetch new segments from the origin during the live event — CDNs usually support low-latency origins for HLS.
- Monitor CDN and origin metrics during your rehearsal to ensure cache hit rates are high and origin load is low.
If you’re unsure which CDN features you need, consult your CDN provider and run a short test stream through your chosen CDN before the big day.
Access control and ticketing strategies
Castio.live supports password-protected streams: viewers enter the password and receive a signed cookie that grants access for 24 hours. Use this for small paid events, member-only streams, or ticketed access. For heavier event monetization or advanced paywall options, check your plan details on the pricing page; integration with WordPress pages and content access controls is straightforward.
Moderation, chat, and safety during high-attendance events
Interactive chat can make or break a large event. Castio.live includes a built-in real-time chat sidebar and moderator tools. Best practices:
- Assign at least two moderators for every few thousand attendees so someone can react quickly to spam or abuse.
- Use pre-moderation for the earliest moments of the event if you expect heavy chat activity right at start time.
- Keep moderators familiar with the admin tools: deleting messages, banning users, and pausing chat when needed.
Rehearsal and monitoring checklist
- Run a full dress rehearsal with the final streaming machine and encoder settings. Publisher browsers must be Chrome/Edge (desktop) or Chrome on Android.
- Test with a CDN-backed stream and measure cache hit ratio and origin bandwidth.
- Verify chat, moderator controls, and password access workflow.
- Record a rehearsal and confirm the resulting VOD is stored and playable.
- Monitor latency during the rehearsal — Premium targets roughly 4 seconds and the free version targets roughly 10 seconds.
Quick operational tips for the event day
- Start 10–15 minutes early with an on-screen countdown to absorb late joiners and reduce chat flooding.
- Keep a small operations channel (separate chat, Slack, or phone tree) for moderators and technical staff.
- Have a second device logged in as a viewer to monitor playback and chat from the attendee perspective.
- If you anticipate very large audiences, plan to keep support documentation and a troubleshooting FAQ page handy for viewers (common items: browser recommendations, password entry, and refreshing a stuck player).
Where to try and learn more
If you want to test Castio.live before an event, try the Live Demo. Read the full feature list to confirm specific capabilities and moderation tools on the Features page. If questions remain about hosting, browser support, or recommended settings, consult the FAQ. When you’re ready to buy a plan with lower latency or advanced support, see Pricing.
Final thought
Large live events are entirely practical on WordPress when you plan for bandwidth, use a CDN, rehearse, and delegate moderation. Castio.live is designed to make that workflow straightforward: browser-based publishing, HLS delivery that scales via ordinary web hosting or CDN, built-in chat and moderation, passworded access, and recording for post-event playback.