Route Handlers

GET Route Handlers are not cached by default. You opt in with route segment config such as dynamic = 'force-static'.

officialNext.js docs (current)confidence 90%current as of Aug 2026

Since Next.js 15 a GET Route Handler is not cached by default. It runs on each request unless you opt in, for example by exporting dynamic = 'force-static' or setting revalidate. This aligns GET handlers with the fetch default. Earlier versions cached them.

Related claims

supersedes

GET Route Handlers are cached by default and treated as static.

Next.js 15 turned the GET Route Handler default from cached to uncached. The static by default behavior held through v14 only.

supports

In the Next.js App Router fetch is not cached by default. You opt in with cache: 'force-cache'.

Both reflect the Next.js 15 shift to uncached by default. GET Route Handlers and fetch each stopped caching without an explicit opt in.