You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NW.js is an app runtime based on Chromium and node.js. You can
write native apps in HTML and JavaScript with NW.js. It also lets you
call Node.js modules directly from the DOM and enables a new way of writing
native applications with all Web technologies.
It was created in the Intel Open Source Technology Center.
Good performance: Node and WebKit run in the same thread: Function calls are made straightforward; objects are in the same heap and can just reference each other.
Easy to package and distribute apps.
Available on Linux, Mac OS X and Windows.
Downloads
v0.106.0: (Nov 23, 2025, based off of Node.js v25.1.0, Chromium 143) : release notes NOTE You might want the SDK build. Please read the release notes.
<!DOCTYPE html><html><head><title>Hello World!</title></head><body><h1>Hello World!</h1>
We are using node.js <script>document.write(process.version)</script>.
</body></html>
$ /path/to/nw . (suppose the current directory contains 'package.json')
Note: on Windows, you can drag the folder containing package.json to nw.exe to open it.
Note: on OSX, the executable binary is in a hidden directory within the .app file. To run node-webkit on OSX, type: /path/to/nwjs.app/Contents/MacOS/nwjs .(suppose the current directory contains 'package.json')
NOTE: Links to the old google group (e.g. https://groups.google.com/forum/#!msg/node-webkit/doRWZ07LgWQ/4fheV8FF8zsJ) that are no longer working can be fixed by replacing node-webkit with nwjs-general (e.g https://groups.google.com/forum/#!msg/nwjs-general/doRWZ07LgWQ/4fheV8FF8zsJ).
Issues are being tracked here on GitHub.
The source code for NW.js and the daily development spans multiple repositories in this organization. This repository is for issue tracking, landing page, and part of the source code.
Verifying Binaries
Starting from 0.32.0 the stable and nightly download directories contain a SHASUMS256.txt
file that lists the SHA checksums for each file available for download, as well as the
checksums for the files inside the download package.
The stable releases (but not Nightlies) also have the GPG detached
signature of SHASUMS256.txt available as SHASUMS256.txt.asc. You can use gpg
to verify that SHASUMS256.txt has not been tampered with.
To verify SHASUMS256.txt has not been altered, you will first need to import
the GPG key of NW.js maintainer to create releases.
Use this command to import the key:
After downloading the appropriate SHASUMS256.txt and SHASUMS256.txt.asc files,
you can then use gpg --verify SHASUMS256.txt.asc SHASUMS256.txt to verify
that the file has been signed by an authorized member of the NW.js team.
Once verified, use the SHASUMS256.txt file to get the checksum for
the binary verification command above.
