Accepted input parameters for live streams and videos

Gcore Streaming accepts two types of video input and applies specific requirements to each.

Live streams: an ongoing stream sent to Gcore by PUSH or pulled by Gcore from the source. Live input must stay stable because transcoding happens in real time.
VOD files: uploaded video files that Gcore processes after upload. VOD input can use many containers and codecs, but the source parameters should stay consistent through the file to avoid transcoding errors.

After ingest or upload, Gcore transcodes the source into ABR outputs and delivers them through CDN.

Live stream input

Live input requires a master stream sent to Gcore with the correct parameters. Configure OBS, FFmpeg, a hardware encoder, or a custom encoding pipeline to push or expose the stream with the parameters below. Gcore receives this master stream and transcodes it for HLS and MPEG-DASH delivery.

The Society of Cable Telecommunications Engineers 35 (SCTE-35) standard uses markers to signal ad insertion opportunities in a live stream. CDN delivery preserves these markers in an existing HLS stream, while SRT ingest requires transcoding to HLS and does not preserve them. A single workflow cannot currently combine SRT-to-HLS transcoding with SCTE-35 marker preservation.

Recommended parameters for the master Live stream:

Parameter	Recommendation
Ingest protocols	RTMP, RTMPS, SRT, RTSP, HLS PULL, WebRTC
Video codec	H.264 for the safest ingest path. Other codecs require validation for the selected protocol and workflow.
Audio codec	AAC
Frame rate	Up to 60 fps
Keyframe interval	1-2 seconds
Bitrate mode	CBR
Pixel aspect ratio	Square
Chroma subsampling	4:2:0
Audio channels	1 audio track
Audio-only input	Not supported for Live streams
Audio bitrate	128 Kbps stereo
Audio sample rate	44.1 or 48 kHz
Subtitles	Not supported for Live input

Recommended bitrate ranges for Live:

Quality	Resolution	Video bitrate range
4K	3840x2160	20,000-51,000 Kbps at 60 fps, 13,000-34,000 Kbps at 30 fps
1440p	2560x1440	9,000-18,000 Kbps at 60 fps, 6,000-13,000 Kbps at 30 fps
1080p	1920x1080	4,500-9,000 Kbps at 60 fps, 3,000-6,000 Kbps at 30 fps
720p	1280x720	2,250-6,000 Kbps at 60 fps, 1,500-4,000 Kbps at 30 fps
480p	854x480	500-2,000 Kbps

Live stream parameters must remain stable during the broadcast. Mid-stream changes to codec, profile, resolution, frame rate, pixel format, color range, chroma format, or audio layout can interrupt ingest or transcoding.

Primary and backup ingest is configured separately.

Ingest and backup covers live ingest setup and backup workflows.

VOD source files

For VOD, the customer manages the source file before upload: container, codec, audio tracks, subtitles, and source consistency. Gcore processes the uploaded source and creates ABR renditions for playback. Recommended VOD input:

Parameter	Recommendation
Max original file size	Up to 30 GB
Video codec	Use a supported input codec from the table below
Audio codec	AAC is recommended
Frame rate	Up to 60 fps
Pixel aspect ratio	Square
Chroma subsampling	4:2:0 is recommended for broad compatibility
Audio tracks	Multiple audio tracks are supported
Audio-only files	Supported
Audio bitrate	128 Kbps stereo is recommended
Audio sample rate	44.1 or 48 kHz
Subtitles	SRT and WebVTT are supported

Supported VOD containers:

3g2, 3gp, asf, avi, dif, dv, flv, f4v, m4v, mov, mp4, mpeg, mpg,
mts, m2t, m2ts, qt, wmv, vob, mkv, ogv, webm, ogg, mxf,
quicktime, x-ms-wmv, mpeg-tts, vnd.dlna.mpeg-tts

The last four entries (quicktime, x-ms-wmv, mpeg-tts, vnd.dlna.mpeg-tts) are MIME type subtype identifiers rather than file extensions. The corresponding file extensions are .mov (QuickTime), .wmv (Windows Media), and .ts or .mts (MPEG-TS variants). For VOD and live-derived recordings, it is not enough that the source starts with supported parameters. These parameters must stay stable for the full duration — a source that changes from yuv420p to yuvj420p near the end can be accepted initially but fail later during transcoding.

Upload via API covers VOD upload options.

Supported input video codecs

The source video must use one of the supported input codecs listed below. If a video is uploaded or streamed with an unsupported codec, transcoding can fail. These input codecs are validated during the initial processing stage before any adaptive bitrate renditions are created.

Codec	Sampling depth	BPP	Format	Max resolution
MPEG2	4:2:0	8	Progressive, interlaced	FHD
AVC	4:2:0	8	Progressive, interlaced	4K
HEVC	4:2:0	8, 10, 12	Progressive	8K
HEVC	4:2:2	8, 10, 12	Progressive	8K
HEVC	4:4:4	8, 10, 12	Progressive	5K
VP9	4:2:0	8, 10, 12	Progressive	8K
VP9	4:4:4	8, 10, 12	Progressive	5K
AV1	4:2:0	8, 10	Progressive	8K

RTMP has protocol limitations described in RTMP.

If the recommended parameters do not fit the workflow, contact support@gcore.com or the account manager. Gcore can review custom codecs, FPS values, ProRes, High 4:4:4, and other advanced requirements.

Live ingest protocols

Both PUSH and PULL methods are available where applicable.

Protocol	Method	Usage
RTMP / RTMPS	PUSH/PULL	Common live contribution protocol. RTMPS adds SSL encryption.
SRT	PUSH/PULL	Secure, reliable, low-latency contribution over unreliable networks.
WebRTC (beta)	PUSH	Browser ingest for low-latency workflows. Bridges to HLS or MPEG-DASH delivery.
HLS PULL	PULL	Gcore pulls an already prepared HLS stream from a publicly reachable encoder or origin.
RTSP	PULL	Pulls a media stream from an RTSP-compatible source — webcams and IP cameras.

HLS over HTTP PUT is not supported.

Account settings

Developer Tools

CDN

FastEdge

Edge Cloud

AI

Gclaw

Managed DNS

Public DNS

Hosting

Colocation

Object Storage

Video Streaming

DDoS protection

Edge Proxy

WAAP

Accepted input parameters for live streams and videos

Live stream input

VOD source files

Supported input video codecs

Live ingest protocols

​Live stream input

​VOD source files

​Supported input video codecs

​Live ingest protocols

Live stream input

VOD source files

Supported input video codecs

Live ingest protocols