Run a Node.js App from a Windows .bat File

To run a Node.js application from a Windows .bat file so non-technical users can double-click to start it, create a one- or two-line batch script that cds into your project directory and runs npm start (or node server.js). A desktop shortcut to the .bat gives users a single click to launch.

Contents

The simplest .bat
Robust version (works from anywhere)
Run a specific script or file
Create a desktop shortcut
For production — install as a Windows service
Frequently asked questions
Related guides
References

Last verified: 2026-05-17 on Windows 11 with Node 20 LTS. Originally published 2022-10-13, rewritten and updated 2026-05-17.

The simplest `.bat`

npm start

Save as start.bat inside your project directory (next to package.json) and double-click. A command prompt opens, runs npm start, and stays open as long as your server runs.

Run Node.js from a .bat — npm start, cd /d %~dp0, pause, NSSM service for production

Robust version (works from anywhere)

@echo off
cd /d "%~dp0"
echo Starting application...
npm start
pause

@echo off — hides command echoing (the script lines themselves) so the user sees clean output.
cd /d "%~dp0" — changes to the directory the .bat lives in. %~dp0 expands to the script’s path; /d allows switching drives. Now the user can place the .bat anywhere and it still works.
pause — keeps the window open after npm exits so the user can read error messages. Drop it for long-running servers that don’t normally exit.

Run a specific script or file

@echo off
cd /d "%~dp0"

REM A specific npm script
npm run dev

REM Or call node directly
node server.js

REM Or with arguments
node server.js --port 4000 --env production

pause

Create a desktop shortcut

Right-click the .bat file → Send to → Desktop (create shortcut).
Right-click the new shortcut → Properties.
Optionally change the icon under Change Icon… to something prettier than the default .bat icon.

The user now has a desktop icon they can double-click to start the app — no command-line knowledge needed.

For production — install as a Windows service

REM Download nssm.exe from https://nssm.cc/ first
nssm install MyNodeApp "C:\Program Files\nodejs\node.exe" "C:\path\to\app\server.js"
nssm set MyNodeApp AppDirectory "C:\path\to\app"
nssm start MyNodeApp

NSSM turns any console process into a Windows service. The app runs in the background, starts on boot, and restarts if it crashes — much better than a .bat for long-running servers in production.

Frequently asked questions

Why does my .bat close immediately after running?

If npm start exits (because there’s no long-running server or it errored out), the command prompt closes the moment the script ends and you don’t see why. Add pause as the last line of the .bat — the window stays open until you press a key, so you can read any error messages.

How do I make sure it works no matter where the user runs it from?

Use %~dp0 at the top — that’s the directory the .bat itself lives in. cd /d %~dp0 changes to that directory before running npm. Without it, double-clicking from a shortcut on the desktop starts in %HOMEDRIVE%%HOMEPATH% and npm start can’t find package.json.

Can I run this hidden so the user doesn’t see the command prompt?

Wrap it with start /B /MIN to start minimized, or use a VBScript wrapper that calls the .bat with no window. For a long-running server, the cleanest option is to install your app as a Windows service with nssm (the Non-Sucking Service Manager) — it runs in the background, starts on boot, and restarts on crash.

Should I distribute the .bat or build an installer?

For a few internal users a .bat + desktop shortcut is fine. For external distribution, consider packaging the app with pkg or nexe (single-binary Node), or wrap it in an Electron-style installer. The .bat approach assumes the user already has Node.js installed and a working npm in PATH.