---
title: How Vercel CDN Works
product: vercel
url: /docs/how-vercel-cdn-works
canonical_url: "https://vercel.com/docs/how-vercel-cdn-works"
last_updated: 2026-03-05
type: conceptual
prerequisites:
  []
related:
  - /docs/regions
  - /docs/how-vercel-cdn-works/compression
  - /docs/cdn-security
  - /docs/vercel-firewall/vercel-waf
  - /docs/bot-management
summary: "Learn how Vercel's CDN processes requests through routing, caching, and compute layers to deliver your content with low latency."
install_vercel_plugin: npx plugins add vercel/vercel-plugin
search_with_vercel_cli: npx vercel@latest docs search "<query>"
---

# How Vercel CDN Works

Every request to a Vercel deployment flows through a globally distributed CDN before it reaches your application code. The CDN handles routing, caching, security, and compression automatically, so your app is fast by default.


<!-- docsgraph:related -->
## Related pages

> **For AI agents:** Follow these links to understand how this page connects to the rest of the Vercel ecosystem. For the full cross-link map (inbound, outbound, prerequisites, and semantic neighbors), see the .graph.md link below.

- [How to choose a Salesforce Commerce Cloud storefront: PWA Kit, Storefront Next, or Next.js](https://vercel.com/kb/guide/salesforce-pwa-kit-vs-storefront-next-vs-nextjs) — Compare PWA Kit, Storefront Next, and a Next.js storefront on Vercel for Salesforce Commerce Cloud. Learn how caching, p
- [How we run Vercel's CDN in front of Discourse](https://vercel.com/blog/how-we-run-vercels-cdn-in-front-of-discourse)
- [Behind the scenes of Vercel's infrastructure: Achieving optimal scalability and performance](https://vercel.com/blog/behind-the-scenes-of-vercels-infrastructure)
- [How to troubleshoot stale content returned from the Vercel CDN when using an external proxy or CDN](https://vercel.com/kb/guide/how-to-troubleshoot-stale-content-returned-from-the-edge-network-when-using-an-external-proxy-or-cdn) — Learn how to diagnose and fix stale content issues when using external proxies or CDNs with Vercel. Understand troublesh
- [Control CDN caching for shared and personalized pages on Vercel](https://vercel.com/kb/guide/cdn-cache-personalized-pages) — Control CDN caching for shared and personalized Next.js pages. Set cache headers, separate per-user content, and verify
- [Life of a Vercel request: What happens when a user presses enter](https://vercel.com/blog/life-of-a-vercel-request-what-happens-when-a-user-presses-enter)
- [How requests flow through Vercel](https://vercel.com/docs/fundamentals/infrastructure) — Learn how Vercel routes, secures, and serves requests from your users to your application.
- [Caching](https://vercel.com/docs/caching) — Learn how Vercel caches content across multiple layers to deliver fast responses and reduce load on your backend.
- [Encryption and TLS](https://vercel.com/docs/cdn-security/encryption) — Learn how Vercel encrypts data in transit and at rest.
- [How Vercel builds your application](https://vercel.com/docs/fundamentals/builds) — Learn how Vercel transforms your source code into optimized assets ready to serve globally.

Full cross-link map for this page: [/docs/how-vercel-cdn-works.graph.md](/docs/how-vercel-cdn-works.graph.md)
<!-- /docsgraph:related -->

When a visitor requests a page, the CDN processes it through a series of layers. Each layer can resolve the request on its own or pass it to the next.

## Ingress layer

Requests arrive at the nearest [Point of Presence (PoP)](/docs/regions#points-of-presence-pops) out of 126 locations worldwide. The PoP terminates TCP and routes the request to the nearest [Vercel region](/docs/regions) over a private network in single-digit milliseconds. The region terminates TLS, applies [compression](/docs/how-vercel-cdn-works/compression), and processes the request through the remaining layers.

## Firewall layer

The [Vercel Firewall](/docs/cdn-security) inspects every request before it reaches your application. It operates in three layers:

- **[Platform-wide firewall](/docs/cdn-security#platform-wide-firewall)**: DDoS mitigation and protection against low-quality traffic, active for all customers at no cost.
- **[Web Application Firewall (WAF)](/docs/vercel-firewall/vercel-waf)**: Custom rules to block or challenge requests based on IP, path, headers, geographic location, and more.
- **[Bot management](/docs/bot-management)**: Detect and manage automated traffic with configurable policies.

Blocked requests never reach the routing or caching layers.

## Traffic management layer

Before the CDN evaluates a deployment's routing rules, it determines which deployment handles the request:

- **[Skew Protection](/docs/skew-protection)**: Locks each client session to a specific deployment version so client-side code and server responses stay in sync. This prevents errors caused by version mismatches during deployments.
- **[Rolling Releases](/docs/rolling-releases)**: Gradually shifts traffic from your current production deployment to a new one across configurable stages. You can monitor metrics at each stage and abort if needed.
- **[Microfrontends](/docs/microfrontends)**: Routes requests to different microfrontend applications based on path configuration in `microfrontends.json`. This routing happens within the same request with no additional network hop.

## Routing layer

Before the CDN checks any cache, it evaluates routing rules. Rules in your framework configuration follow the framework's order: for example, Next.js applies `headers` from `next.config.js` before `redirects`. The CDN evaluates rules in `vercel.json` in this order:

1. [**Redirects**](/docs/routing/redirects): Return a new URL to the client (e.g., enforce HTTPS, move pages, localize paths)
2. [**Headers**](/docs/headers): Add or modify request and response headers, including [security headers](/docs/cdn-security/security-headers) and [cache-control directives](/docs/caching/cache-control-headers)
3. [**Rewrites**](/docs/routing/rewrites): Map a public URL to a different backend path without changing what the visitor sees

If a redirect matches, the CDN responds immediately. Rewrites and header rules continue through the remaining layers.

## Caching layers

Vercel maintains two tiers of caching. Together, they minimize how often your functions run:

- **[CDN cache](/docs/caching/cdn-cache)**: It stores responses in the Vercel region nearest to your visitors and is controlled by [`Cache-Control` headers](/docs/caching/cache-control-headers) your functions return. A CDN hit serves the response without reaching your origin.
- **[ISR cache](/docs/incremental-static-regeneration)**: A durable store in your configured [function region](/docs/functions/configuring-functions/region): Vercel selects one region if you have multiple regions configured. It persists content for up to 31 days. When the CDN misses but the ISR cache has the content, Vercel serves it without invoking your function.
  - [Request collapsing](/docs/incremental-static-regeneration/request-collapsing) further protects this layer by deduplicating concurrent requests to the same ISR path into a single function invocation.

For data fetched inside your functions (individual API calls, database queries), [runtime cache](/docs/runtime-cache) provides an additional caching layer that works alongside response caching.

## Compute layer

If no cache has the content, the request reaches [Vercel Functions](/docs/functions) in the nearest compute region. Your function generates a response. Vercel caches it based on the caching headers or framework configuration, then serves it to the visitor.

## Local development

Vercel supports 35 [frontend frameworks](/docs/frameworks) with local development environments. Through [framework-defined infrastructure](https://vercel.com/blog/framework-defined-infrastructure), Vercel transforms your build outputs into globally [managed infrastructure](/products/managed-infrastructure) for production.

If you use [Vercel Functions](/docs/functions) without a framework, run [`vercel dev`](/docs/cli/dev) to test locally.

## Search the docs from your terminal

Search the Vercel docs and read pages as Markdown with the Vercel CLI. No login required.

```bash
# Find docs pages by keyword
npx vercel@latest docs search "environment variables"
npx vercel@latest docs search "function timeout"

# Print a docs page as Markdown, by path or URL
npx vercel@latest docs inspect <page>
```

---

[View full sitemap](/docs/sitemap)


If you encounter incorrect information, can’t find what you need, need a capability Vercel doesn’t currently offer, or have any other feedback to report, please do it by following the instructions at https://vercel.com/feedback.md.
