Setting Up a Custom Server in Next.js – Request Handling, Routing Control, and Performance Considerations

Next.js includes a built-in server that runs with next start. In rare cases, you may need a custom server to handle advanced routing or request logic. This article explains how to build a custom server using Node.js, configure your scripts, and understand the performance trade-offs and limitations of standalone mode.

Custom serverNext.jsRequest handlingSSR performance

~2 min read · Updated Oct 26, 2025

Introduction


Next.js comes with a built-in server that runs via next start. If your application requires custom routing logic or request handling, you can set up a custom server using Node.js. This approach is only recommended for advanced use cases.


Important Notes Before Using


  • Use a custom server only if Next.js’s built-in router doesn’t meet your needs
  • Custom servers disable performance features like Automatic Static Optimization
  • Standalone mode does not trace custom server files and is incompatible with custom server.js

Example: Custom Server with Node.js


// server.ts
import { createServer } from 'http'
import { parse } from 'url'
import next from 'next'

const port = parseInt(process.env.PORT || '3000', 10)
const dev = process.env.NODE_ENV !== 'production'
const app = next({ dev })
const handle = app.getRequestHandler()

app.prepare().then(() => {
  createServer((req, res) => {
    const parsedUrl = parse(req.url!, true)
    handle(req, res, parsedUrl)
  }).listen(port)

  console.log(
    `> Server listening at http://localhost:${port} as ${
      dev ? 'development' : process.env.NODE_ENV
    }`
  )
})

Updating package.json Scripts


{
  "scripts": {
    "dev": "node server.js",
    "build": "next build",
    "start": "NODE_ENV=production node server.js"
  }
}

You can also use nodemon for automatic reloads during development.


Options for next()


The next() function accepts a configuration object:

OptionTypeDescription
confObjectSame as next.config.js
devBooleanEnable development mode
dirStringPath to Next.js project
quietBooleanSuppress error messages
hostnameStringHostname of the server
portNumberPort number
httpServerServerExisting HTTP server instance
turbopackBooleanEnable Turbopack
webpackBooleanEnable Webpack

Conclusion


Custom servers in Next.js offer advanced control over routing and request handling. However, they should be used cautiously, as they disable key performance features. Avoid combining with standalone mode, and always evaluate whether the built-in router can meet your needs before ejecting.


Written & researched by Dr. Shahin Siami

Related Articles

Advanced Client-Side Routing and Performance Hooks in Next.js

Next.js provides a rich set of client-side hooks and caching utilities that empower developers to build dynamic, responsive, and secure applications. From reading route parameters to tracking navigation state and reporting performance metrics, this guide walks you through the most important tools available in the App Router.

Continue

Handling Authorization and Caching in Next.js: A Developer’s Guide

Next.js introduces powerful experimental features for access control and smart caching. This guide covers the unauthorized() function for custom 401 handling, unstable_cache for persistent memoization, updateTag for instant cache invalidation, and useLinkStatus for inline navigation feedback. Learn how to use these tools to build secure, performant, and responsive applications.

Continue

redirect and refresh in Next.js — Smart Redirects and Client Refreshing via Server Actions

The redirect function in Next.js allows you to navigate users to a new route, returning either a 307 or 303 HTTP response depending on context. It works in Server Components, Client Components, Route Handlers, and Server Actions. The refresh function is used exclusively within Server Actions to refresh the client router. This article explains how both functions work, with practical examples and key considerations.

Continue

NextRequest and NextResponse in Next.js — Managing Cookies, Headers, Redirects, and Rewrites

Next.js extends the native Web Request and Response APIs with NextRequest and NextResponse, offering powerful tools for managing cookies, headers, redirects, rewrites, and JSON responses. These utilities simplify server-side logic and improve control over routing, personalization, and security. This guide walks through their capabilities with practical examples and best practices.

Continue

headers, ImageResponse, notFound, and permanentRedirect in Next.js — Request Handling, Dynamic Images, Errors, and Redirects

Next.js offers powerful tools for handling HTTP requests and responses in Server Components. The headers function lets you read incoming request headers. ImageResponse allows you to generate dynamic images using JSX and CSS. The notFound function renders a custom 404 page, and permanentRedirect enables permanent redirection to another route. This article explains how to use each feature with practical examples.

Continue

A Complete Guide to Using metadata and generateMetadata in Next.js

In modern versions of Next.js, managing page metadata is more powerful and intuitive than ever. Metadata is automatically injected into the <head> of your pages and plays a vital role in SEO, social sharing, and user experience. This guide explains the two main ways to define metadata: using the static metadata object and the dynamic generateMetadata function.

Continue