Chrome says it cannot use an icon from the web app manifest
Error while trying to use the following icon from the ManifestShort 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.
Fix it fast
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.json2Match what you see, then jump to its fix
- 1
The icon shows as failed in the Manifest pane and its URL returns 404The icon path resolves to a file that does not existFix - 2
The file loads in a browser tab but Chrome skips it or picks a poor onesizes or type do not match the real fileFix - 3
A CSP violation for the icon URL in the consoleA Content-Security-Policy img-src blocks the icon originFix - 4
The page is not offered as installableThe 192x192 and 512x512 icons are missingFix
- 1
What does the error look like?
Error while trying to use the following icon from the ManifestIcon 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.png2Fix
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.pngConfirmed by developer.mozilla.org
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.png2Fix
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 > ManifestConfirmed by developer.mozilla.org
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-policy2Fix
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.com3Verify
Reload and confirm the console has no CSP error and the icon loads.
# DevTools > ConsoleConfirmed by developer.mozilla.org
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.json2Fix
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 > ManifestConfirmed by web.dev
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:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- TaskvareA task and project-management suite: React on the web, Flutter on mobile, TypeScript underneath.
Related fixes
Web apps
Chrome reports a syntax error at line 1, column 1 for manifest.json
Manifest: Line: 1, column: 1, Syntax error.
Chrome reads the manifest as JSON.
3 causes, each with a fixWeb apps
Module not found for antd/dist/antd.less after upgrading to Ant Design 5
Module not found: Error: Can't resolve 'antd/dist/antd.less'
Ant Design 5 dropped Less and the bundled CSS file for CSS-in-JS, so antd/dist/antd.less no longer exists.
3 causes, each with a fixWeb apps
Astro Code component fails inside a React component
Astro components cannot be rendered directly via function call
Astro components such as Code only exist on the server and render static HTML.
2 causes, each with a fixWeb apps
React shows Attempted import error when importing a component or function
Attempted import error:
The build found the file but not the name you asked for.
2 causes, each with a fixWeb apps
How to catch and handle a 422 from Axios in a Redux thunk
action.error.message is 'Rejected' and action.payload is undefined
A 422 means the server read the request but cannot process its content, so repeating it unchanged fails again.
4 causes, each with a fixWeb apps
axios gets 429 Too Many Requests from a React app
429 (Too Many Requests)
A 429 comes from the server or an API gateway, not from axios: your client sent too many requests in a window.
4 causes, each with a fix