A content delivery network (CDN) is a geographically distributed network of proxy servers, called edge servers, that keep cached copies of a website’s files at points of presence (PoPs) close to visitors. When someone opens a page, a nearby edge server answers instead of the distant origin server, so pages load faster, the origin carries less load and the site stays available under heavy traffic.
Key Takeaways
- A CDN does not replace web hosting: the origin server still holds the original content, and the CDN delivers cached copies from edge servers near users.
- CDNs arose in the late 1990s; Akamai Technologies, one of the first, was incorporated on August 20, 1998.
- As of October 2026, W3Techs reports Cloudflare on 26.3% of all websites, far ahead of Amazon CloudFront (1.7%), Fastly (0.9%) and Akamai (0.6%).
- What a CDN caches, and for how long, is controlled largely by the HTTP Cache-Control header (max-age, s-maxage, no-store, private).
- CDNs raise privacy and security questions: a German court ruled in 2021 that a university website’s CDN use violated the GDPR.
Content Delivery Network is a geographically distributed network of proxy servers that cache copies of static files and other web objects close to the people requesting them. Most internet users rely on CDNs every day, whether or not they know what a CDN is or how it works. People interact with CDNs while reading articles, shopping online, gaming online and using social media etc.
A large share of everyday online activity is delivered with the help of a CDN. Every web page request involves some delay (latency), and a major part of that delay comes from the distance between the visitor and the website’s server. The main job of a CDN is to keep that delay as short as possible.
What Is a Content Delivery Network (CDN)?
A CDN is a collection of distributed servers that delivers web content to users based on the user’s geographic location, the origin of the content and the location of the CDN’s servers. Using a CDN is a very popular way to improve user experience.
Let’s take an example here: Imagine searching for something on Google and opening the first two or three results. Some websites load fast, while others load more slowly. Most people prefer the website that loads fast, and this is where a CDN comes into the picture. A CDN helps webmasters optimize their websites for a better user experience and better search result ranking.
How Does a CDN Work?
The basic working of a CDN is simple to understand. With the purpose of a CDN clear, here is how one works:
A webmaster integrates a CDN into a website to improve the load time of the website. The CDN stores copies of the website’s static data in multiple geographic locations known as points of presence (PoPs). The CDN’s job is to store this cached data and deliver it.
When a user requests a particular resource from a web page, the CDN, instead of the host, delivers that resource to the user, taking the user’s geographic location into account. For example, when a user in India opens a website hosted in the United States, a CDN PoP in India can respond and provide the necessary resources.
A CDN serves each resource from the location best placed to reach the user, usually a nearby one, which reduces the website’s response time.
If the nearest node does not have the requested resource, another node in that cluster handles the request. Only when no node in the cluster can serve the request is the main (origin) server used to deliver the resource to the user.
Various CDN providers offer their services to webmasters. A webmaster signs up for a service and then integrates the CDN into the website. When a user requests a page, the CDN version of each resource URL is requested in the background, and a nearby node serves the request.
A CDN suits websites that want the following advantages:
- Decreased load on the origin server
- Faster delivery of requested content
- Higher availability of your website (a CDN improves availability but cannot promise 100% uptime)
- The capacity to handle more concurrent users on your website
- The ability to scale your website to a large audience
The working process of a CDN (Content Delivery Network) is easy to follow. The main purpose of a CDN is to give users a fast, reliable experience of a website. CDNs are now widely used by webmasters, and a business that wants to grow its online audience will usually need one. Readers who already use a CDN are welcome to share their experience in the comments. 🙂
For WordPress specifically, the CDN services that speed it up narrows the choice.
Key CDN Terms Explained
CDN documentation uses a small set of terms again and again. These definitions follow the standard vocabulary summarized in Wikipedia’s content delivery network article.
| Term | What it means |
|---|---|
| Origin server | The website’s own web server, which holds the source content. |
| Edge server | A CDN server that answers visitors’ requests from a location near them. |
| Point of presence (PoP) | A physical location where a CDN runs edge servers. Large CDNs operate many PoPs with thousands of servers. |
| CDN footprint | The geographic area the CDN’s edge servers can serve effectively. |
| Origin shield | A CDN service that helps protect the origin server during heavy traffic. |
| Pull caching | The edge server fills its cache when users request content. |
| Push caching | Content is preloaded to the CDN from the content server before anyone requests it. |
How Does a CDN Route Each Request?
A CDN routes each request to the edge server that is best placed to answer it. According to Wikipedia’s overview, “best” usually means the fewest network hops, the shortest response time or the best-performing server, although a CDN optimizing for cost may pick the cheapest location instead.
- DNS-based request routing: the CDN’s DNS answers a lookup with the address of a suitable edge server.
- Anycast: many servers in different locations share one IP address, and internet routers send each visitor’s packets to the nearest location, typically by the lowest number of BGP hops.
- Global server load balancing: traffic is spread across servers and sites so that no single server is overloaded and a failed server’s load is redistributed.
- HTML rewriting: resource URLs in the page are changed to point at the CDN.
How Do Cache-Control Headers Decide What a CDN Stores?
The HTTP Cache-Control header tells a CDN which responses it may store and for how long. MDN Web Docs defines the main directives as follows:
- max-age=N: the response stays fresh for N seconds after it was generated. For example, max-age=604800 means seven days.
- s-maxage=N: how long the response stays fresh in a shared cache such as a CDN; it overrides max-age for shared caches and is ignored by browsers’ private caches.
- no-store: no cache of any kind should store the response.
- private: only the visitor’s own browser cache may store the response, which MDN recommends for personalized content.
- immutable: the response will not change while it is fresh. MDN describes putting a version or hash in static file names, and changing the name instead of editing the file, as a modern best practice.
Who Are the Major CDN Providers?
Cloudflare is by far the most widely used CDN and reverse proxy service. The table below combines W3Techs usage data (survey dated 2 October 2026) with company facts from Wikipedia.
| Provider | Background | Share of all websites (W3Techs, Oct 2026) |
|---|---|---|
| Cloudflare | Founded in 2009, headquartered in San Francisco; acts as a reverse proxy between visitors and the host | 26.3% |
| Amazon CloudFront | Operated by Amazon Web Services since November 2008; more than 1,600 edge locations as of May 2025; pay-as-you-go | 1.7% |
| Fastly | Based in San Francisco; CDN, image optimization, load balancing and security services | 0.9% |
| Akamai Technologies | Incorporated on August 20, 1998, headquartered in Cambridge, Massachusetts | 0.6% |
| Bunny CDN | Smaller CDN provider listed in both Wikipedia’s provider list and the W3Techs survey | 0.1% |
W3Techs notes that 69.1% of websites use none of the reverse proxy services it monitors, and that a single website may use more than one.
How Much Does a CDN Cost?
CDN pricing ranges from free to custom contracts. As of October 2026, Cloudflare’s plans page lists a Free plan at $0 a month, Pro at $20 a month billed annually ($25 monthly), Business at $200 a month billed annually ($250 monthly) and custom-priced Contract plans, with the CDN included on every tier. Amazon CloudFront charges on a pay-as-you-go basis. Prices change often, so check each provider’s current pricing page.
How to Set Up a CDN for a Website
- Choose a provider whose PoP footprint covers the regions most of your visitors come from.
- Connect the site: either route the domain through the provider so it works as a reverse proxy in front of the host (the Cloudflare model), or point static file URLs at a CDN hostname.
- Set caching rules with Cache-Control headers: long max-age values for versioned static files, private or no-store for personalized pages.
- Version static files by adding a hash or version number to file names so updates reach visitors without waiting for cached copies to expire.
- Protect third-party scripts loaded from public CDNs with Subresource Integrity, which makes the browser check the script against a known hash.
- Test and measure page speed before and after the change, following the steps in our guide to improving website speed.
CDN Security and Privacy Considerations
A CDN can strengthen security, but it also adds a third party to every visit. Many CDN vendors also sell DDoS protection and web application firewalls (WAFs); Cloudflare, for example, lists unmetered DDoS protection on all of its plans, including Free. For the wider picture, see our guide on defending a network against DDoS attacks.
On privacy, a CDN receives the IP address of each visitor it serves. In 2021 a German court barred a university website from using a CDN because sending users’ IP addresses to it violated the EU’s General Data Protection Regulation (GDPR). CDNs that serve JavaScript have also been targeted to inject malicious code into websites, which is why the Subresource Integrity mechanism was created. Because CDN routing often depends on DNS, it also helps to understand the major DNS attack types.
Frequently Asked Questions
Is a CDN the same as web hosting?
No. Web hosting provides the origin server that stores a website’s original files, while a CDN keeps cached copies of those files on edge servers near visitors. A site still needs hosting when it uses a CDN. Our beginner’s guide explains what web hosting is.
Is there a free CDN?
Yes. As of October 2026, Cloudflare’s Free plan costs $0 a month and includes its CDN, DNS, universal SSL and DDoS protection. Cloudflare describes the Free plan as intended for personal or hobby projects that are not business-critical.
Does a CDN help SEO?
A CDN helps SEO indirectly by making pages load faster and stay available during traffic spikes, which improves user experience. It does not change a page’s content or relevance. Learn more about how page load time affects SEO.
What is a point of presence (PoP) in a CDN?
A point of presence (PoP) is a physical location where a CDN runs edge servers that answer requests from nearby users. Providers group PoPs into sets such as the United States, Asia-Pacific or Global, and the area they cover is called the CDN’s footprint.
When were CDNs invented?
CDNs arose in the late 1990s to relieve performance bottlenecks as the internet became a critical medium. Akamai Technologies, founded by Thomson Leighton and Daniel Lewin, was incorporated on August 20, 1998.
Can using a CDN break GDPR rules?
It can. Because a CDN receives each visitor’s IP address, a German court ruled in 2021 that a university website’s use of a CDN violated the GDPR. Sites serving EU visitors should review their CDN provider’s data processing terms with a qualified adviser.
1 Comment
In addition, by operating their own content delivery infrastructure, telco operators have a better control over the utilization of their resources.