
Scroll Stack
Scroll
A pinned two-column scroll section that steps through paired text and images, swapping the copy with a fade and slide and wiping each image away to reveal the next.
Sticky Content Wrapper pins a full-height two-column view and turns scroll into a sequence of steps. At each step the text block (heading, paragraph, list and link) fades and slides out while the next one fades in, and the current image is wiped away with a clip-path to reveal the next one scaling into place. Scroll snaps to each step. It is built for product pages that need focus, not fireworks.
Use Sticky Content Wrapper when a story breaks into a handful of steps that each pair a short block of copy with one image. SaaS feature storytelling and product tours are the natural fit because the visitor stays in one place while each step replaces the last, text and image together. The page job is clarity: one step at a time, with the copy and the visual always matched.
The risk in production is reachability. Every step lives inside the pinned view, so its content is reached only by scrolling through the sequence, and the four default steps are set in the component source rather than passed as props.
import StickyContentWrapper from "@/components/effects/sticky-content-wrapper";import { ReactLenis } from"lenis/react"; export default function Page() { return ( <ReactLenis root> <StickyContentWrapper /> </ReactLenis> );} A SaaS team building a product tour: each step pairs one capability's heading, short copy, key points and link with a matching screenshot, and scrolling swaps both together. The outcome is clarity: the visitor always sees the copy and the visual for the same capability side by side.
Not for sections where every item has equal weight or users need to jump straight to a specific answer.
Not for long copy per step on mobile, where the text and image share one pinned screen.
Animate transform and opacity, avoid layout reads in scroll handlers, pre-size media, and clean up timelines/listeners when the route changes.
Steps render in DOM order, and hidden steps use autoAlpha, so they are set to visibility: hidden rather than left focusable. The view stays pinned at every size; below 1024px the image sits above the text inside the pinned screen. The shipped links call preventDefault on click, so wire up real navigation before shipping.
| Prop | Type | Default | Description |
|---|---|---|---|
bgColor | color | #ffffff | Background color of the sticky section, including the gap between the content and image panes. |
textColor | color | #000000 | Color of the text content and the scroll indicator. |
contentEnterYPercent | number | 2 | Vertical offset (% of content height) each content block starts from before sliding into place. |
initialImageScale | number | 1.5 | Scale of an image before it becomes the active image. |
activeImageScale | number | 1.2 | Scale of the image while it is active on screen. |
exitImageScale | number | 1 | Scale of an image after it has exited. |
A reveal animates an element in once; this pins the whole two-column view and steps through several text and image pairs, fading and sliding the copy out and in while each image is wiped away to reveal the next. Scroll snaps to each step. The value is sustained focus, not a single entrance. Use it when a story needs several matched beats of copy and visual in one place.
Below 1024px the component already stacks the image above the text inside the pinned view, so keep each step's copy short enough to fit beneath the image on a phone. If that is not enough, replace the pin with plain stacked sections in your copy of the source. The component itself stays pinned at every size, and reduced motion keeps the pin too: the clip-path wipe and image scale become a crossfade while the text still slides and fades between steps.
Check the pinned view releases cleanly at the end of its range, that snapping to each step feels right with Lenis, and that it re-measures on viewport resize and dynamic mobile toolbars. The "scroll" cue is position: fixed, so confirm it does not linger over the rest of your page. There is no unpinned fallback, so confirm every step is reachable through the pinned sequence on small screens.
A short sequence of steps, each with a heading, a short paragraph, an optional list and link, and one image: a feature explained screen by screen, or a case study told in stages. It needs at least three or four steps to justify pinning; a single pairing doesn't. Keep each step's copy concise so it can be read before the next swap.
Avoid it when each step needs long copy, when the page is short, or when text and image would crowd each other on smaller screens. If the link between each block of copy and its image isn't obvious, the pin just feels like the page is stuck. Skip it on utility routes where scanning beats focus.
Yes, adaptation work tunes the pin range, the pairing logic, and the responsive fallback to your layout, with motion rules, a performance budget, fallback design, source handoff, and implementation notes. You keep the component in your own codebase.
Need a custom effect? Tell us what to create.