[Solved] Kendo JavaScript inclusion in deliverable

1 Answer 16 Views

Licensing

1 Answer, 1 is accepted

answered on 20 Aug 2026, 03:17 PM

Hi Robert,

For Kendo UI for jQuery delivered through local JavaScript files or a custom bundle, the recommended approach is to generate a script license key (KendoLicensing.setScriptKey(....)) and include it in a JavaScript file such as telerik-license.js.

The script key is intentionally designed to be distributed with the client-side application. It is safe to redistribute because it only unlocks the Kendo UI product and is required for the application to run. It is expected that users can view the key in the browser developer tools or obtain it from the delivered JavaScript.

The script key is not a password or an authentication credential. It does not provide access to your Telerik account, private package feeds, source code, or server-side services. You should continue to protect those credentials and any other application secrets, but the script key itself does not need to be treated as a secret.

For local-file delivery, load the scripts in this order, exactly once:

<script src="./kendo.all.min.js"></script>
<script src="./telerik-license.js"></script>

The license script must be loaded after the Kendo UI scripts and before any Kendo UI components are initialized.

This is different from the telerik-license.txt file used for npm or build-time activation. That file contains a personal license key and should not be committed to source control or exposed unnecessarily. It is not the file that needs to be delivered to browser users when using the script-key approach.

You can find more information for the licensing at:

Regards,
Rumen
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.