Frequently Asked Questions
What favicon sizes are generated?
16×16 (browser tab), 32×32 (retina tab), 180×180 (Apple Touch Icon), 192×192 (Android Chrome), and 512×512 (PWA splash). These cover all modern browsers and devices.
What is manifest.json?
A Web App Manifest telling browsers about your app — name, icons, theme color, display mode. Required for PWA support and "Add to Home Screen" on mobile.
What image formats can I upload?
PNG, JPG, SVG, WebP, and GIF. For best results, use a square image at least 512×512 pixels.
Is my image safe?
Yes. All processing happens in your browser using the Canvas API. No images are ever uploaded to any server.
What HTML code do I need?
The tool generates the HTML link tags for your <head> section — favicon link, Apple Touch Icon, and manifest.json reference.
What favicon sizes do I need in 2026?
Essential: 32×32 (browser tab), 180×180 (Apple Touch Icon), 192×192 (Android), 512×512 (PWA splash). Optional: 16×16 (legacy). SVG favicon is increasingly supported and scales perfectly to any size.
Why is my favicon not showing in Chrome?
Common causes: browser cache (hard refresh with Ctrl+Shift+R), incorrect path in HTML, wrong MIME type, or favicon served with caching headers. Chrome also requires the file to be a valid ICO, PNG, or SVG format.
SVG favicon vs PNG — which is better?
SVG favicons scale perfectly, support dark mode via CSS media queries, and have smaller file sizes. However, Safari only supports SVG for pinned tabs. Use both: SVG as primary with PNG fallback for maximum compatibility.