SVG favicons are the dream: one crisp vector file, scales forever, tiny payload. And in 2026 most of that dream works — but "most" is doing a lot of heavy lifting. Depending on which browser, which platform, and which non-browser tool fetches your icon, the SVG you shipped may be read, ignored, or replaced by a request for /favicon.ico you never made. Here's what actually happens, and the link stack that keeps every consumer happy.

Who reads your SVG favicon

Chrome, Firefox, Edge — all read <link rel="icon" type="image/svg+xml" href="/favicon.svg"> and prefer it over raster alternatives when declared correctly. Bonus you can't get from PNG: SVG favicons can embed CSS with media queries, which is exactly how the dark-mode Safari favicon trick swaps colors without JavaScript.

Safari on macOS — supports SVG favicons, with quirks: it historically ignored the type attribute and picked icons by sizes and order instead.…