{"id":2221,"date":"2026-11-16T09:13:00","date_gmt":"2026-11-16T14:13:00","guid":{"rendered":"https:\/\/www.xconvert.com\/blog\/?p=2221"},"modified":"2026-08-31T23:13:55","modified_gmt":"2026-09-01T03:13:55","slug":"favicon-not-showing-blurry","status":"publish","type":"post","link":"https:\/\/www.xconvert.com\/blog\/favicon-not-showing-blurry","title":{"rendered":"Favicon Not Showing or Blurry? Cache, Sizes and Shape Fixes"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Your tab still shows the old logo three days after you replaced it. Or it shows the new one as an unreadable smudge. Favicons fail in a small, predictable set of ways, and almost none of them are \u201cyou exported the PNG wrong\u201d \u2014 the file is usually fine, and something between the file and the pixel is choosing badly. Here is the triage order, and the two ICO traps that quietly hand you the wrong image.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\"><p><strong>Quick answer:<\/strong> Open the icon\u2019s own URL in a tab \u2014 <code>https:\/\/yoursite.com\/favicon.ico<\/code>. <strong>If the image appears<\/strong>, the file is fine and you have a cache or markup problem; confirm in a private window before changing anything. <strong>If it 404s or renders your HTML error page<\/strong>, it was never deployed at that path. <strong>Blurry<\/strong> almost always means the largest layer you shipped is 16\u00d716 while the surface is painting at 32 or 48 device pixels \u2014 Google recommends a favicon \u201clarger than 48x48px\u201d. And if you rebuilt from an existing <code>.ico<\/code>, know that single-image decoders read the <strong>first<\/strong> entry in the directory, which is usually the 16\u00d716 and never the biggest. Rebuild from one square master with <a href=\"https:\/\/www.xconvert.com\/favicon-generator\">xconvert\u2019s favicon generator<\/a>.<\/p><\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Jump to a section<\/h2>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"#serving\">Start with the file, not the browser<\/a><\/li><li><a href=\"#cache\">Why the cache wins, and the fix that doesn\u2019t backfire<\/a><\/li><li><a href=\"#blurry\">Blurry means something upscaled it<\/a><\/li><li><a href=\"#ico-traps\">The two ICO traps<\/a><\/li><li><a href=\"#shape\">Shape, margin, and the background you didn\u2019t set<\/a><\/li><li><a href=\"#tool\">Rebuild the set on xconvert<\/a><\/li><li><a href=\"#faq\">FAQ<\/a><\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"serving\">Start with the file, not the browser<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before you touch a <code>&lt;link&gt;<\/code> tag, request the icon directly: type the full URL of the file into the address bar and look at what comes back.<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>The image renders.<\/strong> The bytes are where you think they are \u2014 skip to <a href=\"#cache\">the cache section<\/a>.<\/li><li><strong>A 404, or your styled \u201cpage not found\u201d page.<\/strong> It was never deployed to that path. A build step that hashes asset filenames produces <code>\/assets\/favicon.a3f9c1.ico<\/code>, which nothing probing <code>\/favicon.ico<\/code> will ever find.<\/li><li><strong>The HTML of your home page.<\/strong> A catch-all route is swallowing the request \u2014 common with SPA routers that serve <code>index.html<\/code> for anything not matched as a static file.<\/li><\/ul>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1600\" height=\"1141\" src=\"https:\/\/www.xconvert.com\/blog\/wp-content\/uploads\/2026\/08\/favicon-triage.png\" alt=\"Five-step triage flow for a broken favicon: request the file directly, rule out the browser cache, check crawlability for search results, check whether only a 16x16 layer exists, and check whether the source image was square\" class=\"wp-image-2218\" srcset=\"https:\/\/www.xconvert.com\/blog\/wp-content\/uploads\/2026\/08\/favicon-triage.png 1600w, https:\/\/www.xconvert.com\/blog\/wp-content\/uploads\/2026\/08\/favicon-triage-300x214.png 300w, https:\/\/www.xconvert.com\/blog\/wp-content\/uploads\/2026\/08\/favicon-triage-1024x730.png 1024w, https:\/\/www.xconvert.com\/blog\/wp-content\/uploads\/2026\/08\/favicon-triage-768x548.png 768w, https:\/\/www.xconvert.com\/blog\/wp-content\/uploads\/2026\/08\/favicon-triage-1536x1095.png 1536w\" sizes=\"auto, (max-width: 1600px) 100vw, 1600px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Four more failure modes live at this level, and all of them are invisible from your own browser:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Symptom<\/th><th>Most likely cause<\/th><th>Fix<\/th><\/tr><\/thead><tbody><tr><td>Shows on <code>example.com<\/code>, not on <code>www.example.com<\/code><\/td><td>Google treats favicons as <strong>one per hostname<\/strong>, and browsers probe the host they\u2019re on<\/td><td>Serve the icon from every hostname you use, or redirect one to the other<\/td><\/tr><tr><td>Missing from Google\u2019s results, fine in the tab<\/td><td>The file or its directory is disallowed in <code>robots.txt<\/code><\/td><td>Google requires that <strong>Googlebot-Image<\/strong> can crawl the favicon <em>and<\/em> <strong>Googlebot<\/strong> can crawl the home page<\/td><\/tr><tr><td>Works in Chrome, blank in Safari<\/td><td>Your only icon is an SVG<\/td><td>Ship raster fallbacks \u2014 see the table below<\/td><\/tr><tr><td>Works everywhere except the iOS Home Screen<\/td><td>iOS does not read <code>rel=&quot;icon&quot;<\/code><\/td><td>Add an <code>apple-touch-icon<\/code>; Apple\u2019s Retina iPhone size is 180\u00d7180<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">That third row deserves its own numbers. Global SVG-favicon support is around <strong>90%<\/strong> per caniuse, and the missing tenth is concentrated in Apple\u2019s browser:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Browser<\/th><th>SVG favicon from<\/th><th>Note<\/th><\/tr><\/thead><tbody><tr><td>Chrome \/ Edge<\/td><td>80<\/td><td>Desktop and Android<\/td><\/tr><tr><td>Firefox<\/td><td>41<\/td><td>Earliest of the majors<\/td><\/tr><tr><td>Safari (macOS and iOS)<\/td><td><strong>26.0<\/strong><\/td><td>Versions 3.1\u201318.7 have no support at all<\/td><\/tr><tr><td>IE, Opera Mini, Android Browser<\/td><td>Never<\/td><td>\u2014<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Declare an SVG favicon in front of a PNG, never instead of one.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"cache\">Why the cache wins, and the fix that doesn\u2019t backfire<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the file renders at its own URL but the tab still shows the old icon, you are fighting a cache \u2014 and favicons are cached far more stubbornly than page assets. A hard reload (Ctrl+Shift+R \/ Cmd+Shift+R) reloads the <em>document<\/em>; it does not reliably force a browser to re-evaluate the icon it has already associated with a site.<\/p>\n\n\n\n<ol class=\"wp-block-list\"><li><strong>Confirm it really is a cache.<\/strong> Open the site in a private window, or a browser you have never visited it in. If the new icon appears there, your deployment is correct and you can stop debugging.<\/li><li><strong>Only then cache-bust.<\/strong> Changing the URL works \u2014 <code>&lt;link rel=&quot;icon&quot; href=&quot;\/favicon.ico?v=2&quot;&gt;<\/code> \u2014 but it collides with Google\u2019s guidance that \u201cthe favicon URL must be stable (don\u2019t change the URL frequently)\u201d. A one-off <code>?v=2<\/code> after a rebrand is fine; rotating a hash in on every deploy is not.<\/li><\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">For the icon in Google\u2019s search results there is no cache to clear at all. You are waiting on a recrawl, which Google says \u201ccan take anywhere from several days to several weeks\u201d.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"blurry\">Blurry means something upscaled it<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A favicon is drawn into a fixed box; the browser takes the closest layer it has and scales it. Blur is what scaling <em>up<\/em> looks like.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The arithmetic that catches most people: a browser tab reserves roughly 16 CSS pixels for the icon. On a 2\u00d7 display that is <strong>32 device pixels<\/strong>, and on the 3\u00d7 displays common on phones, 48. If the only image you shipped is a 16\u00d716, every one of those surfaces is enlarging a 256-pixel bitmap.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Other surfaces ask for much more. Google recommends \u201cusing a favicon that\u2019s larger than 48x48px so that it looks good on various surfaces,\u201d with a floor of 8\u00d78 and a hard square requirement. Apple\u2019s web-clip documentation lists 180\u00d7180 for Retina iPhones, 167\u00d7167 for iPad Pro and 152\u00d7152 for iPad \u2014 and if iOS finds no match it takes \u201cthe smallest icon larger than the recommended size,\u201d falling back to the largest available, so a 32\u00d732 can end up stretched across a Home Screen tile.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Two causes of \u201cfuzzy\u201d aren\u2019t about pixel counts at all. <strong>Your logo may be too complicated for 16 pixels<\/strong> \u2014 if you can\u2019t identify the mark squinting at a thumbnail, that\u2019s a design problem; use the symbol, the monogram or a single letter. And <strong>starting from a JPEG<\/strong> puts blocking artifacts on exactly the hard edges a small icon is made of, with no alpha channel available.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"ico-traps\">The two ICO traps<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">ICO is not an image format, it is a <em>directory<\/em> of images \u2014 one file holding several sizes. That container shape causes two problems people hit while trying to fix a favicon.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Trap 1: a multi-size <code>.ico<\/code> decodes to its first entry, not its biggest.<\/strong> You have an old <code>favicon.ico<\/code> holding 16, 32 and 48 pixel layers and you want a PNG of the logo back out of it. Feed it to an image converter and you get the 16\u00d716 \u2014 a single-image decoder reads directory entry <strong>0<\/strong>, and generators conventionally write smallest-first. If the pipeline then scales that up to the size you asked for, you get a blurry blowup of the smallest layer and no error anywhere. This is not specific to one converter; it is how most single-image pipelines treat a multi-image container, and <a href=\"https:\/\/www.xconvert.com\/convert-ico-to-png\">xconvert\u2019s ICO to PNG converter<\/a> behaves the same way. (That one is server-side: the file uploads over an encrypted connection, converts on our servers, and is deleted automatically a few hours later.) The rule: <strong>never treat an old <code>.ico<\/code> as your master.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Trap 2: the ICO size presets set the height, not the longest side.<\/strong> Every \u201cp\u201d preset in xconvert\u2019s image pipeline \u2014 256P, 192P, 180P, 128P and down \u2014 sets the output <strong>height<\/strong> and lets width follow the aspect ratio. For ICO that\u2019s a trap: each directory entry stores width and height as single-byte fields (<code>BYTE bWidth<\/code> \/ <code>BYTE bHeight<\/code> in Microsoft\u2019s format documentation), capping a declarable dimension at 256, so a landscape source at 256P lands past that ceiling. With a non-square source, <strong>128P is the practical maximum<\/strong> \u2014 fuller explanation in <a href=\"https:\/\/www.xconvert.com\/blog\/favicon-sizes-you-actually-need\/\">Favicon sizes in 2026: the five files you actually need<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"shape\">Shape, margin, and the background you didn\u2019t set<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Every surface that shows a favicon shows it square; Google states it outright \u2014 \u201cYour favicon must be a square (1:1 aspect ratio).\u201d So a non-square source has to be squared by somebody, and if you don\u2019t decide how, the tool decides for you.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">xconvert\u2019s favicon generator fits your image <em>inside<\/em> the square and paints the remainder with the <strong>Background<\/strong> colour. A 3:1 wordmark becomes a thin band across the middle with two-thirds of the canvas as flat colour \u2014 technically correct, visually tiny. Crop to square first, and leave the mark a small margin inside that square so rounded masks don\u2019t clip it. Two related surprises:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>There is no \u201ctransparent\u201d background.<\/strong> <strong>Background<\/strong> is a colour swatch defaulting to white, and the fill is always painted, so a transparent PNG comes out on a solid square. That is usually right for a tab icon \u2014 a dark transparent logo disappears into a dark tab strip \u2014 but pick the colour deliberately instead of inheriting white.<\/li><li><strong>Rounded corners are baked in, and iOS rounds again.<\/strong> <strong>Rounded corners (iOS-style)<\/strong> masks every generated size with a rounded rectangle. iOS also masks Home Screen icons itself, so a pre-rounded 180\u00d7180 can end up double-rounded, with background colour showing as wedges at the corners. Leave it off when the Home Screen is the priority.<\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"tool\">Rebuild the set on xconvert<\/h2>\n\n\n\n<ol class=\"wp-block-list\"><li>Open <a href=\"https:\/\/www.xconvert.com\/favicon-generator\">xconvert.com\/favicon-generator<\/a> and use <strong>Drop image, or click to choose<\/strong>. The page asks for a <strong>square PNG \/ JPG \/ SVG (\u2265 512px recommended)<\/strong> \u2014 start from your largest square master, not the old <code>.ico<\/code>.<\/li><li>Set <strong>Background<\/strong> to a colour that works against both a light and a dark tab strip.<\/li><li>Tick <strong>Rounded corners (iOS-style)<\/strong> only if you want that shape baked into every size.<\/li><li>Click <strong>&#x2699; Generate favicon set<\/strong>, then download the results: a multi-size <code>favicon.ico<\/code> plus PNGs at 16, 32, 48, 180, 192 and 512 pixels.<\/li><li>Use <strong>&#x1f4cb; Copy HTML<\/strong> for the matching <code>&lt;link&gt;<\/code> tags and upload the files to your site root. The snippet also references a <code>site.webmanifest<\/code> \u2014 that small JSON file you write yourself; the generator produces the images, not the manifest.<\/li><\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">The generator runs entirely on your device \u2014 the image is decoded, resized and encoded to ICO inside the page, so nothing is uploaded and there is no file on any server to delete. If you only need a single ICO rather than the whole set, <a href=\"https:\/\/www.xconvert.com\/blog\/convert-an-image-to-ico-favicon\/\">how to convert an image to ICO<\/a> covers that narrower job.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"faq\">FAQ<\/h2>\n\n\n\n<h5 class=\"wp-block-heading\">Why won\u2019t my favicon update, even after a hard refresh?<\/h5>\n\n\n\n<p class=\"wp-block-paragraph\">A hard refresh reloads the document, not the browser\u2019s stored association between your site and its icon. Verify in order: open the icon\u2019s URL directly to confirm the new file is served, then open the site in a private window. If the new icon shows there, your deployment is fine and you are only waiting on your own browser. A single <code>?v=2<\/code> on the <code>href<\/code> forces the issue \u2014 but don\u2019t make URL-versioning a per-deploy habit, because Google asks that the favicon URL stay stable.<\/p>\n\n\n\n<h5 class=\"wp-block-heading\">How long until the new favicon appears in Google search results?<\/h5>\n\n\n\n<p class=\"wp-block-paragraph\">There is no cache to clear and no button to press; it appears after Google recrawls, which Google describes as taking \u201canywhere from several days to several weeks.\u201d What is in your control: <strong>Googlebot-Image must be able to crawl the favicon file<\/strong>, <strong>Googlebot must be able to crawl the home page<\/strong>, and the icon must be square and at least 8\u00d78. Check <code>robots.txt<\/code> first \u2014 a blanket disallow on an assets directory is the usual culprit.<\/p>\n\n\n\n<h5 class=\"wp-block-heading\">Why does my favicon look blurry on a Retina or 4K screen?<\/h5>\n\n\n\n<p class=\"wp-block-paragraph\">The browser is upscaling. A tab reserves about 16 CSS pixels for the icon, which is 32 device pixels at 2\u00d7 and 48 at 3\u00d7. If your largest layer is a 16\u00d716, all of those are enlargements. Ship a 32\u00d732 PNG, put a 48\u00d748 layer inside the <code>.ico<\/code>, and add a 180\u00d7180 \u2014 Google\u2019s \u201clarger than 48x48px\u201d is a sensible floor to design to.<\/p>\n\n\n\n<h5 class=\"wp-block-heading\">I converted my old favicon.ico to PNG and got a tiny 16\u00d716 image. Why?<\/h5>\n\n\n\n<p class=\"wp-block-paragraph\">Because an <code>.ico<\/code> holds several images and a single-image decoder reads <strong>directory entry 0<\/strong> \u2014 for almost every generator the 16\u00d716, since they write smallest-first. Nothing warns you; you get the smallest layer, scaled up to whatever you asked for. Don\u2019t use an old <code>.ico<\/code> as your source of truth: find the vector or large PNG it was made from and regenerate from that.<\/p>\n\n\n\n<h5 class=\"wp-block-heading\">My logo is wide, not square. What\u2019s the least-bad favicon?<\/h5>\n\n\n\n<p class=\"wp-block-paragraph\">Crop to a square element rather than shrinking the whole wordmark. A generator fits a wide image inside the square and fills the rest with the background colour, so a 3:1 logo occupies a third of the icon\u2019s height and reads as a smear at 16 pixels. Use the symbol, the monogram or one letter \u2014 and if you convert a wide image straight to ICO, the size presets set the <strong>height<\/strong>, so 128P is the safe ceiling.<\/p>\n\n\n\n<h5 class=\"wp-block-heading\">Why does the icon show in Chrome but not in Safari?<\/h5>\n\n\n\n<p class=\"wp-block-paragraph\">Usually because the only icon is an SVG. Per caniuse, SVG favicon support landed in Chrome and Edge at 80 and Firefox at 41 \u2014 but <strong>Safari only from 26.0<\/strong>, with none at all in versions 3.1 through 18.7 on macOS or iOS. Keep the SVG if you like it, but declare it in front of a PNG so older Safari falls through to a raster file.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Sources<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Last verified 2026-08-31.<\/em><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/favicon-in-search\">Google Search Central \u2014 Define a favicon to show in search results<\/a> \u2014 square 1:1 requirement, \u201cat least 8x8px,\u201d the \u201clarger than 48x48px\u201d recommendation, one favicon per hostname, stable-URL guidance, the Googlebot-Image \/ Googlebot crawl requirement, and \u201cseveral days to several weeks\u201d for recrawl.<\/li><li><a href=\"https:\/\/learn.microsoft.com\/en-us\/previous-versions\/ms997538%28v%3dmsdn.10%29\">Microsoft \u2014 Icons (ICO file format)<\/a> \u2014 the <code>ICONDIRENTRY<\/code> structure with <code>BYTE bWidth<\/code> and <code>BYTE bHeight<\/code>, and the fact that one ICO file is a directory of several images.<\/li><li><a href=\"https:\/\/caniuse.com\/link-icon-svg\">caniuse \u2014 SVG favicons<\/a> \u2014 support from Chrome\/Edge 80, Firefox 41, Safari 26.0 (none in 3.1\u201318.7 on desktop or iOS), ~90% global.<\/li><li><a href=\"https:\/\/developer.apple.com\/library\/archive\/documentation\/AppleApplications\/Reference\/SafariWebContent\/ConfiguringWebApplications\/ConfiguringWebApplications.html\">Apple \u2014 Configuring Web Applications<\/a> \u2014 apple-touch-icon sizes (180\u00d7180 Retina iPhone, 167\u00d7167 iPad Pro, 152\u00d7152 iPad) and the \u201csmallest icon larger than the recommended size, otherwise the largest available\u201d selection rule.<\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Favicon not showing, stale or blurry? Check the file, the cache, the pixel size and the shape &#8211; plus two ICO traps that hand you the wrong image.<\/p>\n","protected":false},"author":3,"featured_media":2219,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,14],"tags":[],"class_list":["post-2221","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-how-to-guides","category-tools"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.7 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Favicon Not Showing or Blurry? Cache, Sizes and Shape Fixes<\/title>\n<meta name=\"description\" content=\"Favicon not showing, stale or blurry? Check the file, the cache, the pixel size and the shape - plus two ICO traps that hand you the wrong image.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.xconvert.com\/blog\/favicon-not-showing-blurry\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Favicon Not Showing or Blurry? Cache, Sizes and Shape Fixes\" \/>\n<meta property=\"og:description\" content=\"Favicon not showing, stale or blurry? Check the file, the cache, the pixel size and the shape - plus two ICO traps that hand you the wrong image.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.xconvert.com\/blog\/favicon-not-showing-blurry\" \/>\n<meta property=\"og:site_name\" content=\"XConvert Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/xconvertcom\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-16T14:13:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.xconvert.com\/blog\/wp-content\/uploads\/2026\/08\/featured-80.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1600\" \/>\n\t<meta property=\"og:image:height\" content=\"840\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"James\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@xconvert_com\" \/>\n<meta name=\"twitter:site\" content=\"@xconvert_com\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"James\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"11 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/favicon-not-showing-blurry#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/favicon-not-showing-blurry\"},\"author\":{\"name\":\"James\",\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/#\\\/schema\\\/person\\\/3434db135e6a7f239ba8414244df9845\"},\"headline\":\"Favicon Not Showing or Blurry? Cache, Sizes and Shape Fixes\",\"datePublished\":\"2026-11-16T14:13:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/favicon-not-showing-blurry\"},\"wordCount\":2219,\"image\":{\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/favicon-not-showing-blurry#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/featured-80.png\",\"articleSection\":[\"How To Guides\",\"Tools\"],\"inLanguage\":\"en-CA\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/favicon-not-showing-blurry\",\"url\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/favicon-not-showing-blurry\",\"name\":\"Favicon Not Showing or Blurry? Cache, Sizes and Shape Fixes\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/favicon-not-showing-blurry#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/favicon-not-showing-blurry#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/featured-80.png\",\"datePublished\":\"2026-11-16T14:13:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/#\\\/schema\\\/person\\\/3434db135e6a7f239ba8414244df9845\"},\"description\":\"Favicon not showing, stale or blurry? Check the file, the cache, the pixel size and the shape - plus two ICO traps that hand you the wrong image.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/favicon-not-showing-blurry#breadcrumb\"},\"inLanguage\":\"en-CA\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/favicon-not-showing-blurry\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-CA\",\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/favicon-not-showing-blurry#primaryimage\",\"url\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/featured-80.png\",\"contentUrl\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/featured-80.png\",\"width\":1600,\"height\":840,\"caption\":\"The xconvert favicon generator at \\\/favicon-generator with the drop-image area highlighted - upload one square master to rebuild the whole icon set\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/favicon-not-showing-blurry#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.xconvert.com\\\/blog\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Favicon Not Showing or Blurry? Cache, Sizes and Shape Fixes\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/\",\"name\":\"XConvert Blog\",\"description\":\"Blog for XConvert file converter\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-CA\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/#\\\/schema\\\/person\\\/3434db135e6a7f239ba8414244df9845\",\"name\":\"James\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-CA\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/46be416a360dc6b95bffc4b116d86872c03f8d8e4c1047a3a08033742f03d04d?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/46be416a360dc6b95bffc4b116d86872c03f8d8e4c1047a3a08033742f03d04d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/46be416a360dc6b95bffc4b116d86872c03f8d8e4c1047a3a08033742f03d04d?s=96&d=mm&r=g\",\"caption\":\"James\"},\"url\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/author\\\/james\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Favicon Not Showing or Blurry? Cache, Sizes and Shape Fixes","description":"Favicon not showing, stale or blurry? Check the file, the cache, the pixel size and the shape - plus two ICO traps that hand you the wrong image.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.xconvert.com\/blog\/favicon-not-showing-blurry","og_locale":"en_US","og_type":"article","og_title":"Favicon Not Showing or Blurry? Cache, Sizes and Shape Fixes","og_description":"Favicon not showing, stale or blurry? Check the file, the cache, the pixel size and the shape - plus two ICO traps that hand you the wrong image.","og_url":"https:\/\/www.xconvert.com\/blog\/favicon-not-showing-blurry","og_site_name":"XConvert Blog","article_publisher":"https:\/\/www.facebook.com\/xconvertcom","article_published_time":"2026-11-16T14:13:00+00:00","og_image":[{"width":1600,"height":840,"url":"https:\/\/www.xconvert.com\/blog\/wp-content\/uploads\/2026\/08\/featured-80.png","type":"image\/png"}],"author":"James","twitter_card":"summary_large_image","twitter_creator":"@xconvert_com","twitter_site":"@xconvert_com","twitter_misc":{"Written by":"James","Est. reading time":"11 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.xconvert.com\/blog\/favicon-not-showing-blurry#article","isPartOf":{"@id":"https:\/\/www.xconvert.com\/blog\/favicon-not-showing-blurry"},"author":{"name":"James","@id":"https:\/\/www.xconvert.com\/blog\/#\/schema\/person\/3434db135e6a7f239ba8414244df9845"},"headline":"Favicon Not Showing or Blurry? Cache, Sizes and Shape Fixes","datePublished":"2026-11-16T14:13:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.xconvert.com\/blog\/favicon-not-showing-blurry"},"wordCount":2219,"image":{"@id":"https:\/\/www.xconvert.com\/blog\/favicon-not-showing-blurry#primaryimage"},"thumbnailUrl":"https:\/\/www.xconvert.com\/blog\/wp-content\/uploads\/2026\/08\/featured-80.png","articleSection":["How To Guides","Tools"],"inLanguage":"en-CA"},{"@type":"WebPage","@id":"https:\/\/www.xconvert.com\/blog\/favicon-not-showing-blurry","url":"https:\/\/www.xconvert.com\/blog\/favicon-not-showing-blurry","name":"Favicon Not Showing or Blurry? Cache, Sizes and Shape Fixes","isPartOf":{"@id":"https:\/\/www.xconvert.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.xconvert.com\/blog\/favicon-not-showing-blurry#primaryimage"},"image":{"@id":"https:\/\/www.xconvert.com\/blog\/favicon-not-showing-blurry#primaryimage"},"thumbnailUrl":"https:\/\/www.xconvert.com\/blog\/wp-content\/uploads\/2026\/08\/featured-80.png","datePublished":"2026-11-16T14:13:00+00:00","author":{"@id":"https:\/\/www.xconvert.com\/blog\/#\/schema\/person\/3434db135e6a7f239ba8414244df9845"},"description":"Favicon not showing, stale or blurry? Check the file, the cache, the pixel size and the shape - plus two ICO traps that hand you the wrong image.","breadcrumb":{"@id":"https:\/\/www.xconvert.com\/blog\/favicon-not-showing-blurry#breadcrumb"},"inLanguage":"en-CA","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.xconvert.com\/blog\/favicon-not-showing-blurry"]}]},{"@type":"ImageObject","inLanguage":"en-CA","@id":"https:\/\/www.xconvert.com\/blog\/favicon-not-showing-blurry#primaryimage","url":"https:\/\/www.xconvert.com\/blog\/wp-content\/uploads\/2026\/08\/featured-80.png","contentUrl":"https:\/\/www.xconvert.com\/blog\/wp-content\/uploads\/2026\/08\/featured-80.png","width":1600,"height":840,"caption":"The xconvert favicon generator at \/favicon-generator with the drop-image area highlighted - upload one square master to rebuild the whole icon set"},{"@type":"BreadcrumbList","@id":"https:\/\/www.xconvert.com\/blog\/favicon-not-showing-blurry#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.xconvert.com\/blog"},{"@type":"ListItem","position":2,"name":"Favicon Not Showing or Blurry? Cache, Sizes and Shape Fixes"}]},{"@type":"WebSite","@id":"https:\/\/www.xconvert.com\/blog\/#website","url":"https:\/\/www.xconvert.com\/blog\/","name":"XConvert Blog","description":"Blog for XConvert file converter","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.xconvert.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-CA"},{"@type":"Person","@id":"https:\/\/www.xconvert.com\/blog\/#\/schema\/person\/3434db135e6a7f239ba8414244df9845","name":"James","image":{"@type":"ImageObject","inLanguage":"en-CA","@id":"https:\/\/secure.gravatar.com\/avatar\/46be416a360dc6b95bffc4b116d86872c03f8d8e4c1047a3a08033742f03d04d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/46be416a360dc6b95bffc4b116d86872c03f8d8e4c1047a3a08033742f03d04d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/46be416a360dc6b95bffc4b116d86872c03f8d8e4c1047a3a08033742f03d04d?s=96&d=mm&r=g","caption":"James"},"url":"https:\/\/www.xconvert.com\/blog\/author\/james"}]}},"_links":{"self":[{"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/posts\/2221","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/comments?post=2221"}],"version-history":[{"count":1,"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/posts\/2221\/revisions"}],"predecessor-version":[{"id":2222,"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/posts\/2221\/revisions\/2222"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/media\/2219"}],"wp:attachment":[{"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/media?parent=2221"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/categories?post=2221"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/tags?post=2221"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}