To identify the versions of third-party libraries used by Webflow in its generated JavaScript, you need to inspect the compiled and minified code Webflow outputs on publish — but keep in mind many libraries may not show version info directly.
- Publish your Webflow project to a staging domain or custom domain.
- Open the page in your browser, right-click and choose Inspect, then go to the Sources or Network tab in DevTools.
2. Locate the Webflow JavaScript File
- Look for a file like webflow.js or webflow.[hash].js under the site’s domain in the Sources tab or listed in the Network tab under JS resources.
- Open the file to view its contents.
3. Search for Library Names in the Code
- Use Ctrl+F (or Cmd+F) to search for common third-party library names such as:
- jQuery
- lottie
- ix2 (Webflow Interactions 2.0)
- modernizr
- swiper (used in newer Webflow sliders)
- Some libraries may expose version info via comments or initialization code (e.g.,
jQuery.fn.jquery
).
4. Check the Global Window Object in Console
- Go to the Console tab in DevTools and type:
jQuery.fn.jquery
— shows jQuery version, if loaded.window.Webflow
— may expose internal modules or metadata.window.lottie.version
— if Lottie is in use.
5. Look at Network Tab for External Libraries
- In the Network tab, filter by JS or All, then look for requests to CDNs or third-party sources.
- URLs may include versions (e.g.,
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.5.1/jquery.min.js
).
- You can write custom Snippets in DevTools to log
window
keys or analyze script content. - Some extensions like Wappalyzer or WhatRuns can detect frontend libraries and versions.
Summary
To identify third-party library versions in Webflow, inspect the published site’s JavaScript files and DevTools console. Look for identifiable patterns, library initializations, or use commands like jQuery.fn.jquery
. Webflow doesn’t officially document these versions, so manual inspection is necessary.