Using CDN with Telerik UI for ASP.NET MVC
The client-side JavaScript and CSS resources for Telerik UI for ASP.NET MVC are published as npm packages. You can load them from an npm-compatible CDN, such as jsDelivr or unpkg. Including these resources in your project is essential because the Telerik UI helpers are wrappers over the Kendo UI widgets.
As of the R3 2022 release, you must install a license file in your application to use Telerik UI for ASP.NET MVC. For more information, check Installing a License File.
The public npm CDN endpoints shown in this article serve package versions published to the npm registry. To use a private package or an internal build, host the files in a location your application can access.
For production, it is advisable to pin the package version in the URL. If your CDN provider provides Subresource Integrity (SRI) metadata, it is also advisable to use the hash for the exact file and version and include the integrity and crossorigin attributes.
Understanding the CDN Structure
For public npm packages, jsDelivr and unpkg use the following URL structures:
https://cdn.jsdelivr.net/npm/[PACKAGE]@[VERSION]/[MODULE_FORMAT]/[FILE]https://unpkg.com/[PACKAGE]@[VERSION]/[MODULE_FORMAT]/[FILE]
Replace [PACKAGE], [VERSION], and [FILE] with the npm package name, version, and file path. Use js, umd or esm to load the scripts in the desired module format - CommonJs, UMD or ESM, respectively. For example, to load the configured Kendo JavaScript and Default theme versions from jsDelivr, use:
https://cdn.jsdelivr.net/npm/@progress/kendo-ui@2026.4.1111/esm/kendo.all.jshttps://cdn.jsdelivr.net/npm/@progress/kendo-theme-default@14.9.0/dist/default-main.css
To use unpkg for the same files, replace https://cdn.jsdelivr.net/npm with https://unpkg.com.
Adding the Required CSS Files
Adding the Kendo CSS files allows you to use the Kendo UI visual themes. The compiled .css files are available in each theme package's dist folder.
To load the Bootstrap theme, reference its package and compiled stylesheet:
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@progress/kendo-theme-bootstrap@14.9.0/dist/bootstrap-main.css" />
Adding the Required JavaScript Files
To import the JavaScript files required for the Telerik UI components, apply either of the following approaches:
- Using the JavaScript modules—A new approach introduced with version
2022.3.1109. - Using the bundled JavaScript—The traditional way of including the Kendo UI scripts.
Using JavaScript Modules
The JavaScript modules are located in the esm folder of the Kendo npm package.
To include a Kendo JavaScript module in your project:
- Use the
scripttag with thetype=moduleattribute. - Add a reference to the global
aspnetmvc.jsfile.
The two examples below demonstrate how to include individual component modules and all available component modules:
-
Including individual component modules.
html<script src="https://cdn.jsdelivr.net/npm/@progress/kendo-ui@2026.4.1111/esm/kendo.grid.js" type="module"></script> <script src="https://cdn.jsdelivr.net/npm/@progress/kendo-ui@2026.4.1111/esm/kendo.aspnetmvc.js" type="module"></script> -
Including all available modules.
html<script src="https://cdn.jsdelivr.net/npm/@progress/kendo-ui@2026.4.1111/esm/kendo.all.js" type="module"></script> <script src="https://cdn.jsdelivr.net/npm/@progress/kendo-ui@2026.4.1111/esm/kendo.aspnetmvc.js" type="module"></script>
Using Bundled JavaScript
The Kendo UI bundled JavaScript files are located in the umd folder of the Kendo npm package.
To load the full bundle, use a version-pinned URL from your chosen CDN provider:
<script src="https://cdn.jsdelivr.net/npm/@progress/kendo-ui@2026.4.1111/umd/kendo.all.min.js" ></script>
Using the CDN in Your Project
The following complete example demonstrates how to add the CSS files and the bundled JavaScript.
Replace the Telerik UI for ASP.NET MVC version in the script
srcattribute with the version of the product you are using—for example,2026.4.1111. Replace the theme version in the stylesheethrefattribute with the respective version of the theme you are using.
-
Open the layout of the application. By default, it is
~/Views/Shared/_Layout.cshtmlorSite.master, if using ASPX. -
To add the JavaScript files, insert a
scripttag and includekendo.all.min.jsandkendo.aspnetmvc.min.jsafter the jQuery script.HTML<script src="https://cdn.jsdelivr.net/npm/@progress/kendo-ui@2026.4.1111/umd/kendo.all.min.js"></script> <script src="https://cdn.jsdelivr.net/npm/@progress/kendo-ui@2026.4.1111/umd/kendo.aspnetmvc.min.js"></script> -
If using the Telerik MVC Scheduler helper, include
kendo.timezones.min.jsafterkendo.all.min.js.HTML<script src="https://cdn.jsdelivr.net/npm/@progress/kendo-ui@2026.4.1111/umd/kendo.all.min.js"></script> <script src="https://cdn.jsdelivr.net/npm/@progress/kendo-ui@2026.4.1111/umd/kendo.timezones.min.js"></script> <script src="https://cdn.jsdelivr.net/npm/@progress/kendo-ui@2026.4.1111/umd/kendo.aspnetmvc.min.js"></script> -
Setup the License File by following the instructions in the Installing a License File.
Using Legacy Kendo CDNs
Up to Kendo UI version 2026.3.811, 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:
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:
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`;
For new integrations, use a version-pinned URL from an npm CDN provider, as described above.
For troubleshooting historical integrations, see:
To check the status of Progress services, visit the Progress® Telerik® Live Services Status Page. For CDN availability, consult the status page for your chosen provider.
Troubleshooting
If a file fails to load, verify the package name, version, and file path. Check the selected CDN provider's status page and confirm that your network and security settings allow the request.