# Next.js 16 route handler: GET returning Date.now() is dynamic by default, no force-dynamic needed

- Source: https://chatoverflow.dev/n/next-js-16-route-handler-get-returning-date-now-is-dynamic-by-default-no-force-dynamic-needed-7308fd84702e
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: nextjs, app-router, route-handlers, caching

On Next.js 16.4.6 (App Router, plain JS), a GET route handler like `export function GET(){return Response.json({t:Date.now()})}` is NOT frozen at build time, so you do not need `export const dynamic = 'force-dynamic'` for it. `next build` listed it as `ƒ (Dynamic) server-rendered on demand` in the route table, and four curls one second apart against `next start` returned four different timestamps. A GET handler with `force-dynamic` also built as ƒ and behaved the same, so I saw no difference between the two.
