Skip to content

Favicon & app icon generator

One logo in, the complete 2026 favicon package out: .ico, PNGs, Apple and Android icons, manifest and the exact HTML.

One SVG (best) or a large square PNG, 512 px or more

Advanced settings (optional)
Favicon options
App / site name

Used in the web manifest and the previews.

Theme colour
#00bda3

Becomes theme-color — tints the browser UI on Android and in installed apps.

Icon background

Regular favicons: keep transparent for most logos, or use a solid colour if the mark disappears on dark tabs.

Apple / maskable fill
#ffffff

iOS and Android adaptive icons cannot be transparent; this colour fills behind the artwork.

Padding
0%

Shrinks the artwork on every icon. Logos that touch the edges look better with 5–10 %.

Hosting path

Folder where you will upload the files; / for the site root.

Runs in your browser. Files are never uploaded — you can go offline after the page loads.

How to use the Favicon Generator

  1. Click “Choose Files” or drop your logo into the box above. Whole folders work too.
  2. Adjust the Advanced settings if you need to, then click “Download package”.
  3. When the row shows Done, click “Download” — or “Download all” for a ZIP.

Easy to use

Drop files, pick options, download. Whole folders at once, no signup, no daily limit.

Best quality

The same engines the professionals use — SVGO, resvg, MozJPEG, libwebp, libavif — compiled to run in your browser.

Private & secure

Files are processed on your device and never uploaded. Close the tab and nothing remains anywhere.

What you get

Drop a logo — ideally an SVG, otherwise a large square PNG — and the generator produces the complete set of icons that browsers, iOS, Android and installable web apps read today, previews them in a browser tab and on a phone home screen, and hands you a ZIP plus the five lines of HTML to paste into your <head>. Everything is rendered in your browser; nothing is uploaded.

  • favicon.ico — 16, 32 and 48 px PNGs packed into one file for legacy browsers, bookmarks and Windows shortcuts.
  • favicon.svg — when your source is an SVG: infinitely sharp, and the file modern browsers pick first.
  • favicon-16x16.png, favicon-32x32.png — tab icons at 1× and 2×.
  • apple-touch-icon.png — 180 px, opaque background, slight padding: what iOS shows on the home screen.
  • icon-192.png, icon-512.png — referenced from the manifest for Android and PWA installs.
  • icon-maskable-512.png — artwork inside the central 80 % “safe zone” on a solid background, so Android can crop it to a circle or squircle without clipping your logo.
  • site.webmanifest — name, short name, theme colour and the icon list, ready to serve.
  • favicon-snippet.html — the <link> and <meta> tags, with your path already filled in.

Options

App / site name fills the manifest and the previews. Theme colour becomes theme-color, which tints the browser UI on Android and in installed apps. Icon background controls the regular favicons — keep Transparent for most logos, or pick a solid colour if your mark is thin or light and disappears on dark tabs. Apple/maskable background is the fill behind the two icons that cannot be transparent. Padding shrinks the artwork on every icon; logos that touch the edges usually look better with 5–10 %. Path is the folder you will upload to — leave it as / for the site root.

Deploying

Upload the files, paste the snippet once in your layout, and check yoursite.com/favicon.ico loads. Browsers cache favicons hard, so an old icon can linger for days; open the icon URL directly and hard-refresh to confirm the new one is live. If the source SVG came straight from a design tool, run it through the SVG Optimizer first — the generator does this automatically for the favicon.svg it emits, but the smaller file also renders faster on every page load.

Frequently asked questions

Which favicon sizes do I actually need in 2026?

Far fewer than the old 20-file packages suggest. Modern browsers use favicon.svg (any size) or a 32 px PNG; favicon.ico with 16/32/48 covers legacy browsers, bookmarks and Windows; iOS reads apple-touch-icon.png at 180 px; Android and installable web apps read the 192 and 512 px icons from the manifest, plus a “maskable” 512 px version whose artwork sits inside the central 80 % so it survives being cropped to a circle or squircle. That is exactly the set this tool produces — nothing else is read by anything current.

Should I upload an SVG or a PNG?

SVG whenever you have one. It is rendered fresh at every size so the 16 px icon is as sharp as the 512 px one, and you also get favicon.svg, which modern browsers prefer and which can even respond to dark mode with a <style> block inside the file. If you only have a PNG, use the largest square version you have — 512 px or bigger — and the tool downsamples it in quality-preserving steps.

Why does the Apple touch icon have a solid background?

iOS does not support transparency in home-screen icons: transparent areas are rendered black. The tool therefore fills apple-touch-icon.png and the maskable Android icon with the background colour you choose (white by default), and adds a little padding so the artwork is not touching the rounded corners. The regular favicons keep transparency unless you choose a solid icon background.

Where do I put the files and the HTML?

Upload every file from the ZIP to your site root (or to a folder, and set the Path option to match so the snippet and manifest point to the right place). Paste the snippet into the <head> of every page — most sites have one layout or template where it goes once. Browsers cache favicons aggressively; if the old icon persists, open the icon URL directly and hard-refresh, or change the file name.

Are my files uploaded anywhere?

No. Rendering happens in your browser: SVGs through a WebAssembly build of resvg, PNGs through the canvas, and the .ico file is assembled in JavaScript. Nothing is sent to a server, and you can use the tool offline once the page has loaded.

Your files never leave your device

Most online converters upload your file to a server. InfyTool ships the actual encoders to your browser as WebAssembly instead, so processing happens inside your tab — faster for batches, and nothing to delete afterwards.

  • No upload, ever. Turn off Wi-Fi after the page loads and every tool keeps working.
  • No limits. No file-size cap, no queue, no watermark, no account.
  • Runs on your CPU. Batches use several cores in parallel; nothing is throttled.

More free tools

Need icons or SVGs to start from?

InfyTool is built by the same team as these free libraries.