Why Is My Favicon Not Showing on iPhone?

Name the iPhone surface first

A favicon missing in a Safari tab is not the same failure as a generic or stale icon on the home screen. Safari browser candidates, Apple touch icons, and installed PWA assets follow related but separate paths.

Capture the iOS version, browser, page URL, and whether the symptom appears in a tab, favorite, or saved home-screen shortcut before changing files.

Connected next stepApple Touch Icons: Size, Markup, and Cropping for the closest prerequisite or comparison.

Verify the Apple touch response

Declare a square PNG with rel=apple-touch-icon and a stable public URL. Apple’s historical guidance also describes a root apple-touch-icon.png fallback, but an explicit link removes path ambiguity.

Request the file directly and confirm it returns image bytes rather than an HTML rewrite. Inspect the 180×180 composition, opaque or deliberate background, and safe edge spacing.

Connected next stepSafari Favicons: Tabs, Pinned Tabs, and Apple Touch Icons for the next connected implementation decision.

Recreate the saved shortcut after deployment

An existing home-screen item can retain the artwork captured when it was created. Once the production HTML and image are correct, remove the affected shortcut and add it again from the current page.

Do not repeatedly rename the asset while diagnosis is incomplete. First prove which URL the page exposes and which bytes that URL returns; then isolate retained device state.

Connected next stepOpen the most relevant production tool and verify the decision with a working output.

Check iOS-specific composition and discovery

An Apple touch icon is commonly a 180-pixel square PNG, but correct dimensions alone do not guarantee a good result. Important artwork needs enough internal space for system presentation, and transparency should be a deliberate choice rather than an accidental empty canvas. Avoid tiny text and edge details that look acceptable in the source but disappear on the home screen. Open the exact file on the device to confirm its colors and alpha before investigating discovery.

Inspect the rendered page head on the URL the user actually saves. A template may include the link on the homepage but omit it on a nested route, or a relative href may resolve to the wrong directory. Follow redirects and ensure the final image is available without cookies. If no explicit link is present, historical root filename discovery may behave differently from the site’s assumptions; explicit metadata and a stable root fallback make the intended asset easier to prove.

Separate deployment correction from device refresh

First establish server truth: the current page declares the intended URL, the URL returns 200 with PNG bytes, dimensions are correct, and caches at the origin and CDN contain the new file. Only then remove and recreate a saved shortcut. Clearing general Safari history is a broad action and should not be the first diagnostic step, especially when a retained home-screen item is the only failing surface.

Compare a newly created shortcut with the existing one and record the page from which each was saved. If the new item is correct, deployment is working and the old item retained prior artwork. If both fail, compare Safari tab behavior, Apple link discovery, manifest configuration, redirects, and the file itself. Test a second device or clean context before rotating filenames again. These controlled comparisons prevent an iPhone cache symptom from triggering unnecessary changes to otherwise correct browser and search icons.

Evidence to collect before escalating

A useful iPhone report includes the exact page URL, iOS version, browser, whether the problem is a tab or home-screen shortcut, the rendered apple-touch-icon link, its resolved final URL, HTTP status, Content-Type, byte length, and decoded dimensions. Add the date the shortcut was originally created and whether a newly created shortcut behaves differently. If a manifest is involved, include its URL and relevant icon entries. Capture the origin and CDN cache headers without including private cookies. This information lets a maintainer decide whether the failure is missing metadata, a relative path, an HTML rewrite, unsuitable pixels, stale edge content, or retained device state. Without it, “not showing on iPhone” collapses several independent Apple and Safari surfaces into one symptom and encourages disruptive cache clearing or repeated filename changes before production correctness has been established.