WEBSITE ASSETS

Favicon & App Icon Pack Generator

Turn your logo into browser favicons and website app icons. Check the tiny previews, then download the files and installation instructions together.

1. Choose your image

Drop one PNG, JPG or WebP here, or choose a file. Maximum 10 MB, 16 megapixels and 8,000 px per side. PNG is useful for transparent logos. Animated images are frozen to one still frame; use a static logo for predictable results.

No image selected.

Icon settings
Position, transparency & colors

Position changes the crop for wide/tall images, or aligns a fitted image inside the square.

Apple touch icons always use the background color. Theme color is a browser hint, not an image recolor.

Use / for the site root or a folder such as /icons/. Upload the icons and manifest to that folder.

Choose an image or load the example to begin.

Processed locally using scripts hosted on this website. Images and settings are not uploaded or saved.

2. Check small-size clarity

Your icon preview appears here.

Using Favicon & App Icon Pack Generator

Create website icons from a logo and check their appearance before downloading. Images stay in your browser; the generated pack includes files and matching installation instructions.

  1. Choose a PNG, JPG or WebP image up to 10 MB, 16 megapixels and 8,000 pixels per side, or load the example. Use a simple square logo with at least 512 pixels for sharper large icons.
  2. Choose Fit whole image or Crop to square, adjust padding and position, and check the actual-size and light/dark previews. Enter your site name and the folder where you will upload the files.
  3. Generate the pack and download the ZIP or individual files. Upload the icons and manifest to the chosen folder, then copy the HTML tags into your page head. Read README.txt and test the deployed icon URLs.

Example

Source: a 512 × 512 PNG logo.
Icon folder: /icons/
Upload favicon.ico, six PNGs and site.webmanifest to /icons/.
Add the generated links inside <head>; they use paths such as /icons/favicon.ico.

Questions & answers

What files are included?

The pack has ten files: a real ICO containing 16, 32 and 48 pixel images; PNGs at 16, 32 and 48 pixels; an opaque 180 pixel Apple touch icon; 192 and 512 pixel Android website icons; site.webmanifest; installation.html; and README.txt.

Is favicon.ico a renamed PNG?

No. It is an ICO container with three 32-bit bitmap entries, alpha channels and transparency masks. Browser PNG files are also included as alternatives.

How do fit, crop, padding and position work?

Fit whole image preserves the entire image inside a square. Crop to square selects a square region without stretching. Padding adds space around the design; horizontal and vertical position choose the crop region or align a fitted image.

Why does the Apple touch icon have a background?

Apple touch icons are exported as opaque PNGs using your chosen background color. The transparency checkbox applies to browser and Android icons; the source artwork is composited onto the background for the Apple icon.

Does this generate maskable icons or a complete PWA?

No. The Android icons have purpose any. The minimal manifest contains icons, names and colors; merge it into an existing manifest if you have one. It does not create a service worker, guarantee installation, or supply a native app-store icon set.

How should I choose the icon folder?

Use an absolute path ending in a slash, such as / or /icons/. Only letters, numbers, hyphens and underscores are accepted in folder names. HTML links use this folder; icon paths inside the manifest are relative to its own location.

Why do I still see my old favicon?

Browsers often cache favicons. Check that the generated files are available at their expected URLs, reload or test a new private tab, and consider versioning icon URLs when updating an existing website. Search display is not guaranteed by generating an icon pack.

Are my images uploaded or saved?

No. Image decoding and icon creation happen in your browser using locally hosted scripts. Inputs remain in page memory until cleared or the page closes. Downloads are saved by your browser; canvas exports omit source metadata.

Will a small or detailed logo look sharp?

Resizing cannot restore missing detail. A simple logo at least 512 pixels across helps the larger outputs. Check the 16 pixel preview: thin lines, small text and busy artwork can become unreadable.

What happens if I change settings or cancel?

Changes clear previous downloads so they cannot be mistaken for the updated design. Cancellation discards partial results. Decode, PNG and ZIP operations have 15-second timeouts; generated files are limited to 8 MB total.

Help improve this tool

Report a problem or suggest an improvement

Describe the issue without pasting private tool input. Feedback goes to our admin inbox.

Find another tool · Read practical guides