Skip to content

    Static Exports

    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.

    Since Next.js supports this static export, it can be deployed and hosted on any web server that can serve HTML/CSS/JS static assets.

    Note: We recommend using the App Router for enhanced static export support.


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

     * @type {import('next').NextConfig}
    const nextConfig = {
      output: 'export',
      // Optional: Add a trailing slash to all paths `/about` -> `/about/`
      // trailingSlash: true,
      // Optional: Change the output directory `out` -> `dist`
      // distDir: 'dist',
    module.exports = nextConfig;

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

    You can utilize getStaticProps and getStaticPaths to generate an HTML file for each page in your pages directory (or more for dynamic routes).

    Supported Features

    The majority of core Next.js features needed to build a static site are supported, including:

    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',
    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} />;

    Unsupported Features

    Features that require a Node.js server, or dynamic logic that cannot be computed during the build process, are not supported:


    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 the static export into the out folder. Using next export is no longer needed. 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 {

    Version History

    v13.4.0App Router (Stable) adds enhanced static export support, including using React Server Components and Route Handlers
    v13.3.0next export is deprecated and replaced with "output": "export"

    Was this helpful?