Why hosting matters — even with browser-based publishing
Castio.live lets you broadcast directly from the browser without an external RTMP server or third-party account. That makes setup fast and cheap, but the live stream still travels over your site’s HTTP infrastructure as HLS segments — so your hosting and how you serve files have a direct impact on viewer quality and reliability.
Quick checklist (what to check first)
- Confirm you can publish from Chrome/Edge on desktop or Chrome on Android (browser-based publishing requires WebCodecs H.264 support).
- Make sure your site uses HTTPS so viewers don’t get mixed-content blocks.
- Test playback on multiple devices and browsers — viewers can watch on Firefox and Safari even though they can’t publish.
- Try a short test event using the Live Demo to verify end-to-end behavior before a real broadcast.
Encoder and bitrate recommendations
Since Castio.live publishes from the browser using the client machine’s encoder, pick conservative bitrate/resolution settings that match your uploader’s network and CPU.
- 1080p (full HD): 3.5–6 Mbps — only if the broadcaster has a stable upstream connection and a modern CPU.
- 720p: 2.5–4 Mbps — a good balance for most creators.
- 480p: 1–1.5 Mbps — use this for viewers on mobile networks or weaker upload links.
- 360p: 600–900 kbps — fallback for very low bandwidth.
Keep the keyframe (I-frame) interval around 2 seconds if you can — it helps HLS segment alignment and reduces seeking/buffering. If you’re unsure, test with the Live Demo and watch how player seeks and how quickly it recovers from packet loss.
Use HLS and CDNs to scale and smooth playback
Castio.live delivers video via HLS, which runs over plain HTTP and scales well with ordinary web hosting or a CDN. If you expect more than a few dozen simultaneous viewers, put HLS segments and playlists behind a CDN or caching layer to offload bandwidth and reduce viewer buffering.
- CDN benefits: faster global delivery, reduced origin load, and fewer playback stalls for distant viewers.
- How to use a CDN: configure your CDN to cache the .m3u8 and .ts/.fmp4 segment files. HLS works with ordinary HTTP caching — no special streaming server required.
Remember: Castio.live imposes no artificial limits on viewers or bandwidth — capacity is bounded only by your hosting and CDN choices. For pricing details if you’re scaling up, check the Pricing page.
Server and hosting settings that matter
On shared hosting many settings are fixed, but you can still optimize:
- Disk space and retention: HLS segments and recordings consume disk. Keep an eye on free space and set sensible retention for temporary segments.
- HTTP/2 or HTTP/3: Enable modern HTTP if your host supports it — it improves parallel downloads and latency for many small HLS files.
- Cache headers: Configure your origin or CDN to cache HLS segments but not over-cache dynamic playlists. Short cache times for master/variant playlists and longer for segments is ideal.
- Range requests and gzip: Ensure the server supports byte-range requests for seeking and avoid gzip compression on binary segments (it’s unnecessary and can break streaming).
- Max concurrent connections: Some cheap hosts limit concurrent connections per IP — if you see connection errors during tests, ask your host for limits or add a CDN to distribute connections.
Lower latency vs stability: choosing the right plan and settings
Castio.live’s Premium plan targets roughly 4 seconds of latency, while the free version targets about 10 seconds. Lower latency is great for interactive streams, but it can require tighter encoder and network conditions to remain stable. If interaction and near-real-time chat are important, consider Premium — and always validate stability with a rehearsal.
Improve viewer experience with fallback and accessibility
- Multiple playback resolutions: If you can’t transcode server-side, pick a conservative single bitrate that works for your average viewer. For critical productions, use a CDN or external service that can transcode into multiple renditions, or publish at a lower baseline bitrate.
- Offer captions and VOD: Record your streams (Castio.live supports recording) and publish VOD with captions for viewers who missed the live event.
- Chat and moderation: Built-in real-time chat lets you keep viewers engaged during buffering; moderators can delete messages and ban users when needed.
- Password protect or gated access: If you run paid or private events, use password-protected streams (viewers enter a password and receive a signed cookie for 24-hour access) or the PayPal paywall via the plugin’s features.
Troubleshooting common problems
- Frequent rebuffering: Lower your broadcaster bitrate, check upload stability, and move HLS delivery to a CDN.
- Playback stalls for remote viewers: Verify CDN caching, enable HTTP/2/HTTP/3, and ensure origin bandwidth isn’t saturated.
- Publishing fails in a browser: Confirm you’re on a supported browser (Chrome/Edge desktop, Chrome on Android) because publishing requires WebCodecs H.264.
- High CPU on host: Large numbers of file requests can spike Apache/nginx processes on cheap hosts. Offload with a CDN or use a caching reverse proxy.
Where to learn more and test
Get a full rundown of what the plugin can do on the Features page, and try an end-to-end broadcast in the Live Demo. If you have specific hosting or playback questions, check the FAQ for technical details and troubleshooting tips.
Final tip
Start with conservative encoder settings, use a CDN for anything beyond a small local audience, and rehearse on the same hosting plan you’ll use live. With HLS delivery and Castio.live’s browser-based publishing, you can get reliable, scalable streams from ordinary WordPress hosting — you just need to tune the bitrate, caching, and delivery to match your audience.