Angular has fewer first-party icon packages, so most teams use an aggregator or inline SVG.
| Library | Icons | Variants | Grid | License | Package |
|---|---|---|---|---|---|
| Material Design Icons | 14,001 | outlined, rounded, sharp, two-tone and filled | 24×24 | Apache 2.0 | @mui/icons-material |
| Carbon Icons | 2,644 | outline only | 32×32 | Apache 2.0 | @carbon/icons-react |
| Fluent UI Icons | 20,170 | regular and filled | 12–48 | MIT | @fluentui/react-icons |
| Ionicons | 2,607 | outline, filled and sharp | 24×24 | MIT | ionicons |
Material Icons and Carbon both ship official Angular components. For anything else, inlining the SVG from IconStash into a template is reliable and adds no build weight.
For most Angular projects, start with
Material Design Icons — 14,001 icons,
outlined, rounded, sharp, two-tone and filled, Apache 2.0 licensed, installed as
@mui/icons-material. Move to
Carbon Icons if you need
outline only instead.
Material Design Icons is the safest default: 14,001 icons, Apache 2.0 licensed, and a first-party package. Material Icons and Carbon both ship official Angular components. For anything else, inlining the SVG from IconStash into a template is reliable and adds no build weight.
Only if you import the whole set. Every library here tree-shakes, so bundling ten named icon exports ships ten icons. Watch for barrel imports like import * as Icons from "...", which defeat that.
Yes, and for small numbers of icons it is often better — no dependency, no version drift, and full control over attributes. Export any icon from IconStash as an inline SVG or a downloadable file and paste it straight in.