Failed to set Next.js data cache, items over 2MB can not be cached Next.js Origin: On your device OSI layer 7 · Application Last updated 5 Nov 2026

Next.js: Failed to set Next.js data cache for https://api.example.com/data, items over 2MB can not be cached (2437412 bytes)

A fetch response was too large for Next.js's data cache (limit 2 MB), so it wasn't cached.

Exact message you may see Failed to set Next.js data cache, items over 2MB can not be cachedFailed to set Next.js data cache for https://api.example.com/data, items over 2MB can not be cachedFailed to set Next.js data cache items over 2MB can not be cached (2437412 bytes)items over 2MB can not be cached
Explore the map of this error Full error map →
Seen on: Next.js

Meaning

Only the caching fails; the request still works. To fix: fetch less data (pagination, field selection), cache your own processed result in a smaller form, use cache: 'no-store' for large responses, or store large payloads in a database/blob and cache the reference.

Common causes

  • Large API/CMS responses
  • Fetching whole collections
  • Unpaginated lists
  • Data containing images/base64
  • Duplicate large fetches

⚡ Quick fix

  1. Request only needed fields/pagination
  2. Use cache: "no-store" for large responses
  3. Cache a reduced version via your own cache (Redis, KV)

Detailed fix by platform

Next.js

  1. await fetch(url, { cache: "no-store" }) to avoid the cache attempt

How to diagnose

  1. Size — Response bytes?
  2. Need — All fields?
  3. Alternative — Own cache?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: On your device. Errors that are often confused with or caused by this one (click to open):

Conflicting app and page file was found — Next.js: ⨯ Conflicting app and page file was found, please remove the conflicting files to continue: "pages/index.tsx" - "app/page.tsx" (Next.js)Conflicting app and p…Dynamic server usage — Error: Dynamic server usage: Route /x couldn't be rendered statically because it used `cookies` (React)Dynamic server usagenext build: fetch failed ECONNREFUSED (build-time API) — Next.js: Error occurred prerendering page "/blog" TypeError: fetch failed { cause: Error: connect ECONNREFUSED 127.0.0.1:3000 } (Next.js)next build: fetch fai…next build: JavaScript heap out of memory — Next.js: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory (during next build) (Next.js)next build: JavaScrip…Route used revalidatePath during render — Next.js: Error: Route /blog used "revalidatePath /blog" during render which is unsupported. It must happen outside of renders and cached functions (Next.js)Route used revalidate…TypeError: Failed to parse URL from /api/... — Next.js: TypeError: Failed to parse URL from /api/posts (fetch in a Server Component) (Next.js)TypeError: Failed to …Used cookies/headers inside a function cached with unstable_cache — Next.js: Route used `cookies()` inside a function cached with `unstable_cache(...)`. Accessing Dynamic data sources inside a cache scope is not supported (Next.js)Used cookies/headers …Failed to…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.