
Butterfly Trail Cursor
Cursor
Turn particles into a sculptural WebGL centerpiece for bold hero sections that need presence before the first scroll.
Donut Particles turns a particle field into a sculptural brand object. It is the “yes, this site has a GPU budget” moment, used carefully.
Use Donut Particles when a hero needs one bold visual center rather than a decorative background. Brand launches, creative studios, AI pages, and campaign microsites can use it when the particle form supports the message. The page job is presence: the object should make the brand feel more tangible before the visitor reads the supporting copy.
The production risk is excess. The sculpture always draws 25,000 particles, and it can cost more than it communicates if size, spin, glow intensity, and pointer stretch all compete at once. The scene needs a clear focal role next to the copy and a performance check on real devices.
import DonutParticles from "@/components/effects/donut-particles"; const page = () => { return ( <> <DonutParticles particleColor="#9973ff" mouseInteraction={true} /> </> );}; export default page;A brand launch page can place Donut Particles beside a short hero claim to create a memorable first screen. The torus-like form moves slowly while the copy stays sharp and clickable. The outcome is presence: the brand has a visual object instead of another gradient blob.
Not for text-heavy pages, dashboards, checkout flows, dense product sections, or mobile-first routes where the particle scene becomes the page’s heaviest asset.
Not for brands that need calm clarity more than a sculptural first impression.
The particle count is fixed at 25,000 with no prop to change it, so the levers are the dpr prop (default [1, 2]), particleSize, rotationSpeed, and speed. The render loop already pauses when the canvas is offscreen or the tab is hidden, and the material and textures are disposed on unmount. Test on a mid-range laptop, not only on the machine that wrote the code.
The canvas is already marked aria-hidden, so keep the headline and any meaningful copy in HTML around it. At viewport widths of 1025px and below the donut is drawn smaller and shifted, and pointer interaction is switched off. With reduced motion, the spin, waves and pointer stretch stop and the particles hold a still torus.
| Prop | Type | Default | Description |
|---|---|---|---|
particleSize | number | 1 | Scale multiplier applied to every particle's rendered size. |
donutScale | number | 3.5 | Scale applied to the particle donut. |
particleColor | color | #9973ff | Base color used for the particle glow cycle. |
mouseInteraction | boolean | true | Enables cursor-driven particle flow on desktop viewports. |
speed | number | 1 | Playback speed multiplier for rotation and particle motion. |
intensity | number | 1 | Strength multiplier for particle glow and cursor interaction force. |
morphDuration | number | 1.5 | Seconds for scattered particles to settle back into the donut. |
demorphIntensity | number | 1 | How strongly the cursor pulls particles out of the donut shape. |
rotationSpeed | number | 1 | Donut spin speed multiplier. |
tiltX | number | -60 | Donut tilt around the X axis in degrees. |
tiltY | number | 45 | Donut tilt around the Y axis in degrees. |
Use it when a launch page or brand hero needs one sculptural WebGL particle object as the visual center.
It always draws 25,000 particles; the count is fixed in the source and is not a prop. To lighten the scene, lower the dpr prop (default [1, 2]) or reduce particleSize and rotationSpeed, and measure on real devices with the full page around it.
By default the particles react to mouse movement on desktop; set mouseInteraction to false to turn that off. Interaction is switched off automatically at viewport widths of 1025px and below and under reduced motion. The visitor should not need to play with the object to understand the page.
At 1025px and below the component already shrinks the donut and turns off pointer interaction, but it still renders all 25,000 particles. If that is too heavy, lower dpr, slow speed and rotationSpeed, or swap in your own static image on small screens. The hero must still read without live WebGL.
Only for short brand-led sections. For product explanation, use screenshots, diagrams, or feature sections where the product remains the focus.
Yes. A custom version should define shape language, particle behavior, color system, performance budget, fallback design, source handoff, and implementation notes.
Need a custom effect? Tell us what to create.