Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
For most developers, the right way to install Node.js is to download the current LTS release from the official Node.js download page, choose the installer or binary for your operating system and processor, then open a fresh terminal and verify it with node -v and npm -v. Use a version manager instead if you expect to switch Node.js versions between projects. LTS is the sensible default; choose the Current line only when a project or feature specifically calls for it.
Choose the installation method that fits your work
There is no single installer that is best for every machine. The practical decision is whether you need one Node.js version or need to switch among versions, and then which official package matches your operating system and processor.
| Your situation | Recommended route | Why |
|---|---|---|
| You are setting up a typical development machine | Download the current LTS installer from the official Node.js page | It is the straightforward route when one version is enough. |
| Your projects require different Node.js versions | Use a version manager and follow current instructions for your operating system and shell | A version manager is designed to install and select versions as needed. |
| You explicitly need the newest release line | Choose Current from the official download page | Current is distinct from LTS; do not select it merely because its number is higher. |
| You are installing a standalone release file | Use the official archive, select the matching asset, and consult its signed checksum verification instructions | Package and binary availability varies by version, operating system, and architecture. |
Node.js bundles npm in the official installation setup, so you ordinarily do not need to install npm separately. A version manager is also not npm: one manages Node.js versions, while the other is the package manager you use with Node.js.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesPick LTS or Current
For ordinary project work, select LTS (Long Term Support) unless the project documentation requires another release. LTS is the conservative choice for a general setup. Select Current when you have a concrete reason to use the newest release line, such as a project requirement or a need to work with a feature available there.
#1 Best Overall
Release labels and numbers change. On the official download-page snapshot for September 30, 2026, the listed releases were v24.21.0 LTS, v22.23.2 LTS, and v26.10.0 Current. Treat these as a dated snapshot, not permanent recommendations: consult the live download page when you install and choose the LTS release it currently offers, unless your project specifies otherwise.
If a project names a specific Node.js major or exact version, follow that project requirement rather than automatically installing the newest LTS. This is especially important when you work on several projects: the version that suits one repository may not be the one another expects. That is the point at which a version manager is useful.
Install Node.js with the official installer
- Open the official download page. Go to nodejs.org/en/download. Confirm that you are choosing the LTS release unless you have a reason to use Current.
- Match the package to your system. Choose the operating system and processor architecture that match your computer. Do not assume every release offers the same combinations. If you are unsure which architecture applies, check your operating system’s system-information settings before downloading.
- Download and run the offered installer. Use the official page’s current package choice for your platform. Follow the installer prompts and let it finish. The labels and flow can vary by operating system and release, so follow the current on-screen instructions rather than a command copied for a different platform.
- Open a new terminal. A terminal window that was already open during installation may not have refreshed its command search path. Close it and open a fresh one before checking the installation.
- Verify both commands. Run
node -vand thennpm -v. Each should print a version. The Node.js version should be the release you intended to install; the npm version confirms that the package manager command is available.
The exact installer steps differ across Windows, macOS, and Linux, and the official download page is the authority for its current options. Avoid applying instructions for one operating system or shell to another.
Recommended Free Tools
Use a version manager when projects need different versions
A version manager is the better fit when you regularly move between repositories that require different Node.js versions. Instead of relying on one system-wide installation, you follow the manager’s instructions to install and select the version needed for a project. The setup depends on your operating system and shell; use instructions that explicitly match both.
Rank #2
The official Node.js download page currently includes a Linux installation flow using nvm. It covers installing nvm, loading it in the current shell, installing Node.js, and checking node -v and npm -v. Use the live page to obtain the current commands. Do not copy a Linux shell command into Windows or macOS instructions without confirming it applies to your environment. Detailed Windows and macOS version-manager commands are not established here, so use the manager’s own current documentation for those systems.
Node.js warns on its download page that third-party installation scripts are not maintained by the Node.js project. That warning matters when you choose a version-manager setup: distinguish official Node.js downloads and instructions from community-maintained managers or scripts. A community tool can still be useful, but do not mistake it for a project-maintained installer.
Choose a direct archive package carefully
The official Node.js archive is useful when you need a particular release or a standalone package rather than the current download-page choice. Select the exact release first, then check that its asset matches both your operating system and processor architecture. Do not infer that an asset exists for every platform just because it appears in another release’s archive listing.
For example, the archived v22.22.0 listing includes Windows x64, x86, and ARM64 packages; macOS x64 and ARM64 packages; and prebuilt Linux binaries for x64, ARMv7, ARM64, ppc64le, and s390x. These are options for that archived version, not a guarantee that every version has the same set. Consult the archive entry for the release you actually need.
Rank #3
The archive links signed SHASUMS and verification instructions. If you download a standalone release file, follow those official instructions to check its integrity. Use the verification method linked for that release rather than relying on an unverified checksum command.
Confirm the installation and find the active version
In a newly opened terminal, run:
node -v— prints the Node.js version available to that terminal.npm -v— prints the npm version available to that terminal.
If both commands print versions, the basic command-line installation is available. If node -v prints a different version than expected, you may have another installation or a version manager selecting a different one. Check which installation method you used and, if you use a version manager, follow its current instructions for selecting the intended version.
Troubleshoot common installation problems
“node” or “npm” is not recognized or not found
The terminal cannot find the command. First close the terminal and open a new one, then retry both version commands. If they still fail, check that the installer completed and that you selected the package for the correct operating system and architecture. If you used a version manager, follow its instructions for loading it into your current shell; the official Linux nvm flow specifically includes loading nvm in the current shell.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallThe version shown is not the one you expected
You may have selected a different release, or another installation or version-manager selection may be active. Compare the output of node -v with the version required by your project. Revisit the official download page for the current LTS choice, or consult your version manager’s instructions for selecting the project-required release. Avoid installing a second method on top of the first until you understand which one your terminal is using.
Rank #4
The downloaded file does not match your computer
Check the operating system and processor architecture again, then select a matching asset from the official download page or the specific release in the archive. Available packages differ by release. Do not substitute an x64 package for an ARM package based only on the operating system name.
A standalone download fails an integrity check
Do not use the file if its verification fails. Return to the archive entry for that exact release and follow its linked signed SHASUMS verification instructions. If needed, download the file again from the official archive and repeat the documented check.
A project still fails after Node.js is installed
A working node -v does not prove that the active version matches every project’s requirements. Check that repository’s setup instructions and required Node.js version. If several projects need different versions, use a version manager rather than repeatedly replacing a one-version installation.
Installation reliability and cost
Downloading Node.js from the official project page or archive avoids guessing which third-party package matches a release. A direct installer is convenient for a single-version setup; a version manager adds a selection step but is better suited to projects that need different versions. With standalone archive downloads, the official signed checksum instructions add an integrity check.
The material here does not establish a universal installation time, performance difference, or current adoption rate for version managers. A 2018 Node.js survey report described three in four users as using a version manager, typically NVM, based on a 2017 figure. That is historical context only and should not be read as a 2026 estimate.
Or skip the browser setup
Node.js is for building and running JavaScript applications. If your next task is to capture website screenshots from code, ScreenshotNeo offers a separate screenshot API: make one GET request with a URL to receive a PNG, JPEG, WebP, or PDF. See the ScreenshotNeo documentation for API options.
For example, this cURL request captures Stripe as WebP:
Free tools Windows power users keep installed
One-click scans. No signup required.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
ScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each of those steps can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.
The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots. Every feature is on every plan, and yearly billing gives two months free. If you need website screenshots rather than a local Node.js installation, sign up for ScreenshotNeo free.
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.
