Ingest
Video ingest is the process of bringing video into a system, whether by uploading a file or receiving a live stream, so it can be stored, processed and delivered. For on-demand video it covers uploads and imports from URLs or storage buckets. For live video it means accepting a feed over protocols such as RTMP, SRT or WebRTC.
Why it matters
Ingest is the front door of every video system. If uploads fail or live feeds drop at this stage, nothing downstream can fix it. For live events, unstable ingest means a stream that freezes in front of paying viewers. For libraries, slow ingest delays launches and adds manual work.
How it works
- For on-demand video, a file is uploaded or imported from a URL or storage bucket.
- For live video, an encoder pushes a feed using a protocol such as RTMPS, SRT or WebRTC.
- The system checks the incoming file or feed, usually with a stream key or upload token.
- Accepted video moves on to storage, transcoding and packaging for playback.
RTMP vs SRT: which is better for live ingest?
SRT is usually better for live ingest over unreliable networks, while RTMP is the most widely supported option. SRT recovers lost packets and handles poor connections, such as cellular or long-distance links. RTMP works with almost every encoder and platform but has no built-in protection for packet loss. RTMPS adds encryption to RTMP.
What is an ingest server?
An ingest server is the entry point that receives live streams or uploaded files before they are processed. For live video, it is the address an encoder such as OBS sends its feed to, often paired with a stream key. It checks the connection and passes the video on for transcoding and delivery to viewers.
Where it's used
Live sports streamers and live event teams rely on ingest to bring camera feeds in reliably, while OTT services use it to take in large studio libraries. OTT services bringing a library over from another provider can use FastPix's migration tool, which reports each move through status webhooks.
Where it usually goes wrong, and how FastPix handles it
Plain RTMP ingest sends feeds unencrypted and copes poorly with packet loss, so live events on weak venue networks can stutter or drop.
FastPix ingests live streams over RTMPS and SRT from encoders such as OBS and vMix, with a stream key for each stream. On-demand video can be uploaded or imported through the On-Demand API. Paid live events get an encrypted path from the venue, and SRT copes with weak venue networks.
