cdnjs

cdnjs.com · Global

A free public CDN for open-source JavaScript, CSS, fonts and related library files, delivered through Cloudflare with versioned URLs, SRI hashes and a metadata API.

Public resource CDNOpen-source librariesSRIMetadata API
Service marketsMultiple regions
BillingFree
Free trialNot supported
Payments
Not verified
Overall rating
★★★★★★★★★★4.0

On-site interest
4,500index
01

Company introduction

About cdnjs
Founded
2011
Co-founders
Ryan Kirkman, Thomas Davis
Headquarters
Distributed open-source project
Listing
Open-source project supported by Cloudflare infrastructure and maintenance

Community origins and Cloudflare’s role

Ryan Kirkman and Thomas Davis founded cdnjs in 2011 to make open-source front-end resources available through direct website references. Cloudflare took over project maintenance in 2019. The current site names Matt Cowley and Cloudflare Engineering as maintainers, with community contributions to library configurations and project code on GitHub.

cdnjs distributes public open-source libraries using infrastructure and maintenance support from Cloudflare. A website can use it without moving its DNS or all traffic to Cloudflare. The service is separate from Cloudflare’s commercial CDN, WAF and enterprise contracts.

Library inclusion and the current update pipeline

Only libraries already accepted into cdnjs are served; requesting a URL does not fetch an arbitrary npm package on demand. New libraries enter through reviewed configuration submissions to cdnjs/packages. Once accepted, automation follows the configured npm or GitHub source for new versions. The current pipeline checks upstream sources every 10 minutes, while actual publication still depends on configuration and processing.

As of 23 June 2026, cdnjs was running on its migrated Cloudflare Developer Platform architecture, storing asset files in R2 and metadata in services including KV. The old cdnjs/cdnjs asset Git repository no longer receives updates. Library configuration and the live delivery service continue, with maintenance contributions directed to the packages repository.

Integration and dependency management

Find a library, choose its version and file, and add the corresponding script or link tag to the page. HTTPS URLs include the library name, version and filename. Fixed-version URLs remain unchanged when new releases appear; cdnjs does not provide floating latest or semantic-version-range aliases. Upgrades require an explicit URL change and compatibility checks.

SRI helps check downloaded file contents against the selected hash. Match it to the exact version and file, and use the crossorigin setting shown in the integration example. The migration notes describe historical SRI data requiring correction, so existing integrations also need checks against the actual files. SRI does not replace license review, vulnerability tracking or dependency maintenance.

02

Who is this provider for?

Websites using direct library references

Content sites, prototypes and pages without a bundling step can load common JavaScript, CSS and font resources through HTML tags.

Check that the library and required files are included, then pin a specific version.

Integration and developer-tool teams

The API provides library, version, file and SRI metadata for dependency selection, documentation and integration tools.

Distinguish latest-version metadata from historical version details. Request the fields needed and cache results.

Maintainers of public open-source libraries

Submit a library configuration under the contribution guidelines. Accepted configurations enable automation to follow releases on npm or GitHub.

Inclusion requires project review and an appropriate license. This is not private file storage or an arbitrary-origin proxy.

A fit for referencing included public open-source resources. Private assets, origin proxying, custom delivery policies or an enforceable contractual SLA call for a suitable commercial service. Critical pages should also account for third-party resource failures.

03

Services and products

Core products from official sources

Explore products by use case: what they do, how to use them and whether they are billed separately.

Public open-source library delivery

Public resource CDN

Delivers accepted JavaScript, CSS, fonts and related library files through versioned HTTPS URLs. Library pages provide integration tags with SRI; the network supports HTTP/2, HTTP/3 and applicable transfer compression. Published URLs identify fixed versions, with new releases handled through library configuration and automation.

Free public serviceOfficial product information

Library search and metadata API

Developer tools

Search the website or query the unauthenticated api.cdnjs.com API for library metadata, versions, files and SRI. Responses support field selection. The assets array in a library-information response covers only the latest version; use the specific-version endpoint for historical files. Catalog metadata is cached and is unsuitable for real-time release notifications.

Sources: cdnjs official product pages and developer documentationVerified: 2026-11-17
04

Plans and pricing

Official public pricing
Website delivery and security plans · monthly and annual billing shown separately

Free public library service

Websites and developers using included open-source libraries

Free

No subscription or usage bill

  • Reference public assets without opening a paid account or adding a payment method
  • Public library-file delivery and metadata queries
  • Use remains subject to individual library licenses and service terms
  • Community documentation and issue reporting; no bespoke enterprise SLA

This is ordinary free access, rather than a time-limited trial that automatically converts to a paid plan.

The public library service is free. Project documentation states that it does not charge usage fees or define paid usage tiers. GitHub Sponsors, Open Collective and Patreon links support voluntary project funding; they do not purchase delivery allowances or enterprise service entitlements.

Official sources: Project and free service
Prices checked: 2026-11-17
05

CdnChart Selection Guide

ExcellentSelection verdict

A good fit for websites that want direct access to common open-source front-end libraries and can manage their own versions and third-party dependencies. Free access, fixed-version URLs and metadata endpoints simplify integration

critical services still need a plan for availability and contractual requirements.

Use casesProductsPricing and termsDocumentationSupport resources

Why we recommend it

  • A searchable collection of JavaScript, CSS and fonts suits pages that use direct HTML references.
  • Fixed-version URLs, SRI and version endpoints help maintain an explicit dependency inventory.
  • Community inclusion and automated updates provide an ongoing distribution route for public open-source libraries.

Considerations

Pinned files do not upgrade themselves or resolve vulnerabilities in the libraries. Check files, hashes and licenses before release, track dependency updates, and prepare a fallback or self-hosted option for third-party failures. Select a separate service for private content or contractual guarantees.

Related articles

Explore cdnjs products, use cases and buying advice

No articles about cdnjs yet.