How CDNs Speed Up Global File Delivery

When you download a file from a server in San Francisco while sitting in Singapore, each piece of data has to travel approximately 14,000 km — a round trip that adds hundreds of milliseconds of latency on every request. A CDN (Content Delivery Network) solves this by caching copies of your file at edge locations distributed around the world.

How CDN Caching Works

1. You upload a file to the origin server
2. The first time a recipient in Tokyo requests the file, their request goes to the nearest CDN edge location in Tokyo
3. The edge cache doesn't have the file yet, so it fetches it from the origin server and stores a cached copy
4. The second Tokyo user requesting the file gets it directly from the local edge cache — fast
5. All subsequent Tokyo requests serve from cache until the cache TTL (time-to-live) expires

Cloudflare's Network

Cloudflare operates over 300 edge locations in 100+ countries, covering all major population centres. With Cloudflare as the CDN layer, a file you upload is automatically available within milliseconds from an edge node close to any recipient globally.

TiniDrop is built on Cloudflare R2 and Cloudflare Workers, meaning every file served through TiniDrop benefits from Cloudflare's global edge distribution by default — without any extra configuration on your part.

CDN vs Direct Server

Without a CDN, a file hosted on a single server in Frankfurt takes 200-300ms for each request from Australia. With Cloudflare's CDN, the same file is served from Sydney, cutting latency to under 5ms. For large files with many recipients, the difference in perceived speed is dramatic.

Cache Invalidation

The challenge: if you update a file, edge caches still serve the old version until the TTL expires. Strategies: use versioned filenames (file-v2.pdf), set short TTLs for files that change, or use the CDN's cache purge API to invalidate specific cached objects immediately after update.