If a website lives in California, visitors in India face a long trip. A CDN keeps copies closer to everyone.
One fridge in one town is handy for that town. Now imagine the same milk stocked in fridges in every city in the world. Wherever you are, there’s a fridge around the corner.
A CDN is that network of fridges. It keeps copies of a website’s files on computers all over the world, so each visitor gets them from somewhere nearby.
Why it helps
- faster: shorter distance means less latency
- sturdier: if one location has a problem, another takes over
- busy-proof: huge crowds are spread across many locations
- safer: many CDNs also block attacks before they reach the site
What gets copied
Mostly things that don’t change much: pictures, videos, styles and whole pages. Personal things, like your basket, still come from the website itself.
What it isn’t
It isn’t the website’s home. The original still lives with its hosting. The CDN just keeps copies close to visitors.
Where the comparison breaks down
Milk goes off on its own. CDN copies stay until the website says to refresh them, so updates sometimes take a moment to appear everywhere.
How the words fit together
A CDN is a giant cache around the world. It cuts latency. Your site still needs hosting.
Cloudflare, Akamai and Fastly are well-known CDNs. This website uses Cloudflare's, so it loads quickly wherever you are.

When you'll hear it
“It's served from a CDN.” Copies of the website are stored around the world, so it loads fast everywhere.
“Purge the CDN.” Throw away the stored copies so everyone gets the new version.
“The CDN had an outage.” The company storing the copies had a problem, so lots of websites went down at once.
“Does our site load quickly for customers in every country we sell to?”


