Why is your Shopify favicon not showing, and how do you fix it?

October 7, 2026

You uploaded a favicon but the browser tab still shows the default icon. The four usual causes, from aggressive caching to hardcoded theme links, and the fix for each.

The cache trap

Nine times out of ten, the favicon is fine and the browser is lying to you. Browsers cache favicons aggressively, sometimes for weeks, and a hard refresh often does not clear them. You upload the new icon, check the tab, see the old one, and assume the upload failed. It did not.

Test in a fresh incognito window, which starts with a clean cache. If the icon appears there, the problem was caching all along. Clear the browser cache fully, or wait it out: cached favicons expire on their own. This step resolves the majority of favicon tickets, so do it before touching anything else.

Wrong file or wrong format

If incognito still shows nothing, check the file itself. Shopify wants a square image, ideally 32 by 32 pixels or larger, in PNG or ICO format. Oversized images, non-square aspect ratios, and exotic formats all fail silently: the upload appears to succeed but the icon never renders.

Transparency causes its own confusion. A favicon with a transparent background on a dark browser theme can look invisible even when it is technically displaying. Test against both light and dark browser themes before concluding it is broken.

Theme settings vs hardcoded links

Most themes set the favicon in the theme editor under theme settings, and uploading there is the correct path. Problems start when a theme or app hardcodes a favicon link in the theme code that overrides the setting. The editor shows your new icon while the storefront serves the hardcoded old one.

Check the theme code for favicon references, usually in theme.liquid. If you find a hardcoded link, either remove it so the theme setting controls the icon, or update it to point at your file. One source of truth, not two.

Testing the fix properly

After any change, verify in incognito, on a second browser, and on mobile. Favicons also appear in bookmarks, history, and mobile home screen shortcuts, each with its own cache. A fix that works in one place but not others is usually just residual caching elsewhere.

Give it 24 hours before declaring victory. Between browser caches, CDN caching, and device-level caching, favicon propagation is slower than any other site change. Patience is part of the fix.

Prevention

Upload the final favicon before launch, not after, so caches form around the right icon from day one. Keep the source file in your brand assets so future theme changes reuse it. And document which setting controls it, because the next person to touch the theme will thank you.

SVG favicons and modern browsers

Modern browsers support SVG favicons, which stay sharp at every size and weigh almost nothing. If your theme supports it, an SVG version of your mark is the best long-term choice. The catch is Safari, which has been slower to adopt SVG favicons, so keep a PNG fallback for full coverage.

When supplying both, list the SVG first with the PNG as fallback. Browsers pick the first format they understand. Test the fallback explicitly in Safari rather than assuming it works, because the failure mode is silent: Safari just shows nothing.

Finally, remember that the favicon also represents your store in contexts you rarely check: browser bookmarks, mobile home screen shortcuts, and open tab strips where shoppers compare you against competitors. A missing or default icon in those spots quietly signals an unfinished store. It is a five-minute fix with outsized presence, so it belongs on every pre-launch checklist.