
Scroll Stack
Scroll
A scroll-based card stack effect where each card slides up over the last while the previous one tilts, scales down and fades out.
Stacking Cards turns an ordered set into a pinned, full-screen sequence. Each new card slides up from below and covers the current one, which tilts back, scales down to 80% and fades out as it is covered, so only one card is fully visible once each handoff completes.
Use Stacking Cards when an ordered set should be read one step at a time, with each handoff clearly marking progress. SaaS teams and agency process pages are the best fit because each card gets the full screen: a category, a number, a title, a short description and an image. The six cards are defined in the component source; props control image zoom, tilt, corner radius and perspective. The page job is momentum: the sequence moves forward card by card, so put anything the reader must compare elsewhere.
In production, the risk is reachability. The cards are stacked absolutely inside a sticky full-screen view with no unpinned fallback, so every card is reached only by scrolling through the sequence. The component also registers a Lenis scroll callback, so run it inside ReactLenis as the usage shows. Reduced motion does not unpin the section; it keeps the slide-up handoff and crossfade and only drops the tilt, scale, and image zoom.
import StackingCards from '@/components/effects/stacking-cards'import { ReactLenis } from 'lenis/react' const page = () => { return ( <ReactLenis root> <StackingCards /> </ReactLenis> )} export default pageAn agency explaining its delivery process: each phase takes the full screen, then tilts away and fades as the next phase slides up over it, so the method feels staged step by step rather than merely listed. The outcome is trust: the process feels deliberate before the prospect reaches the CTA.
Not for comparison grids, forms, or content readers need to see side by side, since only one card is visible at a time.
Not for cards with links or controls, since faded-out cards stay in the DOM at opacity 0 and keyboard focus could land on content that is not visible.
Animate transform and opacity, avoid layout reads in scroll handlers, pre-size media, and clean up timelines/listeners when the route changes.
Cards sit in DOM order and the sequence plays in the same order. Faded-out and not-yet-arrived cards stay in the DOM, so screen readers can reach all of them. Below 1024px each card switches to a stacked layout with the image between the category and the text, but the section stays pinned at every size.
| Prop | Type | Default | Description |
|---|---|---|---|
imageZoomEnabled | boolean | true | Enables the image zoom-in effect during card reveals. |
tiltEnabled | boolean | true | Enables the outgoing card tilt, scale, and rotateX treatment. |
cardCornerRadius | number | 48 | Corner radius in pixels applied to the cards as they stack (not the images). |
stackPerspective | number | 1200 | Perspective depth for the tilt. Only applies while tilt is enabled. |
Each card slides up over the previous one, which tilts, scales down and fades out as it is covered, so each handoff feels like a new card being dealt on top rather than content scrolling away. The previous card finishes fading just after the new one settles, so the point is the transition, not a visible pile. Use it when a staged, one-at-a-time progression matters more than seeing everything at once.
Only one card is visible at a time, so stack depth is not the issue on a small screen; content density is. Below 1024px each card stacks its category, image and text vertically, so keep titles and descriptions short enough to fit one screen. With reduced motion it stays pinned: each card still slides up over the last and the outgoing card crossfades out, without the tilt, scale, or image zoom.
Confirm the card order matches DOM order, that each outgoing card's fade reads cleanly as the next one settles at your viewport sizes, and that the sequence cleans up on route change. Test with your real card count, not three placeholders. There is no flat fallback, so make sure every card is reachable through the pinned sequence.
Three to six items that build a case: milestones, principles, or proof points where each step should clearly hand over to the next. The shipped component has six cards, each with a category, number, title, description, image and background colour. It's weak for unrelated items that don't benefit from a staged sequence. Give each card one clear claim.
Avoid it when cards are dense or text-heavy, when there are so many that the pinned scroll drags on, or when users need to compare them side by side. If hiding each card behind the next removes information the reader needs, a plain grid serves better. Skip it where scanning speed outranks staged progression.
Need a custom effect? Tell us what to create.