100 Icon Libraries for Product Teams and Solo Founders
Icons are small interface decisions with outsized effects. They influence how quickly a new user understands navigation, whether a dense dashboard feels manageable, and how coherent a product appears across screens. For a solo founder or small team, the challenge is rarely finding an icon. It is choosing a source that fits the product’s visual language, technical stack, and licensing requirements without creating a maintenance problem later.
This is a non-ranked directory of 100 icon libraries and icon sources. Some are tightly designed sets; others are broad catalogs, developer packages, marketplace collections, or brand-icon resources. “Best” depends on the context: a developer tool may need familiar open-source symbols, while a consumer app may need a more expressive illustrated system.
What to evaluate before choosing a library
Start with the product surface where icons will appear. A sparse marketing site can accommodate more decorative icons than a compact data table. A mobile interface may need tested touch-target conventions and clear filled/outlined states. If the product will grow, consistency matters more than finding a one-off symbol for every edge case.
- Visual system: Compare stroke weight, corner treatment, proportions, and filled versus outline styles.
- Coverage: Check the everyday interface icons first: search, settings, filters, alerts, upload, sharing, billing, and status.
- Formats: SVG is common for web workflows, but teams may also need React components, icon fonts, raster exports, or design-tool files.
- License: Review commercial-use, modification, redistribution, attribution, and trademark terms for the exact assets used.
- Accessibility: Decorative icons and meaningful controls should be implemented differently; labels and accessible names remain important.
A consistent icon set usually makes an interface feel more intentional than a collection of individually attractive but mismatched symbols.
100 icon libraries and sources
The following list is organized loosely by type rather than quality. Library names, ownership, license terms, and package availability can change, so verify the current documentation before adopting one.
- Adobe Spectrum Icons
- Ant Design Icons
- Atlas Icons
- Bootstrap Icons
- BoxIcons
- Carbon Icons
- Cham Icons
- Clarity Icons
- Codicons
- Coolicons
- CoreUI Icons
- CSS.gg
- Cuida Icons
- Dashicons
- Devicon
- Dripicons
- Duotone Icons
- Elusive Icons
- Eva Icons
- Feather Icons
- Flaticon
- Fluent UI System Icons
- Font Awesome
- Fontisto
- Fork Awesome
- Google Material Symbols
- Google Material Icons
- Govicons
- Gravity UI Icons
- Grommet Icons
- Hackney Icons
- Heroicons
- Hugeicons
- Humbleicons
- IconArchive
- IconBuddy
- Icones
- Iconfinder
- Iconify
- Iconjar
- Icons8
- Iconsax
- IconScout
- Iconshock
- Iconoir
- IconPark
- IconPharm
- Iconscout Unicons
- Ionicons
- Jam Icons
- Kalium Icons
- Kendo UI Icons
- Kenney Game Icons
- لاج?
- Ligature Symbols
- Line Awesome
- Linearicons
- Lucide
- Majesticons
- Map Icons
- Mapbox Maki
- Material Design Icons
- Microsoft Fluent Emoji
- Mono Icons
- Montserrat Icons
- NG-ZORRO Icons
- Nordicons
- Octicons
- Open Iconic
- OpenMoji
- Orion Icon Library
- Pajamas Icons
- Phosphor Icons
- Pixelarticons
- PrimeIcons
- Radix Icons
- Remix Icon
- Reshot Icons
- SF Symbols
- Shopify Polaris Icons
- Simple Icons
- Simple Line Icons
- Streamline
- SVG Repo
- Tabler Icons
- Teenyicons
- The Noun Project
- Thin Icons
- UIkit Icons
- Untitled UI Icons
- Vaadin Icons
- Visual Studio Image Library
- VS Code Icons
- Web Awesome
- Webfont Icons
- Windows UI Icons
- Wing Icons
- WordPress Dashicons
- Zondicons
- Zurb Foundation Icon Fonts
How to narrow a long list quickly
Rather than reviewing every library in depth, make a short list based on the constraints that are hardest to change later. For example, a React application may prioritize maintained component packages; a native Apple app may begin with SF Symbols; a product that needs technology and social logos may look at a brand-focused source such as Simple Icons or Devicon.
Then test candidates with a small, representative interface. Pick eight to twelve symbols that cover navigation, actions, objects, status, and empty states. Place them at the actual sizes used in the product. This reveals issues that catalog pages can hide: thin strokes may disappear at small sizes, a filled style may feel too heavy in a toolbar, or an otherwise appealing set may lack an important symbol.
Use icons as part of a system
Once a team chooses a direction, define a few operating rules: which size scale is allowed, whether icons sit beside text labels, when filled variants communicate state, and how custom icons will match the base set. Keep the source SVGs or component references centralized rather than copying exports screen by screen. That makes later replacement, color updates, and accessibility reviews much easier.
For AI-assisted product work, a written icon policy is also useful context. It helps AI employees and human collaborators produce interface drafts that use the same vocabulary, rather than mixing symbols from unrelated styles. The goal is not to make every icon identical; it is to make product meaning predictable for the people using it.