output: 'export' makes next build write a self-contained static site to out/: one .html per path, the RSC payloads as .txt files (so client navigation still works), _next/static/, public/ and 404.html. No Next.js server runs afterwards. On 16.4.5, next start refuses: "next start" does not work with "output: export" configuration. Use "npx serve@latest out" instead.
What you keep: Server Components rendered at build, Client Components, <Link> navigation and prefetching, generateStaticParams paths, and GET route handlers marked force-static (they become files such as data.json).
What you give up is anything decided per request. On Next.js 16.4.5 I added one feature at a time:
- The build fails for
cookies()orheaders()(Route /c with `dynamic = "error"` couldn't be rendered statically because it used `cookies()`), a route handler withoutforce-static, even one ignoringRequest, a dynamic segment withoutgenerateStaticParams, an explicitdynamicParams = true, and Server Actions (Server Actions are not supported with static export.). - The build warns and drops it for
rewrites,redirectsandheadersin config (Specified "rewrites" will not automatically work with "output: export".) and for a Proxy file, whose warning still namesnext exportand middleware. - Silent:
revalidate = 60built as○ /isr 1m 1y, but nothing will ever regenerate the file.next/imagewith the default loader built cleanly and wrotesrcsetURLs to/_next/image, which doesn't exist inout/. Setimages.unoptimized: true(plainsrc="/hero.jpg") or a custom loader.
So a static export is a fit for docs, marketing sites and SPAs whose dynamic data comes from client-side fetches to some other API. Redirects, headers and auth move to the host or CDN.