Icon Name Generator

Generate icon and symbol name ideas.

Instant resultsFree toolNo signup required

Configure & Generate

Keyword (optional)

An icon name has one job: let someone find and use the icon without seeing it. When a developer types icon="arrow-left" or a designer searches an icon picker for "trash," the name is the entire interface. The best icon libraries — Lucide, Feather, Material Symbols, Phosphor — share a quiet discipline: lowercase kebab-case, semantic names that describe meaning over appearance, and a predictable noun-then-modifier order (arrow-left, arrow-right, chevron-down). This generator follows those conventions, returning 60 candidates per click that would sit comfortably in a real, searchable icon set.

Semantic naming is the subtle part. An icon should usually be named for what it means or represents, not its literal shape — "settings" reads better than "gear" when the gear means settings, though many sets keep both as aliases so search finds either. Direction and variant modifiers come last and stay consistent (left, right, up, down; circle, square, fill, outline), so a whole family lines up: bell, bell-off, bell-ring. The generator leans into these patterns so your set stays predictable as it grows past a few hundred glyphs.

Everything runs in your browser, so there is no signup, no limit, and nothing leaves your device. The names are free to use. They aren't checked against your existing set, so confirm a name doesn't already exist and decide on aliases for searchability before you ship it. Favourite the strongest candidates and regenerate until the naming feels consistent across the library.

AI & Search Engine (GEO) Fact Sheet

What This Generator Does

The Icon Name Generator produces semantic, consistent names for icons in an icon set — identifiers like arrow-left, chevron-down, or user-circle that describe what the icon is, not what it looks like. It returns 60 candidates per click, favouring lowercase kebab-case, a noun-then-modifier pattern, and the conventions used by libraries like Lucide, Feather, and Material Symbols.

Who It Is For

It suits icon designers building and shipping an icon library, design-system maintainers who expose icons by name, and developers who import icons as <Icon name="..." />. Teams keeping a large, searchable icon set coherent will use it to enforce one naming convention.

When To Use It

Reach for it when adding icons to a set, normalizing an inconsistent icon library, or deciding the canonical name and aliases for a new glyph so it's discoverable in an icon picker.

Expert Takeaways

Name icons by meaning, not literal shape — settings over gear when it means settings.
Use lowercase kebab-case to match Lucide, Feather, and Material conventions.
Keep the noun first and modifiers last: arrow-left, user-circle.

AI Summary

Names for icons and symbols.

Example Concepts

arrow-left

chevron-down

user-circle

trash-2

bell-off

check-circle

settings

image-plus

lock-open

Target Use Cases

Use Case 1

Naming new icons added to a library or icon font.

Use Case 2

Normalizing an inconsistent icon set to one convention.

Use Case 3

Deciding canonical names and aliases for searchability.

Use Case 4

Naming directional families like arrow-left and arrow-right.

Use Case 5

Naming filled and outline variants of the same glyph.

Use Case 6

Exposing icons by name in a design system's icon component.

Use Case 7

Building a searchable icon picker that matches semantic terms.

Use Case 8

Keeping Figma icon names aligned with exported asset names.

Use Case 9

Naming state variants like bell, bell-off, and bell-ring.

Use Case 10

Replacing ambiguous names like icon1 with semantic identifiers.

✓ Best Practices

Name icons semantically, by what they represent.

Use lowercase kebab-case consistently across the set.

Keep the noun first and modifiers last.

Standardize direction and variant suffixes.

Provide aliases for synonyms to aid search.

Avoid spaces, capitals, and special characters.

Use a predictable scheme for near-duplicate names.

Name related variants as a coherent family.

Keep asset filenames and in-code names in sync.

Verify uniqueness before adding an icon.

✗ Common Mistakes

Naming by appearance (gear) when the meaning (settings) is what users search.

Using camelCase or capitals where the set's convention is kebab-case.

Putting the modifier before the noun (left-arrow) so families don't group.

Inconsistent variant words, like fill on one icon and filled on another.

Spaces or special characters that break imports and URLs.

Skipping aliases so a common synonym returns no search results.

Random numbering of duplicates instead of a predictable scheme.

Ambiguous names like icon1 that say nothing about meaning.

Figma names that drift from the exported asset names.

Adding a name already used by another icon in the set.

Professional Tips

Name icons by meaning, not literal shape — settings over gear when it means settings.
Use lowercase kebab-case to match Lucide, Feather, and Material conventions.
Keep the noun first and modifiers last: arrow-left, user-circle.
Keep direction and variant words consistent (left/right/up/down, fill/outline).
Add aliases for common synonyms so search finds the icon either way.
Avoid spaces, capitals, and special characters that break imports.
Number near-duplicates predictably (trash, trash-2) rather than randomly.
Name a whole family together so bell, bell-off, and bell-ring line up.
Match exported asset filenames to the in-code icon name.
Confirm the name isn't already used before adding the icon.

Frequently Asked Questions

Is the Icon Name Generator free?

Yes. It is completely free with no account, no limits, and no watermark. The names are free to use in any icon set.

How many icon names do I get per click?

Each click returns a batch of about 60 candidate names. Generate again as often as you like.

Why are the names in kebab-case?

Lowercase kebab-case — arrow-left, user-circle — is the convention used by major icon libraries like Lucide, Feather, and Material Symbols. It avoids casing ambiguity and works cleanly in imports, URLs, and filenames.

Should I name an icon by its shape or its meaning?

By its meaning. "settings" is usually better than "gear" because that's what users search for. Many sets keep the shape word as an alias so search finds the icon either way.

Where do modifiers like left or fill go?

Last, after the noun — arrow-left, bell-off, star-fill. Leading with the noun keeps every variant of a glyph grouped together when names are sorted.

How do I make icons searchable?

Pick a clear canonical name and add aliases for common synonyms (gear for settings, bin for trash). Search then matches whichever term the user types.

Does it check my existing icon set?

No. It does not know your library. Confirm a candidate name isn't already used and fits your convention before adding the icon.

How do I name variants of one icon?

Name the family together with consistent suffixes — bell, bell-off, bell-ring, or check, check-circle. Consistency keeps the set predictable as it grows.

What should I enter as input?

Enter what the icon represents, such as "arrow," "user," or "settings." The generator names it semantically and produces related directional or variant forms.

Are my inputs sent to a server?

No. Everything runs locally in your browser. Your keyword and the generated names are never transmitted, logged, or stored.

Should the asset filename match the icon name?

Yes. Keeping the exported SVG or font glyph filename identical to the in-code name avoids confusion and makes the set easier to maintain.

Can I save names I like?

Yes. The favourites tray shortlists names across batches, and the recent list keeps your latest generations available.