Prompts for App and Interface Icons

An icon has one job: to be recognised instantly at a size where almost no detail survives. That single requirement should shape every clause in the prompt, and usually does not. Most icon prompts are written as though the result will be viewed full screen, which is why the output looks fine in the preview and turns to mush the moment it sits in a toolbar at thirty-two pixels.

Prompt for the Silhouette

Recognition at small sizes comes almost entirely from outline. Before writing anything, decide what shape the icon makes as a solid black blob — if that blob is ambiguous, no amount of interior detail will rescue it. So the prompt should lead with the silhouette and treat everything else as secondary: a single bold shape, high contrast against the background, generous internal spacing.

That means actively suppressing the things the model wants to add. Ask for flat colour with no gradient, no drop shadow, no reflection, no thin lines, and a shape that fills the frame rather than floating small in the middle. Left alone, models produce the glossy, bevelled, softly-lit object that dominated icon design fifteen years ago, and that treatment is exactly what dissolves when downscaled.

One subject, not two. “A cloud with an arrow and a lock” is three ideas fighting for a space that has room for one. If a concept genuinely needs two elements, make one of them dominant and the other a small structural accent — a corner badge, a single notch — rather than an equal partner.

Name the Icon System

Icon styles are far more standardised than illustration styles, which makes naming a system unusually effective. A rounded solid glyph. A two-pixel monoline outline icon with rounded caps. A duotone icon in one hue with a lighter fill. A skeuomorphic app tile with a rounded square base. Each of these settles stroke weight, corner treatment and colour count in one phrase.

Say which kind of icon you mean, too, because the conventions differ sharply. An app tile is a full-bleed square with a background and lives on a home screen. An interface glyph is a bare mark with no container that must sit comfortably beside text. Prompting for one and using it as the other is a common and very visible mistake.

Build the Set, Not the Icon

Icons almost never ship alone, and a set that does not share a visual language looks worse than any individual icon in it. Fix the style description word for word, change only the subject, and generate the whole set in one pass so nothing drifts. If your generator supports it, keeping the same seed across the set helps hold weight and proportion steady.

Then check them properly. Shrink every candidate to its real display size, put them side by side, and see which ones you can still name. That test takes a minute and rejects more prompts than any amount of reasoning about them beforehand — including some that looked like the best of the batch at full resolution.