Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Next.js and React

Chrome says it cannot use an icon from the web app manifest

ErrorError while trying to use the following icon from the Manifest

Short answer

Chrome logs this when an icon in manifest.json cannot be downloaded or is not usable. Icon paths resolve against the manifest's own URL, so a wrong path gives a 404. Also check that sizes and type match the real file, that CSP allows the image, and that you ship 192x192 and 512x512 PNGs.

  • Applies to Chrome 130+, React 19, Vite 6
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Open DevTools, go to Application, then Manifest. It lists every icon and shows whether each image loads.

    curl -I https://example.com/manifest.json
  2. 2Match what you see, then jump to its fix

    1. 1The icon shows as failed in the Manifest pane and its URL returns 404The icon path resolves to a file that does not existFix
    2. 2The file loads in a browser tab but Chrome skips it or picks a poor onesizes or type do not match the real fileFix
    3. 3A CSP violation for the icon URL in the consoleA Content-Security-Policy img-src blocks the icon originFix
    4. 4The page is not offered as installableThe 192x192 and 512x512 icons are missingFix

What does the error look like?

  • Error while trying to use the following icon from the Manifest
  • Icon shows as failed in DevTools > Application > Manifest

Cause 1 of 4

The icon path resolves to a file that does not exist

1Check

Relative src values resolve against the manifest file's URL, not the page URL. Build the full URL by hand and request it.

curl -I https://example.com/icons/icon-192.png

2Fix

Put the files where the path points or correct src to match.

"icons": [
  { "src": "icons/icon-192.png", "sizes": "192x192", "type": "image/png" }
]

3Verify

The request returns 200 and the Manifest pane shows the image.

curl -I https://example.com/icons/icon-192.png

Confirmed by developer.mozilla.org

Did this fix it?

Cause 2 of 4

sizes or type do not match the real file

1Check

Compare the declared sizes and type with the actual image. Use exact sizes for PNG, and any for SVG.

file public/icons/icon-192.png

2Fix

Set sizes to the true pixel size and type to the true MIME type, or re-export the image.

{ "src": "icons/icon-512.png", "sizes": "512x512", "type": "image/png" }

3Verify

Reload and check the Manifest pane for warnings.

# DevTools > Application > Manifest

Confirmed by developer.mozilla.org

Did this fix it?

Cause 3 of 4

A Content-Security-Policy img-src blocks the icon origin

1Check

Manifest icons are fetched under the img-src directive of the page that links the manifest. An icon on a CDN origin fails if that origin is not allowed.

curl -sI https://example.com | grep -i content-security-policy

2Fix

Add the icon's origin to img-src, or host the icons on your own origin.

Content-Security-Policy: img-src 'self' https://cdn.example.com

3Verify

Reload and confirm the console has no CSP error and the icon loads.

# DevTools > Console

Confirmed by developer.mozilla.org

Did this fix it?

Cause 4 of 4

The 192x192 and 512x512 icons are missing

1Check

Chromium needs at least one 192x192 and one 512x512 icon.

grep -n "sizes" public/manifest.json

2Fix

Add both PNG sizes to the icons array.

"icons": [
  { "src": "icons/icon-192.png", "sizes": "192x192", "type": "image/png" },
  { "src": "icons/icon-512.png", "sizes": "512x512", "type": "image/png" }
]

3Verify

The Manifest pane shows both icons and no installability errors.

# DevTools > Application > Manifest

Confirmed by web.dev

Did this fix it?

How do I stop it coming back?

  • Keep icons next to the manifest and use paths relative to it.
  • Check the Application > Manifest pane after every change to icons.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.