
Helix Slider
Scroll
Let users drag, tap, or browse through looping cards when the section needs momentum instead of a hard first-to-last ending.
Infinite Carousel keeps a card sequence in motion. Drag it, tap it, nudge it, and the lineup keeps arriving.
Use Infinite Carousel when a small set of cards should feel browseable without a hard end. It fits product showcases, property listings, campaign cards, feature highlights, and visual collections where the user can explore at their own pace. The page job is momentum: the next card should feel close without hiding the current one.
The production risk is fake infinity. Looping carousels often duplicate slides visually and accidentally confuse focus order, screen readers, analytics, or active-state logic. The loop can be visual; the content model still needs to remain honest.
import InfiniteCarousel from "@/components/effects/infinite-carousel"; const page = () => { return ( <InfiniteCarousel /> );}; export default page; A property landing page can use Infinite Carousel to let visitors drag through a set of premium locations and property types. The outcome is momentum: the browsing interaction feels fluid while each card still carries a clear title, description, and decision cue.
Not for pricing, legal copy, critical proof, comparison tables, or content users must see all at once.
Not for long card archives where filtering, search, or a grid would serve the visitor better.
Keep card count reasonable, lazy-load heavy media, avoid expensive re-renders during drag, and clean up pointer and animation listeners on unmount.
Provide arrow buttons, keyboard access, visible focus, and swipe support. Screen readers should encounter each real item once. With reduced motion, autoplay and scroll tilt switch off, but the loop and drag, wheel, and arrow navigation stay active.
| Prop | Type | Default | Description |
|---|---|---|---|
infinite | boolean | true | Loops the carousel endlessly instead of stopping at the last card. |
snap | boolean | true | Settles the track on the nearest card after a drag or scroll. |
draggable | boolean | true | Allows dragging the carousel with pointer and touch input. |
showNav | boolean | true | Shows or hides the previous and next arrow buttons. |
autoPlay | boolean | false | Automatically advances the carousel one card at a time. |
autoPlayInterval | number | 3000 | Milliseconds between automatic slide advances. Needs Auto Play on. |
tiltOnScroll | boolean | false | Leans the cards into a fast swipe, then springs them back to level. |
tiltStrength | number | 4.2 | How far the cards lean when tilt on scroll is enabled. Needs Tilt On Scroll on. |
lerpFactor | number | 0.12 | Easing factor for the track - lower glides longer, higher snaps tighter. |
dragSensitivity | number | 0.005 | How far the track moves per pixel of drag. Needs Draggable on. |
snapStrength | number | 0.1 | How firmly the track is pulled towards the nearest card. Needs Snap on. |
cardWidth | number | 33.8 | Desktop card width in viewport width units. The default shows 2.8 cards at a time. |
cardHeight | number | 60 | Card height in viewport height units. |
gap | number | 1.9 | Spacing between cards in viewport width units. |
Use it when a card set benefits from continuous, user-controlled browsing rather than a hard first-to-last sequence.
Keep the source items unique, hide cloned visual duplicates from assistive technology, and maintain predictable focus order.
Only if it pauses on hover, focus, touch, and reduced motion. User-driven drag and controls are usually better.
Use a grid when users need to scan, compare, filter, or see all items before making a choice.
Support swipe and reachable controls. Keep cards large enough to read and avoid drag behavior that fights vertical page scroll.
Yes. A custom version should define card structure, loop behavior, controls, accessibility states, mobile fallback, analytics events, and source handoff.
Need a custom effect? Tell us what to create.