How a CDN works
When a viewer requests a video, the CDN routes the request to the nearest edge server rather than the origin server. If the content is cached locally, it is delivered instantly. If not, the edge server fetches it from the origin, caches it, and serves it — all within milliseconds. This process is transparent to the viewer.
- Content is replicated to edge servers in multiple geographic locations (PoPs)
- DNS-based routing directs each viewer to the closest available server
- Cached content is served directly from the edge, avoiding round-trips to the origin
- Cache invalidation ensures viewers always receive the latest version
Why video delivery needs a CDN
Video files are large and bandwidth-intensive. A single HD video stream consumes 5-8 Mbps, and 4K requires 15-25 Mbps. Without a CDN, an origin server serving hundreds of concurrent viewers would quickly become a bottleneck. CDNs solve this by distributing the load across thousands of servers worldwide.
| Metric | Without CDN | With CDN |
|---|
| Latency | 200-500ms | 10-50ms |
| Buffering rate | 5-15% | <1% |
| Origin server load | 100% | 5-10% |
| Global reach | Single region | Worldwide |
European CDN and GDPR compliance
For organizations handling personal data or operating in Europe, the location of CDN servers matters. Using a European CDN ensures that viewer data (IP addresses, access logs) stays within the EU, simplifying GDPR compliance. This is particularly important for corporate training, healthcare, and education use cases.
How Videas uses CDN technology
Videas stores and transcodes your videos on its own infrastructure, in France, then delivers them over a CDN that caches the segments as close to viewers as possible. The stream URLs handed to the player are signed and expire quickly: an address copied elsewhere stops working within minutes. The player itself sets no advertising cookie and no third-party tracker.
Frequently asked questions
What does CDN stand for?+
CDN stands for Content Delivery Network. It is a distributed system of servers designed to deliver content to users from the closest geographic location.
Why does video streaming need a CDN?+
Video files are large and bandwidth-hungry. A CDN caches video segments on edge servers close to viewers, which cuts latency and buffering wherever they are.
What is an edge node?+
A server on the network, placed near viewers, that keeps already-requested segments in cache. The second viewer in the same region gets the video from that cache, without going back to the origin server.
Are a CDN and hosting the same thing?+
No. Hosting is where the file lives; the CDN is how it reaches the viewer. Videas does both: your file is stored and transcoded on its infrastructure, then delivered over the CDN.
Where are the videos Videas delivers hosted?+
Storage and transcoding are handled by Videas on its own infrastructure, in France. The site's Security and sub-processors page lists the few providers involved beyond that, and what they do.
Do I need to configure anything to get the CDN?+
No. CDN delivery is the default for every uploaded video: nothing to switch on, no third-party account to open, no key to enter.
Does a CDN speed up playback start?+
That is its first effect: the player fetches the manifest and the first segments from a nearby server, so the video starts sooner. The second effect is scale — an audience spike is absorbed by the cache, not by the origin server.
Does a CDN protect my videos?+
It distributes them, it does not protect them. On Videas the protection comes from elsewhere: stream URLs are signed and expire fast, and domain restriction stops your embed code from running on a site you have not authorised.
Is delivery billed?+
EUR 0.02 per gigabyte actually delivered, with the first terabyte free each month. What counts is the data watched: pasting the same video on ten pages changes nothing on the bill.
Does the player set cookies?+
No advertising cookie and no third-party tracker, whether the player is embedded on your site or shown on a channel.