Bring your feed to the server over a fixed or mobile connection. SRT requests lost packets again within the configured buffer. Match bitrate and latency to the link; a prolonged outage can interrupt the stream.
SRT streaming server
SRT streaming for
your live production
Send your encoder feed to XtreamCast and receive it at your studio or headend. SRT is included with video plans, with packet recovery for links that need more tolerance to changing network conditions.
4G mobile network packet loss
Your stream ARQ recovery
Illustration: recovery depends on the buffer, packet loss and available link capacity.
Included with your video plan
Ingest and contribution with no extra SRT fee
Illustrative bars, not measurements or latency guarantees.
Use your channel’s SRT credential. Encryption is confirmed for the server and link configuration.
The base plan and its monthly transfer allowance still apply.
Receive your live feed using the srt:// URL from the panel: VLC, FFmpeg or a compatible receiver connects in caller mode. Professional output and the HLS player for your website serve different purposes.
Tune the buffer for jitter and distance. SRT still needs sufficient connectivity and bandwidth.
Configure the source you will use for your channel. Test encoder changes before the event.
Use compatible encoders
OBS StudiovMixWirecastFFmpegLarix BroadcasterCompatible SRT encoders
Copy the URL and stream ID from your panel. OBS, vMix, Wirecast and FFmpeg require version-specific settings. Start with a 2-second keyframe interval and test the complete connection before going live.
Choose your protocol
SRT vs RTMP vs HLS: each has a role
In an XtreamCast workflow, SRT and RTMP carry the feed to the server and HLS delivers it to the browser . SRT also lets production equipment receive your channel. Each stage adds latency; measure the complete path.
Ingest · encoder → server
SRT
ARQ
RTMP
Variable
| Aspect | SRT | RTMP | HLS |
|---|---|---|---|
| Role in your workflow | Ingest and professional contribution | Ingest from your encoder | Delivery to viewers |
| Transport | UDP with packet recovery | TCP (persistent connection) | HTTP (downloadable segments) |
| When packets are lost | Retransmits within the available buffer | TCP retransmits; delay may increase | The player uses buffering |
| Link security | SRT credential; encryption depends on setup | RTMPS requires a compatible endpoint | Delivery over HTTPS |
| Mobile or unstable networks | Tune buffer and bitrate to the link | Sensitive to outages and jitter | Final delivery uses the player buffer |
| Compatibility | Compatible OBS, vMix, Wirecast and SRT receivers | Broad encoder support | Compatible HLS players and browsers |
RTMP remains an option for stable networks. XtreamCast lets you prepare both protocolsand test the switch before the event. Explore our RTMP server or the guide SRT vs RTMP in depth.
Use cases
SRT connects teams and locations
News and field production
Send reports over 4G/5G connections. Adjust buffer and bitrate to network conditions and validate a backup link where coverage varies.
Stadiums, exhibitions and events
Packet recovery can help on shared networks. Reserve bandwidth and test from the venue.
Links across cities and countries
Connect correspondents and studios over the internet. Choose the origin and buffer for the distance, network quality and audience.
Cable operators and headends
Deliver your channel over SRT to a compatible operator receiver. Confirm codecs and configuration before integration.
Prepare a backup link
You can configure another connection and a backup encoder. Switching requires coordination; this is not automatic failover.
Monitoring and quality checks
Open the origin feed in VLC or FFmpeg to check picture, sound and synchronization before distribution.
Get started
Connect your feed in 3 steps
- Create your account. Try TestDrive+ free for 3 days, without a credit card.
- Enable SRT on your channel. Copy the publishing URL and credentials from the panel. Your encoder connects to the server in caller mode.
- Configure and test your encoder. Check the HLS player and SRT reception with your equipment. Validate latency and stability before the event.
Yes. SRT ingest and professional playback are included with video plans. The base plan and monthly transfer allowance still apply. Copy your channel addresses from the panel.
Your encoder connects as a caller to the ingest server. To receive the output, your compatible receiver also connects as a caller to the playback URL. Copy the complete stream ID from the panel; ingest and playback addresses are different.
No. Packet recovery has a time window limited by the buffer. Lost connectivity, excessive packet loss or a bitrate above available upload capacity can interrupt the stream. Test the network and a backup link before the event.
We do not assume that it does. Publishing uses the channel’s SRT credential; authentication and encryption depend on the server and configuration. If you require transport encryption, confirm it with support before broadcasting and validate both endpoints.
SRT output is for professional software and receivers, such as VLC, FFmpeg or compatible equipment. On the web, use the HLS player or the WebRTC add-on if your configuration supports it.
Yes, over compatible internet connections. Distance, routing and access quality affect latency. Review the origin, transfer allowance and CDN delivery for your audience; identical latency in every country is not guaranteed.
Have more questions?
Our team is available 24/7 to help you with any question about your streaming project.
Your broadcast operation starts today
Ready to operate with broadcast quality?
Reach audiences worldwide with your TV channel, internet radio, live events or corporate broadcasts. 3-day free trial. Your audio or video channel ready in minutes. 24/7 human support.