This article describes how to activate the Kendo UI for jQuery scripts from the CDN and NPM distribution by generating a personal license file.
Kendo UI for jQuery is a UI library distributed under a commercial license.
As of the R2 2022 release, using any of the Kendo UI for jQuery components from the NPM distribution channel and as of R3 2022 from the CDN distribution requires a license registration. Depending on the license type you own, you can register an active trial license or a commercial license key.
If you are experiencing any issues related to the license key, inform the team through the available support channels.
- The script license registration is required only for the commercial NPM package (
@progress/kendo-ui) and the CDN distribution. The other Kendo UI for jQuery commercial distributions or script sources require only an active license. This means that you don't need license registration when using NuGet, Bower, and for locally downloaded Kendo UI bundles.
- The license key will be distributed along with the scripts which cannot not be avoided. However, Progress recommends that you do not publicly announce it.
The license key installation process involves the following steps:
- Download a license file
- Add the license file in your application
- Add a Reference or Import the License File
This section contains auto-generated content based on the license information for your account.
To acquire a license file, generate it:
In order to register the Kendo UI product you need to add the
kendo-ui-license.js file in the root of the application or in the main scripts folder. The following table shows the most common location you can include it according to the type of application you are using.
|Type of Application||Common Locations|
|ASP.NET MVC applications||
|ASP.NET Core applications||
You can reference the
kendo-ui-license.js file by using either of the following approaches:
kendo-ui-license.js as a script reference right after the
kendo.all.min.js reference or the Kendo scripts you are using.
Example: using CDN reference - kendo.all.min.js
<script src="https://kendo.cdn.telerik.com/***/kendo.all.min.js"></script> <script src="./kendo-ui-license.js"></script> <!-- Rest of the HTML -->
Example: using CDN reference - using predefined list of scripts
<script src="https://kendo.cdn.telerik.com/***/kendo.core.min.js"></script> <script src="https://kendo.cdn.telerik.com/***/kendo.userevents.min.js"></script> <script src="https://kendo.cdn.telerik.com/***/kendo.draganddrop.min.js"></script> <script src="https://kendo.cdn.telerik.com/***/kendo.popup.min.js "></script> <script src="https://kendo.cdn.telerik.com/***/kendo.fx.min.js"></script> <script src="https://kendo.cdn.telerik.com/***/kendo.window.min.js"></script> <script src="./kendo-ui-license.js"></script> <!-- Rest of the HTML -->
kendo-ui-license.js file right after the import of the Kendo modules.
Example: using ESM modules
import "@progress/kendo-ui"; import "./kendo-ui-license.js"; $("#grid").kendoGrid();
Example: using CJS modules
require("@progress/kendo-ui"); require("./kendo-ui-license.js"); $("#grid").kendoGrid();
Often, you will need two or more imports of the Kendo UI libraries and you will need to import the license file only in one location, which most likely will be the main script file of your application. In that case, import the
kendo.core.js and register your license code as usual:
Example: using ESM modules
import '@progress/kendo-ui/js/kendo.core'; import './kendo-ui-license.js'; // The rest of the code.
Example: using CJS modules
require("@progress/kendo-ui/js/kendo.core"); require("./kendo-ui-license.js"); // The rest of the code.
This section lists the answers to the most frequently asked questions (FAQs) about working with the Kendo UI for jQuery license key.
Yes, but only If you upgrade the version of our product in your application with the new version.
This doesn’t affect your licensing key. The license key is generated against a specific range of versions and it will be valid as long as the license code is valid for the product version used (i.e., license file should be changed only when you upgrade the Kendo UI for jQuery).
For CDN usage: Starting from R3 2022
For NPM: Starting from R2 2022
No, the licensing mechanism doesn’t control the components behavior. Also, the licensing mechanism performs a check if the user (who authenticated in the docs to generate the license file) has license for the version of our product, used in the application. Note that our licenses are perpetual (see EULA)
Yes, the product will continue to function normally without a license key. However, a warning message will appear in the browser console if a valid license key is not present.
Yes, the license key expires at the end of your support subscription:
For trial users, this is at the end of your 30-day trial.
For licensed developers, this is when your subscription expires.
You will need to obtain and install a new license key after starting a trial, renewing a license, or upgrading a license.
NOTE: An expired license key is valid for all Product versions which are published before its expiration date.
No, the license activation and validation are performed entirely offline.
No network requests are made at any point of the project lifecycle.
To activate Kendo UI for jQuery you can use any of the keys associated with your subscriptions.
No, if you use CDN and a version released prior to R3 2022 and NPM with version released prior to R2 2022 you don’t need to set up the licensing.
- Create Your Own Custom Bundles
- Create Your Own Custom Widgets
- Initialize Widgets as jQuery Plugins
- Initialize Widgets with MVVM
- Widget Script Dependencies