New to Kendo UI for jQuery? Start a free 30-day trial

Using CDN

Updated on Nov 6, 2026

Use jsDelivr to load Kendo UI for jQuery from its NPM packages without hosting the assets locally. Pin the Kendo UI and theme package versions in each URL and use the matching Subresource Integrity (SRI) value.

As of the R3 2022 release, you must activate the CDN distribution by adding your script license key.

Installation Steps

  1. Add the required CSS and JavaScript files.

Load a theme from the @progress/kendo-theme-default package. This example uses the 14.5.0 version of the Ocean Blue theme:

html
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@progress/kendo-theme-default@14.5.0/dist/default-ocean-blue.css" integrity="sha256-eNPRBUJRAdbNuZjjM0HWX4qWYUQONec3soGf9AgbjbE=" crossorigin="anonymous" />

Starting with the 2023 R3 release, the font icons are detached from the Kendo Themes CDN. For more information on referencing the icons in your project, see the font icon usage documentation.

Add the JavaScript files by using either the JavaScript modules or the bundled JavaScript files.

The JavaScript modules are located in the /esm/ folder. To include a JavaScript module in your project, use the script tag with the type="module" attribute.

The following example demonstrates how to include an individual component module from version 2026.4.1111.

html
<script src="https://cdn.jsdelivr.net/npm/@progress/kendo-ui@2026.4.1111/esm/kendo.grid.js" type="module"></script>

The following example demonstrates how to include the bundled module file.

html
<script src="https://cdn.jsdelivr.net/npm/@progress/kendo-ui@2026.4.1111/esm/kendo.all.js" type="module"></script>

The UMD bundles are located in the /umd/ folder. To load the full bundle, use the exact Kendo UI version and its matching SRI value:

html
<script src="https://cdn.jsdelivr.net/npm/@progress/kendo-ui@2026.3.811/umd/kendo.all.min.js" integrity="sha256-Bjy6F9ho2vlkrHseUGTTc+Y6swvrpO7a10REh+IJHD4=" crossorigin="anonymous"></script>

To load the smaller Core bundle, use https://cdn.jsdelivr.net/npm/@progress/kendo-ui@2026.3.811/umd/kendo.ui.core.min.js with its matching SRI value:

html
<script src="https://cdn.jsdelivr.net/npm/@progress/kendo-ui@2026.3.811/umd/kendo.ui.core.min.js" integrity="sha256-/wzJ3w2XwU5qiMCixBzKG0oQkxEJryRsnOB4uiyKNYE=" crossorigin="anonymous"></script>
  1. Add your script license key.

Generate and reference your script license key by following the current licensing instructions for CDN-based installations.

  1. Add the HTML element and initialize the component.

Depending on the component you require, you can initialize the Kendo UI controls from different elements. The following example demonstrates a complete page that adds the input element, loads the CDN assets, and initializes a DropDownList with basic configuration.

Example
View Source
<!DOCTYPE html>
<html lang="en">
    <head>
        <meta charset="utf-8">
        <title>Kendo UI using CDN</title>

        <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@progress/kendo-theme-default@14.5.0/dist/default-ocean-blue.css" integrity="sha256-eNPRBUJRAdbNuZjjM0HWX4qWYUQONec3soGf9AgbjbE=" crossorigin="anonymous" />

        <script src="https://code.jquery.com/jquery-3.7.0.min.js"></script>
        <script src="https://cdn.jsdelivr.net/npm/@progress/kendo-ui@2026.3.811/umd/kendo.all.min.js" integrity="sha256-Bjy6F9ho2vlkrHseUGTTc+Y6swvrpO7a10REh+IJHD4=" crossorigin="anonymous"></script>
    </head>
    <body>
      <input id="ddl" />
      <script>
        $("#ddl").kendoDropDownList({
          dataTextField: "text",
          dataValueField: "value",
          dataSource: [
            { text: "Item1", value: "1" },
            { text: "Item2", value: "2" }
          ]
        });
      </script>
    </body>
</html>

Using Legacy Kendo CDNs

Up to Kendo UI version <DEPRICATION_VERSION>, client-side resources were also hosted on the legacy Kendo CDN services:

  • https://kendo.cdn.telerik.com—The Kendo CDN.
  • https://cdn.kendostatic.com—The cookieless Kendo CDN host.

The historical URL patterns used a Kendo UI version for JavaScript and older CSS files, and a separate theme version for Sass theme CSS:

text
https://kendo.cdn.telerik.com/{KENDO_VERSION}/js/{FILE}
https://cdn.kendostatic.com/{KENDO_VERSION}/js/{FILE}
https://kendo.cdn.telerik.com/{KENDO_VERSION}/mjs/{FILE}
https://kendo.cdn.telerik.com/{KENDO_VERSION}/styles/{FILE}
https://kendo.cdn.telerik.com/themes/{THEME_VERSION}/{THEME}/{SWATCH}.css

For example, a legacy application could build its URLs from the Kendo UI and theme versions:

javascript
const KENDO_VERSION = "2026.3.811";
const THEME_VERSION = "14.5.0";
const kendoAllUrl = `https://kendo.cdn.telerik.com/${KENDO_VERSION}/js/kendo.all.min.js`;
const cookielessKendoAllUrl = `https://cdn.kendostatic.com/${KENDO_VERSION}/js/kendo.all.min.js`;
const themeUrl = `https://kendo.cdn.telerik.com/themes/${THEME_VERSION}/default/default-main.css`;

Use the version-pinned jsDelivr package URLs described above for new integrations.

Next Steps

See Also