For most developers, the correct Node.js setup in 2026 is the latest LTS release from the official Node.js download page. Choose a version manager instead when you regularly switch Node versions between projects. After installation, open a new terminal and verify both node and npm.
Choose your installation method first
Your best method depends on whether you need one stable runtime or several project-specific versions.
| Situation | Recommended route | Why |
|---|---|---|
| Most personal projects or a new machine | Official LTS installer | Simplest setup with a stable support line |
| Projects require different Node versions | Version manager | Install and switch versions without replacing the system installation |
| You explicitly need the newest release line | Official Current release | Earlier access to new features, with more frequent change |
| Automated or minimal Linux environment | Official binary or package route documented for that release | Useful when an interactive installer is unsuitable |
Do not confuse a version manager with npm. npm is the package manager distributed with Node.js in the official installation flow; a version manager controls which Node.js runtime is active.
LTS versus Current: which release should you install?
Use LTS unless a project, framework, or team explicitly requires another line. LTS is the normal choice for production work and learning because it prioritizes a longer maintenance window. Current is the newest release line and is appropriate when you need its specific features or are testing upcoming compatibility.
#1 Best Overall
The official download page showed v24.21.0 LTS, v22.23.2 LTS, and v26.10.0 Current when checked for this article. Those numbers are a dated snapshot, not permanent instructions. Select the LTS label shown on the live page when you install.
Before you download
- Identify your operating system: Windows, macOS, or Linux.
- Identify your processor architecture. Common choices include x64 (Intel/AMD 64-bit) and ARM64 (Apple silicon and many ARM systems).
- Check your project’s required Node range in its documentation or
package.json. - Use administrator privileges only when your operating system’s installer requests them.
Do not assume that every release offers every architecture. The official archive shows the assets available for each version. For example, an archived v22 release lists Windows x64, x86 and ARM64 packages; macOS x64 and ARM64 packages; and Linux binaries for x64, ARMv7, ARM64, ppc64le and s390x.
Install with the official package
Windows
- Open the official download page.
- Select the current LTS release and choose the Windows installer matching your architecture, normally x64 or ARM64.
- Run the downloaded installer. Keep the default features unless your organization has a specific layout requirement; npm is included.
- Finish the wizard, then close any Command Prompt, PowerShell or terminal windows that were already open.
- Open a fresh terminal and verify the installation with the commands below.
macOS
- On the official download page, select the LTS release.
- Choose the macOS package matching your Mac: ARM64 for Apple silicon or x64 for Intel.
- Open the package and complete the installer prompts.
- Start a new Terminal window so the updated PATH is loaded.
- Run the verification commands.
Linux
For a one-version machine, use the official Linux binary or the installation route documented by Node.js for your distribution and architecture. The archive separates prebuilt Linux files by architecture; select the exact asset for your system rather than copying a command intended for another platform.
If you need version switching, use the version-manager instructions on the live download page. The official page provides an nvm flow for Linux that installs nvm, loads it in the current shell, installs Node.js and verifies node -v and npm -v. Follow that page’s current script and shell-specific steps instead of pasting an old command from an unrelated tutorial.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
Node.js warns that third-party installation scripts are not maintained by the Node.js project. Treat community scripts and package-manager recipes as separate, unofficial choices and review them before use.
Use a version manager when projects differ
A version manager is worthwhile when one project targets an older LTS while another tracks a newer line, or when a team’s setup documentation requires exact versions. It also lets you test an upgrade without overwriting the version used by an existing project.
- Read the current version-manager instructions on the official download page for your operating system and shell.
- Install the manager using those instructions.
- Install the Node.js version required by each project.
- Select the project’s version before running its package commands.
- Confirm the active runtime with
node -vand confirm npm withnpm -v.
Do not select a manager merely because it is popular. The Node.js Foundation’s 2017 survey reported that 76% of respondents used a version manager, typically NVM; that historical figure does not establish current usage and should not decide your setup by itself.
Verify Node.js and npm
Open a completely new terminal after installation and run:
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesRank #3
node -v
npm -vnode -v should print the active Node.js release, while npm -v should print npm’s version. If both commands return versions, the basic installation is available on your PATH. A new terminal matters because an already-open shell may still have the old PATH.
For a harmless runtime test, run:
node -e "console.log('Node.js is working')"You should see Node.js is working.
Verify downloaded files when using standalone binaries
If you download a release file directly instead of relying on an installer, use the signed SHASUMS and verification instructions linked from the official archive. Match the checksum file to the exact version and asset you downloaded. Do not substitute an unverified checksum command copied from a different release or operating system.
Common installation problems
node or npm is not recognized
Cause: the shell was open before installation, or the installer did not add Node.js to PATH. Close all terminals, open a new one and retry. If it still fails, rerun the official installer and inspect its PATH option, then restart the shell again.
The wrong version appears
Cause: another Node installation or version manager is earlier on PATH. Check which executable is being selected with your operating system’s command lookup, then remove stale installations or select the intended version through your manager. Avoid mixing several managers unless you understand their PATH order.
Recommended Free Tools
Rank #4
The installer architecture is wrong
Cause: an x64 package was selected for an ARM device, or vice versa. Return to the download page or archive and choose the asset matching the processor architecture reported by your operating system.
npm exists but a project will not install
Cause: the project may require a different Node range, an existing lockfile, private registry credentials or native build tools. Read the project’s setup documentation, select its required Node version and then run the project’s prescribed install command. Do not replace the runtime repeatedly until you have checked the declared requirements.
A Linux shell cannot find nvm after installation
Cause: the manager’s initialization was not loaded into the current shell. Follow the live official nvm instructions for your shell, start a new terminal and verify with node -v and npm -v. Shell startup files differ, so do not assume a Bash instruction applies unchanged to another shell.
A direct binary fails an integrity check
Delete the file, download the matching asset again from the official archive and repeat the signed SHASUMS verification. Do not run an unverified binary.
Performance, maintenance and security choices
- Prefer LTS for routine work: it reduces avoidable compatibility changes while you build or maintain applications.
- Pin project requirements: record the expected Node range in project documentation and use the project’s lockfile consistently.
- Keep one authority: obtain release files from Node.js download or archive pages, not mirrored downloads of uncertain origin.
- Refresh your terminal after changes: PATH and version-manager changes are usually visible only to newly started shells.
- Plan upgrades: test a new Node line against dependencies before changing a production runtime.
Or skip the browser setup
If you are documenting this installation in a guide and need clean screenshots of the Node.js pages, ScreenshotNeo can return an image or PDF from one API request. Its pre-capture cleanup accepts cookie banners and removes more than 60 known consent platforms, newsletter popups and chat widgets; bot checks, blank pages, failed loads and timeouts are not billed, and response headers identify the page verdict and billing result. An MCP server provides take_screenshot, get_page_info and capture_pdf tools for Claude, Cursor and other MCP clients.
Example (see the complete ScreenshotNeo documentation):
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://nodejs.org/en/download/ -o node-download.webpThe Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. Create a free ScreenshotNeo account.
FAQ
Can I install Node.js through npm?
No. npm is included with Node.js; install the runtime first, then use npm to manage packages.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Should I uninstall an older Node.js release?
Remove obsolete installations when they conflict with your PATH. If you use a version manager, let it control the active versions instead of layering unrelated installers.
Which Node.js version should a team document?
Document the LTS line or exact version required by the project, along with the command your team uses to select it.
The Bottom Line
Install the LTS release shown on the official Node.js download page, choose the package for your operating system and architecture, use a version manager only when you need multiple versions, and verify the result in a fresh terminal with node -v and npm -v.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
