
Ring Carousel
Carousels
Scroll image cards along a curved arc while a WebGL shader folds each card as it enters and leaves, so campaign visuals, product shots, and portfolio frames feel authored rather than swapped.
WebGL Slider gives a carousel a real visual engine. Page scroll moves a column of image cards along a curved arc; as each card nears the top or bottom of the screen a vertex shader curls it like a folding page, the cursor pushes a soft bend into the surface, and when scrolling stops the page snaps so the nearest card settles in the centre. Scroll runs through the set once; at the end the view wraps back to the first card, but the page itself stops scrolling.
Use WebGL Slider when a visual sequence needs more atmosphere than a standard carousel can provide. It fits portfolios, launch campaigns, fashion visuals, product storytelling, and experimental editorial pages where the transition itself is part of the art direction. The page job is presentation: each slide should feel authored. There are no buttons; the slider is driven entirely by page scroll.
The production risk is hiding content behind a canvas. A WebGL slider can look expensive while failing as a carousel if slide text, controls, links, and fallback states are weak. Here the images exist only as WebGL textures; the slide labels (PR.00 /10 and so on) are HTML text positioned beside each card, and a visually hidden live region announces the current slide. The meaning still needs usable HTML.
import WebGLSlider from '@/components/effects/webgl-slider' const page = () => { return ( <> <WebGLSlider /> </> )} export default pageA campaign page can use WebGL Slider to move between eleven visual frames as the visitor scrolls, each folding in and out of view. The outcome is presentation: the images feel like a designed sequence rather than a stack of assets in a carousel shell.
Not for pricing, testimonials, critical proof, legal content, or anything users must compare side by side.
Not for pages where a static grid would help users decide faster.
The component caps DPR at 2 and disposes textures, materials and the renderer on unmount. It loads every texture up front, renders every frame while mounted on a fixed full-screen canvas, and sets the page body height to (slides + 1) x 100vh to create scroll room, so give it its own page or route and compress the images.
There are no visible controls, key handlers or touch handlers: the slider moves with page scroll (wheel, trackpad, scrollbar or keyboard scrolling such as arrow keys and Page Down) and snaps to the nearest slide. A visually hidden aria-live="polite" region announces each slide's label and position. Below 768px it does not render the slider and shows an "Open on desktop" message instead, and between 768px and 1024px the fold is turned off. With reduced motion enabled, the fold and hover bend are switched off, scroll is followed directly instead of smoothed, the snap takes 0.15s, and the cards sit further apart.
| Prop | Type | Default | Description |
|---|---|---|---|
distortionStrength | number | 1 | Strength of the shader fold distortion as slides scroll past. |
transitionDuration | number | 0.6 | Duration of the scroll-snap settle animation. |
enableHoverEffect | boolean | true | Enables the pointer-driven hover bend on each slide. |
imageWidth | number | 3.2 | WebGL slide plane width. |
imageHeight | number | 3 | WebGL slide plane height. |
Use it when a visual carousel needs shader-led transitions and a premium image sequence, not when users need fast comparison.
It does not ship with any. Navigation is page scroll with snap, so keyboard users can move through slides with normal page-scrolling keys, but there are no next or previous buttons and no swipe gesture. Add visible buttons that scroll to the next or previous slide if your audience needs them.
The component has no non-WebGL fallback: the images exist only as textures, and the HTML labels only appear once the WebGL renderer starts, so if WebGL is unavailable only the screen-reader live region remains. If that matters, detect WebGL support and render the same images as a normal gallery instead.
It does not autoplay; slides only move when the visitor scrolls. If you add autoplay, give it a clear pause control and turn it off for reduced motion.
With prefers-reduced-motion set, the shader fold and hover bend are off, scroll is followed directly instead of smoothed, and the snap is a quick 0.15s ease. The cards still travel along the arc as you scroll.
Yes. A custom version should define shader style, slide data, controls, fallback behavior, performance budget, source handoff, and implementation notes.
Need a custom effect? Tell us what to create.