Cloud cost · Explainer
Vercel Fast Origin Transfer Explained (and How to Cut It)
Fast Origin Transfer is the Vercel meter for bytes moving between the CDN and your compute: Vercel Functions, Middleware, Blob and the Data Cache used by ISR. It counts both the request coming in and the response going out, at $0.06 per GB in the iad1 region. Because the response then travels on to the visitor as Fast Data Transfer, the same bytes are billed twice. Here is what it measures, how to estimate it, and how to bring it down.
By Jasdeep Bains, SeaGit
·
Key takeaways
- Fast Origin Transfer counts the bytes between the Vercel CDN and your functions, middleware, Blob storage and the Data Cache, in both directions.
- Incoming is the HTTP request, headers and body. For a GET it is usually under 1 KB; for an upload it is the whole file.
- Outgoing is the HTTP response. A function that returns 50 KB of JSON a million times sends about 48 GB, or about $2.90 at $0.06 per GB.
- It is separate from Fast Data Transfer (CDN to visitor, $0.15 per GB) and is not covered by Flat Rate CDN tiers.
- Caching, ETags, smaller responses and direct-to-storage uploads cut it. A high-volume API may need to move next to its data.
What Fast Origin Transfer measures
Vercel splits CDN pricing into three resources:
- Fast Data Transfer: data between the CDN and the visitor's device.
- Fast Origin Transfer: data between the CDN and your compute.
- CDN requests: requests the CDN processes.
Fast Origin Transfer applies to Vercel Functions, Middleware, Blob and the Data Cache used by Incremental Static Regeneration. It counts both directions:
- Incoming: the bytes of the HTTP request, headers and body. A normal GET is under 1 KB. A POST that uploads a file includes the whole file.
- Outgoing: the bytes of the HTTP response, headers and body.
Hobby includes the first 10 GB. On Pro it is usage-based, at $0.06 per GB in iad1. Rates differ by region.
Why the same bytes are billed twice
When a function returns a response, it travels in two hops. The first hop, function to CDN, is Fast Origin Transfer. The second, CDN to visitor, is Fast Data Transfer. The bytes are the same; the meters are different.
Flat Rate CDN tiers cover CDN requests and Fast Data Transfer, but not Fast Origin Transfer. So even inside a flat tier, every uncached function response is still billed per GB.
| Hop | Meter | Rate | 50 KB response × 1 million |
|---|---|---|---|
| Function to CDN | Fast Origin Transfer | $0.06 per GB | about $2.90 |
| CDN to visitor | Fast Data Transfer | $0.15 per GB on demand | about $7.15 |
At 3 billion 5 KB responses a month the first hop alone is about $858. The Vercel vs AWS cost teardown shows where that sits in a full bill.
Estimate it for one route
Multiply the route's monthly requests by its average response size, then by the rate:
monthly GB = requests × response KB ÷ 1,048,576
monthly USD = monthly GB × 0.06Add the request side only for routes that receive bodies, such as uploads or large POSTs. To check the estimate, open Usage, then Fast Origin Transfer, and filter by project and by direction. The region filter matters because the rate depends on the region.
Five ways to reduce it
- Cache responses at the CDN. Add caching headers to responses that can be shared. A cache hit is served from the CDN without invoking the function, so it adds no Fast Origin Transfer.
- Return an ETag or Last-Modified header. The CDN can answer repeat requests with a 304 instead of sending the body again. Next.js generates ETags by default.
- Send only what the page uses. Drop unused fields from API responses. Every byte saved is saved twice, on both hops.
- Upload straight to storage. Have the browser upload with a signed URL rather than posting the file through a function.
- Watch middleware. Middleware runs on CDN requests and its traffic counts too. Keep it to the paths that need it.
If a single API sends most of the bytes and cannot be cached, compare the cost of running it next to its database with the Vercel vs AWS cost calculator.