The CDN swaps the format on the way out
Shopify's developer changelog documents it directly: animated GIFs uploaded to a store are converted to animated WebP automatically, cutting delivered bytes by up to about half, with a GIF served back to any browser that cannot handle WebP. You upload a .gif. Most shoppers receive something else, and neither of you is consulted.
This is good news with a catch. The good news is that a well-made GIF gets a free efficiency pass on the way to the customer, so squeezing your upload to the last kilobyte is less urgent than it is for email or a README. The catch is that a re-encode is a re-encode: everything you threw away to make the file small, mainly colors and frames, is gone before the conversion starts, and WebP cannot invent it back. Feed the pipeline a clean 128-color loop and let it do the compressing.
What the conversion does not fix
Format is the CDN's problem. Everything below is still yours.
- Length. Three to six seconds. A product loop shows one thing: the clasp closing, the fabric moving, the lid twisting off.
- Dimensions. 800 to 1200 px on the long edge covers a product gallery. Shopify's own guidance points at square images around 2048 px for stills, which is generous for a loop where every pixel is multiplied by every frame.
- Frame rate. 12 fps for a slow demonstration, 15 when a hand is moving. Phone footage at 60 gives you four frames for every one that is doing work.
- Frame one. Some surfaces and apps show a still instead of animating, and merchants report it turning up in places it did not before. Whatever frame you start on is the one a shopper might see and never see move.
- The upload ceiling. Product and collection images have to come in under 20 MB as of this writing, and Shopify has published pixel ceilings too. Neither should be anywhere near a problem if the loop is built properly.
Aim for under 2 MB before upload. If a finished loop is heavier, the compression page works through the levers in order of payoff.
Shopify's own video is usually the better listing asset
Worth being straight about, since we sell the loop. Native product video on Shopify is a proper media type with a real player: it keeps audio, it does not pay GIF's per-frame tax, and it can be set to autoplay muted and loop. That last part is a theme setting, passed to the video tag by whoever built your theme, not something Shopify guarantees, so check yours before assuming a product video will move on its own. For a 30-second product story, it wins on every measure that matters.
A GIF earns its place where video cannot go or is not worth the weight. Inside the description block, beside a paragraph of copy, where a player would be clumsy. In the abandoned-cart email, where video arrives as a thumbnail and a GIF arrives moving, which the email guide covers in detail. In a support article or a size guide. And for the three-second detail that does not deserve a play button: the magnetic snap, the color shifting in the light.
Put differently: video for the story, a loop for the detail. Reaching for one because you did not know about the other is the expensive mistake.
A heavy loop above the fold is a conversion problem
The largest image in the first screenful of a product page is usually what browsers measure as Largest Contentful Paint, the metric Google reports on and shoppers experience as the page being slow. Drop a multi-megabyte animation there and you have made the number worse for every visitor, including everyone who was never going to scroll.
The layout fix costs nothing. Lead with a sharp still, put the loop second in the gallery or down in the description where it loads after the page is usable, and let the first paint be light. Mobile shoppers on a cellular connection, which is most of them, feel this more than any wording change you could make on the page.
An unlaunched product on someone else's server
The footage for a product GIF is almost always of a thing that is not for sale yet. Packaging that has not been announced. A colorway with a date attached. A price on a tag in the corner of frame. Every free online converter asks you to upload that file, and the terms you agree to while doing it are not written to protect a launch calendar.
This one has no upload step to worry about. The editor reads the file from your disk, encodes it with your own processor, and hands the result back to your Downloads folder. The first server that ever sees the loop is your own store, on the day you decide. That is not a policy, it is just how the thing is built.