{"course":{"slug":"design-foundations","title":"Design, before Any Software","url":"https://addaly.com/learn/design-foundations","level":"beginner","track":"create"},"lesson":{"slug":"icons-as-a-system","title":"Icons are a set, not a collection","url":"https://addaly.com/learn/design-foundations/icons-as-a-system","position":70,"of":74,"minutes":8,"answer":"Use one icon set, because mismatched grids, stroke weights and detail levels are visible even when nobody can name them, and label icons wherever there is room.","keyIdea":"Use one icon set, because mismatched grids, stroke weights and detail levels are visible even when nobody can name them, and label icons wherever there is room, since comprehension without a label is poor for everything outside a small well-learned set."},"body":{"format":"markdown","text":"## Why mixed icons look wrong\n\nDownload three icons from three sources and put them in a row. They will not match, and the mismatch will be visible to people who cannot name any of the reasons.\n\nThe reasons are specific and measurable:\n\n- **Different grids.** One set is drawn on 24 pixels, another on 20, another on 16 and scaled up.\n- **Different stroke weights.** 1.5px against 2px is a visible difference in apparent weight.\n- **Different corner treatments.** Rounded caps and joins against square ones.\n- **Different levels of detail.** One set draws a camera with a lens and a flash, another with a rectangle and a circle.\n- **Different optical sizing.** One set lets a circle exceed the nominal grid so it looks the same size as a square; another does not.\n\nUse one set. This is the single decision that makes an interface's icons look designed rather than assembled, and it costs nothing.\n\n## The grid and the stroke\n\nThe common convention is a 24 × 24 grid with a 20 × 20 live area, leaving 2 pixels of padding on each side, and a 2-pixel stroke. At 16 pixels the stroke usually drops to 1.5.\n\nTwo consequences worth knowing:\n\n**Optical size overrides the grid.** As covered in the alignment lesson, a circle drawn to exactly 20 pixels looks smaller than a square drawn to exactly 20 pixels. Well-made sets let round shapes exceed the live area by a few per cent. If you draw your own icons, do the same, and judge by eye rather than by the guide.\n\n**Stroke weight should relate to the text it sits beside.** A 1px icon next to 600-weight text looks anaemic. The icon's apparent weight should be close to the stem weight of the accompanying type, which usually means 1.5 to 2 pixels at body size and heavier beside a bold label.\n\n## Free sets worth knowing\n\nAll of these are free for commercial use, and all are permissively licensed, but check for yourself rather than taking this list on trust, because licences change.\n\n- **Lucide**: a community fork of Feather, ISC licence, clean and consistent.\n- **Phosphor**: MIT, six weights including a filled variant, unusually large.\n- **Material Symbols**: Apache 2.0, a variable font with weight, fill and optical size axes.\n- **Tabler Icons**: MIT, very large set on a consistent grid.\n- **Remix Icon**: Apache 2.0, includes line and fill pairs.\n- **Bootstrap Icons**: MIT.\n\nOne caution that catches people out: several popular sets described as free carry attribution requirements. Font Awesome's free icons are licensed under CC BY 4.0, which requires attribution. That is a mild condition and it is still a condition, and it applies to work you hand a client.\n\n## Delivering them\n\n**Inline SVG** is usually correct: it can inherit `currentColor`, it can be styled by CSS, and it adds no network request.\n\n```html\n<svg width=\"24\" height=\"24\" viewBox=\"0 0 24 24\" fill=\"none\"\n     stroke=\"currentColor\" stroke-width=\"2\" aria-hidden=\"true\">\n  <path d=\"M5 12h14M12 5l7 7-7 7\"/>\n</svg>\n```\n\n`stroke=\"currentColor\"` is the important part: the icon takes the colour of the surrounding text automatically, including in dark mode and in every state.\n\n**Icon fonts** were the standard approach for years and have real problems: they fail in a specific and ugly way when the font does not load, screen readers sometimes announce the private-use character, and they cannot be multicoloured. They still work, and there is rarely a reason to choose one now.\n\n## Icons are rarely self-explanatory\n\nThis is the honest part, and it contradicts a lot of practice.\n\nStudies of icon comprehension consistently find that recognition without a label is poor for most icons. A small set is well understood across populations: a magnifier for search, a house for home, a printer, a play triangle, a rubbish bin for delete, a plus for add. Beyond that, comprehension falls off quickly, and icons for abstract concepts such as settings, share, filter or archive are guessed rather than known, with the guesses varying by platform and by age.\n\nThe common hamburger menu is the frequently cited case: it is now widely learned, and studies through the 2010s repeatedly found that labelling it Menu improved discovery.\n\nThe design conclusion:\n\n1. **Label icons wherever there is room.** Icon plus text beats either alone.\n2. **Where an icon must stand alone**, it needs an accessible name regardless (`aria-label` on the button) because a screen reader announces nothing for an unlabelled glyph.\n3. **Decorative icons beside text get `aria-hidden=\"true\"`**, so the label is not announced twice.\n4. **Do not invent an icon for an abstract concept** and expect it to be understood. It will not be."},"check":{"question":"An interface uses icon-only buttons throughout, with tooltips on hover giving each one's name. A usability test finds users guessing wrong about several. The team's proposal is to redesign the icons to be clearer. Why is this unlikely to work?","options":[{"text":"Recognition without a label is poor for abstract concepts whatever the drawing, so a clearer icon does not produce a shared meaning.","correct":true},{"text":"The tooltips are the real problem, since they require hover and are unreachable on touch, so moving them to persistent text beside each icon resolves the comprehension issue.","correct":false,"tempting":"Identifies the right remedy for the wrong reason, treating reachability of the tooltip as the cause rather than the absence of a visible label."},{"text":"The icons were probably drawn on inconsistent grids with mismatched stroke weights, and the resulting visual inconsistency is what users are struggling to interpret.","correct":false,"tempting":"Applies the set-consistency point, which governs whether icons look coherent rather than whether their meaning is understood."},{"text":"Icon-only buttons lack accessible names, so assistive technology announces nothing and the test participants using it had no information to work from at all.","correct":false,"tempting":"Raises a genuine and separate defect that would not explain sighted users guessing wrong about what an icon means."}]},"prev":{"slug":"states-are-part-of-the-component","title":"Every state you did not draw still ships","url":"https://addaly.com/learn/design-foundations/states-are-part-of-the-component"},"next":{"slug":"a-system-you-can-build-in-a-day","title":"The afternoon version","url":"https://addaly.com/learn/design-foundations/a-system-you-can-build-in-a-day"},"authorship":"Founder and series editor: Dr Mustafa Mun. Written by AI models to a written standard. Source and assessment review continues. Academic review invited.","review":{"status":"Draft, open for academic review"},"cite":"Addaly (2026) 'Icons are a set, not a collection', in Design, before Any Software. Edited by M. Mun. Addaly. Available at: https://addaly.com/learn/design-foundations/icons-as-a-system (Accessed: 21 November 2026).","licence":{"name":"CC BY-NC-SA 4.0","url":"https://creativecommons.org/licenses/by-nc-sa/4.0/"},"reader":{"schema":1,"title":"Icons are a set, not a collection","courseTitle":"Design, before Any Software","module":{"index":7,"slug":"making-decisions-once","title":"Making the decision once"},"answer":null,"keyIdea":"Use one icon set, because mismatched grids, stroke weights and detail levels are visible even when nobody can name them, and label icons wherever there is room, since comprehension without a label is poor for everything outside a small well-learned set.","hero":{"kind":"plate","image":null,"alt":null,"caption":null},"blocks":[{"t":"h2","id":"why-mixed-icons-look-wrong","runs":[{"text":"Why mixed icons look wrong"}]},{"t":"p","runs":[{"text":"Download three icons from three sources and put them in a row. They will not match, and the mismatch will be visible to people who cannot name any of the reasons."}]},{"t":"p","runs":[{"text":"The reasons are specific and measurable:"}]},{"t":"ul","items":[[{"text":"Different grids.","b":true},{"text":" One set is drawn on 24 pixels, another on 20, another on 16 and scaled up."}],[{"text":"Different stroke weights.","b":true},{"text":" 1.5px against 2px is a visible difference in apparent weight."}],[{"text":"Different corner treatments.","b":true},{"text":" Rounded caps and joins against square ones."}],[{"text":"Different levels of detail.","b":true},{"text":" One set draws a camera with a lens and a flash, another with a rectangle and a circle."}],[{"text":"Different optical sizing.","b":true},{"text":" One set lets a circle exceed the nominal grid so it looks the same size as a square; another does not."}]]},{"t":"p","runs":[{"text":"Use one set. This is the single decision that makes an interface’s icons look designed rather than assembled, and it costs nothing."}]},{"t":"h2","id":"the-grid-and-the-stroke","runs":[{"text":"The grid and the stroke"}]},{"t":"p","runs":[{"text":"The common convention is a 24 × 24 grid with a 20 × 20 live area, leaving 2 pixels of padding on each side, and a 2-pixel stroke. At 16 pixels the stroke usually drops to 1.5."}]},{"t":"p","runs":[{"text":"Two consequences worth knowing:"}]},{"t":"p","runs":[{"text":"Optical size overrides the grid.","b":true},{"text":" As covered in the alignment lesson, a circle drawn to exactly 20 pixels looks smaller than a square drawn to exactly 20 pixels. Well-made sets let round shapes exceed the live area by a few per cent. If you draw your own icons, do the same, and judge by eye rather than by the guide."}]},{"t":"p","runs":[{"text":"Stroke weight should relate to the text it sits beside.","b":true},{"text":" A 1px icon next to 600-weight text looks anaemic. The icon’s apparent weight should be close to the stem weight of the accompanying type, which usually means 1.5 to 2 pixels at body size and heavier beside a bold label."}]},{"t":"h2","id":"free-sets-worth-knowing","runs":[{"text":"Free sets worth knowing"}]},{"t":"p","runs":[{"text":"All of these are free for commercial use, and all are permissively licensed, but check for yourself rather than taking this list on trust, because licences change."}]},{"t":"ul","items":[[{"text":"Lucide","b":true},{"text":": a community fork of Feather, ISC licence, clean and consistent."}],[{"text":"Phosphor","b":true},{"text":": MIT, six weights including a filled variant, unusually large."}],[{"text":"Material Symbols","b":true},{"text":": Apache 2.0, a variable font with weight, fill and optical size axes."}],[{"text":"Tabler Icons","b":true},{"text":": MIT, very large set on a consistent grid."}],[{"text":"Remix Icon","b":true},{"text":": Apache 2.0, includes line and fill pairs."}],[{"text":"Bootstrap Icons","b":true},{"text":": MIT."}]]},{"t":"p","runs":[{"text":"One caution that catches people out: several popular sets described as free carry attribution requirements. Font Awesome’s free icons are licensed under CC BY 4.0, which requires attribution. That is a mild condition and it is still a condition, and it applies to work you hand a client."}]},{"t":"h2","id":"delivering-them","runs":[{"text":"Delivering them"}]},{"t":"p","runs":[{"text":"Inline SVG","b":true},{"text":" is usually correct: it can inherit "},{"text":"currentColor","code":true},{"text":", it can be styled by CSS, and it adds no network request."}]},{"t":"code","lang":"html","label":"HTML","text":"<svg width=\"24\" height=\"24\" viewBox=\"0 0 24 24\" fill=\"none\"\n     stroke=\"currentColor\" stroke-width=\"2\" aria-hidden=\"true\">\n  <path d=\"M5 12h14M12 5l7 7-7 7\"/>\n</svg>"},{"t":"p","runs":[{"text":"stroke=\"currentColor\"","code":true},{"text":" is the important part: the icon takes the colour of the surrounding text automatically, including in dark mode and in every state."}]},{"t":"p","runs":[{"text":"Icon fonts","b":true},{"text":" were the standard approach for years and have real problems: they fail in a specific and ugly way when the font does not load, screen readers sometimes announce the private-use character, and they cannot be multicoloured. They still work, and there is rarely a reason to choose one now."}]},{"t":"h2","id":"icons-are-rarely-self-explanatory","runs":[{"text":"Icons are rarely self-explanatory"}]},{"t":"p","runs":[{"text":"This is the honest part, and it contradicts a lot of practice."}]},{"t":"p","runs":[{"text":"Studies of icon comprehension consistently find that recognition without a label is poor for most icons. A small set is well understood across populations: a magnifier for search, a house for home, a printer, a play triangle, a rubbish bin for delete, a plus for add. Beyond that, comprehension falls off quickly, and icons for abstract concepts such as settings, share, filter or archive are guessed rather than known, with the guesses varying by platform and by age."}]},{"t":"p","runs":[{"text":"The common hamburger menu is the frequently cited case: it is now widely learned, and studies through the 2010s repeatedly found that labelling it Menu improved discovery."}]},{"t":"p","runs":[{"text":"The design conclusion:"}]},{"t":"ol","start":1,"items":[[{"text":"Label icons wherever there is room.","b":true},{"text":" Icon plus text beats either alone."}],[{"text":"Where an icon must stand alone","b":true},{"text":", it needs an accessible name regardless ("},{"text":"aria-label","code":true},{"text":" on the button) because a screen reader announces nothing for an unlabelled glyph."}],[{"text":"Decorative icons beside text get ","b":true},{"text":"aria-hidden=\"true\"","b":true,"code":true},{"text":", so the label is not announced twice."}],[{"text":"Do not invent an icon for an abstract concept","b":true},{"text":" and expect it to be understood. It will not be."}]]}],"check":{"question":[{"text":"An interface uses icon-only buttons throughout, with tooltips on hover giving each one’s name. A usability test finds users guessing wrong about several. The team’s proposal is to redesign the icons to be clearer. Why is this unlikely to work?"}],"options":[{"text":[{"text":"Recognition without a label is poor for abstract concepts whatever the drawing, so a clearer icon does not produce a shared meaning."}],"correct":true,"tempting":null},{"text":[{"text":"The tooltips are the real problem, since they require hover and are unreachable on touch, so moving them to persistent text beside each icon resolves the comprehension issue."}],"correct":false,"tempting":[{"text":"Identifies the right remedy for the wrong reason, treating reachability of the tooltip as the cause rather than the absence of a visible label."}]},{"text":[{"text":"The icons were probably drawn on inconsistent grids with mismatched stroke weights, and the resulting visual inconsistency is what users are struggling to interpret."}],"correct":false,"tempting":[{"text":"Applies the set-consistency point, which governs whether icons look coherent rather than whether their meaning is understood."}]},{"text":[{"text":"Icon-only buttons lack accessible names, so assistive technology announces nothing and the test participants using it had no information to work from at all."}],"correct":false,"tempting":[{"text":"Raises a genuine and separate defect that would not explain sighted users guessing wrong about what an icon means."}]}],"order":[1,0,2,3],"why":null},"prev":{"slug":"states-are-part-of-the-component","title":"Every state you did not draw still ships","minutes":9},"next":{"slug":"a-system-you-can-build-in-a-day","title":"The afternoon version","minutes":8}}}