<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Alki</title>
    <description>The latest articles on DEV Community by Alki (@alki).</description>
    <link>https://dev.to/alki</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4213273%2F1aea6f08-2ad6-48f9-90e8-86b945babcdd.png</url>
      <title>DEV Community: Alki</title>
      <link>https://dev.to/alki</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/alki"/>
    <language>en</language>
    <item>
      <title>Do scroll animations hurt SEO? A practical Core Web Vitals checklist for image-sequence pages</title>
      <dc:creator>Alki</dc:creator>
      <pubDate>Sun, 08 Nov 2026 10:16:45 +0000</pubDate>
      <link>https://dev.to/alki/do-scroll-animations-hurt-seo-a-practical-core-web-vitals-checklist-for-image-sequence-pages-4o44</link>
      <guid>https://dev.to/alki/do-scroll-animations-hurt-seo-a-practical-core-web-vitals-checklist-for-image-sequence-pages-4o44</guid>
      <description>&lt;p&gt;Apple-style scroll animations don't have to cost you rankings. Here's what Google actually sees, which Core Web Vitals they can break, and a checklist to keep an animated page fast and indexable.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7y8baw20m4j2lyfrun5h.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7y8baw20m4j2lyfrun5h.png" alt="Do scroll animations hurt SEO? A practical Core Web Vitals checklist for image-sequence pages" width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Under almost every "build a 3D scroll website in 10 minutes" video, someone asks the same thing:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"But what about SEO with all this animation?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;It's a fair worry. These pages often ship a few hundred images, a big canvas and a lot of JavaScript. The good news is that the animation itself is rarely what hurts rankings. What hurts is &lt;em&gt;how&lt;/em&gt; it's built: text baked into frames, a huge hero that blocks the first paint, and layout that jumps around while frames load.&lt;/p&gt;

&lt;p&gt;This post explains what Google actually sees on an image-sequence page and gives you a checklist you can run through before you publish.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Google sees (and doesn't)
&lt;/h2&gt;

&lt;p&gt;A scroll image sequence is usually a &lt;code&gt;&amp;lt;canvas&amp;gt;&lt;/code&gt; with numbered frames drawn onto it as you scroll. To a search engine, that canvas is close to invisible: it can't read text or understand anything painted onto it.&lt;/p&gt;

&lt;p&gt;That's fine, as long as the canvas is decoration and not your content. Problems start when:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Headlines and copy are inside the frames.&lt;/strong&gt; If "The lightest headphones we've ever made" only exists as pixels in frame 0042, Google never reads it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The whole page is one giant animation.&lt;/strong&gt; No &lt;code&gt;&amp;lt;h1&amp;gt;&lt;/code&gt;, no paragraphs, nothing to rank for.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Nothing is in the HTML until JavaScript runs.&lt;/strong&gt; Google does render JavaScript, but it's slower and less reliable than plain HTML, and other crawlers and AI assistants often don't render it at all.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Rule of thumb:&lt;/strong&gt; keep every word you want to rank for as real HTML text, layered on top of or next to the canvas. Use one &lt;code&gt;&amp;lt;h1&amp;gt;&lt;/code&gt;, normal headings and paragraphs, and let the animation sit behind them.&lt;/p&gt;

&lt;h2&gt;
  
  
  The three Core Web Vitals an animation can break
&lt;/h2&gt;

&lt;p&gt;Core Web Vitals are Google's page-experience metrics. Image-sequence pages can hurt all three if you're careless.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. LCP (Largest Contentful Paint): the heavy hero
&lt;/h3&gt;

&lt;p&gt;LCP measures how fast the biggest visible element appears. On animated pages, that's usually the first frame of the hero. If the browser has to wait for a script to start, then fetch frames, then draw on a canvas, LCP gets slow.&lt;/p&gt;

&lt;p&gt;What helps:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Render the first (or current) frame immediately&lt;/strong&gt; The visitor (and Google) sees a picture right away.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Don't let the frames compete with the hero.&lt;/strong&gt; Start fetching the rest of the sequence after the page has loaded, or when the section gets close (more on that below).&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  2. CLS (Cumulative Layout Shift): the jumping page
&lt;/h3&gt;

&lt;p&gt;CLS measures how much things move while the page loads. Animated sections often start at zero height, then grow once JavaScript measures them, and everything below jumps.&lt;/p&gt;

&lt;p&gt;What helps:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Reserve the space up front.&lt;/strong&gt; Give the canvas wrapper a fixed &lt;code&gt;aspect-ratio&lt;/code&gt; (for example &lt;code&gt;aspect-ratio: 16 / 9&lt;/code&gt;) or an explicit height in CSS, so the layout is final before any frame arrives.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Set the scroll length in CSS, not after load.&lt;/strong&gt; If the pinned section is &lt;code&gt;300vh&lt;/code&gt; tall, write that in the stylesheet rather than calculating it in JS.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Watch out for iOS Safari's address bar.&lt;/strong&gt; When it shows and hides, the viewport resizes. With GSAP, &lt;code&gt;ScrollTrigger.config({ ignoreMobileResize: true })&lt;/code&gt; stops it from recalculating and jumping mid-scroll. Scrollsequence handles this automatically.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  3. INP (Interaction to Next Paint): the busy main thread
&lt;/h3&gt;

&lt;p&gt;INP measures how quickly the page responds when someone taps or clicks. Decoding and drawing large frames on every scroll event can keep the main thread busy, so buttons feel sluggish.&lt;/p&gt;

&lt;p&gt;What helps:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Draw inside &lt;code&gt;requestAnimationFrame&lt;/code&gt;,&lt;/strong&gt; and skip the draw when the frame index hasn't changed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Do not decode ahead of time.&lt;/strong&gt; &lt;code&gt;await img.decode()&lt;/code&gt; (or &lt;code&gt;createImageBitmap&lt;/code&gt;) just bloats memory and crashes tabs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cap the canvas resolution.&lt;/strong&gt; On phones, limit it to a device pixel ratio of 2. Drawing at 3x on a large screen is a lot of pixels for very little visible gain.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Keep the total weight sane
&lt;/h2&gt;

&lt;p&gt;Search engines don't penalise a page for being "big" as such, but heavy pages do worse on LCP and mobile, and real visitors bounce. Some realistic targets:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Typical AI-demo export&lt;/th&gt;
&lt;th&gt;A sane target&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Format&lt;/td&gt;
&lt;td&gt;JPG, WebP or AVIF, about 75–80 quality&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Frames&lt;/td&gt;
&lt;td&gt;200–300+&lt;/td&gt;
&lt;td&gt;60–150&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Width&lt;/td&gt;
&lt;td&gt;Full source size&lt;/td&gt;
&lt;td&gt;about 1600–1920px desktop, about 960px phones&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Total&lt;/td&gt;
&lt;td&gt;Often 100+ MB&lt;/td&gt;
&lt;td&gt;Usually 5–15 MB&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;If you're starting from a video, ffmpeg gets you most of the way:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;ffmpeg &lt;span class="nt"&gt;-i&lt;/span&gt; hero.mp4 &lt;span class="nt"&gt;-vf&lt;/span&gt; &lt;span class="s2"&gt;"fps=24,scale=1600:-1"&lt;/span&gt; &lt;span class="nt"&gt;-c&lt;/span&gt;:v libwebp &lt;span class="nt"&gt;-quality&lt;/span&gt; 78 frames/hero_%04d.webp
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then make a smaller set for phones (narrower, and every other frame is usually enough).&lt;/p&gt;

&lt;h2&gt;
  
  
  Lazy-load the sequence, not the content
&lt;/h2&gt;

&lt;p&gt;Load the frames only when the section is about to be seen. &lt;code&gt;IntersectionObserver&lt;/code&gt; is the simplest way to do it: think of it as a doorbell that rings when the section comes near the screen.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;section&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;document&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;querySelector&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;.hero-sequence&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;io&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;IntersectionObserver&lt;/span&gt;&lt;span class="p"&gt;((&lt;/span&gt;&lt;span class="nx"&gt;entries&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;entries&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;].&lt;/span&gt;&lt;span class="nx"&gt;isIntersecting&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nf"&gt;loadFrames&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt; &lt;span class="c1"&gt;// your preload function&lt;/span&gt;
    &lt;span class="nx"&gt;io&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;disconnect&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;},&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;rootMargin&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;600px 0px&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt; &lt;span class="p"&gt;});&lt;/span&gt; &lt;span class="c1"&gt;// start a bit before it's visible&lt;/span&gt;

&lt;span class="nx"&gt;io&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;observe&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;section&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Two extra tips:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Load in passes.&lt;/strong&gt; Fetch every 8th frame first so the animation is scrubbable immediately, then fill in the gaps while the visitor scrolls.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Never lazy-load your text.&lt;/strong&gt; Only the frames should wait. Headings and copy belong in the initial HTML.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Accessibility helps too
&lt;/h2&gt;

&lt;p&gt;Accessibility isn't a direct ranking factor, but it overlaps a lot with what search engines can understand:&lt;/p&gt;

&lt;p&gt;Give the canvas &lt;code&gt;role="img"&lt;/code&gt; and an &lt;code&gt;aria-label&lt;/code&gt; describing what the animation shows, or mark it &lt;code&gt;aria-hidden="true"&lt;/code&gt; if it's purely decorative and the text nearby says everything.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pre-publish checklist
&lt;/h2&gt;

&lt;p&gt;Run through this before you ship an animated page:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Every heading and sentence you care about is real HTML text, not pixels in a frame.&lt;/li&gt;
&lt;li&gt;One &lt;code&gt;&amp;lt;h1&amp;gt;&lt;/code&gt;, and a sensible heading structure under it.&lt;/li&gt;
&lt;li&gt;The first (current) frame is shown immediately and is not hidden until animation is loaded.&lt;/li&gt;
&lt;li&gt;The animation section has its size reserved in CSS (no layout jump).&lt;/li&gt;
&lt;li&gt;Frames are WebP or JPG, 60–150 of them, total under about 15 MB.&lt;/li&gt;
&lt;li&gt;There's a lighter frame set for phones.&lt;/li&gt;
&lt;li&gt;Drawing happens in &lt;code&gt;requestAnimationFrame&lt;/code&gt; and skips unchanged frames.&lt;/li&gt;
&lt;li&gt;PageSpeed Insights on mobile shows LCP, CLS and INP in the green (or at least not red).&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  So, does it hurt SEO?
&lt;/h2&gt;

&lt;p&gt;Not if the animation is decoration on top of a real page. Google ranks the text, structure and speed; it doesn't care that a pair of headphones spins while you scroll. Keep the words in HTML, keep the frames light and late, and an animated page can rank just like a static one.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://scrollsequence.com" rel="noopener noreferrer"&gt;Scrollsequence&lt;/a&gt;, a WordPress plugin (with a JS/React SDK in v2) for image-sequence scroll animations. It handles the frame optimisation, mobile frame set and progressive loading described above, so if you'd rather not wire it up by hand, that's an option. Everything in the checklist works without it, too.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on the &lt;a href="https://beta.scrollsequence.com/blog/scroll-animation-seo-core-web-vitals" rel="noopener noreferrer"&gt;Scrollsequence blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>seo</category>
      <category>performance</category>
      <category>javascript</category>
    </item>
    <item>
      <title>How many frames does a scroll animation need? (and how big should each be)</title>
      <dc:creator>Alki</dc:creator>
      <pubDate>Fri, 06 Nov 2026 10:11:38 +0000</pubDate>
      <link>https://dev.to/alki/how-many-frames-does-a-scroll-animation-need-and-how-big-should-each-be-47e8</link>
      <guid>https://dev.to/alki/how-many-frames-does-a-scroll-animation-need-and-how-big-should-each-be-47e8</guid>
      <description>&lt;p&gt;Short answer: for a typical hero scroll animation, 60–350 frames is enough. Aim for about 10–20px of scroll per frame, export each frame at the size it's displayed, and target roughly 15–40KB per WebP frame. On mobile, use a thinner set: smaller dimensions and often 40–100 frames. More frames only help if the scroll distance is long enough to show them.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do I work out the right frame count?
&lt;/h2&gt;

&lt;p&gt;Start from scroll distance, not video length:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;frames ≈ scroll distance (px) ÷ 10–20
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ul&gt;
&lt;li&gt;Animation spans 1,500px of scroll → about 75–100 frames.&lt;/li&gt;
&lt;li&gt;Spans 3,000px → about 150–200 frames.&lt;/li&gt;
&lt;li&gt;Spans 800px → about 40–55 frames.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If your video has more frames than that, drop every second or third frame.&lt;/p&gt;

&lt;h2&gt;
  
  
  When do more frames help?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Long, slow scroll sections where each frame is on screen for a while.&lt;/li&gt;
&lt;li&gt;Fast motion in the source (a quick spin) where gaps would look jumpy.&lt;/li&gt;
&lt;li&gt;Large, high-contrast subjects where frame-to-frame jumps are easy to see.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  When do more frames hurt?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;On mobile, where every extra frame adds loading time if you are on a slow connection.&lt;/li&gt;
&lt;li&gt;Short scroll sections, where several frames get skipped per scroll step anyway.&lt;/li&gt;
&lt;li&gt;Above the fold, where loading hundreds of images delays everything else.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How big should each frame be?
&lt;/h2&gt;

&lt;p&gt;Two numbers matter:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;File size (download):&lt;/strong&gt; WebP at moderate quality, around 15–90KB per frame for a hero. Larger for full-screen detailed shots, smaller for simple renders.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Decoded size (memory):&lt;/strong&gt; width × height × 4 bytes, regardless of format. A 1920×1080 frame is about 8 MB in memory; 1280×720 is about 3.7 MB; 750×1334 is about 4 MB.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Export at the width it's actually displayed. A full-width desktop hero rarely needs more than 1920px; a phone set rarely needs more than ~800–1000px on the long side.&lt;/p&gt;

&lt;h2&gt;
  
  
  What about mobile?
&lt;/h2&gt;

&lt;p&gt;Use a separate mobile frame set: portrait crop, smaller dimensions, and fewer frames if the scroll section is shorter on phones. That's the single biggest fix for phone lag and iOS crashes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick reference
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Desktop hero&lt;/th&gt;
&lt;th&gt;Mobile set&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Frames&lt;/td&gt;
&lt;td&gt;60–150&lt;/td&gt;
&lt;td&gt;40–100&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Scroll per frame&lt;/td&gt;
&lt;td&gt;15–20px&lt;/td&gt;
&lt;td&gt;15–20px&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Long side&lt;/td&gt;
&lt;td&gt;up to ~1920px&lt;/td&gt;
&lt;td&gt;~800–1000px&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Format&lt;/td&gt;
&lt;td&gt;WebP&lt;/td&gt;
&lt;td&gt;WebP&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Per-frame file&lt;/td&gt;
&lt;td&gt;~15–90KB&lt;/td&gt;
&lt;td&gt;~10–25KB&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;These are starting points, not laws. Test on a real phone and adjust.&lt;/p&gt;

&lt;p&gt;Converting a video to frames at these settings is what the free npx scrollsequence vid2ssq converter is for; Scrollsequence v2 also has it built into wp-admin, with multi-resolution sequences for the mobile set.&lt;/p&gt;

&lt;h2&gt;
  
  
  Related reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://beta.scrollsequence.com/blog/image-sequence-lagging-on-mobile-9-fixes" rel="noopener noreferrer"&gt;Image sequence scroll animation lagging on mobile? 9 fixes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://beta.scrollsequence.com/blog/webp-vs-png-vs-jpg-image-sequences" rel="noopener noreferrer"&gt;WebP vs PNG vs JPG for image sequences&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://beta.scrollsequence.com/blog/iphone-safari-scroll-animation-crash-reload" rel="noopener noreferrer"&gt;iPhone Safari crashes or reloads on my scroll animation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Should I match the video's frame rate?&lt;/strong&gt; No. Scroll animations aren't tied to time. Match frames to scroll distance instead.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does a higher frame count make it smoother?&lt;/strong&gt; Only up to about one frame per 10–20px of scroll. Beyond that, frames get skipped and you just pay for them in memory and bandwidth.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What resolution should mobile frames be?&lt;/strong&gt; Around 800–1000px wide is a good start, cropped to fit on phone screen.&lt;/p&gt;

&lt;p&gt;Read the original: &lt;a href="https://beta.scrollsequence.com/blog/how-many-frames-scroll-animation" rel="noopener noreferrer"&gt;How many frames does a scroll animation need? (and how big should each be)&lt;/a&gt;&lt;/p&gt;

</description>
      <category>animation</category>
      <category>frontend</category>
      <category>performance</category>
      <category>webdev</category>
    </item>
    <item>
      <title>iPhone Safari crashes or reloads on my scroll animation: why and how to fix it</title>
      <dc:creator>Alki</dc:creator>
      <pubDate>Thu, 05 Nov 2026 10:11:26 +0000</pubDate>
      <link>https://dev.to/alki/iphone-safari-crashes-or-reloads-on-my-scroll-animation-why-and-how-to-fix-it-3l6b</link>
      <guid>https://dev.to/alki/iphone-safari-crashes-or-reloads-on-my-scroll-animation-why-and-how-to-fix-it-3l6b</guid>
      <description>&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; Safari on iPhone reloads the page (or shows "A problem repeatedly occurred") when a tab uses too much memory, and image sequences are a classic cause. Every frame is decoded into raw pixels at width × height × 4 bytes. Fix it with fewer and smaller frames, a separate mobile frame set, not holding every frame decoded at once, and avoiding large PNGs.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why does Safari reload the page?
&lt;/h2&gt;

&lt;p&gt;iOS gives each Safari tab a limited amount of memory and doesn't swap the way a desktop does. When a tab goes over its budget, iOS kills the web content process. Safari then reloads the page automatically, and if it happens again you get "A problem repeatedly occurred."&lt;/p&gt;

&lt;p&gt;It often feels random because it depends on the device, how many other tabs are open, and how far you've scrolled.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why do image sequences use so much memory?
&lt;/h2&gt;

&lt;p&gt;The file you download is compressed. To draw it, the browser decodes it into raw pixels:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;width × height × 4 bytes&lt;/code&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;1920×1080 → about 8.3 MB per frame&lt;/li&gt;
&lt;li&gt;150 frames held decoded → about 1.2 GB&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Compression (WebP, JPG, AVIF) doesn't change this number. A 30KB WebP and a 3MB PNG at the same dimensions take the same memory once decoded.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to fix it
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Do not store frames in memory.&lt;/strong&gt; Avoid &lt;code&gt;createImageBitmap&lt;/code&gt; for every frame.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Use smaller frames on phones.&lt;/strong&gt; Around 800–1000px wide, not the full desktop size.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Serve a separate mobile frame set&lt;/strong&gt;, ideally a portrait crop. Scrollsequence v2 supports multi-resolution sequences for this.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Don't hold every frame decoded.&lt;/strong&gt; If you write your own code, keep a window of frames around the current position and release the rest, rather than keeping hundreds of Image or ImageBitmap objects alive. (Call &lt;code&gt;.close()&lt;/code&gt; on ImageBitmaps you no longer need.)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Avoid giant PNGs.&lt;/strong&gt; They're slow to download and decode. Use JPG or WebP when you need transparency.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cap the canvas resolution.&lt;/strong&gt; Sizing the canvas to a 3× device pixel ratio multiplies its memory by 9 compared to 1×. Cap DPR at around 1.5–2.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How do I check it's fixed?
&lt;/h2&gt;

&lt;p&gt;Test on a real iPhone, not just desktop responsive mode, which uses your computer's memory. Scroll the animation fast, several times, with a few other tabs open. If you have a Mac, Safari's Web Inspector (connected to the iPhone) can show memory use while you scroll.&lt;/p&gt;

&lt;p&gt;For lag and blank frames that aren't crashes, see the full list: &lt;a href="https://beta.scrollsequence.com/blog/image-sequence-lagging-on-mobile-9-fixes" rel="noopener noreferrer"&gt;image sequence lagging on mobile? 9 fixes&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Why does it only crash on iPhone and not Android or desktop?&lt;/strong&gt; iOS is strict about per-tab memory and kills the tab rather than slowing down. Low-memory Android phones can do the same; desktops have more memory and swap.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Will switching from PNG to WebP fix the crash?&lt;/strong&gt; It helps download and decode speed, but decoded memory depends on dimensions. You also need smaller frames or fewer of them held at once.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is this a Safari bug?&lt;/strong&gt; No, it's how iOS manages memory. The fix is to use less of it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can I just show a video on iPhone instead?&lt;/strong&gt; A normally playing video or a static image is a fine fallback. Scrubbing a video with scroll tends to stutter, so a light mobile image sequence is usually better.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on the &lt;a href="https://beta.scrollsequence.com/blog/iphone-safari-scroll-animation-crash-reload" rel="noopener noreferrer"&gt;Scrollsequence blog&lt;/a&gt;. Scrollsequence is a free-to-start scroll animation toolkit that works on any site.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>safari</category>
      <category>ios</category>
      <category>performance</category>
    </item>
    <item>
      <title>WebP vs PNG vs JPG for image sequences: file-size and performance test</title>
      <dc:creator>Alki</dc:creator>
      <pubDate>Wed, 04 Nov 2026 10:10:20 +0000</pubDate>
      <link>https://dev.to/alki/webp-vs-png-vs-jpg-for-image-sequences-file-size-and-performance-test-59nd</link>
      <guid>https://dev.to/alki/webp-vs-png-vs-jpg-for-image-sequences-file-size-and-performance-test-59nd</guid>
      <description>&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; for scroll image sequences, &lt;strong&gt;WebP and JPG are the sensible choices&lt;/strong&gt;, while &lt;strong&gt;PNG is almost always a mistake&lt;/strong&gt;. PNG files are 5× to 10× larger, destroying load times, stalling network queues, and blowing past mobile cellular limits. If you don't need transparency, JPG and WebP offer fast decode and compact file sizes (15–90KB per frame). If you do need transparency, use &lt;strong&gt;lossy WebP with alpha&lt;/strong&gt; instead of PNG to get the same clean transparent edges at 70–85% smaller file sizes. Remember: whatever the format on disk, decoded memory in RAM is always the same: width × height × 4 bytes per frame.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why does format matter more for sequences than for normal images?
&lt;/h2&gt;

&lt;p&gt;A normal webpage shows each image once. A scroll sequence downloads, decodes, and draws &lt;strong&gt;dozens to hundreds&lt;/strong&gt; of frames in rapid succession while the visitor scrolls. This compounds three separate costs:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Total download size&lt;/strong&gt;: frames × average file size. An extra 100KB per frame turns a snappy 4MB sequence into a bloated 19MB payload.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Network concurrency &amp;amp; latency&lt;/strong&gt;: browsers open a limited number of parallel HTTP connections. Giant frame files queue up, leaving the canvas blank on fast scrubs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Decompression overhead&lt;/strong&gt;: uncompressing heavy files continuously consumes CPU cycles on the main thread, competing with scroll handlers and layout recalculation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A format that inflates file size ruins the smoothness before a single frame even hits the screen.&lt;/p&gt;

&lt;h2&gt;
  
  
  Comparison overview
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Format&lt;/th&gt;
&lt;th&gt;Transparency&lt;/th&gt;
&lt;th&gt;Typical frame size (1080p hero)&lt;/th&gt;
&lt;th&gt;Decode speed&lt;/th&gt;
&lt;th&gt;Browser support&lt;/th&gt;
&lt;th&gt;Verdict for scroll animations&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;WebP&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Yes (Lossy &amp;amp; Lossless)&lt;/td&gt;
&lt;td&gt;15–90 KB&lt;/td&gt;
&lt;td&gt;Fast&lt;/td&gt;
&lt;td&gt;Universal (iOS 14+, all modern browsers)&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;Best default&lt;/strong&gt; for modern web&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;JPG&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;20–100 KB&lt;/td&gt;
&lt;td&gt;Fastest (hardware decode)&lt;/td&gt;
&lt;td&gt;Universal (all browsers)&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;Safe fallback&lt;/strong&gt; for opaque footage&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;PNG&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Yes (Lossless only)&lt;/td&gt;
&lt;td&gt;300–1500 KB+&lt;/td&gt;
&lt;td&gt;Slowest&lt;/td&gt;
&lt;td&gt;Universal (all browsers)&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;Avoid&lt;/strong&gt; — burns bandwidth and chokes loading&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  What the formats mean in practice
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. JPG: The fast, reliable workhorse for opaque footage
&lt;/h3&gt;

&lt;p&gt;JPG has existed for decades, and modern mobile hardware chips decode JPGs blisteringly fast.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Strengths:&lt;/strong&gt; Universally supported, highly reliable, and decodes with minimal CPU overhead.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Weaknesses:&lt;/strong&gt; No alpha channel (no transparency). At identical visual quality levels, JPG files are typically 25–35% larger than equivalent WebP frames.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;When to use:&lt;/strong&gt; Great for full-bleed photography, live-action footage, and as a guaranteed fallback when transparency is not required.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  2. WebP: The modern standard for scroll animations
&lt;/h3&gt;

&lt;p&gt;Developed by Google and supported in all modern browsers (including Apple Safari on iOS 14 and macOS Big Sur onwards), WebP is the sweet spot for web animation:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Strengths:&lt;/strong&gt; 25–35% smaller than JPG for photography, fast decode times, and crucially: &lt;strong&gt;lossy compression with alpha transparency&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Weaknesses:&lt;/strong&gt; Encoding can take slightly longer than JPG when generating sequences from command line tools (though tools like &lt;code&gt;vid2ssq&lt;/code&gt; optimize this).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;When to use:&lt;/strong&gt; The recommended default for all scroll image sequences today.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  3. PNG: The bandwidth trap
&lt;/h3&gt;

&lt;p&gt;PNG is a lossless format designed for crisp line-art, icons, and archival graphic assets—not video sequences.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The problem:&lt;/strong&gt; Because PNG does not discard imperceptible pixel data, a single 1080p frame from a 3D render or video clip frequently weighs 500KB to 2MB. A 120-frame hero sequence exported in PNG can easily exceed &lt;strong&gt;80MB to 150MB&lt;/strong&gt;!&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Decode cost:&lt;/strong&gt; Decompressing complex PNG zlib streams frame-by-frame while scrubbing puts unnecessary load on mobile CPUs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The transparency myth:&lt;/strong&gt; Developers often default to PNG because "I need transparent cutout frames for my product rotation." But WebP supports alpha channels with lossy compression, providing identical transparent cutouts at a tiny fraction of the weight.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Does format change memory use?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;No.&lt;/strong&gt; This is the biggest misconception about image formats.&lt;/p&gt;

&lt;p&gt;Compression formats (WebP, JPG, PNG) only dictate the file size stored on disk and sent over the network. Once the browser decodes an image to paint it onto a &lt;code&gt;&amp;lt;canvas&amp;gt;&lt;/code&gt;, it decompresses into a raw bitmap:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Decoded size = width × height × 4 bytes (Red, Green, Blue, Alpha)&lt;/p&gt;
&lt;/blockquote&gt;

&lt;ul&gt;
&lt;li&gt;A 1920×1080 frame takes &lt;strong&gt;~8.3 MB in memory&lt;/strong&gt; whether the file was a 35KB WebP, a 60KB JPG, or a 1.8MB PNG.&lt;/li&gt;
&lt;li&gt;100 frames at 1920×1080 consume &lt;strong&gt;~830 MB of memory&lt;/strong&gt; if kept decoded simultaneously.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Converting from PNG to WebP will fix your network bottlenecks, eliminate initial loading lag, and prevent mobile data caps from being blown—but it will not prevent iOS memory crashes by itself. To solve memory issues, you must reduce &lt;strong&gt;dimensions&lt;/strong&gt;, &lt;strong&gt;frame counts&lt;/strong&gt;, and avoid holding all decoded frames at once (see &lt;a href="https://beta.scrollsequence.com/blog/image-sequence-lagging-on-mobile-9-fixes" rel="noopener noreferrer"&gt;image sequence lagging on mobile? 9 fixes&lt;/a&gt;).&lt;/p&gt;

&lt;h2&gt;
  
  
  Recommendations: Which should you choose?
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;For opaque animations (full-screen video, product spins, landscape heroes):&lt;/strong&gt;
Use &lt;strong&gt;WebP&lt;/strong&gt; at quality 75–85 (or optimized JPG). Target roughly &lt;strong&gt;15–90KB&lt;/strong&gt; per desktop frame and &lt;strong&gt;10–35KB&lt;/strong&gt; for mobile frames.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;For cutouts and transparent products (floating 3D models, UI overlays):&lt;/strong&gt;
Always use &lt;strong&gt;lossy WebP with alpha&lt;/strong&gt;. Never use PNG unless you have an ultra-short sequence (10–15 frames) of flat vector graphics.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;For conversion:&lt;/strong&gt;
Use tools built specifically for scroll sequences like &lt;code&gt;vid2ssq&lt;/code&gt; (&lt;code&gt;npx scrollsequence vid2ssq&lt;/code&gt; or built into Scrollsequence for WordPress), which automatically optimizes frame sizing and WebP compression for smooth canvas delivery. For general frame extraction tools, check out &lt;a href="https://beta.scrollsequence.com/blog/how-to-convert-video-to-images" rel="noopener noreferrer"&gt;how to convert video to images: free tools tested&lt;/a&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Related reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://beta.scrollsequence.com/blog/image-sequence-lagging-on-mobile-9-fixes" rel="noopener noreferrer"&gt;Image sequence lagging on mobile? 9 fixes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://beta.scrollsequence.com/blog/how-many-frames-scroll-animation" rel="noopener noreferrer"&gt;How many frames does a scroll animation need?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://beta.scrollsequence.com/blog/iphone-safari-scroll-animation-crash-reload" rel="noopener noreferrer"&gt;iPhone Safari crashes or reloads on my scroll animation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://beta.scrollsequence.com/blog/how-to-convert-video-to-images" rel="noopener noreferrer"&gt;How to convert video to images: free tools tested&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Does WebP work on iPhone?&lt;/strong&gt;&lt;br&gt;
Yes. Safari has natively supported WebP since iOS 14 (released in 2020). The myth that iPhones can't display WebP is years out of date.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why is PNG so bad for scroll image sequences?&lt;/strong&gt;&lt;br&gt;
Because PNG is lossless. A 1080p PNG frame is easily 500KB–1.5MB. Multiply that by 100 frames, and visitors must download over 100MB of data before they can smoothly scroll your hero section.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can WebP replace transparent PNGs?&lt;/strong&gt;&lt;br&gt;
Yes. WebP supports full alpha transparency (variable opacity) using lossy compression. You get the transparent background and crisp foreground object with 70–85% lower file sizes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What quality setting should I use for WebP sequences?&lt;/strong&gt;&lt;br&gt;
Start around quality 75–80. Because images are in rapid motion while the user scrolls, visual artifacts that might be visible in a stationary photograph are completely imperceptible during scroll animation.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://beta.scrollsequence.com/blog/webp-vs-png-vs-jpg-image-sequences" rel="noopener noreferrer"&gt;Scrollsequence&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>performance</category>
      <category>javascript</category>
      <category>webp</category>
    </item>
    <item>
      <title>Image sequence scroll animation lagging on mobile? 9 fixes</title>
      <dc:creator>Alki</dc:creator>
      <pubDate>Tue, 03 Nov 2026 10:10:20 +0000</pubDate>
      <link>https://dev.to/alki/image-sequence-scroll-animation-lagging-on-mobile-9-fixes-260k</link>
      <guid>https://dev.to/alki/image-sequence-scroll-animation-lagging-on-mobile-9-fixes-260k</guid>
      <description>&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; mobile lag in a scroll image sequence almost always comes from the frames themselves: too many, too large, decoded at full resolution into the phone's limited memory, and loaded all at once. Use fewer frames, a separate smaller mobile frame set, JPG or WebP at sensible quality, progressive loading, and canvas drawing tied to animation frames rather than raw scroll events. The nine fixes below cover each cause, in the order that usually gives the biggest win.&lt;/p&gt;

&lt;p&gt;If your animation is fine on a laptop and falls apart on a phone, you're not alone. It's the single most common problem we see from people building Apple-style scroll pages, whether they wrote the code by hand, generated it with an AI assistant, or used a plugin. The good news: it's fixable, and you rarely have to give up the effect.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why do image sequences lag on phones but not on desktop?
&lt;/h2&gt;

&lt;p&gt;A scroll image sequence is a folder of numbered images (frame_0001.webp, frame_0002.webp...) drawn onto a &lt;code&gt;&amp;lt;canvas&amp;gt;&lt;/code&gt; one at a time as you scroll. It's a simple idea, but it asks three things of the device:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Download&lt;/strong&gt; every frame (network and data).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Decode&lt;/strong&gt; each frame into raw pixels (CPU and memory).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Draw&lt;/strong&gt; the right frame fast enough to keep up with your thumb (GPU and main thread).&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A desktop has a fast connection, gigabytes of spare memory, and a strong CPU. A phone has a fraction of that memory available to a single browser tab, a variable connection, and an operating system that will happily kill a tab that uses too much. The same sequence that feels instant on desktop can be several times too heavy for mobile.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix 1: Use fewer frames
&lt;/h2&gt;

&lt;p&gt;More frames don't automatically mean smoother. Smoothness comes from how many frames change per unit of scroll, not the total count. For a typical hero animation, &lt;strong&gt;60–350 frames&lt;/strong&gt; is usually plenty. Around &lt;strong&gt;10–20px of scroll per frame&lt;/strong&gt; feels fluid; tighter than that and most visitors can't see the difference, but their phone feels it.&lt;/p&gt;

&lt;p&gt;If you exported every frame of a 10-second, 30fps clip, that's 300 frames. Dropping to every second or third frame often looks identical on scroll when there is no fast movement.&lt;/p&gt;

&lt;p&gt;Read more in &lt;a href="https://beta.scrollsequence.com/blog/how-many-frames-scroll-animation" rel="noopener noreferrer"&gt;how many frames a scroll animation needs&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix 2: Make each frame smaller (dimensions first, then format)
&lt;/h2&gt;

&lt;p&gt;Frame dimensions matter more than most people think. A 1920×1080 frame shown in a 390px-wide phone viewport is wasted pixels. Export at the size the frame is actually displayed, with a sensible allowance for screen density (capping canvas DPR at 1.5–2×; see Fix 5 for mobile sets).&lt;/p&gt;

&lt;p&gt;Then pick a compact format. For most sequences today, &lt;strong&gt;JPG or WebP&lt;/strong&gt; at moderate quality is the best default: small files, fast decode, and universal support in current browsers. Avoid PNG and use WebP for transparency, and even then test the size. A useful target is roughly &lt;strong&gt;15–90KB per frame&lt;/strong&gt; for a hero sequence.&lt;/p&gt;

&lt;p&gt;Format comparison: &lt;a href="https://beta.scrollsequence.com/blog/webp-vs-png-vs-jpg-image-sequences" rel="noopener noreferrer"&gt;WebP vs PNG vs JPG for image sequences&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix 3: Understand decoded memory (width × height × 4)
&lt;/h2&gt;

&lt;p&gt;This is the part almost nobody explains. File size is what you download; &lt;strong&gt;decoded size&lt;/strong&gt; is what the browser holds in memory to draw the frame. A decoded image takes roughly:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;width × height × 4 bytes (one byte each for red, green, blue, alpha)&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;So:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;One 1920×1080 frame ≈ 8.3 MB decoded, no matter whether the file was 40KB or 400KB.&lt;/li&gt;
&lt;li&gt;150 of those ≈ 1.2 GB if they're all kept decoded at once.&lt;/li&gt;
&lt;li&gt;The same 150 frames at 750×1334 ≈ 4 MB each, about 600 MB total. Still heavy.&lt;/li&gt;
&lt;li&gt;At 540×960 ≈ 2 MB each, about 310 MB total.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That's why compressing the file harder doesn't fix mobile crashes on its own. You have to reduce &lt;strong&gt;dimensions&lt;/strong&gt; and &lt;strong&gt;how many frames are decoded at the same time&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix 4: Don't let mobile address bar resizes trash your layout
&lt;/h2&gt;

&lt;p&gt;On mobile Safari and Chrome, scrolling down automatically hides the browser's top address bar and bottom navigation toolbar; scrolling up brings them back. Every time this happens, the browser window height changes by 60–100px.&lt;/p&gt;

&lt;p&gt;If your animation setup isn't prepared for this, two problems ruin your page:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Layout jump (CLS):&lt;/strong&gt; If your sticky section or canvas container uses CSS &lt;code&gt;100vh&lt;/code&gt; (or &lt;code&gt;100dvh&lt;/code&gt;), its height changes dynamically mid-scroll, causing visible jerking and content jumps.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Performance thrashing:&lt;/strong&gt; If your JavaScript recalculates the canvas dimensions, scroll triggers, or timeline on every window &lt;code&gt;resize&lt;/code&gt; event, the browser fires resize handlers while the user is actively scrolling. Tearing down and rebuilding scroll calculations mid-gesture destroys frame rates.&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  How to fix it:
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Filter window &lt;code&gt;resize&lt;/code&gt; events in JS:&lt;/strong&gt; Only recalculate your layout when the viewport &lt;strong&gt;width&lt;/strong&gt; changes (such as device rotation / orientation change). Ignore vertical-only height changes caused by the address bar:
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;  &lt;span class="kd"&gt;let&lt;/span&gt; &lt;span class="nx"&gt;lastWidth&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;window&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;innerWidth&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

  &lt;span class="nb"&gt;window&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;addEventListener&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;resize&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="c1"&gt;// Ignore height-only resizes from mobile URL bar collapsing&lt;/span&gt;
    &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nb"&gt;window&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;innerWidth&lt;/span&gt; &lt;span class="o"&gt;===&lt;/span&gt; &lt;span class="nx"&gt;lastWidth&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="nx"&gt;lastWidth&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;window&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;innerWidth&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

    &lt;span class="nf"&gt;recalculateScrollAnimation&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;
  &lt;span class="p"&gt;});&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Fix 5: Serve a separate portrait / mobile frame set
&lt;/h2&gt;

&lt;p&gt;A landscape 16:9 sequence on a portrait phone is usually either tiny or cropped, and you're shipping pixels nobody sees. One of the clean fixes is a &lt;strong&gt;second frame set made for mobile&lt;/strong&gt;: portrait or square crop, smaller dimensions, and often fewer frames.&lt;/p&gt;

&lt;p&gt;This also solves composition: you can reframe the subject so it fills a phone screen properly instead of shrinking a desktop shot.&lt;/p&gt;

&lt;p&gt;In Scrollsequence v2, sequences support multi-resolution packaging, allowing you to deliver a dedicated, lower-resolution image set specifically tailored to phone viewports.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix 6: Don't preload everything; load progressively
&lt;/h2&gt;

&lt;p&gt;The classic tutorial approach is "load all 300 images, then start." On mobile that means a long blank wait, a big data bill, and a memory spike.&lt;/p&gt;

&lt;p&gt;Better strategies:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Load the first frame immediately&lt;/strong&gt; so something is visible at once (and it can be your poster image).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Load a sparse pass first&lt;/strong&gt; (every 4th or 8th frame) so scrubbing works early at lower smoothness, then fill in the gaps.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Start loading when the section approaches the viewport&lt;/strong&gt;, not on page load, if the animation isn't at the top.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Release or avoid keeping every frame decoded&lt;/strong&gt; at once on low-memory devices.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Scrollsequence implements this with a smart sparse preload algorithm: Frame 0 loads first with atomic priority so the poster image is immediate, followed by a distributed pass across the sequence so visitors can scrub right away. The remaining frames fill in progressively in the background without flooding memory.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix 7: Stop the blank canvas on fast scroll
&lt;/h2&gt;

&lt;p&gt;If you flick fast and the canvas flashes blank or white, the code is trying to draw a frame that hasn't loaded or decoded yet, and clearing the canvas before it has anything to draw.&lt;/p&gt;

&lt;p&gt;Fixes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Never clear the canvas unless you have a frame to draw.&lt;/strong&gt; If the target frame isn't loaded yet, keep drawing the nearest loaded neighbor frame instead of flashing blank or white.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Draw inside &lt;code&gt;requestAnimationFrame&lt;/code&gt;&lt;/strong&gt;, not on every raw &lt;code&gt;scroll&lt;/code&gt; event. Scroll events can fire hundreds of times per second; you only need one canvas draw per display refresh.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The "pre-decode" dead end (&lt;code&gt;createImageBitmap&lt;/code&gt; / &lt;code&gt;img.decode()&lt;/code&gt;):&lt;/strong&gt; Many tutorials and AI code generators attempt to fix stutter by pre-decoding upcoming frames with &lt;code&gt;createImageBitmap()&lt;/code&gt; or &lt;code&gt;img.decode()&lt;/code&gt;. On mobile, this is a trap:

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;createImageBitmap()&lt;/code&gt; forces uncompressed RGBA bitmap buffers directly into RAM. Holding dozens of uncompressed bitmaps in memory will quickly exhaust iOS Safari's tab memory limit and crash the page (see Fix 8).&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;img.decode()&lt;/code&gt; is designed to prevent DOM jank when inserting an &lt;code&gt;&amp;lt;img&amp;gt;&lt;/code&gt; tag into the document; it doesn't prevent canvas draw cost or memory bloat.&lt;/li&gt;
&lt;li&gt;The true cure for canvas flashing on fast scrolls is nearest-neighbor fallback, not forcing ahead-of-time bitmap allocations.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is the same family of issues covered in &lt;a href="https://beta.scrollsequence.com/blog/ai-scroll-animation-lag-fix" rel="noopener noreferrer"&gt;why your AI-built scroll animation lags&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix 8: Know when iOS Safari is killing the tab
&lt;/h2&gt;

&lt;p&gt;If the page &lt;strong&gt;reloads by itself&lt;/strong&gt; on an iPhone, or Safari shows "A problem repeatedly occurred," that isn't lag: iOS ran out of memory for the tab and killed it. It's the extreme end of Fix 3. The cure is the same set of fixes (fewer, smaller frames, a mobile set, not holding everything decoded), but it deserves its own checklist: &lt;a href="https://beta.scrollsequence.com/blog/iphone-safari-scroll-animation-crash-reload" rel="noopener noreferrer"&gt;iPhone Safari crashes or reloads on my scroll animation&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix 9: Protect LCP and Core Web Vitals
&lt;/h2&gt;

&lt;p&gt;A heavy sequence at the top of a page can hurt &lt;strong&gt;Largest Contentful Paint&lt;/strong&gt; (the main content takes too long to appear) and &lt;strong&gt;Interaction to Next Paint&lt;/strong&gt; (the main thread is busy decoding images). Practical steps:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Give the section a &lt;strong&gt;real poster image&lt;/strong&gt; (the first frame) that loads fast, so LCP isn't waiting on the sequence.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Don't block the page&lt;/strong&gt; on loading frames; load them after the first paint.&lt;/li&gt;
&lt;li&gt;Keep your &lt;strong&gt;headline and key text as real HTML&lt;/strong&gt;, not baked into the frames. That helps both search engines and AI assistants read the page.&lt;/li&gt;
&lt;li&gt;Reserve the section's height so the layout doesn't jump (CLS).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Full checklist: &lt;a href="https://beta.scrollsequence.com/blog/scroll-animation-seo-core-web-vitals" rel="noopener noreferrer"&gt;do scroll animations hurt SEO?&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  WordPress-specific: why "it's just a shortcode" can still be heavy
&lt;/h2&gt;

&lt;p&gt;In WordPress, you'll usually place a sequence with a Gutenberg block or, in builders like Elementor, Bricks, Divi or Oxygen, a shortcode such as &lt;code&gt;[scroll-sequence id="..."]&lt;/code&gt;. The shortcode is tiny, but &lt;strong&gt;what it renders still loads your frames&lt;/strong&gt;. Wrapping it in a builder widget, a hidden tab, or a "desktop only" container doesn't automatically stop the images from downloading.&lt;/p&gt;

&lt;p&gt;Because page builder responsive toggles (like Elementor's "Hide on Mobile") typically apply &lt;code&gt;display: none&lt;/code&gt; in CSS rather than removing the DOM nodes from server output, the script and images will still initialize and download in the background. If you want to disable a sequence on phones, use conditional server-side rendering or supply a tiny mobile frame set instead.&lt;/p&gt;

&lt;p&gt;WordPress-specific things to check:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Caching/CDN&lt;/strong&gt; helps a lot: frames are static files and should be served from a CDN with long cache headers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Don't stack too many sequences.&lt;/strong&gt; Five heavy sequences on one page multiplies every problem above.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Avoid scrubbing MP4 instead.&lt;/strong&gt; It feels like the lighter option but stutters badly on scroll, especially on mobile. Why: &lt;a href="https://beta.scrollsequence.com/blog/video-on-scroll-why-scrubbing-stutters-mp4-vs-image-sequence" rel="noopener noreferrer"&gt;video on scroll: why scrubbing stutters (MP4 vs image sequence)&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Mobile scroll-sequence checklist
&lt;/h2&gt;

&lt;p&gt;Copy this and work through it top to bottom:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Hero sequence uses roughly 60–350 frames, not every frame of the source video&lt;/li&gt;
&lt;li&gt;Frames exported and rendered near display size, not original video size&lt;/li&gt;
&lt;li&gt;JPG or WebP at moderate quality; avoid PNG unless transparency is required&lt;/li&gt;
&lt;li&gt;Average frame around 15–90KB&lt;/li&gt;
&lt;li&gt;Decoded memory estimated (width × height × 4 × frames held) and sane for phones&lt;/li&gt;
&lt;li&gt;Canvas DPR capped around 1.5–2&lt;/li&gt;
&lt;li&gt;Pinned section uses stable units (100svh or locked height) and resize handlers ignore address bar height changes&lt;/li&gt;
&lt;li&gt;Separate portrait / mobile frame set (smaller, maybe fewer frames)&lt;/li&gt;
&lt;li&gt;First frame visible immediately; rest load progressively&lt;/li&gt;
&lt;li&gt;Drawing in &lt;code&gt;requestAnimationFrame&lt;/code&gt;; canvas never cleared without a frame to draw&lt;/li&gt;
&lt;li&gt;Tested on a real iPhone with Safari, not only the desktop emulator&lt;/li&gt;
&lt;li&gt;Poster image, real HTML headings, reserved height for Core Web Vitals&lt;/li&gt;
&lt;li&gt;Frames served from CDN, excluded from conflicting optimization plugins&lt;/li&gt;
&lt;li&gt;One heavy sequence per page, ideally&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How Scrollsequence handles this
&lt;/h2&gt;

&lt;p&gt;You can do every fix above by hand with ffmpeg and your own canvas code. If you'd rather not, Scrollsequence is a WordPress plugin built around exactly these problems: it turns any video into a scroll image sequence (with the free &lt;code&gt;vid2ssq&lt;/code&gt; converter, either &lt;code&gt;npx scrollsequence vid2ssq&lt;/code&gt; or built into wp-admin in v2), supports multi-resolution sequences, and works as a native Gutenberg block or a shortcode in Elementor, Bricks, Divi and Oxygen. There's a free version to try on your own footage.&lt;/p&gt;

&lt;p&gt;You can test the core canvas engine with the free version of Scrollsequence on &lt;a href="https://scrollsequence.com" rel="noopener noreferrer"&gt;scrollsequence.com&lt;/a&gt; or from the WordPress plugin repository, complete with the free &lt;code&gt;vid2ssq&lt;/code&gt; converter. Multi-resolution responsive packaging, visual canvas layout, and 3D WebGL depth maps are available in the Pro edition.&lt;/p&gt;

&lt;h2&gt;
  
  
  Related reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://beta.scrollsequence.com/blog/how-many-frames-scroll-animation" rel="noopener noreferrer"&gt;How many frames does a scroll animation need?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://beta.scrollsequence.com/blog/iphone-safari-scroll-animation-crash-reload" rel="noopener noreferrer"&gt;iPhone Safari crashes or reloads on my scroll animation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://beta.scrollsequence.com/blog/webp-vs-png-vs-jpg-image-sequences" rel="noopener noreferrer"&gt;WebP vs PNG vs JPG for image sequences&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://beta.scrollsequence.com/blog/ai-scroll-animation-lag-fix" rel="noopener noreferrer"&gt;Why your AI-built scroll animation lags&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://beta.scrollsequence.com/blog/video-on-scroll-why-scrubbing-stutters-mp4-vs-image-sequence" rel="noopener noreferrer"&gt;Video on scroll: why scrubbing an MP4 stutters&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Why is my scroll animation smooth on desktop but laggy on my phone?&lt;/strong&gt;&lt;br&gt;
Phones have far less memory per browser tab and slower decode. The same full-resolution frames that a laptop can hold decoded will overwhelm a phone. Smaller frames and a mobile frame set fix most cases.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Will converting to WebP fix mobile lag?&lt;/strong&gt;&lt;br&gt;
It helps download time, but not decoded memory. A 1920×1080 frame takes about 8 MB in memory whether it's WebP, JPG or PNG. Reduce dimensions and frame count too.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Should I just use an MP4 video on mobile instead?&lt;/strong&gt;&lt;br&gt;
Playing a video normally is fine. Scrubbing a video with scroll is not: browsers aren't built to seek video that fast, so it stutters. An image sequence with a light mobile set is usually smoother.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How many frames is too many for mobile?&lt;/strong&gt;&lt;br&gt;
There's no single limit, but if frames × width × height × 4 adds up to several hundred MB, you're at risk. A thinner mobile set of 40–100 smaller frames is a safe starting point.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does hiding the animation on mobile in my page builder stop it loading?&lt;/strong&gt;&lt;br&gt;
Not necessarily. Many builders hide elements with CSS, and the images can still download. Check the network tab on a phone-sized viewport, or use a dedicated mobile frame set instead.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://beta.scrollsequence.com/blog/image-sequence-lagging-on-mobile-9-fixes" rel="noopener noreferrer"&gt;Scrollsequence blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>performance</category>
      <category>javascript</category>
      <category>wordpress</category>
    </item>
    <item>
      <title>GSAP ScrollTrigger image sequence in WordPress without code: when DIY isn't worth it</title>
      <dc:creator>Alki</dc:creator>
      <pubDate>Mon, 02 Nov 2026 19:03:15 +0000</pubDate>
      <link>https://dev.to/alki/gsap-scrolltrigger-image-sequence-in-wordpress-without-code-when-diy-isnt-worth-it-2p5a</link>
      <guid>https://dev.to/alki/gsap-scrolltrigger-image-sequence-in-wordpress-without-code-when-diy-isnt-worth-it-2p5a</guid>
      <description>&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; building a scroll image sequence with GSAP ScrollTrigger and canvas is fine if you're a developer, it's one page, and you're happy to maintain it. It stops being worth it when you need mobile frame sets, smooth loading, editing inside Elementor, Bricks or Gutenberg, or non-developers updating content. Then a plugin like Scrollsequence does the same job without custom code.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does the DIY GSAP version actually involve?
&lt;/h2&gt;

&lt;p&gt;The core demo is short: load frames into an array of images, create a ScrollTrigger that pins a section, and on update draw &lt;code&gt;images[frame]&lt;/code&gt; onto a canvas. That's maybe 30–50 lines and it works on your laptop.&lt;/p&gt;

&lt;p&gt;The production version is where the time goes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Frame export&lt;/strong&gt;: ffmpeg commands, frame step, sizes, format.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Loading strategy&lt;/strong&gt;: first frame first, progressive loading, not blocking the page.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Memory&lt;/strong&gt;: not holding hundreds of decoded frames on a phone.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Mobile&lt;/strong&gt;: a separate portrait frame set, DPR capping, resize handling.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Blank-frame handling&lt;/strong&gt;: drawing the nearest loaded frame on fast scroll.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Layout&lt;/strong&gt;: pinning, scroll length, overlapping text, resize and orientation changes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;WordPress integration&lt;/strong&gt;: enqueueing scripts, getting it into a builder, surviving theme and plugin updates, caching and optimization plugins.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Each one is solvable; together they're days or weeks, and then they're yours to maintain.&lt;/p&gt;

&lt;h2&gt;
  
  
  When is DIY GSAP the right call?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;You're a front-end developer and enjoy it.&lt;/li&gt;
&lt;li&gt;The site is custom-coded anyway, not built in a page builder.&lt;/li&gt;
&lt;li&gt;It's a single, one-off animation.&lt;/li&gt;
&lt;li&gt;You need behaviour no plugin offers.&lt;/li&gt;
&lt;li&gt;You'll be around to fix it when browsers, GSAP or the theme change.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That's a perfectly good reason to build it. If that's you, start from our performance checklist: &lt;a href="https://beta.scrollsequence.com/blog/image-sequence-lagging-on-mobile-9-fixes" rel="noopener noreferrer"&gt;image sequence lagging on mobile? 9 fixes&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  When does a plugin win?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;You (or your client) build in Elementor, Bricks, Divi or Oxygen.&lt;/strong&gt; Scrollsequence drops in with a shortcode, &lt;code&gt;[scroll-sequence id="..."]&lt;/code&gt;, that renders in the builder and on the live site.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You use Gutenberg.&lt;/strong&gt; Scrollsequence has native blocks (Scene, Layer, Canvas 2D/3D). See the &lt;a href="https://docs.scrollsequence.com/v2/wordpress" rel="noopener noreferrer"&gt;Scrollsequence WordPress documentation&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You start from a video.&lt;/strong&gt; The free vid2ssq converter (&lt;code&gt;npx scrollsequence vid2ssq&lt;/code&gt;, or built into wp-admin in v2) handles export.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Mobile matters.&lt;/strong&gt; Multi-resolution sequences let phones get a lighter set without extra code.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Non-developers edit the page.&lt;/strong&gt; Text and layers stay editable in WordPress, not in a JS file.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You build several of these&lt;/strong&gt;, for different pages or clients.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why not just scrub an MP4 with GSAP?
&lt;/h2&gt;

&lt;p&gt;It's tempting: one file instead of hundreds. But setting &lt;code&gt;video.currentTime&lt;/code&gt; on every scroll update makes the browser seek constantly, and most browsers can't seek compressed video that fast. Result: stutter, especially on mobile and in Safari. Full explanation: &lt;a href="https://beta.scrollsequence.com/blog/video-on-scroll-why-scrubbing-stutters-mp4-vs-image-sequence" rel="noopener noreferrer"&gt;video on scroll: why scrubbing an MP4 stutters&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick decision guide
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Your situation&lt;/th&gt;
&lt;th&gt;Go with&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Developer, custom theme, one animation&lt;/td&gt;
&lt;td&gt;DIY GSAP&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Page builder site (Elementor, Bricks, Divi, Oxygen)&lt;/td&gt;
&lt;td&gt;Plugin via shortcode&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Gutenberg / block theme&lt;/td&gt;
&lt;td&gt;Plugin with native blocks, or DIY if you're a dev&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Client site someone else will edit&lt;/td&gt;
&lt;td&gt;Plugin&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Mobile performance is critical and you don't want to build it&lt;/td&gt;
&lt;td&gt;Plugin&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;You need something truly custom&lt;/td&gt;
&lt;td&gt;DIY, using the performance checklist&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Related reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://beta.scrollsequence.com/blog/video-on-scroll-why-scrubbing-stutters-mp4-vs-image-sequence" rel="noopener noreferrer"&gt;Video on scroll: why scrubbing an MP4 stutters&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://beta.scrollsequence.com/blog/image-sequence-lagging-on-mobile-9-fixes" rel="noopener noreferrer"&gt;Image sequence lagging on mobile? 9 fixes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://beta.scrollsequence.com/blog/ai-video-scroll-animation-wordpress-elementor" rel="noopener noreferrer"&gt;AI video scroll animation in WordPress and Elementor&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Do I need GSAP to make a scroll image sequence in WordPress?&lt;/strong&gt;&lt;br&gt;
No. GSAP is one way to build it yourself. A plugin like Scrollsequence handles scroll tracking and drawing for you.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can I use GSAP and Scrollsequence on the same site? Does Scrollsequence use GSAP?&lt;/strong&gt;&lt;br&gt;
Scrollsequence v2 does not use GSAP. Versions (v1) uses GSAP, but we moved completely away from it: GSAP ScrollTrigger frequently caused friction inside page builders like Elementor (especially with nested scroll containers, sticky sections, and dynamic resize calculations), and GSAP's timeline syntax introduced maintenance overhead across version upgrades. Also, if another plugin was using different version of GSAP it caused conflicts.&lt;/p&gt;

&lt;p&gt;Today, Scrollsequence is powered by &lt;strong&gt;Motion&lt;/strong&gt;, which serves as a modern wrapper around the browser's native &lt;strong&gt;Web Animations API (WAAPI)&lt;/strong&gt;. This offloads animation timing and interpolation directly to the browser's compositor thread and GPU instead of executing heavy JavaScript timer loops on the main thread. Because Scrollsequence doesn't bundle GSAP, you can run GSAP elsewhere in your theme or custom scripts with zero library conflicts.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is the DIY approach faster on the frontend?&lt;/strong&gt;&lt;br&gt;
Not inherently. Performance comes from frame count, sizes, loading and memory handling, whichever tool draws the frames.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is there a free way to try the plugin route?&lt;/strong&gt;&lt;br&gt;
Yes: the free version of Scrollsequence and the free vid2ssq converter.&lt;/p&gt;




&lt;p&gt;If you've got a half-working GSAP demo and a deadline, try the plugin route on the same video first. Convert it with vid2ssq, drop it into your page with a block or shortcode, and compare on a real phone.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://beta.scrollsequence.com/blog/gsap-scrolltrigger-image-sequence-wordpress-without-code" rel="noopener noreferrer"&gt;Scrollsequence&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>gsap</category>
      <category>wordpress</category>
      <category>webdev</category>
      <category>javascript</category>
    </item>
    <item>
      <title>From video to scroll animation - DIY with ffmpeg, or free with Scrollsequence vid2ssq</title>
      <dc:creator>Alki</dc:creator>
      <pubDate>Thu, 29 Oct 2026 09:05:24 +0000</pubDate>
      <link>https://dev.to/alki/from-video-to-scroll-animation-diy-with-ffmpeg-or-free-with-scrollsequence-vid2ssq-5134</link>
      <guid>https://dev.to/alki/from-video-to-scroll-animation-diy-with-ffmpeg-or-free-with-scrollsequence-vid2ssq-5134</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fivw4xi6oqiqcdipkvu78.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fivw4xi6oqiqcdipkvu78.png" alt="AI video to scroll animation" width="800" height="536"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Whether the clip came from Kling, Veo, Seedance, After Effects, or a phone, the web problem is the same: &lt;strong&gt;scroll wants random access to frames&lt;/strong&gt;. An MP4 wants a decoder and keyframes. That is why &lt;code&gt;video.currentTime = progress * duration&lt;/code&gt; jumps - especially scrolling back, especially on iOS.&lt;/p&gt;

&lt;p&gt;The industry pattern (Apple product pages included) is:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Turn the video into numbered stills.&lt;/li&gt;
&lt;li&gt;Draw the current still on a &lt;code&gt;&amp;lt;canvas&amp;gt;&lt;/code&gt; from scroll progress.&lt;/li&gt;
&lt;li&gt;Serve a lighter set on phones.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You can do that by hand. Or you can generate a production bundle with Scrollsequence’s free local pipeline.&lt;/p&gt;

&lt;h2&gt;
  
  
  Part 1 - The generic DIY way
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Extract frames with ffmpeg
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;# Example: ~24 fps stills, 1600px wide WebP
ffmpeg -i clip.mp4 -vf "fps=24,scale=1600:-1" frame_%04d.webp
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then &lt;strong&gt;thin the set&lt;/strong&gt;. You rarely need every frame. A practical hero is often ~100–150 frames on desktop, fewer on mobile.&lt;/p&gt;

&lt;p&gt;If you insist on scrubbing the MP4 anyway, re-encode with frequent keyframes first (&lt;code&gt;-g 1&lt;/code&gt; or &lt;code&gt;-g 2&lt;/code&gt;). That helps seeking; it still will not match true frame sequences for reverse scrub and memory control.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Scrub on a canvas (vanilla idea)
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;&amp;lt;section id="pin" style="height: 300vh;"&amp;gt;
  &amp;lt;canvas id="seq" style="position: sticky; top: 0; width: 100%; height: 100vh;"&amp;gt;&amp;lt;/canvas&amp;gt;
&amp;lt;/section&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;const frames = []; // preload Image() / createImageBitmap for each frame_%04d.webp
const canvas = document.getElementById('seq');
const ctx = canvas.getContext('2d');
let current = -1;

function draw(i) {
  const img = frames[i];
  if (!img) return;
  // size canvas to CSS * devicePixelRatio (cap at 2 on phones)
  ctx.drawImage(img, 0, 0, canvas.width, canvas.height);
}

function onScroll() {
  const el = document.getElementById('pin');
  const rect = el.getBoundingClientRect();
  const total = el.offsetHeight - window.innerHeight;
  const scrolled = Math.min(total, Math.max(0, -rect.top));
  const progress = total &amp;gt; 0 ? scrolled / total : 0;
  const i = Math.round(progress * (frames.length - 1));
  if (i === current) return;
  current = i;
  requestAnimationFrame(() =&amp;gt; draw(i));
}

window.addEventListener('scroll', onScroll, { passive: true });
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That is the whole “Apple-style” trick in spirit: &lt;strong&gt;progress → index → draw&lt;/strong&gt;, only when the index changes.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. What DIY usually forgets (and why demos lag)
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Concern&lt;/th&gt;
&lt;th&gt;DIY habit that breaks&lt;/th&gt;
&lt;th&gt;Better default&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;File weight&lt;/td&gt;
&lt;td&gt;One 1920px set for everyone&lt;/td&gt;
&lt;td&gt;Separate ~1280 and ~1920 tiers&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Memory (iOS)&lt;/td&gt;
&lt;td&gt;Decode 150 full-HD frames&lt;/td&gt;
&lt;td&gt;Cap DPR at 2; fewer/narrower frames on phones&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Loading&lt;/td&gt;
&lt;td&gt;Wait for all frames&lt;/td&gt;
&lt;td&gt;Load every Nth frame first, fill gaps&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Layout&lt;/td&gt;
&lt;td&gt;Fixed-height parent fights sticky&lt;/td&gt;
&lt;td&gt;Tall scroll section + sticky canvas&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SEO&lt;/td&gt;
&lt;td&gt;Text baked into frames&lt;/td&gt;
&lt;td&gt;Real HTML overlays beside/over the canvas&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Window Resize&lt;/td&gt;
&lt;td&gt;When window resizes, the canvas overflows or underflows&lt;/td&gt;
&lt;td&gt;Resize canvas and redraw on resize&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;You can wire GSAP ScrollTrigger instead of the raw scroll math - same idea: scrub a number from 0→1, map to &lt;code&gt;frameIndex&lt;/code&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  Part 2 - Free Scrollsequence path: &lt;code&gt;npx scrollsequence vid2ssq&lt;/code&gt;
&lt;/h2&gt;

&lt;p&gt;Scrollsequence v2 is built around the same model on every stack: &lt;strong&gt;Scene → Layer → Canvas&lt;/strong&gt;. The asset side is a pipeline that turns raw &lt;code&gt;.mp4&lt;/code&gt; / &lt;code&gt;.webm&lt;/code&gt; into multi-resolution folders plus a &lt;code&gt;scrollsequence-manifest.json&lt;/code&gt; that React, vanilla JS, and WordPress all consume the same way.&lt;/p&gt;

&lt;h3&gt;
  
  
  Free vs optional AI (important)
&lt;/h3&gt;

&lt;p&gt;From the &lt;a href="https://docs.scrollsequence.com/v2/asset-pipeline" rel="noopener noreferrer"&gt;Asset Pipeline docs&lt;/a&gt; and &lt;a href="https://docs.scrollsequence.com/v2/wordpress/credits" rel="noopener noreferrer"&gt;credits docs&lt;/a&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;100% free / local:&lt;/strong&gt; frame extraction, responsive resizing, format/quality, frame step, manifest generation (CLI uses local FFmpeg via Node / Wasm - no credits).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Optional / API key + credits:&lt;/strong&gt; &lt;code&gt;--depth&lt;/code&gt; (3D depth maps), &lt;code&gt;--track "sports car"&lt;/code&gt; (subject tracking), &lt;code&gt;--vision&lt;/code&gt; (scene / camera / subject metadata for agents and automation).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So the default “video → scroll-ready bundle” path is free. Depth maps and vision are extras when you want WebGL tilt or agent-readable metadata.&lt;/p&gt;

&lt;h3&gt;
  
  
  Run the wizard
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;# Interactive wizard (beta package URL - see docs for current .tgz)
npx https://docs.scrollsequence.com/scrollsequence-2.0.0-beta.52.tgz vid2ssq

# Or if already installed:
npx scrollsequence vid2ssq
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Non-interactive example (free local processing):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;npx scrollsequence vid2ssq input.mp4 \
  --name hero-sequence \
  --sizes 1280,1920 \
  --format jpg \
  --quality 80
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Optional AI (needs &lt;code&gt;SSQ_API&lt;/code&gt;):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;npx scrollsequence vid2ssq input.mp4 \
  --name car-reveal \
  --sizes 1280,1920 \
  --depth \
  --track "sports car" \
  --vision
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  What you get that hand-rolled ffmpeg usually skips
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Multiple size tiers&lt;/strong&gt; (e.g. &lt;code&gt;1280&lt;/code&gt; + &lt;code&gt;1920&lt;/code&gt;) so phones are not force-fed desktop frames. The runtime picks a tier from canvas CSS width × devicePixelRatio.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;scrollsequence-manifest.json&lt;/code&gt;&lt;/strong&gt; - one file describing paths, frame counts, optional &lt;code&gt;files.d&lt;/code&gt; depth maps, &lt;code&gt;tracking&lt;/code&gt;, and &lt;code&gt;vision&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Depth maps (optional)&lt;/strong&gt; - grayscale per frame for WebGL 2.5D mouse / gyro tilt (shared lower-res depth across color tiers).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tracking + vision (optional)&lt;/strong&gt; - bounding data and scene/camera/subject JSON so an AI agent (or your own UI) can pin labels to a moving subject or reason about the shot.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Same output for WordPress, React, and vanilla&lt;/strong&gt; - no separate “Elementor-only” asset format.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Inside Next.js / Vite, if a &lt;code&gt;public/&lt;/code&gt; folder exists, the CLI writes straight to &lt;code&gt;public/&amp;lt;name&amp;gt;/&lt;/code&gt; so the dev server can serve frames immediately.&lt;/p&gt;

&lt;h3&gt;
  
  
  Drop the manifest into the page
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Vanilla (free engine pattern):&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;&amp;lt;div class="scrollsequence-scene" data-ssq-duration="1500" data-ssq-scrub="1"&amp;gt;
  &amp;lt;div class="scrollsequence-scene_inner"&amp;gt;
    &amp;lt;div class="scrollsequence-layer"&amp;gt;
      &amp;lt;div
        class="scrollsequence-canvas2d"
        data-ssq-media-groups='[{
          "type": "manifest",
          "rootDir": "/hero-sequence/",
          "imageSizes": { /* from scrollsequence-manifest.json */ }
        }]'
      &amp;gt;
        &amp;lt;canvas&amp;gt;&amp;lt;/canvas&amp;gt;
      &amp;lt;/div&amp;gt;
    &amp;lt;/div&amp;gt;
  &amp;lt;/div&amp;gt;
&amp;lt;/div&amp;gt;

&amp;lt;script type="module"&amp;gt;
  import ScrollsequenceManager from 'scrollsequence';
  import 'scrollsequence/scrollsequence.css';
  ScrollsequenceManager.initialize().preloadAll();
&amp;lt;/script&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;React / Next.js:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;'use client';
import { Scene, Layer, Canvas2d } from 'scrollsequence/react';
import manifest from '@/public/hero-sequence/scrollsequence-manifest.json';

export default function Hero() {
  return (
    &amp;lt;Scene duration={1500}&amp;gt;
      &amp;lt;Layer&amp;gt;
        &amp;lt;Canvas2d
          mediaGroups={[{
            type: 'manifest',
            rootDir: '/hero-sequence/',
            imageSizes: manifest.imageSizes,
          }]}
        /&amp;gt;
      &amp;lt;/Layer&amp;gt;
    &amp;lt;/Scene&amp;gt;
  );
}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;WordPress v2 uses the same Canvas 2D + Media Tools &lt;code&gt;vid2ssq&lt;/code&gt; flow (basic extraction free in-browser; AI toggles credit-based).&lt;/p&gt;

&lt;p&gt;Install note (public beta): package currently installs from the docs &lt;code&gt;.tgz&lt;/code&gt; until the npm name settles — see &lt;a href="https://docs.scrollsequence.com/v2" rel="noopener noreferrer"&gt;docs.scrollsequence.com/v2&lt;/a&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  Which path should you use?
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;DIY ffmpeg + custom JS&lt;/th&gt;
&lt;th&gt;Free &lt;code&gt;vid2ssq&lt;/code&gt; + Scrollsequence runtime&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Learning / one-off&lt;/td&gt;
&lt;td&gt;Great&lt;/td&gt;
&lt;td&gt;Optional&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Multi-size + manifest&lt;/td&gt;
&lt;td&gt;You build it&lt;/td&gt;
&lt;td&gt;Included, free&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Depth / track / vision&lt;/td&gt;
&lt;td&gt;DIY or other tools&lt;/td&gt;
&lt;td&gt;Optional flags&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;WP + React + vanilla same assets&lt;/td&gt;
&lt;td&gt;Manual&lt;/td&gt;
&lt;td&gt;Native&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cost for basic convert&lt;/td&gt;
&lt;td&gt;Your time&lt;/td&gt;
&lt;td&gt;Free local&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;DIY teaches the mechanism. &lt;code&gt;vid2ssq&lt;/code&gt; is the same mechanism packaged so you are not reinventing responsive tiers and a manifest every project — and the basic convert stays free.&lt;/p&gt;

&lt;p&gt;Docs: &lt;a href="https://docs.scrollsequence.com/v2/asset-pipeline" rel="noopener noreferrer"&gt;Asset Pipeline &amp;amp; CLI&lt;/a&gt; · &lt;a href="https://docs.scrollsequence.com/v2/vanilla" rel="noopener noreferrer"&gt;Vanilla&lt;/a&gt; · &lt;a href="https://docs.scrollsequence.com/v2/react" rel="noopener noreferrer"&gt;React&lt;/a&gt; · &lt;a href="https://docs.scrollsequence.com/v2/wordpress" rel="noopener noreferrer"&gt;WordPress&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://beta.scrollsequence.com/blog/ai-video-scroll-animation-wordpress-elementor" rel="noopener noreferrer"&gt;Scrollsequence&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
      <category>wordpress</category>
      <category>animation</category>
    </item>
    <item>
      <title>Video on scroll in Elementor — why scrubbing an MP4 stutters (and what to do instead)</title>
      <dc:creator>Alki</dc:creator>
      <pubDate>Wed, 28 Oct 2026 14:35:39 +0000</pubDate>
      <link>https://dev.to/alki/video-on-scroll-in-elementor-why-scrubbing-an-mp4-stutters-and-what-to-do-instead-156l</link>
      <guid>https://dev.to/alki/video-on-scroll-in-elementor-why-scrubbing-an-mp4-stutters-and-what-to-do-instead-156l</guid>
      <description>&lt;p&gt;Originally published at: &lt;a href="https://beta.scrollsequence.com/blog/video-on-scroll-why-scrubbing-stutters-mp4-vs-image-sequence" rel="noopener noreferrer"&gt;https://beta.scrollsequence.com/blog/video-on-scroll-why-scrubbing-stutters-mp4-vs-image-sequence&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Tutorials like this one from Nicolai Palmkvist that scrub a video with GSAP ScrollTrigger in Elementor look great in the demo. Then you try it on your site and it jumps, freezes when you scroll back up, or completely falls apart on iPhone.&lt;/p&gt;

&lt;p&gt;That is not you "doing Elementor wrong." It is how browsers seek video.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Those Tutorials Actually Do
&lt;/h2&gt;

&lt;p&gt;The usual pattern you see in tutorials:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Drop a &lt;code&gt;&amp;lt;video&amp;gt;&lt;/code&gt; (or a background video widget) in a tall section.&lt;/li&gt;
&lt;li&gt;Pin the section with ScrollTrigger.&lt;/li&gt;
&lt;li&gt;On scroll progress, set:
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="nx"&gt;video&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;currentTime&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;progress&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="nx"&gt;duration&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On paper, that cleanly maps scroll distance to video playback time. In practice, the browser does not store every frame as a clean, random-access image.&lt;/p&gt;

&lt;p&gt;Modern video codecs store keyframes (I-frames) and delta frames (P-frames and B-frames). Seeking to an arbitrary &lt;code&gt;currentTime&lt;/code&gt; forces the browser's video decoder to snap to the nearest keyframe or decode intermediate frames on the fly. As a result, the animation stutters—especially when you scrub backwards.&lt;/p&gt;

&lt;p&gt;iOS Safari is the harshest case:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Stricter seeking throttles.&lt;/li&gt;
&lt;li&gt;Aggressive memory pressure and hardware decoder throttling.&lt;/li&gt;
&lt;li&gt;Mandatory &lt;code&gt;muted&lt;/code&gt; + &lt;code&gt;playsinline&lt;/code&gt; attributes, or the video will refuse to behave like an inline scrubbable timeline at all.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Quick Fix If You Must Keep the MP4
&lt;/h2&gt;

&lt;p&gt;If you need to stay on video for now, these adjustments will get you the best possible results:&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Re-encode With Frequent Keyframes
&lt;/h3&gt;

&lt;p&gt;Use FFmpeg to force keyframes at short intervals:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;ffmpeg &lt;span class="nt"&gt;-i&lt;/span&gt; input.mp4 &lt;span class="nt"&gt;-an&lt;/span&gt; &lt;span class="nt"&gt;-c&lt;/span&gt;:v libx264 &lt;span class="nt"&gt;-g&lt;/span&gt; 2 &lt;span class="nt"&gt;-keyint_min&lt;/span&gt; 2 &lt;span class="nt"&gt;-sc_threshold&lt;/span&gt; 0 &lt;span class="nt"&gt;-crf&lt;/span&gt; 24 &lt;span class="nt"&gt;-pix_fmt&lt;/span&gt; yuv420p output.mp4
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;-g 2&lt;/code&gt; places a keyframe approximately every 2 frames.&lt;/li&gt;
&lt;li&gt;Seeking becomes dramatically smoother because the decoder never has to jump far to find a reference frame.&lt;/li&gt;
&lt;li&gt;Trade-off: File size increases significantly.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  2. Keep the Video Short and Light
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Mute it (&lt;code&gt;-an&lt;/code&gt;):&lt;/strong&gt; Audio is completely useless for scroll scrubbing and wastes bandwidth.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep it brief:&lt;/strong&gt; Prefer 8–12 seconds over a long timeline.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cap resolution:&lt;/strong&gt; Often 1280px wide is more than enough for a hero section.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  3. Respect Mobile Video Rules
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Ensure &lt;code&gt;muted&lt;/code&gt; and &lt;code&gt;playsinline&lt;/code&gt; attributes are set on the &lt;code&gt;&amp;lt;video&amp;gt;&lt;/code&gt; element.&lt;/li&gt;
&lt;li&gt;Preload carefully: avoid downloading a massive video file before the section is actually near the viewport.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This can get your MP4 scrubbing to "pretty good." It rarely gets you to Apple-style, frame-perfect control.&lt;/p&gt;

&lt;h2&gt;
  
  
  Better Approach: Scroll an Image Sequence
&lt;/h2&gt;

&lt;p&gt;Apple product pages (and most high-end scrollytelling websites) do not scrub an MP4. Instead, they render numbered image stills onto an HTML5 &lt;code&gt;&amp;lt;canvas&amp;gt;&lt;/code&gt; (or swap images) driven by scroll progress.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Extract and Prepare Stills
&lt;/h3&gt;

&lt;p&gt;You can extract frames manually with FFmpeg:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Extract ~24 fps stills, then thin them to ~100–150 frames total&lt;/span&gt;
ffmpeg &lt;span class="nt"&gt;-i&lt;/span&gt; clip.mp4 &lt;span class="nt"&gt;-vf&lt;/span&gt; &lt;span class="s2"&gt;"fps=24,scale=1600:-1"&lt;/span&gt; frame_%04d.jpg
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Or run the automated Scrollsequence CLI wizard, which extracts frames, creates responsive resolution folders (e.g., mobile vs. desktop), and builds a manifest:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx scrollsequence vid2ssq
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  2. Implement on the Page
&lt;/h3&gt;

&lt;p&gt;If writing custom JavaScript from scratch, you preload frames into an array, place a &lt;code&gt;&amp;lt;canvas&amp;gt;&lt;/code&gt; in a sticky container, and draw on scroll:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;frameIndex&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;Math&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;round&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;progress&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;frames&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;length&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;));&lt;/span&gt;
&lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;frameIndex&lt;/span&gt; &lt;span class="o"&gt;!==&lt;/span&gt; &lt;span class="nx"&gt;currentFrameIndex&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nx"&gt;currentFrameIndex&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;frameIndex&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nf"&gt;requestAnimationFrame&lt;/span&gt;&lt;span class="p"&gt;(()&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="nf"&gt;drawFrame&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;currentFrameIndex&lt;/span&gt;&lt;span class="p"&gt;));&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Or using Scrollsequence Canvas2D (vanilla JS), which handles responsive tiering, sticky pinning, and canvas rendering automatically:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;div&lt;/span&gt;
  &lt;span class="na"&gt;class=&lt;/span&gt;&lt;span class="s"&gt;"scrollsequence-canvas2d"&lt;/span&gt;
  &lt;span class="na"&gt;data-ssq-media-groups=&lt;/span&gt;&lt;span class="s"&gt;'[{"type":"manifest","rootDir":"/sequence/","imageSizes":{"1920":{"width":1920,"height":1080,"files":{"i":"1920/%04d.jpg"},"frameCount":150}}}]'&lt;/span&gt;
&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;canvas&amp;gt;&amp;lt;/canvas&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/div&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;script &lt;/span&gt;&lt;span class="na"&gt;type=&lt;/span&gt;&lt;span class="s"&gt;"module"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="nx"&gt;ScrollsequenceManager&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;scrollsequence&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;scrollsequence/scrollsequence.css&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nx"&gt;ScrollsequenceManager&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;initialize&lt;/span&gt;&lt;span class="p"&gt;().&lt;/span&gt;&lt;span class="nf"&gt;preloadAll&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/script&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Why This Feels Smoother
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Instant random-access:&lt;/strong&gt; Every frame is a discrete, seekable image—no keyframe guessing or decoder lag.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Bidirectional symmetry:&lt;/strong&gt; Scrolling backward is just as instantaneous and fluid as scrolling forward.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Responsive asset control:&lt;/strong&gt; Serve a desktop set vs. a lightweight mobile set tailored to device capabilities.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Frame Budget (Where Most Demos Fail)
&lt;/h2&gt;

&lt;p&gt;Lag in image sequence demos is almost never because "GSAP is slow." It is almost always caused by serving too many, overly large frames.&lt;/p&gt;

&lt;h3&gt;
  
  
  Recommended Starting Budget
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Metric&lt;/th&gt;
&lt;th&gt;Desktop&lt;/th&gt;
&lt;th&gt;Mobile / Phone&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Frame count&lt;/td&gt;
&lt;td&gt;~100–150&lt;/td&gt;
&lt;td&gt;~60–80 (or every 2nd desktop frame)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Width&lt;/td&gt;
&lt;td&gt;~1400–1920px&lt;/td&gt;
&lt;td&gt;~960px&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Format&lt;/td&gt;
&lt;td&gt;jpg (or AVIF) ~q80&lt;/td&gt;
&lt;td&gt;jpg&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Draw logic&lt;/td&gt;
&lt;td&gt;Only when frame index changes&lt;/td&gt;
&lt;td&gt;Same, and cap canvas DPR at 2&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  Performance Wins (The Scrollsequence Strategy)
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Probability-based preloading (Gauss curve):&lt;/strong&gt; Don't load frames purely sequentially from 0 to 150. Scrollsequence prioritizes images closest to the user's current scroll position using a Gaussian probability distribution. Frames near the active view load first so scrubbing is instantly responsive, expanding outward as bandwidth allows.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Multi-size responsive tiers:&lt;/strong&gt; Generate separate image sizes (e.g., 960px, 1280px, 1920px) matched to screen and container width. Serving an 800KB mobile batch instead of a 20MB 4K sequence prevents crashes and data waste.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Avoid DOM bloat:&lt;/strong&gt; Never inject hundreds of &lt;code&gt;&amp;lt;img&amp;gt;&lt;/code&gt; tags into the DOM—draw to a single &lt;code&gt;&amp;lt;canvas&amp;gt;&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Watch iOS memory:&lt;/strong&gt; Decoded memory is roughly width × height × 4 bytes × frame count. Decoding 150 uncompressed Full HD frames can consume over 1 GB of RAM and crash the mobile Safari tab.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Elementor-Specific Notes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Pin / sticky height:&lt;/strong&gt; The height of your container or spacer must match the scroll distance you want (e.g., 300vh). A parent container with an unexpected fixed height or broken overflow is the most common reason the effect appears to do nothing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;One hero sequence per page at first:&lt;/strong&gt; Multiple heavy sequences require separate preload arrays and a &lt;code&gt;ScrollTrigger.refresh()&lt;/code&gt; after images finish loading so trigger start/end positions recalculate accurately.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Background video widgets:&lt;/strong&gt; Elementor's native background video widgets are designed for looping ambient background video—they are not built for interactive scroll scrubbing.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What About CSS Scroll-Driven Animations?
&lt;/h2&gt;

&lt;p&gt;As of Firefox 159, CSS scroll-driven animations (&lt;code&gt;animation-timeline: scroll()&lt;/code&gt;) are effectively Baseline for fades, parallax, and progress bars.&lt;/p&gt;

&lt;p&gt;However, they do not replace a 100+ frame product sequence. A giant image sprite sheet using &lt;code&gt;steps()&lt;/code&gt; works for short micro-animations (10–20 frames), but quickly becomes impractically large for cinematic sequences. For Apple-style scrubbing, &lt;code&gt;&amp;lt;canvas&amp;gt;&lt;/code&gt; with image frames remains the industry standard.&lt;/p&gt;

&lt;h2&gt;
  
  
  Minimal Checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] &lt;strong&gt;If scrubbing MP4:&lt;/strong&gt; Re-encode with frequent keyframes (&lt;code&gt;-g 2&lt;/code&gt;), mute audio (&lt;code&gt;-an&lt;/code&gt;), and keep the timeline short.&lt;/li&gt;
&lt;li&gt;[ ] &lt;strong&gt;If you need frame-perfect scrub:&lt;/strong&gt; Export Jpeg frames, render to &lt;code&gt;&amp;lt;canvas&amp;gt;&lt;/code&gt;, and map scroll progress → frameIndex.&lt;/li&gt;
&lt;li&gt;[ ] &lt;strong&gt;Cap frame budgets:&lt;/strong&gt; Keep total frames under control and serve a lighter set to mobile devices.&lt;/li&gt;
&lt;li&gt;[ ] &lt;strong&gt;Render selectively:&lt;/strong&gt; Only invoke &lt;code&gt;canvas.drawImage()&lt;/code&gt; when the calculated frame index actually changes.&lt;/li&gt;
&lt;li&gt;[ ] &lt;strong&gt;Test on real devices:&lt;/strong&gt; Test on a real iPhone or Android and a mid-range Android phone, not just desktop Chrome DevTools.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Optional: WordPress Without Pasting the Whole Stack
&lt;/h2&gt;

&lt;p&gt;If you are on WordPress / Elementor and would rather not hand-wire FFmpeg, canvas rendering loops, and responsive loaders every time, Scrollsequence is the plugin built specifically for this workflow.&lt;/p&gt;

&lt;p&gt;You can upload your frames (or directly convert video in v2) and get an editable, responsive section or block. The checklist above still applies either way—the mechanics of image frames and mobile memory limits remain identical.&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>elementor</category>
      <category>webdev</category>
      <category>performance</category>
    </item>
  </channel>
</rss>
