Construct 3 NW.js desktop app [Deprecated]

5 favourites
From the Asset Store
Casino? money? who knows? but the target is the same!
  • The NW.js version of the editor is being retired

    Update May 2022: Historically we distributed files that allowed running Construct 3 in NW.js. The download files for this were provided in this post. However support for this is being removed. Please switch to using Construct in the browser at instead.

    For testing NW.js features in your project, you can still use the Remote Preview for NW.js tool below.

    All other NW.js features are still supported, such as exporting your projects with NW.js. Only running the editor in NW.js is being retired.


    In the past browsers lacked many desktop-style features like accessing local files, integrating with external image editors, and associating with the .c3p file extension. Over time pretty much all of this has now come to Chromium-based browsers. For example since Chrome 86 local file & folder saves are now supported using the Chrome browser. Other features like copying and pasting images, and as of Chrome 102 support for associating the .c3p file extension, mean that there are basically no good reasons left to use Construct in NW.js.

    Meanwhile we have a lot of complicated code to support some NW.js features, there have historically been lots of difficult bugs that only happen in NW.js and don't happen in browsers, the NW.js editor has been effectively unmaintained for some time now, and only a very small number of Construct users still use the NW.js editor. Therefore we have decided to retire the NW.js editor and only support Construct in the browser.


    Using Construct in NW.js is now deprecated. Support will be removed in future. You should switch to using Construct in the browser now to avoid ending up with broken software later on.

    As of Construct 3 r296+, a warning message will appear when using the editor in NW.js indicating that support will be dropped.

    The code for NW.js specific editor features will be removed in the next release cycle (the first beta release after the next stable release), around June or July. Beyond that point we cannot guarantee that the editor will keep running at all in NW.js: it may stop working at any time and we will not fix any issues or provide any support for it.

    Remote Preview for NW.js

    This tool allows you to test your project with NW.js features when using the editor in the browser. Download it here:

    Follow these instructions to use it:

    1. Download the file linked above.
    2. Download the version of NW.js you want to use from Note: We recommend downloading the 'SDK' version because it provides the browser dev tools, which are useful for development. The 'Normal' version does not include dev tools.
    3. Extract both the package file and a version of NW.js to the same folder (so both nw.exe and package.json are the same folder).
    4. Run nw.exe. You may need to approve a security prompt, or wait for an antivirus scan.

    Remote Preview for NW.js loads in NW.js. This works the same as it does in the Chrome browser, but the features of the NW.js object will work since it's running in NW.js. You can start a Remote Preview in the editor, and then load it in Remote Preview for NW.js.


  • Let's see...current memory usage...

    Running C3 in Chrome (with no other tabs open).......667 mb

    Running C3 desktop build beta......................................157 mb

    Yeah, I know what I'm using from now on.

  • Lancifer - if I try comparing the memory usage and leave them idle for a minute (so they garbage collect/compact memory etc), then the difference is only about 50mb (~190mb vs ~240mb). I mean, they use the same browser engine, so it's expected their memory usage would be similar.

    If you have a browser addon that wastes tons of memory, that could explain the difference, but that's the addon, not Chrome. (I've seen some ad blockers can waste hundreds of megabytes of RAM!)

  • Chromes not known for being light on its feet.

    Of course that does beg the question of why use it as the default.

  • Ashley

    Right, I understand that. But, I shouldn't be expected to have to disable my addons every time I use C3. I do appreciate the effort in giving us an alternative, though. Thanks.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • Thank you! I was waiting for this

  • Thanks! Looking forward to using this for source control (I use bitbucket / git). Just last week I lost a day of work due to a user (i.e. me) cloud save / local *.c3p mixup that source control could have saved for me.

    I do still like the browser option of working anywhere I have chrome, so will still use that sometimes too.

  • Nice job guys, looking good. Will get in and do some testing in the near future.

  • Yes! Project saves. Now every time I save, it doesn't resave the ~1GB of video I'm currently using. Thanks!

    Edit: FYI I spent 30 mins making some changes, saved it as a project, tried to open it again and the app crashes. No error code or message.

  • Great upgrade to Construct 3 !

    The next step should be a permanent purchase option for those who can't stand subscription model.

    I hope to see this coming, for now... I'll have to use other options.

    Anyway, keep up the good job! it's looking great so far.

  • Oh wow, finally a desktop build.

    Thanks a lot Ashley, I've been waiting for this.

    Also, I agreed with Alon. Please also include a one-time license model, subscription models aren't really good for some companies/developers.

  • Great, thank you! ๐ŸŽˆ๐Ÿ˜ƒ ๐ŸŽˆ

  • Well done! thanks

  • Wow! Nice Work!

    Now i get 1/2GB RAM free....

    I know its use the same engine.... but i have addons and other things on my Chrome Browser making alot of RAM used for anything, now with this version of C3 i using only 100- MB

    Keep the Awesome work!

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)