A universal icon framework providing a unified syntax for over 200,000 icons from 150+ open-source icon sets.
Iconify is a universal icon framework that provides a single syntax for accessing over 200,000 icons from more than 150 open-source icon sets. It solves the problem of managing multiple icon libraries by offering on-demand icon loading through an API and components for popular frontend frameworks. This allows developers to use icons from sets like FontAwesome, Material Design Icons, and Feather Icons without bundling all icon data upfront.
Frontend developers building web applications with React, Vue, Svelte, or other modern frameworks, as well as designers using tools like Figma, Sketch, or Adobe XD who need a consistent icon workflow.
Developers choose Iconify for its massive icon collection, framework-agnostic approach, and efficient on-demand loading, which eliminates the need to manually manage and bundle icon assets. Its unified syntax and design tool integrations streamline icon usage across both development and design teams.
Universal icon framework. One syntax for FontAwesome, Material Design Icons, DashIcons, Feather Icons, EmojiOne, Noto Emoji and many other open source icon sets (over 150 icon sets and 200k icons). SVG framework, React, Vue and Svelte components!
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Integrates over 200 icon sets with 250,000+ icons, eliminating the need to manage multiple dependencies for diverse icon needs.
Provides a web component and native components for React, Vue, and Svelte, with wrappers for frameworks like SolidJS and Next.js, ensuring broad compatibility.
Icons are fetched only when needed from the Iconify API, reducing initial bundle size and improving performance by avoiding upfront bundling.
Plugins for Figma, Sketch, and Adobe XD enable seamless icon usage from design to development, streamlining team workflows.
Relies on the Iconify API for on-demand icon loading, which can introduce latency, single points of failure, and requires internet connectivity.
Older native components like the React component are being phased out in favor of web components, forcing users to migrate and potentially causing disruption.
Frameworks like Nuxt 3 require custom configuration (e.g., compiler options) to use the web component, adding overhead and potential for errors.