JxBrowser is a commercial library that requires a valid license key in order to work. This guide focuses on technical aspects of working with the licenses.

For pricing information and details on terms and conditions please see the Licensing and Pricing section at the product page of our main website.

See also our video tutorial that shows how to get and install a license key:

Adding the License to a Project

JxBrowser needs a license key, which represents a string with combination of letters and digits. The key must be provided to the library using one of the following ways.

You can provide the key via the jxbrowser.license.key System Property. For example:

System.setProperty("jxbrowser.license.key", "your_license_key");

Only one license key could be configured through this system property. It is possible to use separate license keys for different Engine instances:

Engine engine = Engine.newInstance(

Setting the license key through the API allows you to override the license key specified in the jxbrowser.license.key System Property.

Evaluation License

Before purchasing a commercial license you can evaluate the product for 30 days. Evaluation is free.

To request Evaluation License please fill in this form. You will receive an email message with a 30-days evaluation license key.


The evaluation period starts right after you request an Evaluation License at our website. In 30 days the license stops working.

If you request another 30-day Evaluation License, it will not work in the environment where you already tried the previous, already expired license.

Extending Evaluation Period

There might be cases when your company’s procurement procedures take longer than 30 days. If you need more time to finalize the purchase formalities, please contact our Sales team at with brief details of your situation.

Commercial Licenses

When you purchase a commercial license, we will send you an email with a license key.

You can use this license key both for development of your application with JxBrowser, and for distribution of our library as part of your application.

Per Developer License

This kind of license can be issued to a company or an individual.

The license is not tied to a person name. So, if a developer stopped working on the project and another one picked up that work, you do not need another license.

The only requirement is that the number of licenses should equal to the number of developers involved in the project, which uses JxBrowser.

If you have 5 developers involved into your project and only 2 of them work with JxBrowser, you need 2 licenses only.

When you purchase a commercial license for 2 developers you will get one license key that can be used by 2 developers in your company.

If you have a team of 3 and more people using JxBrowser and you plan to do one project only, you may want to purchase a Project License.

Project License

The license is issued to a company.

The license is tied to a package of your project. When you purchase a Project license we will ask you to provide the name of the package where you will be creating an Engine instance. You can work with the created Engine instance and make calls to the library’s API in other packages without any restrictions.

The package name is expected to be in the format.

This option is cost effective for three or more developers working on a product.

Company-Wide License

Grants you an unlimited number of developers for any number of projects in your company. This option is cost effective with more than 10 developers planned for a project, or for more than 3 projects.

Chromium Open-Source Components’ Licenses

JxBrowser is based on the open-source Chromium project that includes the source code and libraries written by developers in the Chromium community. The project also includes a number of open-source third-party libraries.

JxBrowser is using Blink and FFmpeg components, supplied under LGPL. Learn more about JxBrowser Compliance with LGPL.

One of the key questions arising when an open-source code is used in commercial products, is the permitted use of the open-source code, and possible restrictions of use and distribution of the works based on this open-source code.

We are performing a regular review of the licenses, associated with the Chromium components used by JxBrowser, to make sure that there are no terms that would restrict the commercial distribution of JxBrowser or the customer applications using it. We also make sure that licenses requiring disclosure of the source code (like GPL) do not apply to JxBrowser or applications based on it.

Please see below the links to Chromium components’ licenses associated with JxBrowser releases:

If you have any questions, not covered by this article, please email us at

Go Top