Favicon Generator
Create your favicon in all required sizes for free, right in your browser.
.jpg, .png, .webp · up to 50 MB
Why use it
The right favicon for every device and browser
All formats
Generates .ico, .png, and all sizes for iOS, Android, and PWA.
100% private
Processing happens in your browser. Your logo never leaves your device.
All sizes
16×16, 32×32, 180×180, 192×192, and 512×512. Production-ready.
Instant
Immediate result. No queues, no signup, no limits.
How it works
Three steps, no hassle
Upload your image or logo
Drag and drop or select a square PNG, SVG, JPG, or WebP. Minimum 512×512 px recommended.
Preview the generated sizes
Automatically get 16×16, 32×32, 180×180 (Apple Touch Icon), 192×192 and 512×512 px.
Download the favicon package
Download all generated sizes, ready to add to your web project.
FAQ
Got questions?
A complete modern favicon set requires: 16×16 px (browser tab on Windows/Linux), 32×32 px (tab on macOS and bookmarks), 180×180 px (Apple Touch Icon, saved to iOS home screen), 192×192 px (Android Chrome add to home screen), and 512×512 px (PWA splash screen on Android). The favicon.ico file in the site root can contain multiple embedded resolutions (16, 32, 48 px) in a single file. For modern browsers, a single 32×32 PNG referenced in HTML is sufficient. However, for maximum compatibility with Apple devices, bookmarking apps, and PWA, the full set is necessary.
The .ico format is the original favicon format, introduced by Internet Explorer 5 in 1999. It can contain multiple resolutions in a single file and has universal support, including very old browsers. The .png format is simpler: one file per size, native support in all modern browsers, and better compression quality than .ico for high resolutions. The .svg format as a favicon is supported by modern Chrome, Firefox, and Edge but not by Safari or iOS. The advantage of SVG is that it scales perfectly to any size and can adapt its appearance to the system dark mode via CSS media queries (@media (prefers-color-scheme: dark)). Current recommendation: use .ico for basic compatibility, .png for specific resolutions, and optionally .svg for modern browsers.
The Apple Touch Icon is the icon iOS and macOS Safari use when the user saves a website to the iPhone/iPad home screen or adds it to the Mac dock. Unlike regular favicons (which iOS ignores for this purpose), the Apple Touch Icon must be a 180×180 px PNG (for Retina), without transparency layers (iOS automatically adds rounded corners and gloss), declared in HTML as: <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>. If no Apple Touch Icon is specified, iOS automatically captures a screenshot of the page as the icon, with very poor visual results.
The correct way to declare modern favicons in the HTML <head> is: <link rel='icon' type='image/x-icon' href='/favicon.ico'> for basic compatibility, <link rel='icon' type='image/png' sizes='32x32' href='/favicon-32x32.png'> for modern browsers, <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'> for iOS, and <link rel='manifest' href='/site.webmanifest'> for PWA. The site.webmanifest file is a JSON that declares the 192×192 and 512×512 icons. Modern browsers prioritize the manifest over individual link tags, so the manifest is especially important for PWA.
favicon.ico is the de facto standard since 1999, interpreted by all browsers even without any HTML tag (browsers automatically look for /favicon.ico at the root). The web app manifest (manifest.json or site.webmanifest) is the modern standard for PWA (Progressive Web Apps), introduced with the W3C Web App Manifest standard in 2013. In addition to icons, the manifest declares name, theme colors, display mode, and other application properties. For a normal website without PWA functionality, favicon.ico + PNG + Apple Touch Icon is sufficient. For a full PWA with home screen installation, the manifest is essential.
Favicons: history, web standards, and browser tab branding
The favicon is one of the smallest and most recognizable elements of a website's visual identity. Its history begins in March 1999 when Microsoft Internet Explorer 5 introduced favicon.ico support as part of the 'Favorites' feature: when saving a site, IE5 made a request to /favicon.ico to display the icon next to the bookmark. The name 'favicon' comes from 'favorites icon'. The standard was formalized in RFC 2616 and W3C in 2000 with the <link rel='shortcut icon'> tag. Today, more than 25 years later, the favicon has evolved from a simple 16×16 pixel .ico file to an ecosystem of icons for browser tabs, bookmarks, mobile home screens, and app splash screens.
The ICO format is technically an image container that can include multiple resolutions and color depths in a single file. It was originally developed by Microsoft for Windows desktop icons and adapted for the web. A technical curiosity: a .ico file can include compressed PNG images inside the ICO container since Windows Vista (2007), significantly reducing file size. SVG favicons, supported by Chrome 80+ and Firefox 41+, have a unique advantage: they can use CSS media queries to automatically adapt the design to the system dark mode. This allows having a black-on-white favicon in light mode and white-on-black in dark mode, all in a single vector file of a few kilobytes.
In the context of Google's Core Web Vitals, the favicon has a performance implication that is often overlooked. The browser downloads the favicon in a separate request when loading the page, and if the favicon.ico file does not exist, the server responds with a 404 that may include an HTML error page of several kilobytes. For sites receiving millions of visits, this repeated 404 can generate a significant amount of unnecessary traffic. The solution is to always have a favicon.ico at the root, even if it's just a minimal 16×16 px file, to avoid these 404s on every visit.