What is the output: 'standalone' build in Next.js and when do you use it?

Q: What is the output: 'standalone' build in Next.js and when do you use it?

**Target Audience:** Frontend engineers preparing for Next.js interviews — assumes basic React and App Router familiarity. **Difficulty:** Medium > **How to read this doc:** Each idea is explained in plain language first, then tagged with `📌 Interview term:`. Every behaviour claim was checked against the Next.js docs shipped with the package (written on 16.3.4, re-reviewed against 16.4.2) and, in the **Verified** section, against real output from a build or a running server; each Verified block says which version it ran on. ## 1. Why This Even Matters — A Story First Packing for a work trip, you do not take your whole wardrobe; you take what the itinerary needs. Standalone output reads the itinerary (the traced imports of your server) and packs only those clothes, plus a suitcase key (server.js). You still have to add your shoes (static files and public) yourself, because they travel in a different bag. ## 2. The Core Idea 📌 **Interview term: Standalone output** — a build mode t

The problem

Question presented to candidate: "Our Docker images for a Next.js app are over a gigabyte. What does output: 'standalone' do and how does it change the Dockerfile?"

What a strong answer should cover:

output: "standalone" makes next build produce .next/standalone with a minimal server.js and only the files the server needs.
It uses output file tracing to copy just the traced dependencies from node_modules, so no npm install is needed in the runtime image.
Run it with node server.js; configure PORT and HOSTNAME through environment variables.
.next/static and public are not copied by default: copy them next to server.js or serve them from a CDN.
Use it for Docker and other self-hosted deployments; managed platforms do not need it.

Clarifying questions expected:

"Are static assets served by a CDN?" — then you may not need to copy them into the image.
"Do any packages load files at runtime that tracing might miss?" — they may need outputFileTracingIncludes.

Code / implementation expected: Yes — the config and the copy steps.

nextjs
standalone
docker
deployment

Try it yourself

Sketch your approach before you read the solution. That is what the interview tests.

Stuck? Get a hint.

A short nudge toward the approach. It will not give the answer away.

Solution

Target Audience: Frontend engineers preparing for Next.js interviews — assumes basic React and App Router familiarity. Difficulty: Medium

How to read this doc: Each idea is explained in plain language first, then tagged with 📌 Interview term:. Every behaviour claim was checked against the Next.js docs shipped with the package (written on 16.3.4, re-reviewed against 16.4.2) and, in the Verified section, against real output from a build or a running server; each Verified block says which version it ran on.

1. Why This Even Matters — A Story First

Packing for a work trip, you do not take your whole wardrobe; you take what the itinerary needs. Standalone output reads the itinerary (the traced imports of your server) and packs only those clothes, plus a suitcase key (server.js). You still have to add your shoes (static files and public) yourself, because they travel

The solution is hidden so you can try first

4 min read · 8 sections

Read the code

Config, copy steps and start command

# next.config.ts
#   const nextConfig = { output: "standalone" };

npm run build
cp -r .next/static .next/standalone/.next/static
cp -r public .next/standalone/public
cd .next/standalone
PORT=3000 HOSTNAME=0.0.0.0 node server.js

Discussion

Other approaches, follow-ups and how it went in real interviews.

Sign in to join the discussion.

No comments yet. Share how you would answer it.

The solution is hidden so you can try first

Keep your momentum going.