[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live)

[Help](/c/help/9)

# Why Vercel costs spiked after upgrading Next.js from version 15 to 16

21 views · 1 like · 1 post


ALBA-s.aizawa (@saizawa-alba) · 2026-03-24 · ♥ 1

Between March 18 and March 23, we updated `Next.js` from `version 15` to `version 16`.

## Problem

Are the costs during that period off? What’s going on? They’re way over our budget.

![スクリーンショット 2026-03-24 112257 - コピー](https://global.discourse-cdn.com/vercel/original/3X/8/a/8ab578304d0b68536b6b9b66a49fd5ff1360988d.png)

| Period	| Cost per PV |
|----|----|
| Before upgrade (March 13-17)	| $0.00012 – $0.00025 |
| After upgrade (March 18-22)	| $0.00038 – $0.00073	|	| |

Root Cause:

Next.js 16 changed caching from implicit (automatic) to explicit (`"use cache"` directive). Our previously cached content was suddenly being served dynamically, causing increased Fast Origin Transfer and Edge Request charges.

Workaround:

We had to downgrade to Next.js 15 to stop the cost increase.