Cloud cost · Troubleshooting
Why Is My Vercel Bill So High? 8 Meters to Check
A Vercel invoice that jumps is almost never one big charge. It is usually one of eight usage meters that grew with your traffic: CDN requests, function invocations, two kinds of data transfer, CPU, memory, image transformations or networking add-ons. This guide shows how to find the meter that moved, what each one costs on the Pro plan, and the fix for each.
By Jasdeep Bains, SeaGit
·
Key takeaways
- Open Usage in the Vercel dashboard and sort by project first. One project and one meter usually explain most of the increase.
- CDN requests and function invocations are billed per request. Past 150 million requests a month, every request is billed on demand at $2.00 per million, plus $0.60 per million invocations.
- The same response bytes are billed twice: Fast Origin Transfer from the function to the CDN, then Fast Data Transfer to the visitor.
- Caching function responses at the CDN is the biggest single fix. It removes the invocation, CPU and Fast Origin Transfer for every cache hit.
- For a high-volume API, the request meters do not go away. Run the numbers for moving that API next to its database.
Find the meter that grew
Start in the dashboard, not in your code. Vercel's Usage page breaks every meter down by project, and most charts can also be split by region and by direction (incoming or outgoing). The CLI gives the same data by day with vercel billing usage.
- Open Usage and compare this billing cycle with the last one.
- For the meter that grew, filter by project. One project usually accounts for most of it.
- For Fast Origin Transfer, filter by direction. Outgoing means function responses; incoming means request bodies such as uploads.
- For function meters, filter by invocations to find the route that is called most.
Once you know the project, the meter and the route, the fix is usually one of the ones below.
The eight meters behind most surprise bills
Rates are the on-demand prices for the Washington, D.C. (iad1) region on the Pro plan. Other regions differ.
| Meter | What it counts | Rate | Usual cause of a jump |
|---|---|---|---|
| CDN requests | Every request the CDN handles | $2.00 per million | An API or a bot sending many small requests |
| Function invocations | Every request that reaches a function | $0.60 per million | Uncached API routes and server-rendered pages |
| Fast Origin Transfer | Bytes between the CDN and your functions | $0.06 per GB | Large JSON responses, uploads through a function |
| Fast Data Transfer | Bytes from the CDN to visitors | $0.15 per GB | Large assets, video, big API responses |
| Active CPU | CPU time while your code runs | $0.128 per hour | Heavy rendering, image or PDF work |
| Provisioned memory | Memory for each instance's lifetime | $0.0106 per GB-hour | Long-running requests and high concurrency |
| Image transformations | Images optimized on demand | $0.05 per 1,000 | Many image sizes or uncached image URLs |
| Static IPs | Fixed egress IPs for a project | $100 per project a month, plus Private Data Transfer | Turned on for a database IP allowlist |
Two included allowances soften the first numbers. Pro comes with $20 of monthly usage credit, and the included Flat Rate CDN tier covers 1 million CDN requests and 1 TB of transfer. Larger flat tiers go up to 150 million requests for $300 a month. Usage above the top tier moves to on-demand pricing at the start of the next cycle.
Fixes, from cheapest to biggest
- Cache function responses at the CDN. Add caching headers to responses that can be shared. A cache hit skips the invocation, the CPU and Fast Origin Transfer. It is still a CDN request and still Fast Data Transfer.
- Return ETag or Last-Modified headers. The CDN can then answer repeat requests with a 304 and no body. Next.js does this by default.
- Trim responses. Return only the fields the page uses. Every byte is billed twice, once from the function and once to the visitor.
- Upload straight to storage. A file uploaded through a function counts as incoming Fast Origin Transfer. Upload from the browser with a signed URL instead.
- Match the function region to your database. It saves cross-Region transfer and makes every query faster.
- Set spend alerts. Vercel notifies new teams at $200 a billing cycle by default. Lower it, or add an automatic action, under spend management.
- Move the busiest API. If one high-volume API drives the request meters, run it as a container next to its database. The full teardown prices that move line by line, and the calculator runs it for your traffic.
When the fix is moving, not tuning
Caching and trimming reduce bytes, but they cannot remove the per-request meters. At 100 million API reads a day an uncached JSON API on Vercel costs about $11,900 a month at list prices, and the same API on Amazon EKS next to its DynamoDB table about $2,400.
The tipping point in that model is about 5 million reads a day, when requests pass the largest Flat Rate CDN tier. Below it, staying on Vercel is usually the better deal. Above it, compare both before the next invoice.