Origin server
An origin server is the main server that holds the original copy of video files and manifests, from which a CDN fetches content when it does not already have a copy cached. Viewers rarely talk to the origin directly. Instead, edge servers request content from the origin once and then serve many viewers from their cache.
Why it matters
The origin is the single source of truth for a video library or live stream. If it slows down or fails, every CDN edge that needs new content is affected. Origin capacity, location and protection decide how well a service handles launches, live events and cache misses, and origin egress adds to delivery costs.
How it works
- Encoded segments and manifests are written to the origin, often cloud storage or a packager.
- When an edge server lacks a requested segment, it asks the origin for it.
- The origin returns the segment, and the edge caches it for later viewers.
- For live streams, the origin receives new segments every few seconds and updates manifests.
What is the difference between an origin server and an edge server?
The origin server holds the master copy of content, while edge servers hold cached copies close to viewers. Viewers usually talk only to edge servers. Edges contact the origin when they do not have a requested file. A healthy setup keeps most traffic at the edge, so the origin handles only a small share of requests.
Why does my origin server get overloaded?
Origin servers get overloaded when many edge servers ask for the same content at once, usually because it is new or not cached. Live events, new releases and short cache times are common triggers. Adding an origin shield, setting longer cache lifetimes for segments and pre-warming popular content all reduce the load.
Where it's used
OTT services keep one master library on the origin, which every CDN pulls from when an episode is first requested, and live sports streamers publish fresh segments there every few seconds.
