
Scroll Distortion
Scroll
A canvas-led scroll effect that splits or reveals visual states for before-after stories, AI launches, and transformation sections.
Split Canvas makes scroll feel like a cut through the visual field. It is for pages where the transition between states matters.
Use Split Canvas when the page message benefits from a visual split that feels deliberate. Creative studios, AI launches, and experimental brand pages can use it to frame contrast, reveal, or transformation. The page job is contrast: two sides of the idea should feel connected by the interaction.
The production risk is canvas dependency. If the split effect fails, the core message, headline, and CTA must still exist in HTML and remain visually complete.
import SplitCanvas from '@/components/effects/split-canvas' const page = () => { return ( <> <SplitCanvas /> </> )} export default pageAn AI launch page contrasting before-and-after product states: Split Canvas frames the transformation as a designed reveal rather than a static comparison. The outcome is contrast: the visitor feels the shift before reading the detail.
Not for content where the before/after state is not obvious without motion.
Not for pages where split motion would hide the CTA or interrupt reading.
Animate transform and opacity, avoid layout reads in scroll handlers, pre-size media, and clean up timelines/listeners when the route changes.
The animated sequence must match DOM order. On mobile, replace pinned or horizontal mechanics with stacked sections, native swipe, or static cards.
| Prop | Type | Default | Description |
|---|---|---|---|
bgColor | color | #F5F5F0 | Page background color. |
gridSize | number | 16 | Pixel-dissolve shader's grid cell size, in px. |
numSlices | number | 32 | Number of horizontal slices the pixel-wipe transition is split into. |
canvasSize | number | 599 | Size (px) of the central transitioning canvas panel on desktop - mobile/tablet sizes scale proportionally. |
Scroll acts like a cut through the visual field, splitting and shifting the canvas between two states rather than revealing one element. The transition between states is the message. Use it where the change itself is what you want noticed.
Reduce the split travel and ensure the two states stack or transition cleanly on a narrow screen. Keep any text content in the DOM, not painted into the canvas. With reduced motion, the slice-blind and pixel motion is replaced by a plain crossfade between images, still driven by scroll.
The component renders a Three.js WebGL canvas that already pauses offscreen and when the tab is hidden; confirm it cleans up on route change and keeps meaningful HTML alongside it. Check the split doesn't clip content at the seam. There is no static fallback, so check the section still reads if WebGL fails to load.
A two-state moment — before/after, open/closed, or a strong scene change — where the cut dramatizes a transition. It's wrong for continuous reading or many states. Keep it to a single, clear split.
Avoid it where the meaning lives in text that would end up inside a canvas, on content-dense pages, or where the seam could hide information. If there's no real two-state story, the cut is empty. Skip it when a fade would do the same job.
Need a custom effect? Tell us what to create.