Skip to main content

Documentation Index

Fetch the complete documentation index at: https://gcore.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

​
Input requirements

Gcore Streaming accepts two types of video input:
  • Live streams: an ongoing stream sent to Gcore by PUSH or pulled by Gcore from your 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 adaptive bitrate streaming outputs and delivers them through CDN.

​
Live stream input

For Live, you must produce and send the master stream to Gcore with the correct parameters. Configure OBS, FFmpeg, a hardware encoder, or your own 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. Recommended parameters for the master Live stream:
ParameterRecommendation
Ingest protocolsRTMP, RTMPS, SRT, RTSP, HLS PULL, WebRTC
Video codecH.264 for the safest ingest path. Other codecs require validation for the selected protocol and workflow.
Audio codecAAC
Frame rateUp to 60 fps
Keyframe interval1-2 seconds
Bitrate modeCBR
Pixel aspect ratioSquare
Chroma subsampling4:2:0
Audio channels1 audio track
Audio-only inputNot supported for Live streams
Audio bitrate128 Kbps stereo
Audio sample rate44.1 or 48 kHz
SubtitlesNot supported for Live input
Recommended bitrate ranges for Live:
QualityResolutionVideo bitrate range
4K3840x216020,000-51,000 Kbps at 60 fps, 13,000-34,000 Kbps at 30 fps
1440p2560x14409,000-18,000 Kbps at 60 fps, 6,000-13,000 Kbps at 30 fps
1080p1920x10804,500-9,000 Kbps at 60 fps, 3,000-6,000 Kbps at 30 fps
720p1280x7202,250-6,000 Kbps at 60 fps, 1,500-4,000 Kbps at 30 fps
480p854x480500-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.
For Live ingest setup and backup workflows, see Ingest and backup.

​
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:
ParameterRecommendation
Max original file sizeUp to 30 GB
Video codecUse a supported input codec from the table below
Audio codecAAC is recommended
Frame rateUp to 60 fps
Pixel aspect ratioSquare
Chroma subsampling4:2:0 is recommended for broad compatibility
Audio tracksMultiple audio tracks are supported
Audio-only filesSupported
Audio bitrate128 Kbps stereo is recommended
Audio sample rate44.1 or 48 kHz
SubtitlesSRT 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
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. For example, a source that changes from yuv420p to yuvj420p near the end can be accepted initially but fail later during transcoding.
For VOD upload options, see Upload video via API.

​
Supported input video codecs

To ensure successful transcoding, your 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.
CodecSampling depthBPPFormatMax resolution
MPEG24:2:08Progressive, interlacedFHD
AVC4:2:08Progressive, interlaced4K
HEVC4:2:08, 10, 12Progressive8K
HEVC4:2:28, 10, 12Progressive8K
HEVC4:4:48, 10, 12Progressive5K
VP94:2:08, 10, 12Progressive8K
VP94:4:48, 10, 12Progressive5K
AV14:2:08, 10Progressive8K
RTMP has protocol limitations. For details, see RTMP.
If the recommended parameters do not fit your workflow, contact support@gcore.com or your manager. Gcore can review custom codecs, FPS values, ProRes, High 4:4:4, and other advanced requirements.

​
Live ingest protocols

You can use PUSH or PULL methods where applicable.
ProtocolMethodUsage
RTMP / RTMPSPUSH/PULLCommon live contribution protocol. RTMPS adds SSL encryption.
SRTPUSH/PULLSecure, reliable, low-latency contribution over unreliable networks.
WebRTC WHIPPUSHBrowser and app ingest for very low-latency workflows. Used as ingest only, then bridged to HLS or DASH delivery.
HLS PULLPULLGcore pulls an already prepared HLS stream from your publicly reachable encoder or origin.
RTSPPULLUsed to pull media streams from RTSP-compatible sources.
HLS over HTTP PUT is not supported.