Next.js can be deployed as a Node.js server, Docker container, static export, or adapted to run on different platforms.

Node.js server

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

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

Then, run npm run build to build your application and npm run start to start the Node.js server. This server supports all Next.js features. If needed, you can also eject to a custom server.

Node.js deployments support all Next.js features. Learn how to configure them for your infrastructure.

Templates

• Flightcontrol
• Railway
• Replit
• Hostinger

Docker

Next.js can be deployed to any provider that supports Docker containers. This includes container orchestrators like Kubernetes or a cloud provider that runs Docker. For best practices on containerizing your app, refer to Docker's official Next.js and React.js guides.

Docker deployments support all Next.js features. Learn how to configure them for your infrastructure.

Note for development: While Docker is excellent for production deployments, consider using local development (npm run dev) instead of Docker during development on Mac and Windows for better performance. Learn more about optimizing local development.

Templates

The following examples demonstrate best practices for containerizing Next.js applications:

• Docker Standalone Output - Deploy a Next.js application using output: "standalone" to generate a minimal, production-ready Docker image with only the required runtime files and dependencies.
• Docker Export Output - Deploy a fully static Next.js application using output: "export" to generate optimized HTML files that can be served from a lightweight container or any static hosting environment.
• Docker Multi-Environment - Manage separate Docker configurations for development, staging, and production environments with different environment variables.

Additionally, hosting providers offer guidance on deploying Next.js:

• DigitalOcean
• Fly.io
• Google Cloud Run
• Render
• SST

Static export

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

Since Next.js supports static exports, it can be deployed and hosted on any web server that can serve HTML/CSS/JS static assets. This includes tools like AWS S3, Nginx, or Apache.

Running as a static export does not support Next.js features that require a server. Learn more.

Templates

• GitHub Pages

Adapters

Next.js can be adapted to run on different platforms to support their infrastructure capabilities. The Deployment Adapter API lets platforms customize how Next.js applications are built and deployed.

Verified Adapters

Verified adapters are open source, run the full Next.js compatibility test suite, and are hosted under the Next.js GitHub organization. The Next.js team coordinates testing with these platforms before major releases. Publicly visible test results for each adapter are coming soon. Learn more about verified adapters.

• Vercel
• Bun

Cloudflare and Netlify are working on verified adapters built on the Adapter API. In the meantime, they offer their own Next.js integrations (see below).

Other Platforms

The following platforms offer their own Next.js integrations. These are not built on the public Adapter API and are not verified by the Next.js team, so feature support and compatibility may vary. Refer to each provider's documentation for details:

• Appwrite Sites
• AWS Amplify Hosting
• Cloudflare
• Deno Deploy
• Firebase App Hosting
• Netlify

For details on which Next.js features require specific platform capabilities, see Deploying to Platforms.

Source: docs/01-app/01-getting-started/17-deploying.mdx