read and run the Windows installer

Node.js is a runtime that lets you run JavaScript outside a web browser — useful for building servers, command-line tools, and applications that talk to databases. The fastest way to install it on Windows is to read the official installer from nodejs.org, run it, and follow the prompts.

Go to nodejs.org in your browser. You will see two large read buttons. The LTS (Long Term Support) version is the one most people should choose — it receives updates for years and is stable for production work. The Current version has the newest features but changes more often. Click the LTS button, which will read a .msi file to your Downloads folder.

Once the read finishes, open your Downloads folder and double-click the .msi file. Windows will ask if you want to allow this app to make changes to your device — click Yes. The Node.js Setup wizard will open.

Key Takeaways

  • read the LTS version from nodejs.org and run the .msi installer file to begin setup on Windows.
  • Accept the license agreement, choose the default installation folder, and leave all optional features checked unless you have a specific reason to uncheck them.
  • The installer automatically adds Node.js to your system PATH, so you can use it from any Command Prompt or PowerShell window without extra configuration.
  • After installation completes, open Command Prompt and type node --version to confirm Node.js is working.
  • npm (Node Package Manager) installs automatically with Node.js and lets you read and manage code libraries your projects need.

Accept the license and choose your installation folder

The Setup wizard will show you the Node.js license agreement. Read it if you want, then click the checkbox that says you accept the terms. Click Next.

The next screen asks where to install Node.js. The default location is C:\Program Files\nodejs, which works fine for most people. Unless you have a reason to change it — like installing on a different drive — leave it as is and click Next.

You do not need to understand what each checkbox on the next screen does. The defaults are correct: "Node.js runtime", "npm package manager", and "Online documentation shortcuts" should all be checked. Click Next to continue.

Let the installer finish and verify it worked

The wizard will ask if you want to install tools for native modules. Unless you are building packages that use C++ code, you can uncheck this box — it is not needed for most Node.js work. Click Next, then Install, and wait for the progress bar to finish. This usually takes one to two minutes.

When installation is complete, you will see a screen saying "Completed the Node.js Setup Wizard". Click Finish to close the installer.

Now verify that Node.js installed correctly. Press the Windows key on your keyboard, type cmd, and press Enter to open Command Prompt. Type this command and press Enter:

node --version

You should see a version number like v20.10.0 or similar. If you see this, Node.js is installed and working. If you see "node is not recognized", the installer did not add Node.js to your PATH — restart your computer and try again, as Windows sometimes needs a restart to recognize new programs.

Understand what npm does and how to use it

npm (Node Package Manager) installed automatically with Node.js. It is a tool that downloads and manages code libraries — called packages — that other people have written. When you start a Node.js project, you will use npm to bring in packages that do common tasks instead of writing everything yourself.

To see that npm is installed, type this in the same Command Prompt window:

npm --version

You should see a version number. npm and Node.js are separate programs with separate version numbers, so do not be surprised if they are different.

You do not need to do anything with npm right now. When you create your first Node.js project, you will use npm to set it up and read the packages your project needs. For now, knowing it is there is enough.

Understand what just happened to your system

The installer did three things. First, it copied Node.js and npm to C:\Program Files\nodejs. Second, it added that folder to your system PATH — a list of places Windows looks when you type a command in Command Prompt. This is why you can type node from any folder and Windows finds it, instead of having to type the full path every time.

Third, it created a folder at C:\Users\[YourUsername]\AppData\Roaming\npm where npm stores global packages — packages you install once and use in many projects. You will not need to touch this folder directly.

The installer did not change any files on your computer besides adding these new folders. If you ever want to remove Node.js, you can uninstall it from Settings > Apps > Apps & Features, find Node.js in the list, and click Uninstall. This removes Node.js and npm completely.

Update Node.js when a new version comes out

Node.js releases updates regularly. You do not have to update when ready — LTS versions are supported for years. But when you do want to update, the process is straightforward: go back to nodejs.org, read the new LTS installer, and run it. The new version will replace the old one, and your projects will keep working.

If you have installed global npm packages and want to keep them, the installer has an option to preserve them. You will see a checkbox during setup that says "Automatically install the necessary tools" or similar — leaving it checked will preserve your global packages.

To check what version you currently have, open Command Prompt and type node --version again. Compare the version number to what nodejs.org shows as the current LTS. If yours is older, you can update whenever you have time.

Troubleshooting common installation problems

If you see "node is not recognized as an internal or external command" after installation, Windows has not yet registered the new PATH. Restart your computer completely — not just logging out and back in, but a full restart. After restart, open a new Command Prompt window and try node --version again.

If you installed Node.js but Command Prompt still does not recognize it after a restart, the installer may have failed silently. Uninstall Node.js from Settings > Apps > Apps & Features, restart your computer, then read the installer again and run it. This time, right-click the .msi file and choose "Run as administrator" before clicking Yes.

If you see an error about permissions when trying to use npm later, do not use sudo (that is a Mac and Linux command). Instead, open Command Prompt as administrator by pressing Windows key, typing cmd, right-clicking "Command Prompt", and choosing "Run as administrator". Then run your npm command again.

Frequently Asked Questions

Should I choose LTS or Current version?

Choose LTS unless you need a specific new feature. LTS versions are supported for years and are tested more thoroughly. Current versions change every few months and are for people who want the newest features and do not mind potential instability.

Do I need to restart my computer after installing Node.js?

Not always, but if Command Prompt does not recognize the node command right after installation, restart your computer. Windows sometimes needs a restart to register changes to the system PATH.

Can I have multiple versions of Node.js installed at the same time?

You can, but it requires extra tools like nvm-windows (Node Version Manager for Windows). For most people starting out, one version is enough. You can always uninstall and reinstall a different version later if you need to.

What is the difference between Node.js and npm?

Node.js is the runtime that runs JavaScript code. npm is the package manager that downloads and manages libraries. They are separate tools that install together — you need both, but they do different jobs.

Is Node.js safe to install on my work computer?

Node.js itself is safe — it is open-source software used by millions of developers. However, check your company's policy before installing any new software on a work computer. Some workplaces restrict what you can install.