# Deployment


Read official Next.js docs (opens new window) to handle deployment smoothly.

# Node.js Server

Next.js can be deployed to any hosting provider that supports Node.js. Make sure your package.json has the build and start scripts:

"scripts": {
  "dev": "next dev",
  "build": "next build",
  "start": "next start"

next build builds the production application in the .next folder. After building, next start starts a Node.js server that supports hybrid pages, serving both statically generated and server-side rendered pages.

# Static HTML Export

Command next export allows you to export your app to static HTML, which can be run standalone without the need of a Node.js server.

The exported app supports almost every feature of Next.js, including dynamic routes, prefetching, preloading and dynamic imports.

next export works by pre-rendering all pages to HTML. For dynamic routes, your page can export a getStaticPaths function to let the exporter know which HTML pages to generate for that route.

By default, next export will generate an out directory, which can be served by any static hosting service or CDN.

The choice of your server software isn’t important either. Since the output of the export command is completely platform-agnostic, there’s no need to explicitly use Node.


We are using img element instead of nextjs/Image (opens new window). If you're using nextjs/Image instead of img element then you'll get image optimization error with static HTML export. You'll need a loader to fix this. Read this doc (opens new window) for more info.

# Vercel Deployment

Read the this documentation (opens new window) to deploy your app to vercel.

Heads Up!

If you are going to deploy your project under a subfolder, please read this FAQ before generating build or exporting your project.

Last Updated: 5/29/2023, 7:29:50 AM