We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Find CDN links for popular JavaScript libraries and copy ready-to-use code snippets to speed up frontend development.
Builds jsDelivr, unpkg or esm.sh URLs/snippets from bundled fixed versions and paths. It does not fetch latest versions or verify every asset. Check path, version, licensing and browser loading before use. Reference
https://cdn.jsdelivr.net/npm/react@18.3.1/umd/react.production.min.js<script src="https://cdn.jsdelivr.net/npm/react@18.3.1/umd/react.production.min.js"></script>import * as React from "https://esm.sh/react@18.3.1";Overview
Understand what the tool solves, how it works, and the boundaries of its data.
This page provides a searchable catalog of common JavaScript and CSS packages. Search by library name, package name, category, tags or catalog description, select a result, and choose a delivery option. For the selected package and catalog version it displays a script URL or tag, an optional stylesheet link when available, and an ES module import example. The catalog is preset rather than a live index of every package or release.
A CDN URL points your page to a file hosted by another service. A classic script tag loads a script file; a module import uses JavaScript’s module loading rules. These approaches are not interchangeable in every project: the package build, browser support, script order and the library’s documented setup still matter. A displayed version is a convenient starting point, not proof that it is the newest, compatible, maintained, secure or properly licensed choice.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Example: if a selected catalog entry shows package example-lib at version 1.2.3, inspect the copied URL to confirm both the package and version are what you intended. The example is illustrative; it is not a catalog entry or guarantee about a real package.
Use cases
See how the tool fits into real work and everyday tasks.
Find a preset library and copy a starting script or module snippet while exploring a small browser demo. Validate that the selected package build exposes the API used in the example.
Switch among available providers and inspect script, CSS and module output for a chosen catalog item before deciding how it fits an existing page.
Q&A
Find concise answers to common questions and confusing cases.
No. It is a preset collection. A missing package or newer release may not be represented, so check the package registry and provider documentation for current availability.
No. The page formats a URL and snippet; it does not audit source code, verify a publisher, assess supply-chain risk or check a package’s license. Review and pin dependencies according to your project’s policy.
Browser module imports require module-compatible code and resolvable module URLs. A package may need a different entry point, build tool configuration or setup; use its documentation and check the browser console.
Notes
Review scope, result limitations, and important precautions before use.
A copied CDN resource is loaded from a third-party host when your page requests it. Confirm the exact file, version, provider terms, availability, license and security posture independently. Do not treat a generated snippet as a compatibility or performance recommendation, and avoid silently switching versions in production. For dependable projects, use a tested dependency policy and document who controls each external resource.
Related
Discover related tools, collections, and available API capabilities.