gsap-performance

Fix GSAP animation jank by replacing layout-affecting properties with transforms and opacity, enabling will-change, and batching reads and writes to minimize layout thrashing for smooth 60fps.

GSAP ScrollTrigger animations cause layout thrashing when unbatched read/write cycles force synchronous layout recalculations, which you solve by batching operations and carefully managing pinning and scrub settings.

The best way to animate high element counts in complex GSAP timelines is using Stagger and gsap.quickTo for performance-critical properties while enforcing will-change on animating elements.

GSAP performance optimization works best with transforms and opacity because it shifts animation work to the compositor thread, bypassing the main thread layout and paint bottlenecks.

Do not use will-change on every element or permanently, as overuse consumes excessive memory; apply it only to elements that will animate and remove it when animations complete to maintain 60fps.