JavaFX GUI for the popular neural-style Torch program.
Switch branches/tags
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


Neural Style GUI is designed for rapid prototyping art from Neural Style. To that end, it supports all Neural Style settings, a GUI designed around the process, immediate iterative feedback of results, session history, and saving and loading of style settings and images.


Inputs Tab of Neural-Style-GUI Layers Tab of Neural-Style-GUI Output Tab of Neural-Style-GUI Log Tab of Neural-Style-GUI


  • Neural-Style
  • Java 8
  • JavaFX 8 (included with Oracle, separate package for OpenJDK)


  • All Neural Style settings are supported, and most are grouped in a settings pane
  • Image lists for quick preview and selection of Style & Content images
  • Style image list supports single selection or multiple selections and weights
  • Layer selections, including parsing available layers from chosen Model/Proto files and adding/removing layers
  • Saving/Loading of all style settings, including input images, to a JSON format
  • Shortcuts for common operations
  • Immediate image feedback during iterations supports zoom/pan
  • Easy chaining of multiple Neural Style outputs for better large image quality
  • Quick permanent saving of feedback images
  • Output Queue for batching of style outputs
  • View session output image history
  • Load recently used settings or initialize with recently created images
  • vRAM usage gauge (NVIDIA only)
  • Log of Neural Style command output


Unzip the release to a folder of your choice (or build from source and check the target/jfx/app folder). Run the file or run java -jar neural-style-gui-*-jfx.jar with any additional options you desire.

Minimum Required Steps

  1. Set the Neural Style path
  2. Modify Advanced settings based on your machine, i.e., CPU or GPU and backend
  3. Set the Style Folder path to a folder containing style images
  4. Select a style image in the Style Image List
  5. Set the Content Folder path to a folder containing content images
  6. Select a content image in the Content Image List
  7. Press Queue
  8. Press Start!


After you have performed the Minimum Required Steps and chosen an Output Folder path, you may want to use the Save button in the Settings Pane to save all of this information into a 'default' settings file that you can load next time you run the application. If you're getting a File Not Found exception for the 'th' command because it's not properly in your PATH, you can set the path to 'th' below the Neural Style path.

The Chaining section of the Settings Pane allows you to quickly run multiple Neural Style commands that feed into each other with the previous result. A few settings that are commonly changed in this method are available. First, pick how many times to run the network. Then, the ratios determine those settings' values for each run. Basically, the current settings will apply to the final image in the chain, and for each result before the final image the values are multiplied by the ratio. For example, with a 0.5 Size Ratio over 3 runs for a final result of 1200px, the runs will start at 300px before going to 600px and finally 1200px. This can allow you to make higher quality and larger images than with a single run with single settings, and sometimes faster because less iterations are typically used with this.

The Progress Update and Image Update inputs under the Advanced Tab allow you to configure how often the Progress Bar and Output Images update.

The rest of the settings are better explained in the Neural-Style readme, but each input has helpful information in a tooltip if you hover over it for long enough. Numeric inputs can be controlled by their slider or input field; the input fields have unrestricted ranges while the sliders have reasonable ranges for each setting.

Choosing different Proto & Model Files will additionally try to parse the layer information and update the Layers tab with the appropriate layers.

The Input Tab and Style List can be quickly accessed with the shortcut Ctrl+S. In the default Single Selection mode, selecting a Style image will suffice. For Multiple Selection mode, pressing the space-bar on any selected Style image will toggle the Selected checkbox for that item. Weights can be adjusted by double-clicking the numerical value if using Multiple Selection mod. I find the best way to work with this list is to use the arrow keys for navigation and the space-bar for selection.

The Input Tab and Content List can be quickly accessed with the shortcut Ctrl+C. Because only one image can be selected here, the list's selection is used for image selection, so no checkbox is necessary.

The Layers Tab and Lists are normally filled with the default values for the default Proto & Model files, but they will update based on other Proto & Model file selections. It's possible to add or remove layers from these lists with the relevant buttons. Layers can be renamed by double-clicking their names.

The Output Tab can be quickly accessed with the shortcut Ctrl+O. Ctrl+Enter will Queue the current settings. Additionally, Ctrl+Shift+Enter will start the Neural Style Queue, and any time this process is started the Output tab is focused. The Fit to View and Actual Size buttons are quick ways to view the image. The mouse scroll-wheel zooms the image, and clicking-and-dragging pans. If an image with a different aspect ratio is loaded, the view is reset in the Fit to View mode. The Save Image button (and optional file name) will save the currently shown image to the selected Output Folder.

In the Output Tab and next to the Image is the Output Queue Tree. Any started process will show up here, and items are grouped by each process run. The top-level items contain a Load button to re-load the style settings used for that process. The child items are each iteration image, and can quickly set the Initialize With Image setting. With no selection, the Image will always show the most recent iteration processed. Selecting a top-level style will continuously update the Image with the most recent iteration from that process. Selecting a child image will only show that selection in the Image.

The Neural Style Log Tab will show the output from the most recent running process. This is rarely used, but it's helpful to understand why a process might have failed, usually because of out-of-memory errors.



  • Fixed an issue where 'nvidia-smi' was not available
  • New optional path to set 'th' in case it cannot be found


  • Support for recent neural-style features:
    • Initialization Image
    • Multi-GPU Setups
    • lbfgs nCorrection
  • Simple/Advanced Tabs in the Settings Pane
  • The most recently started Style is loaded when the app starts
  • Ability to quickly initialize with any previously generated images
  • Significantly improved performance when running many iterations repeatedly
  • History Tree is now a Queue Tree to show past and future outputs
  • The Neural Service now runs until all Queued items are finished
  • Chained runs allow larger images and better results
  • Bugfixes


  • Prototxt parsing supports current version of Loadcaffe Layers


  • Saving an Output Image also saves the Style with it
  • Style and Content Images are sorted by their name
  • Fixed an issue with the Output View and History not always recognizing the latest iteration


This GUI Application takes a small amount of the precious vRAM necessary for Neural Style, or even more if using CPU mode because the larger amounts of RAM used. If you find this inhibiting, consider using it for quick previews and using the generated command to run Neural Style without the GUI for final results. I have an advanced setup with bumblebee and vfio-pci, so this is not an issue for me.

Known Issues

  • Stopping/Cancelling a running Neural Style won't actually kill the process until the next output line is received, which can be a particularly long time if using infrequent progress updates or on slow computers.


Feature requests and development efforts for bug fixes and new features are certainly welcome. This project is developed using IntelliJ IDEA and the basic project for it is included in the repo.

IntelliJ IDEA Code Insight Issue

By default, IntelliJ IDEA restricts Code Insight to files of a small size, and the file is too large for this to work. This results in some files showing errors where Loadcaffe is used because it cannot parse the file. To get rid of these errors, you must follow the instructions in this Stack Overflow answer.


To see logging levels other than the default of just the NeuralService output, you can add the following option to the 'VM Options' setting in your Run Configuration (be sure to update the path to the included file): -Djava.util.logging.config.file=/path/to/