Favicon and app icon sizes: the files you actually need

2026-11-19 · 6 min read

Favicon size charts run long: 57×57, 72×72, 114×114, 144×144, 152×152 and on down the page. A website needs two or three files, and an iOS app needs one. The sizes are rarely what goes wrong. The shapes are: iOS, Android and Chrome each cut your icon into their own outline, and a logo that runs to the edge loses its corners.

Your squareiPhoneCircleMark to the edge
Mark in the middle
The same square icon, cut two ways. The iPhone only rounds the corners. A circle, the shape many Android launchers and installed web apps use, takes much more. The faint parts are what gets cut off; a mark kept to the middle survives both.

The short list

  • Website: a favicon.ico at the site root and a 180×180 apple-touch-icon.png. An SVG favicon is a good extra.
  • Installable web app: 192×192 and 512×512 PNGs listed in a web manifest, plus a maskable version of each.
  • iOS app: one 1024×1024 image.
  • Android app: an adaptive launcher icon built on a 108×108 dp canvas, and a separate 512×512 PNG for the Google Play listing.

Everything else is optional.

Browser tabs: keep the favicon.ico

The HTML standard lets browsers request /favicon.ico from your site root when a page declares no icon at all. So a file at that exact path still shows up on any page that forgot its <link> tags.

An .ico can also hold several bitmaps in one file; we pack 16, 32 and 48 px versions into ours. When a page does list several icons, the browser picks between them using their type, media and sizes attributes, according to MDN, so declaring more than one does no harm.

16px
32px
48px
180px
One mark at 16, 32, 48 and 180 CSS pixels, drawn at that size. The 16-pixel version is what sits in a browser tab, so check the mark still reads there.

Google Search shows a favicon next to your result and sets its own rules for it. Google's favicon guidelines ask for a square image of at least 8×8, recommend going larger than 48×48, and require that Googlebot can crawl both the icon and your home page. Google reads apple-touch-icon links as well as icon ones, so the 180-pixel file below already gives it something above that 48-pixel line.

SVG favicons: add one, but not on its own

An SVG favicon is one file that stays sharp at every size, and support is now broad. Can I use lists Chrome and Edge from version 80, Firefox from 41, and Safari on Mac and iOS from 26.

Search is the exception. Google's guidelines list the formats it supports for favicons as BMP, GIF, ICO, PNG, JPEG, PPM and TIFF. SVG isn't on that list. Ship the SVG next to the .ico and the PNGs, never instead of them.

Apple touch icon: one file at 180×180

When someone adds your site to an iPhone home screen, iOS doesn't use your rel="icon" links. MDN notes that it reads the non-standard apple-touch-icon instead. Apple's Safari web content guide (archived, last updated in 2016) shows 180×180 for Retina iPhones, alongside 152 and 167 for iPads.

The same guide explains why you don't need all three. When no icon matches the device exactly, iOS uses the smallest icon larger than the size it wants, and if none is larger, the largest one available. A single 180×180 file covers every case. If you don't declare one at all, Safari looks for apple-touch-icon.png in the site root, so that is the filename to use.

Give it a solid background color rather than relying on transparency. Our generator flattens it onto the color you pick.

Installable web apps: 192, 512 and the maskable pair

If your site isn't meant to be installed, skip this section. If it is, web.dev's manifest guide is specific: Chromium needs at least a 192×192 and a 512×512 icon in the manifest, and Chrome scales those two to fit the device.

Android and Chrome then crop installed-app icons into circles, squircles and other shapes. A maskable icon is one designed to survive that. Per web.dev's maskable icon article, anything important has to sit inside a centered circle whose radius is 40% of the icon's width, and you mark the file with "purpose": "maskable". The same article recommends against using one file as both the regular and the maskable icon, so ship two of each size: a regular one with your artwork at full size, and a maskable one with padding and a filled background.

iOS apps: one 1024×1024 master

Apple's app icon guidelines give a single 1024×1024 size for iOS, iPadOS and macOS, and say the system scales it down for smaller places like Settings and notifications. Keep the artwork square: the system applies the rounded-corner mask itself, and Apple says pre-masked artwork makes the edges look jagged. If you supply a background layer, it has to be full-bleed and opaque.

Layers are optional. You can supply a plain PNG or a layered file from Apple's Icon Composer, and given a flat image the system tries to separate the foreground from the background on its own.

Android apps: two different icons

Android has two icons that people mix up. The one on the home screen comes from your app package. The one on your store page is uploaded separately in Play Console, and Google's Play icon spec says outright that they are separate assets.

The launcher icon is an adaptive icon: a foreground layer and a background layer, each 108×108 dp. Each phone maker supplies its own mask shape. Only the inner 66×66 dp is guaranteed to stay visible, and the outer 18 dp on each side is reserved for masking and motion effects. Android's guidance is a logo of at least 48×48 dp that never goes past that 66 dp box. From Android 13, an optional third monochrome layer lets the icon follow the user's themed colors.

The Play listing icon is simpler: 512×512, a 32-bit PNG in sRGB, 1024 KB at most, and a full square. Play rounds the corners itself (to a radius of 30% of the icon size) and adds the drop shadow, so leave both out of your file. Transparent areas show Play's own background color through them, which is a good reason to fill the square.

Start from one big square

Every file above is a resize of one square image, so the one design call is the safe zone. Android's is the tightest: 66 of 108 dp, or about 61% of the width. If the important part of your mark fits inside a centered circle about that wide, it also clears the maskable 40% radius, and it sits well inside the rounded squares Play and Apple cut. Start from an SVG or a PNG of at least 1024×1024, since that's the iOS master size, and check that the mark still reads at 16 pixels.

  • Maskable web app icon: keep it inside a circle 80% wide (40% radius)
  • Android: the most a launcher shows, 72 of 108 dp
  • Android: always visible, 66 of 108 dp (about 61%)
  • The full square: 108 dp on Android, 1024 px for iOS
The guides on one square. Android’s is the tightest, so a mark that fits its 66 dp circle fits everywhere else too.

If you don't have a mark yet, the icon maker builds one from text or an open-source icon on a styled background. If you do, drop it into the favicon and app icon generator. It writes everything on the short list: favicon.ico, the PNG favicons, the Apple touch icon, the manifest icons with their maskable versions, the Android adaptive set and an iOS AppIcon set, plus the <head> tags to paste. It runs in your browser, so the image is never uploaded.

And if the icon is for an app about to go into a store, check the name first. Store names follow their own collision rules, and a name check covers the App Store and Google Play alongside domains and trademarks.


Ready to check a name? Run it through dibbed.dev →