Animated Favicons: What Works and What to Test
A favicon helps people recognise a site in a crowded browser tab. Start with a static image that is still legible at a small size. If you want the icon to indicate a change, such as an unread message, use a distinct state that people can recognise without watching an animation.
Keep a fallback in the page
Declare a normal icon with a link element whose relationship is icon. If JavaScript changes the icon, preserve a reliable static starting point and reuse a small set of assets. Browser caching and update timing can differ. Check a fresh browser session and a previously visited page.
Avoid relying on motion
Use the visible interface to communicate any important status as well. Respect reduced-motion preferences, stop unnecessary updates in background tabs and avoid flashes. A single state change is often easier to recognise and costs less to run than a loop that continually replaces the image.
Test the places the icon can appear
Try open tabs and pinned tabs in the browsers your customers use. Check dark and light browser themes and what happens after a reload. Search results and device shortcuts may use different assets or cached versions, so keep the static brand mark suitable for those uses.
