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

Using CDN

The Kendo UI for jQuery CDN is hosted on the Amazon CloudFront.

Only the official Kendo UI for jQuery releases and service packs are uploaded to the CDN. Internal builds are not available on CDN. To access the Kendo UI for jQuery CDN services, you can use either the HTTP or the HTTPS protocol. Use any of the following CDN services:

  • (a cookieless CDN service)

Using the HTTP Protocol

The minified versions of all JavaScript files are available at the following locations:


For example, the 2022.2.621 version can be loaded from the following locations:


The minified Kendo UI for jQuery scripts are available as of the Kendo UI Q1 2014 SP1 release. To load them, use the URL.

Using the HTTPS Protocol

The URL remains active but is no longer recommended for new projects.

To access the Kendo UI for jQuery CDN service through the HTTPS protocol, use the same host name and replace the scheme (protocol) with https. For example,


This section provides solutions for common issues you might encounter while using the Kendo UI CDN services.

General disruption and connection issues occur

Description Although the Amazon CloudFront service provides a reliable level of uptime support, you might encounter disruption or connection issues. After you check the status of the systems at, the CDN status is reported as healthy and operates normally.

Cause You might be experiencing Internet, network connectivity, or DNS problems. It is also possible that firewalls, antivirus, or other security software incorrectly filters out the CDN scripts or modifies (breaks) them on the fly.

Solution Contact your system administrator because remote investigation of connection problems is outside the scope of the Kendo UI for jQuery Support Team.

It is not possible to refer Kendo UI internal builds from CDN

Cause The internal Kendo UI for jQuery builds are not uploaded to CDN because they are intended only for clients with a commercial license. Only major Kendo UI for jQuery releases and service packs are available on CDN.

Solution For internal builds, use private CDN services. It is recommended that you implement a local fallback when you use any kind of CDN. For more information, refer to Scott Hanselman's blog post Fallback from CDN to Local Scripts.

<!DOCTYPE html>
    <title>Welcome to Kendo UI for jQuery</title>
    <link rel="stylesheet" href="" />
    <link rel="stylesheet" href="" />

    <script src=""></script>
        if (typeof jQuery == "undefined") {
            // Fallback to local jQuery.
            document.write(decodeURIComponent('%3Cscript src="/path/to/local/jquery.min.js" %3E%3C/script%3E'));

    <script src=""></script>
        if (typeof kendo == "undefined") {
            // Checking for loaded CSS files is cumbersome,
            // therefore assume that if the scripts have failed, so have the stylesheets.

            // Fallback to local Kendo UI for jQuery stylesheets.
            document.write(decodeURIComponent('%3Clink rel="stylesheet" href="/path/to/local/kendo.common.min.css" %3C/%3E'));
            document.write(decodeURIComponent('%3Clink rel="stylesheet" href="/path/to/local/kendo.blueopal.min.css" %3C/%3E'));

            // Fallback to local Kendo UI for jQuery scripts.
            document.write(decodeURIComponent('%3Cscript src="/path/to/local/kendo.all.min.js" %3E%3C/script%3E'));
            // Also add kendo.aspnetmvc.min.js or kendo.timezones.min.js if needed.
    Hello world!

Next Steps

See Also

In this article