Professional streaming FAQ

RTMP and SRT are contribution protocols: they carry your encoder feed to our origin. SRT recovers lost packets, which is why it performs better over public internet links. HLS is the delivery format that browsers, mobile devices and smart TVs play, included in every paid plan. WebRTC is a USD 20/month add-on for interactive playback, with latency of up to 0.3 s. DASH plays a role similar to HLS; XtreamCast delivers in HLS. For cable operators and headends, the channel can also deliver an SRT output.

It depends on the delivery format. Standard HLS: about 30 s, the margin our player keeps on purpose to absorb network drops. LL-HLS: around 3 s, as a USD 20/month add-on we enable per channel. WebRTC: up to 0.3 s, as a USD 20/month add-on. On the contribution side, SRT retransmits lost packets without cutting the feed. The encoder, the viewer's network and the player buffer add to those figures: measure camera-to-screen delay in your real workflow before the event.

The recommended ingest is H.264 video with AAC audio, the standard that browsers, mobile devices and smart TVs play. With the ABR Transcoder add-on, a 1080p source is delivered in 1080p, 720p, 480p and 240p with aligned keyframes, and each viewer gets the quality their connection supports.

The ABR Transcoder add-on (USD 20/month per channel) takes your feed, passes the original quality through without re-encoding and generates 720p, 480p and 240p with aligned keyframes. The player switches quality according to each viewer's connection without restarting playback.

With Live Station 24/7 (a USD 10/month add-on per channel) you load a playlist of H.264 MP4 files, up to 30 fps and 10 Mbps, and the channel plays it in a loop or in random order. With Auto Start, if your encoder disconnects, the playlist resumes on its own after 10 minutes. For your own live feed around the clock, size transfer with headroom or assess Enterprise+ with an expert.

Yes. SecureToken requires a valid token on every playback request (HLS, LL-HLS, WebRTC and SRT), geo-blocking limits access by country and domain restriction makes the player load only on your intranet or authorized site. If you need per-employee login, your intranet handles identity and the protected player is embedded there.

Yes. Copy the player iframe from the panel and embed it in Moodle, Canvas or any LMS that accepts embedded content; the platform administrator enables the embed. Your LMS controls classroom access, and with domain restriction the player only loads inside it.

Yes. Player v2 inserts VAST pre-roll, mid-roll and post-roll ads with Google IMA. For subscriptions or ticket sales, your payment platform handles access and embeds the player protected with SecureToken and domain restriction. We assess projects with DRM or their own paywall with an expert.

Yes. Restream sends your feed to up to 10 RTMP or RTMPS destinations at once, including custom servers. Connect each account, confirm the network has live streaming enabled for it and test every destination before the event.

Every paid plan delivers HLS from our origins in Chile and North America. Global CDN is a USD 20/month per-channel add-on that distributes your feed through our CDN providers, with presence in 77 countries; it is not included in Started+, Pro+ or Max+. Enable it when your audience is spread across regions.

Yes. With Recording Cloud and auto-upload enabled, every finished recording is published to the YouTube or Facebook accounts you connected. Keep those accounts' permissions current; each network processes the video before publishing it.

An encoder (OBS, vMix, Wirecast, LiveU Solo, FFmpeg, XSplit or Streamlabs) and the RTMP or SRT ingest URL and key from the panel. Enter them, check audio and video in the ingest diagnostics and test the player before announcing the broadcast. You can start with our free plan, no card required.

As an H.264 starting point: 2.5 to 4 Mbps for 720p30 and 4.5 to 6 Mbps for 1080p30, in CBR with a keyframe every 2 s. Keep upload headroom and run a sustained test before the event. On unstable links, SRT recovers lost packets better than RTMP.

XtreamCast ingest is RTMP (port 1935) or SRT, and both work on the same channel. RTMPS, which is RTMP over TLS, is what we use for restream to networks that require it, such as Facebook. If your link crosses the public internet with packet loss, use SRT: it recovers lost packets and publishing is validated with a token.

Copy the player iframe code from the panel and paste it into your website, WordPress or LMS. The player is HTML5 and carries your brand. With domain restriction, it only loads on the sites you authorize.

Paid video plans start at USD 25/month with Started+ (1 TB of transfer and 5 GB of storage); Pro+ and Max+ go up to 3 and 6 TB. All of them include RTMP and SRT ingest, HLS output, player, recording and restream to 10 destinations, with no automatic overage charges. Enterprise+ is quoted per project from 100 TB/month.

Checkout shows the payment methods available for your country, the currency and any applicable taxes before you pay. You can choose monthly or annual billing: annual equals 2 months free.

Yes, especially if your operation needs human 24/7 support in Spanish, SRT ingest, SRT output for cable operators and transfer with no automatic overage charges. We have operated streaming servers since 2011, and the site's comparisons contrast each provider feature by feature.

Human support 24/7/365 in Spanish via WhatsApp, email and portal tickets. 90% of tickets get a first response in under 30 minutes (historical average). We review your channel with the panel's ingest diagnostics, and Enterprise+ adds an account manager and priority support. The free video plan does not include committed response times.

Every paid plan, Enterprise+ included, has a 99.995% monthly contractual SLA, measured on ingest and delivery, with the exclusions in section XV of the Terms. In a 30-day month, 0.005% equals 2.16 minutes. Availability is measured externally every 60 s and published at status.xtreamcast.co. The SLA does not generate service credits, compensation or automatic refunds: remedies are governed by sections XIV and XVI of the Terms.

SecureToken requires a valid token on every playback request (HLS, LL-HLS, WebRTC and SRT), which cuts off hotlinking of your feed. Domain restriction stops other sites from embedding your player, and geo-blocking limits access by country with an allow list or a block list. Everything is configured from the panel, and panel access is protected with 2FA.

Each origin runs per-IP connection limits, tuned so they do not block audiences behind corporate NAT, and continuous monitoring that restarts any frozen session without manual intervention. SecureToken, geo-blocking and domain restriction reduce abuse of your feed. If your event has a high risk profile, we review the scenario with an expert before you go on air.

Your channels are hosted on our origins in Chile (Santiago) and North America; each channel runs on one of them. With Global CDN, delivery also goes through our CDN providers. Data processing is governed by our Privacy Policy; if your project requires contractual GDPR or LGPD terms, write to privacidad@xtreamcast.co and we will review them.