Where Do NW.js Apps Store User Data?
NW.js apps store local data per app under a Chromium-style user data folder named after the manifest name field on each OS.
Last updated
Every NW.js app gets its own user data folder, and the name comes from the app, not the framework. The manifest's name field decides the folder name under the platform's app-data root. Inside sits the usual Chromium furniture: Local Storage, IndexedDB, caches, and crash dumps.
That per-app naming is what separates one NW.js tool from another on the same machine. Wiping the folder resets the app to first-launch state without touching the install. Developers debugging storage issues should look here before blaming their code.
Where NW.js stores this, by platform
%LOCALAPPDATA%\<AppName>
Local Storage, IndexedDB, caches, and crash dumps for that app. <AppName> is the manifest name field verbatim. Override per launch with --user-data-dir.
~/Library/Application Support/<AppName>
Same per-app naming under Application Support. The folder appears on first run, so a missing folder usually means the app never launched successfully.
~/.config/<AppName>
Same convention under XDG config home. Crash-pad and cache subfolders can linger after uninstalls; they are safe to delete once the app is gone.
Frequently asked questions
Which folder belongs to my app?
Read the name field in the app's package.json manifest. The data folder uses exactly that string, which is why two apps from one developer still keep separate storage.
How do I relocate an NW.js app's data?
Pass --user-data-dir with a custom path when launching. Crash dumps may still touch the default spot, so check both locations when verifying a relocation.
Notice an outdated path? Let us know.