Say you are trying to ship a 200-icon set by Friday, and three days in you notice that some icons sit slightly off-center in their frames while others line up perfectly. Nobody changed anything on purpose. The set just drifted, the way icon sets always seem to when enough people touch them over enough weeks. This post is built around that kind of moment — a visible symptom, a root cause you have to dig for, and a plugin-shaped fix — rather than a straight list of tools.
Treat it like a troubleshooting guide. Find the symptom that matches what you’re looking at, skip to that section, and move on.
Symptom: Icons Look Slightly “Off” Next to Each Other, But You Can’t Say Why
You place two icons side by side. Something is wrong. The stroke on one looks thicker. Maybe the padding is different. Maybe it’s the corner radius on the containing frame. You stare for a while and still can’t pin it down precisely.
Cause: This is almost always a sizing or padding inconsistency that’s too small to spot by eye but large enough to register as “wrong” once icons sit next to their peers. A 1-2px difference in internal padding across a 24x24 frame is invisible in isolation and obvious in a grid.
Fix: Run an auto-layout/sizing checker plugin across the full set before you consider anything finished. These plugins compare frame dimensions, padding, and layout configuration across a batch and flag outliers automatically. This catches drift that casual visual review reliably misses, because your eyes adapt to gradual inconsistency the same way they adapt to a slightly tilted picture frame you’ve walked past for a month.
Symptom: Stroke-Based Icons Look Inconsistent Even Though the Fills Are Fine
Your icon set uses outlined strokes rather than filled shapes, and something about the line weight feels uneven across icons — even though each individual icon looks fine on its own.
Cause: Stroke width and cap/join treatment are easy to set inconsistently, especially when icons were drawn at different times or by different people. A 1.5px stroke next to a 2px stroke reads as a real difference once you’re looking at a full set rather than one icon at a time.
Fix: Use a dedicated stroke and path consistency plugin rather than trying to eyeball corrections one icon at a time. These tools check stroke width and join/cap treatment across a selection and can correct mismatches in bulk. General design consistency plugins aren’t built with this specific stroke-level check in mind, so this is a case where a narrow, purpose-built tool genuinely outperforms a broad one.
Symptom: You Keep Redrawing Icons That Already Exist Somewhere
You need a settings gear, a search icon, a chevron. You draw it. Later you realize a teammate already drew nearly the same thing three weeks ago, in a slightly different style, sitting in a file nobody remembers to check.
Cause: Standard interface icons get redrawn constantly because there’s no default habit of checking an existing library first. This is duplicated effort on a problem that’s already been solved many times over, in libraries that are well-maintained and free to use.
Fix: Reach for a plugin like Iconify before drawing anything standard from scratch. It gives you searchable access to a large number of established open-source icon libraries directly inside Figma — search, insert, done. Save custom drawing time for icons that need brand-specific distinctiveness; let the library handle the search icon.
Symptom: Exporting the Full Set Takes Longer Than Designing It Did
You finish the icon set. Now you need SVG for the web build, three PNG resolutions for mobile, and a couple of platform-specific formats besides. Figma’s standard export panel handles this, technically, but one icon at a time, or in small batches, and the process eats an entire afternoon.
Cause: Standard export tooling wasn’t built with large, multi-format icon sets in mind. It works fine for a handful of assets and becomes a bottleneck once you’re dealing with a real-sized library across several output formats.
Fix: A bulk export plugin lets you select the entire set once and export every required format and size in a single pass. The gap between this and manual batch export widens considerably as your icon count grows — the difference is barely noticeable at 10 icons and hard to ignore at 200.
Symptom: Nobody Can Find the Right Icon Anymore
The library has grown past the point where anyone can scroll through and locate what they need. Naming is inconsistent — some icons use camelCase, some use hyphens, a few have no descriptive name at all. New team members ask where things are more often than they should have to.
Cause: Naming conventions that worked fine for 20 icons stop working at 200. Without enforced structure, an icon library grows organically into something unsearchable, and the cost shows up as wasted time rather than a visible design flaw.
Fix: Use a bulk renaming plugin to apply a consistent naming pattern retroactively, and pair it with an organizational plugin that groups icons into categorized structures. This is less glamorous than the stroke-consistency or export fixes above, but it’s often the one that saves the most collective time across a team, week after week.
Symptom: A Generic Icon Set Feels Wrong for This Specific Product
You pulled standard icons from a library, and the set works, but it doesn’t feel like it belongs to your product. Reviewers can’t always articulate why — it just reads as generic.
Cause: Standard library icons are built for broad applicability, not brand distinctiveness. That’s the entire point of a shared library, and it’s also the exact reason a fully library-sourced set can feel undifferentiated once a brand identity is meant to come through.
Fix: This isn’t a plugin problem so much as a decision point. Keep library icons for standard, non-differentiated concepts — navigation, settings, common actions — and reserve custom design time for icons where brand distinctiveness genuinely matters to how the product feels. A hybrid approach outperforms both extremes: building everything from scratch wastes effort on problems that are already solved, and relying entirely on generic libraries leaves differentiation opportunities unused.
A Troubleshooting Reference Table
| Symptom | Likely Cause | Fix |
|---|---|---|
| Icons look “off” next to each other | Sizing/padding drift | Auto-layout/sizing checker plugin |
| Stroke weight feels uneven | Inconsistent stroke width or cap/join | Stroke consistency plugin |
| Redrawing icons that already exist | No habit of checking existing libraries | Iconify or similar library-access plugin |
| Export takes longer than design | Manual, single-icon export process | Bulk export plugin |
| Nobody can find the right icon | Inconsistent naming, no categorization | Bulk renaming/organization plugin |
| Set feels generic for the product | Overreliance on standard library icons | Hybrid custom/library approach |
How to Use This Guide Going Forward
Bookmark this less as a one-time read and more as a diagnostic you return to whenever an icon set starts feeling off in some way you can’t immediately name. Most icon problems repeat themselves across projects — the same drift, the same export bottleneck, the same naming chaos six months in — so the symptom-to-fix mapping above tends to hold up project after project, not just for the one you’re working on today.
If none of these symptoms match what you’re seeing, describe the specific problem — what it looks like, when it started showing up — and it’s usually possible to trace it back to one of these root causes even when the surface symptom looks unfamiliar at first glance.