Node-Webkit File Player – A File player for your desktop10 min read

A few days ago, Ignacio Tartavull reached out to me mentioning that he had built a file viewer based on Node Webkit powered Dashboard application and associated the node webkit app as the default opener for.ipynb files. Which I thought was a pretty genius idea. You can check out the INotebook app here.

Inspired by that idea, I have written a file browser/player app with node webkit that can “play” basic files like txt, log, json, md, mp3, mp4, png and jpeg.

Also, mustapha has reached out to me requesting another tutorial on Node webkit. And Mitesh Agarwal reached out to me requesting a post on a node webkit file viewer. So here it goes.

The final product we are going to build will look like

You can find the completed code here.

So, let us get started.


In this post, we will be building a nwk file player. This app will be built using node-webkit, Express.js and Angular.js.

If you are new to node-webkit refer

If you are new to Express.js refer

If you are new to Angular.js refer

We are also going to use a jQuery plugin named jstree. We will be leveraging this plugin in our app using an Angular directive. Also refer to the below post on how to build a file browser with this plugin

Setup project

We will be using a slush generator named slush-wean to scaffold a basic node webkit, Express.js and Angular.js app. And then we will build our application on top of it.

First, create a new folder named nwkFilePlayer. Open new terminal/prompt here. We will install gulp, slush and slush-wean modules globally. Run

npm install -g gulp slush slush-wean

Once this is done, we will scaffold a new wean app. Run

slush wean

and fill the project name as nwkFilePlayer. It will take a couple of mins to download all dependencies. Your final project structure would be like

To get an overview of the project structure, please refer the file browser app in the prerequisites above.

Now, to the run the app, we will execute

gulp run

For the first time, nwbuilder will run and download the required libs to run the nwk app for your OS. This may take upto 5 minutes. Once that is downloaded, nwbuild will launch the app. You will see a splash screen and then the boilerplate home page appears. Sweet scaffolder right!

Continue Development

Now that we have the boilerplate working, we will begin working on the app.

Our application logic is very simple. When the app loads, we will show all the folders right from the root on the left hand side of the app in a tree view. And when a user clicks on the resource, we play that file. Play here refers to viewing an image, displaying a md/log/json/txt file and playing media. A simple app that is more than a “media center”.

Open app.js and we will add 2 new routes.

Line 21 and line 22 point to the new routes which we are going to create. Next open routes/index.js and update it as below

Things to notice

Line 4 : Dispatches the main index.html

Line 8 : The logic for serving the tree. If the == 1  this means that the tree is loading for the first time. So, we dispatch the root files and folders. If not, we dispatch the files and folders from the requested path.

Line 24 : If a resource is selected, we dispatch the resource. If the resource is text based, we dispatch it completely. If the resource is media, we stream it for live playback.

“Client Side”

To manage “client side” dependencies, we will use bower. Before shipping the app, it is highly recommend to remove the unwanted files and ship the ones which are only required. Back to terminal/prompt, run

bower init

This will create a bower.json file. Next, create a file at the root of the project named .bowerrc. This file will consist of the bower config. Update it as below

To keep the code organized, we will delete the existing public/lib folder. So, all our dependencies are inside the libs folder. To add the required dependencies, run

bower i --save angular angular-route bootstrap jstree-directive jstree

It will take a couple of minutes for all the dependencies to be downloaded.

Now, we will work on the User Interface. Open views/index.ejs and update it as below

Here we refer the downloaded libraries. We will update the existing public/partials/head.html to reflect the App name. Update it as below

Finally the main view of the app. The Tree and the players. Create a new file named home.html inside public/partials folder and update it is as below

Next, we will setup the Angular.js code. Open public/js/app.js and update it as below

We have added a HomeCtrl – The main controller for the app and a default route.  Next, we will create a Factory to interact with the Express.js server.

Create a new file named factory.js inside the public/js folder and update it as below.

Things to notice

Line 1 : Our resource factory. This factory is responsible for fetching the resource when we click on a file in the browser.

Line 15 : A Factory that is responsible for maintaining a single instance of the Audio tag. So, that only one file plays at once. We are not going to use any of the API methods written here except  play(fileName) and stop() .  But you can use this code to customize or rebuild a custom player with your own controls.

Line 56 : A factory for Video tag. Same purpose as above.

This way we can have more control on the Audio and Video elements.

Finally the controller. Create a new file named controller.js inside public/js folder. Update it as below

Things to notice

Line 5 : This function will get triggered when a user clicks on a tree node/leaf. We check if the clicked node/leaf is a leaf and then start processing it on line 24.

Line 27 : We determine the extension of the file and depending on it, we trigger the respective media players. If it is a text/image file we simply fetch the resource and display it.

As of now, we are supporting only a mp3/mp4 and log, txt, json and md file types. You can add your own file types and dispatch an appropriate response from routes/index.js when the file is requested.

Using the video & audio tags inside Node Webkit

This is one of the most important steps. By default node webkit ships with only open source libraries. But if you want to play mp3 or mp4 files you need to modify the node webkit binaries.

Due to licensing issues, the pre-built binary doesn’t ship with the necessary codecs for patented media formats. If you require support for these formats, see the instructions below.

Consult a lawyer if you do not understand the licensing constraints and require patented media formats in your application.

So once we update the binaries with the new ffmpegsumo file for your OS, your project will automatically become a GPL licensed.

Below is how we enable Mp3 and Mp4 support for our app.


  1. Locate the Chrome\Application folder (e.g. C:\Program Files\Google)
  2. Copy ffmpegsumo.dll to your node-webkit distribution directory


  1. Head to your Applications folder and right-click on Google Chrome. Select Show Package Contents and navigate to Versions > Most recent # > Framework > Libraries.
  2. Copy to  /nwkFilePlayer/node_modules/node-webkit-builder/cache/0.10.5/osx/ Framework.framework/Libraries

You can find more info on how to set up for your OS here.

Note : Every time you download a new instance of node-webkit, be sure to update this.

Finally to cleanup the UI, we will apply styles. Delete public/css/bootstrap.css. Open public/css/app.css and update it as

Create another folder named imgs inside the public folder and download the images from hereThis will be the icons for the tree.

That is it. Now save all the files and execute

gulp run

And you should see your file browser/player!

If you want to distribute the app, you can use the gulp build task for the required Operating System.

Hope this post gave you a decent idea on how to work with file system, node modules and HTML5 media elements.

Thanks for reading! Do comment.