Usage guide

How to use the app icon generator well

The tool itself is simple, but the quality of the result depends on your source artwork, fit choice, and padding decisions. This page covers the practical workflow that makes the exported PNG files easier to use later.

Start with the source, not the export list

The best icon packs usually begin with one strong square source image. If the original artwork is blurry, cramped, or built too close to the edges, exporting more sizes does not fix the underlying problem. It only repeats it in more places.

Use a square master image

Begin with a square image, ideally 1024 x 1024 or larger. That is the easiest way to avoid quality loss in the largest outputs and keeps the proportions consistent when the tool scales the artwork down.

Upload and inspect the preview

After you upload the file, check the source preview before generating anything. If the icon already looks cramped or visually off-center there, it will keep that problem in the exported pack.

Choose fit mode based on the artwork

Contain is the safer choice for most logos and detailed marks because it preserves the full design inside the icon area. Cover is more aggressive and only works well when the artwork can tolerate edge cropping.

Use padding on purpose

The safe padding control matters more than people think. A little spacing helps icons survive rounded masking, launcher treatment, and small-size display without feeling crowded. It is especially useful when you plan to export PWA maskable icons.

Select only the packs you actually need

If you are preparing artwork for one app release, you usually do not need every pack every time. iOS, Android, PWA, and favicon exports serve different workflows. Selecting only the relevant groups keeps your download output cleaner and easier to manage.

Pick the background that matches the icon style

Transparent output works best when the artwork already has its own shape and space. A solid background is better when the icon is meant to sit on a fixed color tile or when you want the export to feel more stable across platforms.

Use contain by default

Contain is the practical default because it protects the whole symbol. Cover makes sense only when the icon artwork is bold enough to absorb cropping without losing meaning.

What usually causes weak exports

  • Starting with a small image and expecting the 1024 export to look sharp.
  • Using edge-to-edge artwork with no padding, then discovering it looks cramped in smaller contexts.
  • Choosing every pack by default instead of matching the output to the actual release task.
  • Assuming flat PNGs automatically replace adaptive icon resources, manifest setup, or Xcode packaging.

Practical rule of thumb

If you are unsure, use a large square source, choose contain, keep a transparent background unless the design clearly needs a color tile, and add a little padding. That combination is the safest starting point for most app icon work.