---
title: "CDN (Content Delivery Network) for Video | Kinescope"
description: "A CDN is a global network of edge servers that caches video close to viewers — cutting latency and buffering and absorbing traffic spikes at scale."
url: https://kinescope.com/glossary/cdn
---

# *CDN* (Content Delivery Network)

The global network of edge servers that puts your video close to every viewer — so it starts fast, plays smoothly, and holds up under a traffic spike.

**Updated:** May 2026 **5 min read** **Delivery**

In short

A CDN is a worldwide mesh of edge servers that keeps copies of your video near viewers, so playback starts fast, stalls less, and survives a traffic spike instead of hammering one distant origin.

## What is a CDN (Content Delivery Network)?

A CDN (Content Delivery Network) is a geographically distributed network of servers that caches copies of your content — video segments, images, files — close to where viewers are. When someone presses play, the video is served from a nearby edge server instead of a single origin that might be thousands of kilometres away.

For video this is not a nice-to-have. Streaming means delivering many short [segments](https://kinescope.com/glossary/hls) HLS (HTTP Live Streaming)Apple’s adaptive streaming protocol. Uses .m3u8 manifests and segmented delivery; supported on every browser, device and smart TV.[Open definition →](https://kinescope.com/glossary/hls) in quick succession; the closer the server, the lower the [latency](https://kinescope.com/glossary/latency) LatencyThe delay between a moment happening and a viewer seeing it. Critical for live — Low-Latency HLS brings it down to 2–5 seconds.[Open definition →](https://kinescope.com/glossary/latency) and the less chance of [buffering](https://kinescope.com/glossary/buffering) BufferingWhen playback pauses to load more data. ABR exists largely to prevent it by stepping quality down before the buffer empties.[Open definition →](https://kinescope.com/glossary/buffering) . A CDN also absorbs demand: a video that suddenly gets thousands of concurrent viewers is served from hundreds of edges, not from one overloaded machine.

## How a CDN works

**Origin holds the master**

Your [transcoded](https://kinescope.com/glossary/transcoding) TranscodingRe-encoding a source video into multiple resolutions and bitrates so a player can switch between quality levels on the fly.[Open definition →](https://kinescope.com/glossary/transcoding) renditions and [manifests](https://kinescope.com/glossary/manifest) ManifestA small index file (.m3u8 or .mpd) that lists every available rendition and segment so the player knows what it can request.[Open definition →](https://kinescope.com/glossary/manifest) live on the origin (the hosting layer) — the authoritative copy.

**Edges cache on demand**

The first viewer in a region triggers the edge to fetch and cache the needed segments. Everyone after them is served from that cache — fast, and without touching the origin.

**Routing to the nearest edge**

Viewers are directed to the closest healthy edge automatically, so a viewer in São Paulo and one in Berlin each stream from a server near them.

**Scaling with demand**

Spikes are spread across the whole edge network, so concurrency scales with the CDN rather than being capped by a single server.

The key efficiency metric here is the **cache hit ratio** — the share of requests served from the edge rather than fetched from origin. The higher it is, the faster viewers get their video and the less load (and cost) lands on the origin. Popular content warms the cache and keeps that ratio high, and a shield tier between the edges and the origin raises it further — see [origin shield and tiered caching](https://kinescope.com/glossary/origin-shield) Origin shield (tiered caching)A cache tier between CDN edges and the origin that collapses duplicate requests, so a traffic spike reaches your server once, not thousands of times.[Open definition →](https://kinescope.com/glossary/origin-shield) .

## CDN vs. hosting

| Aspect | Hosting (origin) | CDN (edge) |
| --- | --- | --- |
| Role | Stores the master copy | Distributes copies near viewers |
| Optimised for | Storage, management, processing | Speed and scale of delivery |
| Without it | Nowhere to keep the video | Slow starts, buffering, spikes overwhelm the origin |
| On Kinescope | Both, in one platform — [hosting](https://kinescope.com/products/video-hosting) + owned CDN |

## Owned vs rented CDN

Not all "our CDN" claims mean the same thing. Most video platforms rent capacity from a third party (Cloudflare, Fastly, Akamai) and resell it; a few build and run their own network. The difference shows up in price and in who fixes problems — and since delivery is billed per gigabyte, price per GB is most of a video bill (see [egress fees](https://kinescope.com/glossary/egress-fees) Egress feesWhat a provider charges per GB of data leaving its network. For video it grows with watch time, so bitrate, caching and per-GB price set the bill.[Open definition →](https://kinescope.com/glossary/egress-fees) ).

| Aspect | Rented (third-party) | Owned |
| --- | --- | --- |
| Pricing | Often a reseller markup | No middleman margin |
| Escalations | Cross a vendor boundary | One team owns the whole chain |
| SLA | Depends on the vendor's | Set and honoured directly |

Kinescope runs its own network — points of presence across Latin America, the US, Europe and the CIS — with a 99.98% uptime SLA.

How Kinescope handles this

### Kinescope runs its own global video CDN

Kinescope runs its [own global video CDN](https://kinescope.com/products/content-delivery-network) — infrastructure it builds and operates rather than reselling AWS or Cloudflare. One product team owns the whole chain — upload, transcode, delivery, playback — behind a 99.98% uptime SLA. That means predictable pricing with no reseller markup, and escalations that never cross a vendor line.

[See the global CDN](https://kinescope.com/products/content-delivery-network)

## Further reading

-   [Content delivery network — Wikipedia](https://en.wikipedia.org/wiki/Content_delivery_network) — a vendor-neutral overview.

[![Denis Konnov](https://kinescope.com/blog-assets/authors/denis-konnov.jpeg)](https://kinescope.com/authors/denis-konnov)

Written by

[Denis Konnov](https://kinescope.com/authors/denis-konnov) Verified

CMO at Kinescope

Denis leads marketing and content at Kinescope, working closely with the platform's engineers. This glossary is reviewed and kept up to date by the team building Kinescope's streaming, encoding and CDN delivery infrastructure.

## FAQ

Can’t find the answer you need? Check out our [Help Center](https://docs.kinescope.com/).

A CDN caches your video segments on edge servers spread around the world, so each viewer streams from a location physically close to them. That cuts startup time and buffering, and absorbs traffic spikes that would overwhelm a single origin server — the difference between smooth playback and constant stalls at scale.

Hosting stores the master copy of your video (the origin). A CDN distributes copies to edge servers near viewers for fast delivery. You need both: hosting to keep and manage the files, and a CDN to serve them quickly worldwide. Kinescope provides both in one platform.

Indirectly, yes. A CDN does not change the video itself, but by delivering segments faster and more reliably it lets the adaptive player sustain higher quality with less buffering. Lower latency to the edge means the player can request higher renditions with confidence.

Many platforms rent CDN capacity from Cloudflare, Fastly or Akamai, which works but adds a vendor layer and, often, a reseller markup. Kinescope runs its own CDN across Latin America, the US, Europe and the CIS, so one team owns the whole chain from upload to playback — no middleman on price or on escalations.

## Delivery you don't have to think about.

Kinescope streams your video from its own global CDN — no third-party middleman, 99.98% SLA.

[Start free](https://app.kinescope.io/user/create?lang=en)[Read the docs](https://docs.kinescope.com/)
