Drop a PNG, JPG, or WebP logo and ConvertRS creates a multi-size favicon package with favicon.ico, browser PNG sizes, Apple Touch Icon, Android Chrome icons, a web manifest, and copy-paste HTML - all inside your browser.
ConvertRS fits your logo onto square icon canvases for browser tabs, home-screen icons, and PWA manifests.
Practical favicon files and install code, with precise no-upload copy for privacy-conscious site owners.
Use the favicon generator to turn a PNG, JPG, or WebP logo into a complete, production-ready favicon set without uploading anything. ConvertRS assembles a multi-size favicon.ico with 16x16, 32x32, and 48x48 frames, explicit 16x16 and 32x32 browser PNGs, a 180x180 apple-touch-icon.png, 192x192 and 512x512 Android Chrome icons, a ready-to-edit site.webmanifest, and a favicon-code.html snippet with the matching links. Everything is generated locally in your browser with WebAssembly, so unreleased logos and brand assets never leave your device. Drop your image, choose transparent padding or a background color, preview each icon size, and download the ZIP with copy-paste HTML.
Drop your PNG logo into the favicon generator, choose padding or a background color, and generate the package locally. The ZIP includes a multi-size favicon.ico with 16x16, 32x32, and 48x48 frames, plus PNG app icons and the HTML code to link them.
Yes. ConvertRS reads your PNG, JPG, or WebP image in the browser and creates the favicon ZIP locally on your device. The source file is never sent to a server, which matters for unreleased logos and confidential brand assets.
The ZIP includes favicon.ico, favicon-16x16.png and favicon-32x32.png, apple-touch-icon.png, android-chrome-192x192.png and android-chrome-512x512.png, site.webmanifest, and a favicon-code.html snippet with the matching links. The names follow the common convention, so most setup guides you find online will match.
Yes. The favicon.ico file contains 16x16, 32x32, and 48x48 PNG frames in one file. Browsers pick the frame they need, which keeps small icons sharp instead of stretching a single 16x16 image.
Use both when possible. Modern browsers can use PNG icons linked directly, while favicon.ico provides several small sizes in one broadly compatible file, including for older browsers and crawlers. The generated ZIP includes both formats plus the HTML for each.
Chrome picks a 16x16 or 32x32 PNG for tabs, Apple devices use the 180x180 apple-touch-icon.png, and Android uses the 192x192 and 512x512 icons declared in site.webmanifest. The 48x48 frame inside the ICO covers legacy requests and, for example, the icon Google shows next to mobile search results, which expects at least 48x48.
Some modern browsers accept SVG favicons linked with type="image/svg+xml", and WebP is technically renderable, but support is inconsistent and Safari in particular does not fully support SVG icons. A multi-size ICO plus explicit PNGs remains the only combination that works everywhere, which is what the generator produces.
Ship favicon.ico together with explicit PNG links and a manifest. That combination covers the browser tab, bookmarks, iOS and Android home screens, and installed PWA windows from one generated package. Keep an SVG version only as an optional enhancement if you control the target browsers.
Browsers cache favicons aggressively, sometimes across restarts. Do a hard refresh (Ctrl+Shift+R or Cmd+Shift+R), open the icon URL directly with a cache-busting query such as /favicon.ico?v=2, and make sure the file at the old URL was actually replaced. Some surfaces can take a day or more to refresh on their own.
Upload all files from the ZIP to your site's root directory (the same place as your home page file), then paste the favicon-code.html contents into the <head> of your pages. In WordPress you can upload the files via FTP or your host's file manager and add the links with a header-scripts or SEO plugin.
Not strictly, but it costs nothing and future-proofs Android and install flows. The manifest tells Android Chrome which 192x192 and 512x512 icons to use when your site is added to a home screen. You can ship it and ignore it; browsers that do not need it skip it.
iOS uses apple-touch-icon.png (180x180 here) when someone adds your site to their iPhone or iPad home screen. Android and desktop browsers ignore it. Without the file, Apple devices fall back to a screenshot of your page, which usually looks worse than your logo.
