Static Export

Note: Support for static exports is currently only available on next@canary.

Next.js enables starting as a static site or Single-Page Application (SPA), then later optionally upgrading to use features that require a server.

When running next build, Next.js generates an HTML file per route. By breaking a strict SPA into individual HTML files, Next.js can avoid loading unnecessary JavaScript code on the client-side, reducing the bundle size and enabling faster page loads.


To enable a static export, change the output mode inside next.config.js:

 * @type {import('next').NextConfig}
const nextConfig = {
  output: 'export',

module.exports = nextConfig

After running next build, Next.js will produce an out folder inside .next/build which contains the HTML/CSS/JS assets for your application.

Supported Features

The core of Next.js has been designed to support static exports.

Server Components

When you run next build to generate a static export, Server Components consumed inside the app directory will run during the build, similar to traditional static-site generation.

The resulting component will be rendered into static HTML for the initial page load and a static payload for client navigation between routes. No changes are required for your Server Components when using the static export, unless they consume dynamic server functions.

export default async function Page() {
  // This fetch will run on the server during `next build`
  const res = await fetch('');
  const data = await res.json();

  return <main>...</main>;

If you want to fetch dynamic data in the browser, this is also supported with a static export using client components.

Dynamic Route Segments

When dynamic route segments are known during next build, you can use generateStaticParams to choose which segments to generate. For example, the following page will generate a route for every post.

export async function generateStaticParams() {
  const posts = await fetch('https://.../posts').then((res) => res.json());

  return => ({

export default function Page({ params }: { params: { id: string } }) {
  return <div>{}</div>;

If you do not know the route segments during next build, you can fetch dynamic data in the browser using client components.

Dynamic Fetching with Client Components

If you want to display dynamic data based on the route segment, where the values are not known during next build, you can use a Client Component:

'use client';

import useSWR from 'swr';

const fetcher = (url: string) => fetch(url).then((r) => r.json());

export default function Page({ params }: { params: { id: string } }) {
  const { data, error } = useSWR(
  if (error) return 'Failed to load';
  if (!data) return 'Loading...';

  return data.title;

Since route transitions happen client-side, this behaves like a traditional SPA. For example, the following index route allows you to navigate to different posts on the client:

import Link from 'next/link';

export default function Page() {
  return (
      <h1>Index Page</h1>
      <hr />
          <Link href="/post/1">Post 1</Link>
          <Link href="/post/2">Post 2</Link>

Image Optimization

Image Optimization through next/image can be used with a static export by defining a custom image loader in next.config.js. For example, you can optimize images with a service like Cloudinary:

/** @type {import('next').NextConfig} */
const nextConfig = {
  output: 'export',
  images: {
    loader: 'custom',
    loaderFile: './app/image.ts',
  experimental: {
    appDir: true,

module.exports = nextConfig;

This custom loader will define how to fetch images from a remote source. For example, the following loader will construct the URL for Cloudinary:

export default function cloudinaryLoader({
}: {
  src: string;
  width: number;
  quality?: number;
}) {
  const params = ['f_auto', 'c_limit', `w_${width}`, `q_${quality || 'auto'}`];
  return `${params.join(

You can then use next/image in your application, defining relative paths to the image in Cloudinary:

import Image from 'next/image';

export default function Page() {
  return <Image alt="turtles" src="/turtles.jpg" width={300} height={300} />;

Route Handlers

Route Handlers will render a static response when running next build. Only the GET HTTP verb is supported. This can be used to generate static HTML, JSON, TXT, or other files from dynamic or static data. For example:

import { NextResponse } from 'next/server';

export async function GET() {
  return NextResponse.json({ name: 'Lee' });

The above file app/data.json/route.ts will render to a static file during next build, producing data.json containing { name: 'Lee' }.

If you need to read dynamic values from the incoming request, you cannot use a static export.

Browser APIs

Client Components are pre-rendered to HTML during next build. Because Web APIs like window, localStorage, and navigator are not available on the server, you need to safely access these APIs only when running in the browser. For example:

'use client';

import { useEffect } from 'react';

export default function ClientComponent() {
  useEffect(() => {
    // You now have access to `window`
  }, [])

  return ...;

Unsupported Features

After enabling the static export output mode, all routes inside app are opted-into the following Route Segment Config:

export const dynamic = 'error';

With this configuration, your application will produce an error if you try to use server functions like headers or cookies, since there is no runtime server. This ensures local development matches the same behavior as a static export. If you need to use server functions, you cannot use a static export.

The following additional dynamic features are not supported with a static export:


With a static export, Next.js can be deployed and hosted on any web server that can serve HTML/CSS/JS static assets.

When running next build, Next.js generates an HTML file per route. For example, let's say you have the following routes:

  • /
  • /blog/[id]

After running next build, Next.js will generate the following files:

  • /out/index.html
  • /out/404.html
  • /out/blog/post-1.html
  • /out/blog/post-2.html

If you are using a static host like Nginx, you can configure rewrites from incoming requests to the correct files:

server {
  listen 80;

  root /var/www;

  location / {
      try_files /out/index.html =404;

  location /blog/ {
      rewrite ^/blog/(.*)$ /out/blog/$1.html break;

  error_page 404 /out/404.html;
  location = /404.html {