Home / Favicon & App Icon Tools / Favicon Size Generator

Favicon & App Icon Tools

Favicon Size Generator

Generate every practical favicon size from one image: multi-size ICO, 16/32/48/96 PNGs, Apple 180, PWA 192/512, a maskable icon, web manifest and copy-ready HTML — all locally.

Source image

Fit

Background for contain mode

Choose an imageCreates 16×16, 32×32, and 48×48 PNG files locally.

Wave112 · Favicon design & deployment authority

Favicon Design & Deployment Studio

Create the artwork, inspect it at real favicon sizes, build browser/Apple/PWA assets, audit maskable safety, and leave with the install snippets and project evidence needed to ship. The fast three-size generator above remains available for a quick PNG task.

Image · SVG · Text · EmojiICO + PNG + Apple + PWALive 16–512px previewsMaskable safe-zone evidenceStatic · Next.js · Vite handoffBrowser-local

1. Source & design

Start from existing artwork, preserve an uploaded SVG as vector output, or generate a favicon from initials/text or emoji without leaving the browser.

design source

Source mode

Image or SVG

Text or emoji

Typeface

Generated shape

Image fitBackground modePadding

10%

Corner radius

24%

Light backgroundDark backgroundLight foregroundDark foreground

Text · "WA" · generated locally

2. Real-size preview

Inspect the same design at the sizes that actually expose legibility problems instead of judging only a large 512px preview.

tiny-size QA

Browser-tab approximation

My App

Maskable safe-zone preview

The maskable export forces at least 18% inset so important artwork is not pushed into the most aggressive crop region. The dashed circle is planning evidence, not a promise about every launcher shape.

3. Package & manifest

Build each raster directly from the source/design, pack 16/32/48 into one ICO, add Apple/PWA assets, and keep manifest metadata explicit.

ship-ready bundle

App nameShort nameStart URLExtra PNG sizesLight theme colorDark theme color

Package plan—

ICO entries—

SVG handoff—

Maskable—

Last package size: —. ZIP creation, resizing and ICO packing stay in this browser.

File	Size/type	Purpose

4. Source & deployment audit

Keep the limitations visible: local generation can inspect source geometry and package structure, but deployed URLs and platform caches still need real-world verification.

evidence

Preparing audit…

Ready.

5. Install handoff

Use the snippet that matches the deployment workflow. The generated ZIP also contains the static HTML snippet and README.

Static HTML

Next.js metadata

Vite / React public handoff

6. Local recent designs & project

The latest 12 package builds are stored only in this browser. Project JSON carries settings; uploaded image bytes are deliberately not embedded, so a private source image is never slipped into a project or share link.

Project imports are capped at 1 MB. Portable links omit source text/emoji and all uploaded image bytes; they carry style/package settings only.

Rendering boundary. Raster favicons are sampled by browsers and operating systems, so a design that looks sharp at 512px can still fail at 16px. Uploaded raster artwork below 512px is upscaled for large outputs and should be reviewed. Uploaded SVG is preserved as favicon.svg; generated text/emoji mode creates an SVG that depends on the target system's available font/emoji rendering. Deployment boundary. This browser-local tool cannot crawl your live site, invalidate caches, verify HTTP headers or service workers, certify PWA installability, or guarantee Google Search will display a particular favicon after recrawl.

How to use the Favicon Size Generator

Use the quick generator at the top when you only need a few PNG sizes. For a complete deployment, use Favicon Design & Deployment Studio: start from an image or SVG, or create initials/text/emoji artwork, inspect the 16–512px previews, review the maskable safe area, then build the ICO, PNG, Apple, PWA, manifest and install files together.

Why a favicon package needs more than favicon.ico

Desktop and legacy contexts still benefit from a multi-size ICO, while modern browsers, Apple home-screen shortcuts and installable web apps use additional raster or manifest-declared assets. The Studio creates those files from one source so their naming and sizing stay consistent.

SVG and tiny raster sizes serve different jobs

An SVG favicon can stay crisp in modern browsers, but raster fallbacks remain useful for compatibility, search surfaces and platform-specific assets. The Studio preserves an uploaded SVG as vector output and independently renders each PNG size rather than repeatedly shrinking one generated bitmap.

Text and emoji favicon creation

Initials and emoji are useful when a project has no finished logo. The generated vector keeps light/dark color rules, while PNG, Apple and PWA files use the selected light design. Emoji appearance varies by operating system and font, so the real-size preview is a planning aid rather than a promise of identical cross-platform artwork.

Maskable icons and safe zones

Maskable PWA icons may be cropped into circles, rounded rectangles or other launcher shapes. The Studio adds extra inset to the maskable export and shows an 80% safe-circle overlay so important artwork can be kept away from risky edges.

Deployment still needs real verification

Generating correct files locally does not prove a live site serves them from the expected URLs, that a browser cache has refreshed, that a service worker is correct, or that a search engine has recrawled the page. After deployment, open the asset URLs directly and test the actual browser, device and PWA flow.

Privacy and portability

Image processing, previewing, ZIP creation and ICO packing run in the browser. Recent package builds use localStorage. Project JSON contains settings but deliberately omits uploaded image bytes, and the portable settings link omits source text, emoji and image content.