iconLintIcon Set Audit

Drop a folder of SVG icons and get back everything that makes a developer wince: mixed stroke widths, hardcoded colours, duplicate ids, editor leftovers, rogue sizes. Every icon is checked against the rest of the set, not just against a rulebook. Nothing leaves your browser.

Drop SVG icons here

A whole folder is fine. Or ·

What gets checked

Set-level checks compare each icon with the majority. Icon-level checks are the things that break when an SVG is inlined next to fifty others.

  • Set: viewBox size, stroke width (normalised to a 24 grid), stroked vs filled style, artwork extent inside the viewBox, colour handling, file naming, and ids that repeat across files.
  • Icon: missing viewBox, embedded raster images, live text, scripts, hidden or empty elements, artwork outside the viewBox, hardcoded black instead of currentColor, <style> blocks with generic class names, and editor leftovers from Illustrator, Sketch, Figma and Inkscape.
  • Not checked yet: pixel-grid alignment and optical weight. Those are next.

Questions people ask

What does "checked against the set" mean?
Instead of a fixed rulebook, each icon is compared with what most of the set does. If 40 icons use a 1.5 stroke on a 24 grid and two use 2, the two are flagged. If everything uses 2, nothing is.
Why does it care about duplicate ids?
Illustrator and Figma export ids like "a" or "clip0" in every file. Inline two of those icons on one page and their clip-paths and gradients cross-wire. It is one of the hardest icon bugs to spot, and one of the easiest to catch here.
Can I run this in CI?
Yes. The same checks are in the iconlint command-line tool and GitHub Action, so a pull request can fail when an icon does not match the set.