What format should I share an icon set in for client review?

A labelled PNG grid at 2× is the most reviewable format. It lets clients see the full set in context, compare icons against each other, and reference specific icons by name or number. A ZIP of SVG files is the right developer handoff — it's a bad review format because clients can't open SVGs reliably in a browser and can't see the set as a whole. For a large set (60+ icons), split the grid by category before exporting so no single image is too dense to read on a phone screen.

How do I stop clients from giving vague feedback like 'make them more modern'?

Vague feedback on icon sets almost always means the client can't pinpoint which icon they're reacting to. Two fixes: label every icon so they can reference it by name, and give them a way to click the exact icon and pin a note there. When a client can click icon 12 and write 'the stroke feels thicker than the others,' that's an actionable note. When they have to describe it in an email, you get 'some of the icons look a bit heavy' — which requires a whole round of clarification before you can make a change.

Can a client comment on an icon set without a Figma account?

Not in Figma — leaving a comment requires a login. For a non-designer client, export the icon grid as a PNG or PDF and share it via a browser-based review tool that allows guest commenting. They click the exact icon, leave a note pinned to it, and you see the feedback in context without an account prompt blocking the way.

How many rounds of revisions are normal for an icon set?

Two structured rounds is standard: the first round covers concept and style direction across the full set, the second covers per-icon refinements to the approved direction. Sets with unclear brief alignment or vague initial feedback regularly run to four or five rounds. The single biggest predictor of round count isn't the number of icons — it's whether feedback in round one was specific enough to close the direction question. Labelled exports and pinned annotation keep round one tight.

How do I get feedback on icon consistency specifically?

Ask alongside the export: 'Do any icons feel visually heavier or lighter than the rest?' This focuses the client's eye on optical weight without requiring design vocabulary. Pair it with a side-by-side at two sizes (24px and 48px) — inconsistencies invisible at one size often become obvious at another. A tight grid with all icons at the same frame size makes weight differences easier to spot than a free-form layout.

How do I handle feedback from multiple stakeholders on an icon set?

Give all reviewers one link and make it the only place for notes. When the PM, marketing lead, and founder each send separate Slack messages or emails, you're reconciling three sources of truth before you touch a single icon. When all three comment on the same image at the same URL, conflicts are visible — 'I like the outline style' next to 'can we try filled?' is a decision to resolve in the thread, not a contradiction you discover mid-revision.

drafty

How to get feedback on an icon set

Quick answer

To get useful feedback on an icon set, export the icons as a labelled grid — not a ZIP of individual SVGs — so your client can see every icon at once and reference them by name. Then give them a way to click the exact icon they mean and pin a note right there, rather than describing it in an email. Icon sets are the hardest deliverable to get feedback on because 'the one that looks a bit heavy' could be any of 48 icons. Annotation eliminates that ambiguity before the first round of revisions.

Step 1

Export a labelled preview grid, not individual SVG files

A ZIP of SVGs is the right handoff format for a developer. It is a terrible review format for a client. Export the full set as a PNG grid in Figma — select the icon frame, export at 2× with labels on, and number any icons that don't have a natural name. The goal: your client opens one image and can say 'icon 14, the arrow one' instead of 'the one that feels heavy — not the circular ones, the pointed one.' Show the icons at two sizes (24px and 48px); a stroke that reads fine at 48px can disappear at 16px, and your client is the one who catches that mismatch first.

Step 2

Ask one consistency question and one usage question per round

Open feedback ('what do you think?') produces one of two useless answers: 'looks great!' or 'can you make them more modern?' Neither tells you which icons to change. Ask two questions instead. Consistency: 'Do any icons feel visually heavier or lighter than the rest?' — this trains the client's eye on optical weight without requiring design vocabulary. Usage: 'Are there any actions or states in the product with no obvious icon here?' — this surfaces gaps before handoff, not in a developer review six weeks later. Two targeted questions per round close faster than open feedback every time.

Step 3

Share a Figma view link for tech-comfortable stakeholders

If your client is a product manager or designer, a Figma view link ('Anyone with the link can view') works well — they can inspect stroke widths and compare icons without downloading files. The gap: leaving a comment requires a Figma account. Any non-designer stakeholder — the marketing lead, the founder, the comms manager who will use these icons in decks — hits the login prompt and emails you instead. One missing decision-maker outside the thread means you discover their conflicting opinion mid-revision. Worth checking who your reviewers are before you send the Figma link.

Step 4

Share a review link they can annotate without an account

The most reliable method for a mixed-seniority review group: export the labelled grid as a PNG or PDF, share it through a browser-based review tool, and send one URL. Every reviewer — the designer, the PM, the founder, the brand manager — opens the same image in their browser, clicks the exact icon they mean, and pins a note to it. No Figma account, no extension, works on a phone. 'The lock icon — stroke is too heavy' lands anchored to the lock icon, not buried in a reply-all email. When two reviewers leave conflicting notes on the same icon, you see the conflict in one thread instead of discovering it three days later when you're halfway through revisions. Each new version replaces the previous one at the same URL, so there is no v3_FINAL_revised_2.png to track.

The faster way

If you're collecting sign-off on an icon set — not annotating it yourself — export the grid as a PNG and drop it into Drafty. Share the link. Your client clicks the exact icon they mean — the lock, the arrow, the one with the slightly heavy stroke — and pins a note right there. No Figma account required. You reply, resolve it, push the next version to the same URL. Feedback stays in one place instead of split across iMessage, email, and a Slack thread.

Open a live demo

Questions

What format should I share an icon set in for client review?: A labelled PNG grid at 2× is the most reviewable format. It lets clients see the full set in context, compare icons against each other, and reference specific icons by name or number. A ZIP of SVG files is the right developer handoff — it's a bad review format because clients can't open SVGs reliably in a browser and can't see the set as a whole. For a large set (60+ icons), split the grid by category before exporting so no single image is too dense to read on a phone screen.
How do I stop clients from giving vague feedback like 'make them more modern'?: Vague feedback on icon sets almost always means the client can't pinpoint which icon they're reacting to. Two fixes: label every icon so they can reference it by name, and give them a way to click the exact icon and pin a note there. When a client can click icon 12 and write 'the stroke feels thicker than the others,' that's an actionable note. When they have to describe it in an email, you get 'some of the icons look a bit heavy' — which requires a whole round of clarification before you can make a change.
Can a client comment on an icon set without a Figma account?: Not in Figma — leaving a comment requires a login. For a non-designer client, export the icon grid as a PNG or PDF and share it via a browser-based review tool that allows guest commenting. They click the exact icon, leave a note pinned to it, and you see the feedback in context without an account prompt blocking the way.
How many rounds of revisions are normal for an icon set?: Two structured rounds is standard: the first round covers concept and style direction across the full set, the second covers per-icon refinements to the approved direction. Sets with unclear brief alignment or vague initial feedback regularly run to four or five rounds. The single biggest predictor of round count isn't the number of icons — it's whether feedback in round one was specific enough to close the direction question. Labelled exports and pinned annotation keep round one tight.
How do I get feedback on icon consistency specifically?: Ask alongside the export: 'Do any icons feel visually heavier or lighter than the rest?' This focuses the client's eye on optical weight without requiring design vocabulary. Pair it with a side-by-side at two sizes (24px and 48px) — inconsistencies invisible at one size often become obvious at another. A tight grid with all icons at the same frame size makes weight differences easier to spot than a free-form layout.
How do I handle feedback from multiple stakeholders on an icon set?: Give all reviewers one link and make it the only place for notes. When the PM, marketing lead, and founder each send separate Slack messages or emails, you're reconciling three sources of truth before you touch a single icon. When all three comment on the same image at the same URL, conflicts are visible — 'I like the outline style' next to 'can we try filled?' is a decision to resolve in the thread, not a contradiction you discover mid-revision.

Keep exploring

How to get feedback on a logo How to get feedback on a brand identity Design feedback tool How to get feedback on a Figma design

Stop emailing files back and forth.

Share one link. They comment on the exact spot — no account, always the current version.

Open a live demo