1. In the Gcore Customer Portal, navigate to Streaming > Live Streaming.
2. Click Create Live stream.
If the button is non-responsive, you have exceeded your live stream limit. To create a new stream, remove an existing stream from the list or request technical support to increase your limits.
2. Enter the name of your live stream in the window that appears and click Create.
A new page will appear. Perform the remaining steps there.
1. Make sure that the Enable live stream toggle is on.
By default, we offer live streams with low latency (a 4–5 second delay.) Low latency is available in two protocols: LL-DASH (compatible with all devices except iOS) and LL-HLS (compatible with iOS). You can also obtain legacy HLS with MPEGTS format segments, in which case, please read our article.
2. (Optional) Review the live stream name and update it if needed.
3. Enable additional features If you activated them previously:
4. Select the relevant stream type: Push, Pull, or WebRTC => HLS.
Choose Push if you don't use your own media server. Establish the URL of our server and the unique stream key in your encoder (e.g. OBS, Streamlabs, vMix, or LiveU Solo). You can use protocols RTMP, RTMPS, and SRT too. The live stream will operate on our server, will be converted to MPEG-DASH and HLS protocols, and will be distributed to end users via our CDN.
Choose Pull if you have a streaming media server. The live stream will operate on your server. Our server will convert it from the RTMP, RTMPS, SRT, or other protocols to MPEG-DASH and HLS protocols. Then, our CDN will distribute the original live stream in the new format to end users.
Choose WebRTC => HLS if you want to convert your live video stream from WebRTC to HLS (HTTP Live Streaming) and DASH (Dynamic Adaptive Streaming over HTTP) formats.
1. Select the protocol for your stream: RTMP, RTMPS, or SRT. The main difference between these protocols is their security levels and ability to handle packet loss.
2. Copy the relevant data to insert into your encoder.
Insert the following values:
rtmp://vp-push-ed1.gvideo.co/in/
.Copy the Push URL SRT. It contains the server URL, port, stream ID (internal for Gcore,) and stream key. For example:
srt://vp-push-ed1-srt.gvideo.co:5001?streamid=000000#12ab345c678901d…
We provide backup links, which you can specify in the encoder interface. In case of inaccessibility and overloading of your primary server, the stream will be minimally interrupted and will continue automatically from the backup server.
In the URL field, insert a link to the stream from your media server. Check the full list of supported protocols in our Input parameters guide.
You can specify multiple media servers separated by space in the URL field.
In this case, the first media server will be the primary source, and the subsequent ones will serve as backup servers. If the signal from the first source fails, we will automatically continue the stream from the second source. For example: rtmps://main-server/live1 rtmp://backup-server/live1 rtmp://backup-server/live2
.
Insert the link from the WHIP URL field to any library or tool that supports WHIP (WebRTC-HTTP Ingestion Protocol). This will convert your stream into HLS format.
Start a live stream on your media server or encoder. You will see a streaming preview on the Gcore Live Stream Settings page if everything is configured correctly.
Embed the created live stream into your web app by one of the following methods:
That’s it. Your viewers can see the live stream.
We only support statistic data collection for Gcore players. If you use your own, non-Gcore player, the statistics page will be empty. Independent of the player, you can view monitoring metrics for performance analysis and troubleshooting.
Was this article helpful?
Explore the Streaming Platform by Gcore