Favicon Generator for ICO, PNG, Manifest and ZIP

Turn an image or initials into a complete developer-ready favicon package with browser icons, Apple touch icons, PWA and maskable assets, metadata files and installation tags.

Favicon source and package settings

Choose artwork, configure platform files and generate the complete package.

Choose or drop a source image

PNG, JPEG, WebP or GIF. A square image of at least 512 × 512 pixels is recommended.

Artwork fit and appearance

Image fit

Output background

Artwork padding

Corner radius

18%

Keep transparent background for standard browser and PWA icons when the source permits it

Maskable icon safe-zone padding

12%

Web app and integration details

Application or website name

Short name

Start URL

App scope

Display mode

Icon asset pathUsed in the generated manifest and HTML snippet.

Theme colour

Manifest background

Icon groups and custom sizes

Browser favicon set16, 32, 48, 64 and 96 px PNG plus multi-size ICOApple touch icons57, 60, 72, 76, 114, 120, 144, 152, 167 and 180 pxPWA app icons36, 48, 72, 96, 128, 144, 152, 192, 256, 384 and 512 pxMaskable icons192 and 512 px with safe-zone paddingMicrosoft tile icons70, 144, 150 and 310 pxMetadata and install filesManifest, browser config, HTML and README

Additional square PNG sizesComma-separated values from 8 to 2048 pixels. Duplicate sizes are removed.

Upload an image or create an initials icon to begin.

Live favicon preview

Inspect tiny browser icons and larger app-icon output before export.

Local preview

16 × 16 browser

32 × 32 browser

180 × 180 touch

192 × 192 maskable

Package not generatedPreview changes appear immediately.

HTML integration tags

Generate the package to create favicon link tags.

Generate every essential favicon and web app icon from one source

A favicon is used in browser tabs, bookmarks, history, home-screen shortcuts, installed web apps and operating-system surfaces. This generator prepares a practical cross-platform package so developers can resize once, inspect the results and deploy consistent files with accurate markup.

Multi-size favicon.ico

Create one ICO file containing 16, 32 and 48 pixel browser icons instead of a renamed PNG with an incorrect file structure.

Complete PNG size set

Generate browser, Apple, PWA, maskable, Microsoft and custom square sizes with platform-aware backgrounds.

Manifest and configuration

Build site.webmanifest, browserconfig.xml, installation tags and a deployment README from the settings you enter.

Maskable safe zone

Add protective spacing so important artwork remains visible when mobile platforms apply adaptive icon masks.

Image or initials source

Use existing artwork or create a simple letter icon directly in the browser with editable colours and type style.

ZIP and individual files

Download the complete package in one archive or save specific assets independently for an existing project structure.

How to create and install a favicon package

Follow the same workflow shown in the generator interface.

Choose the icon sourceUpload a PNG, JPEG, WebP or GIF image, or create an icon from one to three initials.
Adjust the artworkChoose contain or cover cropping, padding, corner radius, transparency and background colours.
Configure the packageEnter app and manifest details, select the platform icon groups and add any custom square sizes.
Generate and inspectCreate the package, review the small and large previews, and check the generated file list.
Download and installDownload the complete ZIP or individual files, upload them to your site and paste the supplied HTML tags into the document head.

Favicon sizes and generated files explained

Different browsers and operating systems request different assets. The default package covers the most commonly deployed square sizes while allowing extra developer-defined PNG dimensions.

Output group	Generated sizes or files	Typical use
Browser favicons	`16, 32, 48, 64, 96 px` and `favicon.ico`	Tabs, bookmarks, history and legacy favicon requests.
Apple touch icons	`57, 60, 72, 76, 114, 120, 144, 152, 167, 180 px`	Home-screen shortcuts on iPhone and iPad devices.
PWA application icons	`36, 48, 72, 96, 128, 144, 152, 192, 256, 384, 512 px`	Installable web applications, launchers and app surfaces.
Maskable icons	`192, 512 px`	Adaptive shapes on supporting mobile operating systems.
Microsoft tiles	`70, 144, 150, 310 px`	Tile and pinned-site artwork used with browser configuration.
Metadata	`site.webmanifest`, `browserconfig.xml`, HTML and README	Browser discovery, installation details and deployment guidance.

Favicon design quality, privacy and browser limitations

Design for 16 pixels first

Use a simple silhouette and high contrast.
Keep important artwork away from the edges.
Avoid thin strokes and small text.
Check both light and dark browser interfaces.
Use the live 16 and 32 pixel previews.

Understand platform cropping

Contain preserves the full source.
Cover may crop source edges.
Apple and tile icons use a solid background.
Maskable icons include additional safe spacing.
Operating systems may still apply their own shape.

Private local processing

Your files are protected and safe; we never collect or share your data. The source image is decoded, resized and packaged in your browser. Reset removes the selected file and generated objects from the current page session.

Practical browser limits

Very large source images, many high-resolution custom sizes or low-memory mobile devices can cause canvas or package creation to fail. Animated images use one decoded frame, and unsupported or corrupted image data cannot be processed.

Troubleshooting favicon generation and installation

The uploaded image is rejected

Confirm that it is a real PNG, JPEG, WebP or GIF file. Renaming an unsupported file extension does not convert its contents.

Small favicons look unclear

Increase padding, simplify the artwork, remove tiny text and inspect the 16 pixel preview at its real display size.

The favicon does not update

Replace the deployed files, confirm the HTML paths, purge any CDN cache and test in a new private browser window because favicons are cached aggressively.

The manifest icon is missing

Serve the manifest with an appropriate content type, verify each icon path and inspect the Application or Manifest panel in browser developer tools.

The ZIP cannot be created

Check the connection used to load the packaging component, reduce custom sizes, close memory-heavy tabs or download the generated files individually.

The installed app crops the logo

Increase maskable safe-zone padding and ensure every important element remains near the centre of the source artwork.

Frequently asked questions about favicon generation

Answers about source images, ICO structure, icon sizes, PWA manifests, maskable assets, privacy, downloads and deployment.

What does this favicon generator create?

It creates a complete website icon package containing browser favicon PNG files, a multi-size favicon.ico file, Apple touch icons, PWA icons, maskable icons, Microsoft tile icons, a web app manifest, browser configuration markup, an HTML integration snippet and a ZIP download.

Which source image formats can I use?

You can use PNG, JPEG, WebP or GIF images that the browser can decode. Animated GIF files are treated as a still image using the first decoded frame. SVG is intentionally not accepted because untrusted SVG files can contain active content.

What image size should I upload for the best favicon quality?

A square source of at least 512 by 512 pixels is recommended. A 1024 by 1024 source gives additional detail for large app icons, but very fine details and small text may still disappear at 16 or 32 pixels.

Can I generate a favicon without uploading an image?

Yes. Switch to the initials option, enter one to three letters, choose background and text colours, and the tool will create a clean letter-based icon package.

Does the generator create favicon.ico?

Yes. The ICO output contains PNG-encoded 16 by 16, 32 by 32 and 48 by 48 icon entries in one favicon.ico file for broad browser and legacy compatibility.

Which favicon sizes are included?

The default package includes browser sizes from 16 through 96 pixels, legacy and current Apple touch sizes from 57 through 180 pixels, PWA sizes from 36 through 512 pixels, maskable 192 and 512 pixel icons, Microsoft tile sizes and optional custom square sizes entered by the user.

What is a maskable PWA icon?

A maskable icon is designed so an operating system can crop it into circles, rounded squares or other adaptive shapes without cutting off important artwork. This generator adds a configurable safe-zone margin and a solid background for maskable exports.

What is site.webmanifest used for?

The web app manifest describes an installable website or PWA. It can define the app name, short name, start URL, scope, display mode, theme colours and the icon files a compatible browser may use.

Does the tool generate the HTML favicon tags?

Yes. The package includes a ready-to-copy HTML snippet for favicon.ico, 16 and 32 pixel PNG icons, the Apple touch icon, the web app manifest and theme colour. Update the asset path when your icons are stored in a subdirectory.

Can I add custom favicon sizes?

Yes. Enter comma-separated square dimensions such as 64, 256 or 1024. Duplicate sizes are removed automatically, and each accepted value is generated as a PNG file.

Should a favicon have a transparent background?

Transparency works well for standard browser favicons when the artwork remains visible on both light and dark browser interfaces. Apple touch, Microsoft tile and maskable icons are exported with a solid background for more predictable platform rendering.

Why does my favicon look blurry or unreadable?

Small favicons have very few pixels. Use a simple silhouette, strong contrast, generous spacing and minimal detail. Avoid thin lines and long words, then inspect the 16 and 32 pixel previews before downloading.

What is the difference between contain and cover cropping?

Contain keeps the entire source image visible and may leave background space around it. Cover fills the icon canvas completely and may crop edges. Padding can be added to either mode to protect important content.

Can I use the generated package on WordPress or another CMS?

Yes. The files are standard web assets. Upload them to the location used by your site or theme, then add the supplied tags or use the CMS favicon and site icon settings where available.

Are my uploaded images sent to a server?

No. Image decoding, resizing, ICO creation, manifest generation and package preparation occur in the browser. The selected image is not uploaded by this tool. A packaged script is fetched only when you request the ZIP file, and your image data is not sent with that request.

Is there a generation or download limit?

CorrectionCopy does not impose an artificial usage or download limit. Practical limits depend on browser memory, source-image dimensions, the number of custom sizes and the device canvas implementation.

Why did ZIP creation fail?

The packaging component may have been blocked by the network, a content policy or a browser extension, or the requested package may exceed available memory. Retry with fewer custom sizes, close memory-heavy tabs or download individual files.

How do I verify the generated favicon package?

Upload the files, add the supplied tags, clear browser and CDN caches, open the page in several browsers, inspect the manifest in developer tools and test installation on a mobile device when PWA support matters.