Home Design Tools PNG to ICO

PNG to ICO - Multi-Size Favicon Builder with Browser Preview

Convert PNG to ICO with full control - choose which sizes to bundle (16×16 to 256×256), preview your favicon exactly as it appears in a browser tab, get ready-to-paste HTML code, and learn exactly how favicons affect your SEO. All client-side - your image never leaves your browser.

Always Free Multi-size ICO bundling Live browser preview Never uploaded to server
16px · 32px · 48px · 64px · 128px · 256px in one ICO
Bundle up to 6 sizes in one ICO file - browsers pick the right one
See your favicon in a real browser tab simulation before downloading
100% client-side - image processed in your browser, never uploaded
🖼️
Drop your PNG here or click to upload
PNG, JPG, WebP, GIF supported · Square images work best · Never uploaded to any server
Quality analysis
Browser tab preview
My Website
My Website
All sizes preview
Your ICO file is ready
HTML implementation code

      
Place this code inside the <head> section of your HTML file. Put favicon.ico in your website root directory.
Interactive favicon size guide - which size serves which context
Size Context Used by Priority
16×16 Browser tab favicon - the one everyone sees ChromeFirefoxSafariEdge Essential
32×32 Windows taskbar, high-DPI browser tabs, Firefox on retina Chrome retinaWindowsFirefox Essential
48×48 Windows desktop shortcut icon, taskbar pinned sites Windows 7+Win taskbar Recommended
64×64 Windows high-DPI desktop icons, some Linux environments Win HiDPILinux Optional
128×128 macOS dock and Spotlight, Chrome Web Store icons macOSChrome Store Optional
256×256 Windows Vista+ large icon view, high-DPI Windows icons Windows Vista+Win 10 HiDPI Recommended
Browser compatibility - which size each browser picks
🌐 Chrome / Edge
Prefers 32×32 on HiDPI Falls back to 16×16 Ignores sizes above 32px in tab
🦊 Firefox
Uses 32×32 first Falls back to 16×16 Supports all ICO sizes
🧭 Safari
Uses .ico from root Prefers apple-touch-icon for iOS Use 180×180 PNG for home screen
🪟 IE 11
Uses 16×16 from ICO Requires favicon.ico in root Does not use link tag for ICO
🤖 Android Chrome
Uses 192×192 PNG for PWA Uses 32×32 for tab Needs manifest.json for install
🤖 Google Search
Shows favicon in mobile SERP Uses favicon.ico or linked PNG Must be at least 48×48 for SERP
How your favicon affects SEO and search rankings
Google Mobile Search Results
Google displays your favicon next to every result in mobile search. A clear, recognisable favicon improves brand recognition and click-through rate - a direct SEO signal.
Missing favicon = wasted crawl budget
Without a favicon.ico in your root directory, browsers request it on every page load and get a 404 error. This wastes your crawl budget and creates error entries in Google Search Console.
💡
Google's favicon requirements
Google requires your favicon to be at least 48×48 pixels, accessible (not blocked by robots.txt), and consistent with your site's branding. It must also be square - rectangular favicons are not shown.
🔍
PWA install eligibility
A properly configured favicon with a web manifest makes your site eligible for "Add to Home Screen" on Android Chrome - increasing returning visitor rate, a positive engagement signal for SEO.
🏆
Brand recognition in bookmarks
Users who bookmark your site see your favicon in their browser bookmarks bar. A distinctive, memorable favicon increases direct return visits - the highest-quality traffic signal in SEO.
⚠️
Wrong MIME type warnings
Serving an ICO file with the wrong Content-Type header causes browser console warnings. Ensure your server serves favicon.ico with Content-Type: image/x-icon or image/vnd.microsoft.icon.

Other converters give you one size.
This gives you every size, properly.

Multi-size bundling, quality analysis, browser preview, HTML code, size guide, and SEO education - not just a file converter.

Multi-size bundling

Bundle 16, 32, 48, 64, 128, and 256px into one ICO file. Browsers automatically pick the right size for each context - tab, taskbar, desktop, or search results.

one file, all sizes

Smart quality advisor

Analyses your PNG before conversion - checks if it's square, has transparency, has enough resolution, and flags issues that would produce a bad favicon.

fix before converting

Browser tab simulation

See exactly how your favicon looks in a light and dark browser tab - at 16×16 - before downloading. The #1 issue with favicons is bad readability at small sizes.

see before you ship

Ready HTML code

Four implementation snippets: minimal, modern, complete, and PWA - copy and paste straight into your HTML head section, no manual coding needed.

paste and ship

SEO impact explained

Google displays favicons in mobile search results. A missing favicon causes 404 errors that waste crawl budget. Learn exactly how favicons affect your rankings.

SEO most tools skip

100% client-side

Your image is processed in your browser using the Canvas API. It is never uploaded to any server - completely private, works offline once loaded.

private by design

Create your perfect favicon in 3 steps

1

Upload your PNG

Drop your image or click to upload. The quality advisor analyses it and flags any issues before you convert.

2

Choose your sizes

Select which sizes to bundle. For most websites, the Standard preset (16+32+48) covers all major browsers and platforms.

3

Download and implement

Download favicon.ico, copy the HTML code for your head section, and place the file in your website root directory.

The complete guide to favicons - beyond just converting

A favicon is not just a decorative icon. It appears in browser tabs, bookmarks, browser history, Windows taskbar, macOS dock, iOS home screens, Android home screens, and crucially - in Google mobile search results next to your site's name. Getting it right has measurable impact on brand recognition and click-through rates.

Why an ICO file instead of a PNG?

The ICO format has one key advantage over PNG: it bundles multiple image sizes into a single file. This means the browser, operating system, or search engine can choose the most appropriate size for its context without making multiple HTTP requests. A 16×16 ICO for a browser tab and a 256×256 ICO for a Windows desktop shortcut can coexist in one favicon.ico file.

The best favicon workflow in 2024. Use ICO for maximum compatibility (especially IE and Windows), but complement it with PNG favicons in your HTML for modern browsers. Serve favicon.ico from your root directory (browsers request it automatically even without a link tag), and add <link rel="icon"> tags pointing to PNG versions for current browsers. Add an apple-touch-icon at 180×180 for iOS, and a manifest.json with 192×192 and 512×512 icons for PWA eligibility.

What makes a good favicon at 16×16?

The most common mistake is using a detailed logo as a favicon. At 16×16 pixels - 256 pixels total - fine details, thin strokes, and small text all disappear. The best favicons at this size are: a single letter or initial, a simple icon or symbol, a bold geometric shape, or a highly simplified version of a logo. Test your favicon at 16×16 before publishing - this tool's browser tab preview shows you exactly what to expect.

Favicon questions,
answered.

Ask a question
An ICO file is a special image format used for website favicons and Windows icons. Unlike PNG, a single ICO file can contain multiple sizes bundled together, allowing the browser or OS to pick the most appropriate size for each context.
Start with a square PNG of at least 256×256 pixels. This gives enough resolution to scale down cleanly to all smaller sizes. Avoid starting with anything smaller than 64×64.
At minimum, include 16×16 and 32×32. For complete coverage add 48×48 and 256×256. The Standard preset (16+32+48) covers all major browsers and Windows contexts.
Yes. A missing favicon causes 404 errors that waste crawl budget. Google shows favicons in mobile search results, improving brand recognition and click-through rate. See the SEO impact section above for full details.
No. The entire conversion happens in your browser using the Canvas API. Your image is never sent to any server and remains completely private.
favicon.ico works in all browsers including old IE. favicon.png works in all current browsers but not IE. Best practice: serve both - favicon.ico in your root as a universal fallback, and PNG favicons in your HTML for modern browsers.