A free, fast, and reliable open-source CDN for npm, GitHub, WordPress, and ES modules with multi-CDN failover.
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.
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.
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
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
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.
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.
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.
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.
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.
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.
Purging cache requires an email request and is rate-limited, slowing down deployment workflows for frequent updates, as explained in the Purge cache notes.