
Numeric Tunnel Loader
Loaders
Six draggable Canvas 2D windows that each show a different slice of the same looping video, thrown around the screen with GSAP Draggable and Inertia.
Draggable Canvas splits one looping video across six floating windows that visitors can drag and throw.
Use it when exploration is the point: a project surface, product visual, or branded scene that should respond to touch and drag without turning navigation into a toy.
The production risk is discoverability. Drag can enhance exploration, but it cannot be the only path to understand content or reach controls.
import DraggableCanvas from '@/components/effects/draggable-canvas' const page = () => { return ( <> <DraggableCanvas/> </> )} export default pageA film production company can use Draggable Canvas on its showreel page. Six framed windows each show a different crop of the same reel, and visitors can drag and throw them around the screen to piece the footage together.
The outcome is tactile exploration. The reel feels handled rather than just played, while the play button, project list, and contact link stay in normal page controls so drag is never the only path.
Not for low-power-first pages, dense content, dashboards, checkout, or routes where performance is the main conversion lever.
Each of the six windows redraws its slice of the video every frame on a Canvas 2D backing store sized to the full devicePixelRatio. The draw loops already pause when a window is offscreen or the tab is hidden. The main cost is the video itself, so keep the source file short and compressed.
The canvases are aria-hidden and the windows have no keyboard control, so keep meaningful content in HTML outside the effect. The windows are sized in vw, so they are small on phones; the built-in caption tells smaller screens it is best on desktop. With reduced motion, a released window stops where you let go and does not scale up on press. If the video fails to load, no windows render.
| Prop | Type | Default | Description |
|---|---|---|---|
friction | number | 0.12 | Inertia friction after drag release. |
scaleOnDrag | number | 1.04 | Scale applied while dragging. |
backgroundColor | string | #000000 | Canvas background color. |
canvasBorderColor | string | #71717a | Border color for each draggable canvas window. |
rounded | number | 0 | Corner radius for each draggable canvas window. |
All six windows redraw their slice of the video every frame while they are on screen, not only during a drag, at the full device pixel ratio. There is no DPR prop, so the practical levers are a smaller, well-compressed video and fewer windows if you edit the source. Test sustained dragging on mobile, where heat and battery show up fast.
If the video errors, the windows never render and only the background colour and caption remain, so provide a static image of the composition yourself. Ensure nothing important was only reachable by dragging. Any HTML you place around the effect remains intact.
It already does this for drawing: each window's redraw loop stops when that window is offscreen or the tab is hidden, and resumes on return. The GSAP Draggable instances stay attached until the component unmounts, when they are killed.
Any real content or controls labels, descriptions, links that stay in the DOM, and the drag should enhance exploration, not gate information. Provide a non-drag path to the same material for keyboard and assistive-tech users. The canvas is the playground, not the content store.
Choose a static visual when exploration adds nothing, when the audience is mostly touch, or when the interactivity risks more frustration than delight. If users won't actually benefit from moving the scene, the cost isn't justified. Reserve drag for showcases where exploring is the point.
Need a custom effect? Tell us what to create.