FAQ

  • We follow the Chromium schedule and start upgrading Chromium to the latest stable release as soon as it’s available for download. An upgrade to a new Chromium version takes 3-4 weeks depending on the number of changes in the latest Chromium version.
  • The format of the video you are trying to play might not be supported by JxBrowser. Please check the list of supported video and audio formats.
  • No, since JxBrowser is based on the desktop version of Chromium. For the complete list of supported platforms, please see the System requirements page.

  • JxBrowser provides the Swing, JavaFX, SWT, and Compose BrowserView components that can be embedded into a Java GUI application to display the content of a web page. This component does not include the tabs and address bar with the back and forward buttons. Such controls are part of a standalone browser like Google Chrome.


    We decided not to provide such GUI controls and recommend that our customers develop their own tabs, address bar, etc. using JxBrowser and appropriate UI toolkit API. It is because every Java GUI application provides its own requirements for the GUI look and feel, label texts, internationalization, button icons, etc. and providing our own controls based on our own GUI guidelines would not meet the requirements of most Java applications.

  • The size of JAR files can’t be reduced.


    The biggest part of the JxBrowser distribution is the Chromium binaries. To minimize their size, we build optimized native code and include only the files required for JxBrowser. The binaries are already as compact as possible.


    When packaging your application, include only the Chromium binary JAR that matches the target platform, but not others. A typical application needs only three JAR files at runtime:

    • — jxbrowser-8.13.0.jar ~13MB.
    • — jxbrowser-<UI TOOLKIT>-8.13.0.jar ~200KB.
    • — jxbrowser-<PLATFORM>-8.13.0.jar 85MB+.


    Alternatively, you can host binaries in a shared location and download them at runtime using custom delivery.

  • Yes. JxBrowser works in the WebSwing environment in the OFF_SCREEN rendering mode.
  • No. JxBrowser uses an in-house embedding technology that we have been independently developing since 2008.
  • No. JxBrowser works offline and does not require access to external servers. In particular, license checks are performed locally.
  • Yes. Commercial JxBrowser licenses are perpetual, so JxBrowser will continue to work. Subscription expiration only affects access to updates and support.