A comprehensive collection of 2,500+ optimized SVG icons for cryptocurrencies, networks, wallets, and exchanges, available as React components.
Web3 Icons is an open-source icon library specifically designed for the web3 ecosystem. It provides over 2,500 optimized SVG icons for cryptocurrencies, blockchain networks, wallets, and exchanges. The project solves the problem of fragmented and inconsistent icon sourcing for developers building blockchain-related applications by offering a single, comprehensive, and well-maintained collection.
Frontend and full-stack developers building cryptocurrency exchanges, wallets, dashboards, DeFi applications, or any web3 interface that requires displaying token logos, network badges, or wallet icons.
Developers choose Web3 Icons for its unparalleled comprehensiveness, hand-curated quality, and developer-friendly delivery as tree-shakable React components and optimized SVGs. It saves significant time compared to manually collecting and maintaining icon assets from various sources.
2000+ crypto svg icons for react
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
With over 2,500 hand-curated icons covering tokens, networks, wallets, and exchanges, it's the most extensive library specifically for the web3 space, as highlighted in the badges and metadata.
Most icons come in mono, branded, and background variants, allowing developers to maintain consistent styling across different UI contexts without manual editing.
Tree-shakable React components ensure only imported icons are included in the bundle, minimizing performance impact for static usage.
Dynamic components like TokenIcon and NetworkIcon provide easy runtime loading based on symbols or addresses, though with trade-offs noted in the README.
Dynamic components are explicitly client-side only and not tree-shakable, making them unsuitable for SSR-heavy applications like Next.js with server components.
While React components are well-supported, other frameworks like Vue or Angular only get raw SVGs via the core package, requiring extra integration effort.
Using dynamic components can increase bundle size since they load icons at runtime without tree-shaking, a trade-off the README admits for convenience.