How to minify a CSS file using jsDelivr?

Simply add '.min' before the file extension in the URL, like /npm/package@version/file.min.css. jsDelivr will generate a minified version on first request and store it for future use, including source maps for debugging, as shown in the usage documentation.

jsDelivr vs unpkg: which is better for npm packages?

jsDelivr offers multi-CDN redundancy, China optimization, and automatic minification, making it more reliable for global production use. unpkg is simpler but may have fewer uptime guarantees and features. For critical applications, jsDelivr's failover mechanisms provide better resilience.

Can I use jsDelivr for private GitHub repositories?

No, jsDelivr only serves files from public repositories on npm, GitHub, and WordPress. For private assets, you need a different solution, as jsDelivr is designed exclusively for open-source content with no support for authentication.

How does caching work on jsDelivr and can I force updates?

Static versions are cached permanently, version aliases for 7 days, and branches for 12 hours. You can purge cache for aliases via API after email approval, but static files require a new release, as detailed in the Caching and Purge cache sections.

Is jsDelivr free for commercial high-traffic websites?

Yes, jsDelivr is completely free with no bandwidth limits, optimized for production use on large sites. It's funded by sponsors and uses multi-CDN partnerships to maintain service without charging users, as highlighted in the philosophy.

How to combine multiple JavaScript files into one request with jsDelivr?

Use the /combine/ endpoint with comma-separated URLs, like /combine/gh/jquery/jquery@3/dist/jquery.min.js,gh/bootstrap/bootstrap@4/dist/js/bootstrap.min.js. This reduces HTTP overhead and includes source maps, though large combinations may delay first requests.

jsDelivr — Free Open Source CDN for NPM & GitHub

What is jsDelivr?

jsDelivr is a free, open-source content delivery network that serves files from npm, GitHub, WordPress, and other sources with high speed and reliability. It solves the problem of hosting static assets for open-source projects by providing a globally distributed, production-ready CDN with automatic optimizations and robust failover. Developers can use it to load libraries directly in browsers without managing their own infrastructure.

Target Audience

Web developers, open-source maintainers, and companies needing a reliable CDN for serving JavaScript, CSS, and other static assets from public repositories like npm and GitHub.

Value Proposition

Developers choose jsDelivr because it's completely free, uses multiple CDN providers for exceptional uptime, and guarantees that files remain available even if packages are deleted. Its smart load balancing and China-optimized network make it a top choice for global projects.

A free, fast, and reliable Open Source CDN for npm, GitHub, Javascript, and ESM

Use Cases

Best For

Serving JavaScript and CSS libraries from npm or GitHub in production websites
Automatically minifying and optimizing frontend assets on-demand
Ensuring high availability with multi-CDN failover and smart routing
Delivering assets to users in China with low latency
Combining multiple files into a single request to reduce HTTP overhead
Hosting WordPress plugins and themes via a public CDN

Not Ideal For

Projects requiring private asset hosting not on public repositories like npm or GitHub
Applications needing real-time asset updates without cache delays or manual purging
Environments with strict compliance requirements that prohibit third-party CDNs
Hosting very large files exceeding the 150 MB package or 20 MB single file limits

Pros & Cons

Pros

Multi-CDN Redundancy

Uses Cloudflare and Fastly with smart load balancing based on real user metrics, ensuring high uptime and performance globally, as detailed in the Multi-CDN and Smart Load Balancing sections.

Permanent File Storage

Files are stored permanently in S3, so even if packages are deleted from npm or GitHub, jsDelivr continues to serve them without breaking websites, emphasized in the production-ready reliability description.

Automatic Minification

On-demand minification of JS, CSS, and SVG files with source maps, demonstrated by adding '.min' to file paths in usage examples, and stored for future requests.

Version Fallback Safety

If a file is missing in a newer version, it falls back to the previous version, preventing 404 errors, as noted in the npm and GitHub endpoint documentation.

Cons

File Size Restrictions

Does not support packages over 150 MB or single files over 20 MB on GitHub by default, requiring manual intervention for larger assets, as stated in the Restrictions section.

Inflexible Static Caching

Static versions are cached permanently, meaning critical fixes require a new release, which can delay updates, as admitted in the Caching and Purge cache sections.

Manual Cache Purge

Purging cache requires an email request and is rate-limited, slowing down deployment workflows for frequent updates, as explained in the Purge cache notes.

Frequently Asked Questions

What is jsDelivr?

Target Audience

Web developers, open-source maintainers, and companies needing a reliable CDN for serving JavaScript, CSS, and other static assets from public repositories like npm and GitHub.

Value Proposition

Use Cases

Best For

Serving JavaScript and CSS libraries from npm or GitHub in production websites
Automatically minifying and optimizing frontend assets on-demand
Ensuring high availability with multi-CDN failover and smart routing
Delivering assets to users in China with low latency
Combining multiple files into a single request to reduce HTTP overhead
Hosting WordPress plugins and themes via a public CDN

Not Ideal For

Projects requiring private asset hosting not on public repositories like npm or GitHub
Applications needing real-time asset updates without cache delays or manual purging
Environments with strict compliance requirements that prohibit third-party CDNs
Hosting very large files exceeding the 150 MB package or 20 MB single file limits

Pros & Cons

Pros

Multi-CDN Redundancy

Uses Cloudflare and Fastly with smart load balancing based on real user metrics, ensuring high uptime and performance globally, as detailed in the Multi-CDN and Smart Load Balancing sections.

Permanent File Storage

Automatic Minification

On-demand minification of JS, CSS, and SVG files with source maps, demonstrated by adding '.min' to file paths in usage examples, and stored for future requests.

Version Fallback Safety

If a file is missing in a newer version, it falls back to the previous version, preventing 404 errors, as noted in the npm and GitHub endpoint documentation.

Cons

File Size Restrictions

Does not support packages over 150 MB or single files over 20 MB on GitHub by default, requiring manual intervention for larger assets, as stated in the Restrictions section.

Inflexible Static Caching

Static versions are cached permanently, meaning critical fixes require a new release, which can delay updates, as admitted in the Caching and Purge cache sections.

Manual Cache Purge

Purging cache requires an email request and is rate-limited, slowing down deployment workflows for frequent updates, as explained in the Purge cache notes.

Frequently Asked Questions

jsDelivr

What is jsDelivr?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

jsDelivr

What is jsDelivr?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?