nextjs App on Shared Server

[arunbm123]

Summary

Can We Install Nextjs App on shared server or any other server..
independant of Veceral

Additional information

No response

Example

No response

[icyJoseph]

Hi, Next.js, from the very beginning has supported self-hosting.

The good ol' next build and then next start, this got some optimizations via output: 'standalone'

It'll work just about the same. We call this baseline fidelity. Additionally, hosting providers such as Vercel, can offer additional optimizations.

• https://nextjs.org/docs/app/guides/rendering-philosophy#portability-and-fidelity
• https://nextjs.org/docs/app/guides/self-hosting
• https://nextjs.org/docs/app/getting-started/deploying

[shareefmx]

Yes, you can absolutely self-host a Next.js app on any shared or VPS server without Vercel.

Basic steps

npm run build
npm run start

Optimized self-hosting

Use standalone output in next.config.js:

module.exports = {
  output: 'standalone',
}

Then run:

node .next/standalone/server.js

You can host this on any server running Node.js — a VPS, shared hosting with Node support, Railway, Render, etc.

Official guide: https://nextjs.org/docs/app/guides/self-hosting

[vignesh0x]

Yes, but it depends on what you mean by "shared hosting".

If the shared hosting provider supports running a persistent Node.js process, then a Next.js app can be deployed without Vercel. In that case, you can build the app with:

npm run build
npm run start

or use the standalone output for a smaller deployment.

However, many traditional shared hosting plans are designed only for PHP applications and do not allow you to run a Node.js server continuously. In those environments, a Next.js application may not work even though it works fine on a VPS.

Before choosing a host, I would check:

• Whether Node.js is supported
• Which Node.js versions are available
• Whether custom processes can stay running
• Whether SSH access is provided

If your hosting provider supports those requirements, then you can host a Next.js application independently of Vercel without any issues.

[icyJoseph]

This is true though, some hosting providers have tiers too, where the typically used tier, only supports email, static file hosting and some PHP scripting.

That being said, output: 'export' is a thing too, so a Next.js app can be packaged, given some limitations, to be served as static html, https://nextjs.org/docs/app/guides/static-exports

[vignesh0x]

Good point. My original comment was mainly focused on Next.js deployments that require a Node.js runtime (SSR, Route Handlers, Server Actions, etc.). For applications that fit within the static export limitations, output: 'export' is definitely another viable option for traditional shared hosting environments.

[logusivam]

Yes — Next.js is completely independent of Vercel. Vercel maintains it, but it's open source and runs anywhere. You have two main self-hosting paths, and which one works on a "shared server" depends on whether that host lets you run a Node.js process.

Option 1 — Node.js server (supports all Next.js features)

If your host can run a long-running Node process, just build and start it:

npm run build
npm run start   # runs `next start`

This supports everything: SSR, API routes, ISR, image optimization, middleware, etc. Works on any VPS or Node-capable host (DigitalOcean, AWS EC2, Hetzner, Railway, Render, a self-managed Linux box, etc.). For smaller/Docker deployments, set output: 'standalone' in next.config.js — it produces a minimal .next/standalone folder with a server.js you can run with node server.js, no node_modules install needed.

Option 2 — Static export (works on basic/cheap shared hosting)

If you're on traditional shared hosting (cPanel, Apache/Nginx, PHP-style hosts) that only serves static files and can't run Node, use a static export:

// next.config.js
const nextConfig = {
  output: 'export',
}
module.exports = nextConfig

next build then generates an out/ folder of plain HTML/CSS/JS you can upload to any static host (shared hosting, S3, Nginx, Apache, GitHub Pages, etc.).

⚠️ The trade-off: static export drops features that need a server at runtime — SSR, API routes/Route Handlers, on-demand ISR, middleware, and built-in Image Optimization. If you need those, you need a Node host (Option 1).

Quick decision guide

• Cheap/shared host, static files only → output: 'export' (Option 2).
• Host that runs Node / VPS / Docker → next build && next start or output: 'standalone' (Option 1, full features).

So the short answer: yes, you can host it anywhere — a basic shared server works with a static export, and any Node-capable server runs the full app.

Hope this resolves it — if so, would you mind clicking "Mark as answer" so others searching for the same thing can find it quickly? Happy to clarify further.