What Is a CDN and How Does It Work?
A Beginner-Friendly Guide

What is a CDN?

A CDN, or Content Delivery Network, is a group of servers spread across many cities and countries that store copies of your website's files and hand them to visitors from the closest location.

A shipping analogy helps. Imagine an online store that ships everything from a single warehouse in one city. Customers nearby get their parcels quickly, and customers on the other side of the world wait days. Now imagine the store stocks its best sellers in regional warehouses. Most orders now ship from a warehouse a few hours away, and the main warehouse only handles rare items. A CDN does this for web content.

Why websites need one

Every website has an origin server, the machine where your files and application actually live. When a visitor loads your page, their browser doesn't make just one request. It usually makes dozens: the HTML, stylesheets, scripts, fonts, logos, and images.

Two things go wrong when all of that comes from one place:

1. Distance adds delay. Data travels fast, but every request still crosses many network hops, and each round trip costs time. A visitor 10,000 km from your server waits noticeably longer than one 100 km away.
2. One server takes all the load. If a thousand people request the same product image, your origin serves it a thousand times. Once traffic climbs high enough, pages slow down or the server stops responding.

A CDN answers both problems. It shortens the distance, and it keeps most repeat requests away from your origin.

The main building blocks

• Origin server: your real server, where the original files live.
• Edge servers: the CDN's servers that sit close to users, keep cached copies, and answer requests directly.
• Points of Presence (PoPs): the physical locations, usually data centers, where edge servers are housed. Large CDNs have hundreds of them.
• Routing system: the technology that decides which edge server a visitor should talk to. This is done through DNS or anycast, where the same IP address is announced from many locations and the network delivers each request to the nearest one.
• Cache: the storage on each edge server that holds copies of your files.

What happens when someone visits your site

Here's the journey of a single file, such as a product photo:

1. The visitor's browser looks up your domain. Since you've connected your site to the CDN, the lookup leads to a nearby edge server instead of your origin.
2. The edge server checks whether it already has that photo in its cache.
3. If it does (a cache hit), it sends the photo right away. Your origin isn't involved at all.
4. If it doesn't (a cache miss), the edge server requests the photo from your origin, passes it to the visitor, and keeps a copy.
5. The next visitor in that region gets the stored copy, so only the very first request pays the long trip.

The share of requests answered from cache is called the cache hit ratio. It's the number to watch when you want to know whether your CDN is doing its job. A high ratio means your origin is mostly resting.

How caching is controlled

The CDN doesn't guess how long to keep a file. You tell it, mainly through the Cache-Control header your server sends with each response:

Cache-Control: public, max-age=86400

That line says the file may be reused for 86,400 seconds (one day). This period is the TTL, or time to live. Once it expires, the edge server checks with your origin for a fresh version.

Some practical habits will save you headaches:

• Cache long-lived files for a long time. Fonts, logos, and versioned scripts can safely have a TTL of months.
• Version your filenames. If you name a file app.4f2a9c.js and change the name whenever the content changes, you never have to worry about stale copies.
• Purge when you must. Every serious CDN lets you clear a file, a folder, or everything from its caches on demand.
• Keep private pages out. Anything personal, such as an account page or a cart, should be marked private or no-store so it isn't shared between visitors.

Static and dynamic content

Static content is the same for everyone: images, videos, CSS, JavaScript, fonts, and downloadable files. It's the perfect fit for caching.

Dynamic content changes per request or per user, like search results, a logged-in dashboard, or live prices. A CDN can't simply store and replay these, but it still helps in other ways. It can keep a fast, already-open connection to your origin, handle the secure handshake near the visitor, and compress data on the way. Many modern CDNs also let you run small pieces of code at the edge to tweak responses, redirect users, or personalise content without going back to your server.

Pull CDN vs push CDN

Most sites use pull, because the cache fills itself and you don't need to change how you publish content.

More than caching: what else a CDN does

Modern CDNs have grown well beyond storing files. Depending on the provider and plan, you can get:

• HTTPS and TLS handling, including free certificates.
• DDoS protection, which absorbs floods of malicious traffic across a large network.
• A web application firewall (WAF) that blocks common attacks such as SQL injection.
• Bot management to filter scrapers and abusive crawlers.
• Image optimisation, resizing and converting images to formats like WebP or AVIF on the fly.
• Compression with Gzip or Brotli, and support for newer protocols like HTTP/2 and HTTP/3.
• Analytics that show traffic, cache performance, and errors by region.

Where CDNs are used in the real world

• Streaming video: Netflix built its own CDN, called Open Connect, and places servers inside internet providers' networks so popular shows travel a much shorter path.
• Online shopping: product images and scripts load fast, and sale-day rushes don't flatten the site.
• News and blogs: when an article suddenly goes viral, the CDN takes the surge instead of the origin.
• Software and games: large downloads and patches are served from nearby servers, so they finish faster.
• APIs and mobile apps: even API responses can be cached for a few seconds to cut load.

Well-known providers include Cloudflare, Amazon CloudFront, Akamai, Fastly, Google Cloud CDN, and Azure CDN.

CDN vs load balancer vs web hosting

These three often get mixed up, but they do different jobs.

They work well together. A typical large site has a CDN in front, a load balancer behind it, and several application servers behind that. A CDN doesn't replace hosting, because something still has to produce the original content.

Common mistakes to avoid

• Caching pages that shouldn't be shared. Serving one user's account page to another is the worst-case outcome. Set your cache headers carefully for anything personal.
• Forgetting about cookies. Many CDNs treat requests with certain cookies differently, or skip caching them, which can quietly drop your hit ratio.
• Leaving the origin exposed. If your real server accepts traffic from anywhere, attackers who learn its IP can bypass the CDN. Restrict it to the CDN's addresses.
• Setting TTLs too short. A one-minute TTL on a file that changes yearly sends needless traffic to your origin.
• Never checking whether it works. Look at the response headers (for example cf-cache-status on Cloudflare or x-cache on CloudFront) to confirm files are actually coming from cache.

How to set up a CDN, in short

1. Pick a provider that has good coverage where your visitors live, and check pricing for your expected traffic.
2. Connect your domain, either by changing your DNS records or by pointing a subdomain like cdn.yoursite.com at the CDN.
3. Turn on HTTPS.
4. Set caching rules, and make sure your origin sends sensible Cache-Control headers.
5. Test with a few pages and inspect the response headers.
6. Watch the analytics for a week or two, then tune your TTLs and rules.

Do you actually need a CDN?

Probably yes if your visitors come from several regions, your pages are heavy with images or video, you expect traffic spikes, or you want extra protection against attacks. Free plans mean even a small blog can benefit.

The gain is smaller if your audience lives in one city right next to your server and your site is tiny. Even then, the security and HTTPS features can be worth having.

Summary

A CDN puts your content near your visitors, shields your server from traffic it doesn't need to handle, and adds a layer of security along the way. Setup is usually an afternoon's work, and the effect on speed and stability is often visible straight away. If your site serves people in more than one part of the world, it's one of the highest-return improvements you can make.