google/material-design-icons
Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.
google/material-design-icons
Official Google repository for Material Symbols and classic Material Icons: a large, active icon asset source rather than an application codebase. It is widely used and heavily forked, with frequent updates to Symbols and multiple distribution formats.
Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.
Choose a fork to inspect
Choose this fork only if you specifically need the older 2023-era state. For active use, upstream is a better choice because this fork has no added capabilities and is significantly behind current icon updates.
Choose this fork only if you specifically want an older pinned copy of Google’s icon assets. If you need current Material Symbols or an actively maintained distribution, upstream is the better choice.
Choose this fork only if you specifically need the PDF-packaged legacy icon workflow it provides. If you want current Material Symbols, modern asset formats, or ongoing upstream updates, upstream is the better choice.
Prefer this fork only if you explicitly need an old, frozen copy. If you want current Material Symbols or ongoing updates, upstream is the better choice.
Prefer upstream unless you specifically need a frozen copy or plan to maintain the fork yourself; this fork adds no visible value and is already behind.
Prefer this fork only if you want an older, stable copy of the official icon set. If you need current Material Symbols or ongoing upstream parity, the upstream repository is the better choice.
Prefer the upstream repo for anything current. Use this fork only if you specifically want a frozen copy and are comfortable missing recent Material Symbols updates.
Prefer this fork only if you want a frozen snapshot. If you need current Google Material Symbols assets or ongoing updates, upstream is the better choice.
Prefer this fork only for legacy SVG-only/Bower workflows. For any active project, upstream is the safer choice because this fork is extremely stale and omits the current Material Symbols distribution.