Checklist

Common iOS icon export mistakes and how to avoid them

Icon export mistakes are rarely dramatic, but they create polish issues that users notice immediately. A fuzzy icon, bad edge spacing, or incomplete asset set makes the app feel less deliberate than it should.

Using a weak source file

Starting with a tiny logo and scaling up is one of the most common mistakes. Always begin with a large square asset. If possible, export from vector or high-resolution source files instead of screenshots.

Ignoring visual padding

Logos with different visual weight need different breathing room. Simply centering the asset is not enough. Check whether the icon feels balanced at smaller sizes, especially around 29x29 and 40x40 derived exports.

Forgetting the App Store icon

The 1024x1024 icon is often treated separately, but it is still part of the export workflow. If the marketing icon looks different from the in-app icon family, your brand presentation becomes inconsistent.

Exporting PNG files without metadata

A folder full of PNG files is not the same thing as a valid AppIcon.appiconset. The asset catalog also needs a matching Contents.json so Xcode knows which file belongs to each slot.

If you want to avoid these mistakes entirely, use the generator tool to export the icon files and metadata together.