How can animation or flashing content cause issues?
Still have a question, spotted an error, or have a better explanation or a source we should cite?
You've added a looping GIF to your email header: a product rotating slowly, a countdown timer ticking down. It looks polished in your design tool. Then it lands in Outlook and your subscribers see a static image of the first frame. Or it opens on a device where the flash rate is fast enough to trigger a seizure for a small percentage of your audience. Animation in email is useful, but it carries real risks worth understanding before you deploy it.
The compatibility problem is well-documented: Outlook for Windows doesn't support animated GIFs. It renders only the first frame. That means your animated countdown or product reveal shows as a frozen image for a significant portion of your list, depending on how many subscribers are on desktop Outlook. The fix is simple: design your GIF so that the first frame works as a standalone static image. Put the key message or offer in frame one, not buried in frame four of the animation.
The accessibility concern is less discussed but more serious. Content that flashes faster than three times per second can trigger photosensitive epileptic seizures. WCAG (Web Content Accessibility Guidelines) defines the safe threshold at fewer than three flashes per second. Email clients don't enforce this automatically. It's your responsibility as the sender. Beyond seizure risk, rapidly flashing content is also disruptive for subscribers with attention sensitivities or vestibular disorders, and it tends to feel aggressive regardless of your intent.
CSS animations have slightly different support characteristics than GIF animations. They work in Apple Mail, Gmail webmail, and most modern clients, but they also fail in Outlook. AMP for Email supports richer interactive animation, but it's only available in Gmail and a handful of other clients, so it always needs a static fallback. If you want to see how your animation actually renders across your subscribers' clients, a client rendering preview tool will show you the real output without guessing.
Keep animations under three flashes per second, make sure the first frame stands on its own in Outlook, and test before you send. If the animation is purely decorative, ask whether it's adding enough value to justify the rendering complexity. Often a well-designed static image performs just as well.
Contributors
Who worked on this answer
Every name links to their profile. Every company links to their site. Real people, real accountability.
