swiper
Most modern mobile touch slider and framework with hardware accelerated transitions
About
Most modern mobile touch slider and framework with hardware accelerated transitions
What detecting swiper tells you about a site
swiper reveals a touch-enabled slider/carousel — the most widely-used one on the web, powering hero sliders, product galleries and onboarding flows. Its presence tells you the page has a swipeable, often mobile-first interactive component, and its relatively large size means it is a noticeable part of the bundle when present.
Why the exact swiper version matters
Swiper's module system and the React/Element wrappers changed across major versions (v8 to v11); the exact version tells you which module-import style and component API the integration uses.
swiper in a real-world stack
When you find swiper in a bundle, it rarely travels alone. On React, the swiper/react components; often alongside a lazy-loading image strategy for the slides.
Quick facts
npm install swiperHow Sourcemap Explorer detects swiper
swiper ships as v14.0.7, published 2026-07-28 and carries 0 direct dependencies, 363 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when swiper rides inside a deployed bundle — here is how the detection works.
We catch swiper from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/swiper/ paths inside the JavaScript sourcemap's sources[] array — that's the canonical signal. When the matching package.json is also captured in sourcesContent[], we read the exact version field — patch number included. No regex guessing, no version inference.
- 1
Confirm the site exposes sourcemaps
In DevTools Network, check the response headers of any application script for `SourceMap` or `X-SourceMap`. Failing that, fetch the script's last 4 KB and look for a `//# sourceMappingURL=` comment — that map is where the `swiper` paths live.
- 2
Find the package in the bundle
Open DevTools → Network → reload. Click any application script and look at its sourcemap. Inside, search `sources[]` for entries matching `node_modules/swiper/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/swiper/package.json` gives you the exact installed version.
- 3
Read the version directly from package.json
Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/swiper/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.
Major releases of swiper
When each major version first landed. Major bumps are where breaking changes live, so this timeline is the fastest way to date the swiper version a site actually ships against the ecosystem.
Recent security advisories for swiper
The 2 most recent advisories affecting some versions of swiper, aggregated from OSV.dev (GitHub Advisory + CVE data). A listing here doesn't mean the version a given site ships is affected — each advisory applies to a specific version range. Sourcemap Explorer reads the exact bundled version so you can check it against these ranges.
Prototype pollution in swiper
Prototype Pollution in swiper
Recent versions
swiper README
Live mirror of the GitHub README, for reference. Updated whenever the repo's default branch changes.
Get Started | Documentation | Demos
Swiper
Swiper - is the free and most modern mobile touch slider with hardware accelerated transitions and amazing native behavior. It is intended to be used in mobile websites, mobile web apps, and mobile native/hybrid apps.
Swiper is not compatible with all platforms, it is a modern touch slider which is focused only on modern apps/platforms to bring the best experience and simplicity.
Features
- Tree-shakeable: Only modules you use will be imported into your app's bundle.
- Mobile-friendly: It is intended to be used in mobile websites, mobile web apps, and mobile native/hybrid apps.
- Library Agnostic: Swiper doesn't require any JavaScript libraries like jQuery, which makes Swiper much smaller and faster. It can be safely used with libraries such as jQuery, Zepto, jQuery Mobile, etc.
- 1:1 Touch movement: By default, Swiper provides 1:1 touch movement interaction, but this ratio can be configured through Swiper settings.
- Mutation Observer: Swiper has an option to enable Mutation Observer, with this feature Swiper will be automatically reinitialized and recalculate all required parameters if you make dynamic changes to the DOM, or in Swiper styles itself.
- Rich API: Swiper comes with a very rich API. It allows creating your own pagination, navigation buttons, parallax effects and many more.
- RTL: Swiper is the only slider that provides 100% RTL support with correct layout.
- Multi Row Slides Layout: Swiper allows a multiple row slides layout, with a few slides per column.
- Transition Effects: Fade, Flip, 3D Cube, 3D Coverflow.
- Two-way Control: Swiper may be used as controller for any number of other Swipers, and even be controlled at the same time.
- Full Navigation Control: Swiper comes with all required built-in navigation elements, such as Pagination, Navigation arrows and Scrollbar.
- Flexbox Layout: Swiper uses modern flexbox layout for slides layout, which solves a lot of problems and time with size calculations. Such layout also allows configuring the Slides grid using pure CSS.
- Most Flexible Slides Layout Grid: Swiper has a lot of parameters on initialization to make it as flexible as possible. You can control slides per view, per column, per group, space between slides, and many more.
- Images Lazy Loading: Swiper Lazy Loading delays loading of images in inactive/invisible slides until the user swipes to them. Such feature could make the page load faster and improve Swiper performance.
- Virtual Slides: Swiper comes with Virtual Slides feature that is great when you have a lot of slides or content-heavy/image-heavy slides so it will keep just the required amount of slides in DOM.
- Loop mode
- Autoplay
- Keyboard control
- Mousewheel control
- Nested sliders
- History navigation
- Hash navigation
- Breakpoints configuration
- Accessibility (A11y)
- And many more ...
Community
The Swiper community can be found on GitHub Discussions, where you can ask questions, voice ideas, and share your projects
Our Code of Conduct applies to all Swiper community channels.
Dist / Build
On production use files (JS and CSS) only from dist/ folder, there will be the most stable versions.
Development Build
Install all dependencies, in repo's root:
$ npm install
And build development version of Swiper:
$ npm run build
The result is available in dist/ folder.
Running demos:
All demos located in ./playground folder. There you will find Core (HTML, JS), React, Vue versions.
To open demo, run:
- Core:
npm run core - React:
npm run react - Vue:
npm run vue
Production Build
$ npm run build:prod
Production version will available in dist/ folder.
Contributing
All changes should be committed to src/ files only. Before you open an issue please review the contributing guideline.
Major Roadmapped Features
- Top Feature Requests (Add your own votes using the 👍 reaction)
- Top Bugs 😱 (Add your own votes using the 👍 reaction)
Sponsors
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
![Fastest Payout Casinos in Canada [2022]](https://swiperjs.com/images/sponsors/fastbet-bet-ca.png)
|
|
|
|
|
|
|
|
|
|
Code Contributors
This project exists thanks to all the people who contribute. [Contribute].
FAQ
What is swiper used for?
Most modern mobile touch slider and framework with hardware accelerated transitions
How can I tell if a website is using swiper?
Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `swiper` from two complementary signals: `node_modules/swiper/` paths inside the JavaScript sourcemap, and the embedded `package.json` we read for exact-version detection. Without the extension you can do the same lookup manually in DevTools — the steps are listed in the "How Sourcemap Explorer detects" section above.
How do I find out which version of swiper a website is running?
Read it straight from the site's JavaScript sourcemap. When a build ships source maps, the bundled `swiper/package.json` carries the exact `version` string — Sourcemap Explorer extracts it in one click on the Stack tab, and you can do it by hand in DevTools by opening the `.map` file and searching for `node_modules/swiper/package.json`. That is far more reliable than inferring the version from an asset-hash or a `?ver=` query string, which is all surface-level detectors have to go on. The current npm release is 14.0.7, but real deployments frequently run an older pinned version — which is exactly why reading the bundled number matters.
What is the latest version of swiper?
14.0.7, as published on the npm registry. The "Recent versions" table on this page lists the most recent 8 releases with their release dates. Sourcemap Explorer reports the version actually bundled into a site, which can lag the latest release by months on real-world deployments.
Is swiper actively maintained?
Very actively maintained — the last release shipped within the past three months. The last published release was 2026-07-28. Source code: https://github.com/nolimits4web/Swiper.
Does swiper have known security vulnerabilities?
2 recent advisories affecting some versions of swiper are listed in the "Recent security advisories" section above, aggregated from OSV.dev (GitHub Advisory + CVE data). Whether a particular site is exposed depends entirely on the exact version it ships — each advisory applies to a specific version range, not to the package as a whole. That is why the precise bundled version matters: Sourcemap Explorer reads the version a site actually runs, so you can check it against the affected ranges instead of assuming the latest release is what's deployed.
Where can I read more?
Project homepage: https://swiperjs.com. Source code: https://github.com/nolimits4web/Swiper. Published on npm: https://www.npmjs.com/package/swiper. Licensed as MIT.
Keep reading on Sourcemap Explorer
Detection deep dives
Alternative tools
Detected by Sourcemap Explorer
When a bundle ships sourcemaps, we read the embedded package.json for swiper and report the precise version (the registry's latest is v14.0.7, published 2026-07-28; the bundled copy is often older). Without sourcemaps, an import / require in the page's scripts is enough to flag it.