I already investigated this issue for iOS because RealFaviconGenerator is in the process of generating only one, 180x180 icon. Else, declaring a single, large icon is fine.Īs and discussed it above, scaling down can be an issue. it's angular on purpose, such as pixel art) AND you want a perfect result, you should create and declare all icons.

TL DR Regarding scaling down, if the image requires a specific scaling algorithm (eg. Update: conversation below indicates you need fewer than this: 192, 512ĭec 2020 edit: some related stuff in #11762

If you'd like to provide native rendering of icon for home-screen and splash-screen across supported screen densities, you should provide an icon in these sizes: 72, 96, 144, 192, 256, 384, 512Īnd all of these should be explicitly indicated in your manifest. I dumped our key dp numbers into (and hacked the page with devtools) for this 💰 💰 💰 screenshot: (The Android One is hdpi) You can ignore anything less than hdpiįor example, the nexus 5 and nexus 6p are xxhdpi and xxxdpi respectively. dp and pxįor phone-sized android devices, we mostly care about hdpi and up. So far, our magic numbers are 48dp and 128dp. See how the splash layout and icon is chosen in //src/chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappActivity.java Icon was auto-generated by Chrome and whether the icon is bigger than a threshold. There are three possible layouts for splash screens, which is chosen based on whether an from chromium /src/chrome/android/java/res/values/dimens.xml

Google chrome logo 512x512