# Icon: One Shared Grid, Stroke, and Component for Every Symbol

> Learn how a design system draws icons on one grid, labels them for every user, and ships them through one reusable Icon component.

**In short:** An icon in a design system is a symbol drawn on one shared grid and stroke, labelled for every user and shipped through one reusable Icon component.

From "Design systems", a free course by Venkat R. Murty: https://designervenkat.online/learn/design-systems/icon

## Start Here

This lesson teaches the icon as it works inside a design system. An icon here is not a one-off picture. It is a shared part, drawn with the same rules as every other icon, and reused on every screen that needs it. By the end you will know how teams keep icons looking like one family, how they keep icons understandable to every user, and how they deliver icons so product teams can use them without copying files around.

Read this lesson with a product in mind. Pick any app you use every day and look at its top bar or side menu. You will see icons there, and many of the rules below explain why those icons look and behave the way they do.

- **Icon:** A small symbol that stands for an action, an object, or a state, such as a trash can for delete.
- **Design system:** A shared set of parts and rules that a team uses to build every screen the same way.
- **Grid:** An invisible square area that a designer draws inside, so every shape sits in a predictable place.
- **Stroke:** The line that draws the outline of an icon. Its thickness is the stroke weight.
- **Token:** A named design decision, such as a color or a size, stored once and reused everywhere.
- **Metaphor:** A picture that stands for an idea because it looks like something familiar, such as an envelope for mail.
- **Decorative icon:** An icon that adds no meaning beyond the text next to it.
- **Accessible name:** The short label that a screen reader speaks aloud for a control, so people who cannot see the screen know what it does.
- **SVG:** A file format that describes shapes with points and lines, so it can grow or shrink without getting blurry.
- **Component:** A reusable piece of a product that is built once and placed many times.
- **Props:** The settings you pass into a component, such as which icon to show, how big it is, and what color it takes.

## What does an icon do in a design system?

Icons give quick visual meaning. A person scanning a toolbar can often spot the right button faster from a picture than from a word. Inside a design system, though, an icon has three extra jobs. It must look like the other icons. It must be understood by people who use the product in very different ways. And it must be shipped as a shared part, not as a loose file that each designer or builder handles in their own way.

- **Quick meaning:** An icon shows what an action or state is at a glance. A bell can mean notifications, and a star can mean saved. The picture saves reading time when the screen is crowded.
- **Shared and reusable:** The same trash can icon should appear in the email list, the file list, and the settings page. One shared drawing means one place to fix a mistake.
- **Usually paired with a label:** Many icons work best next to a short text label. The label removes doubt, especially for symbols that have more than one meaning.

A design system also decides which icons exist at all. Teams usually avoid adding a new icon when an existing one already works. Every new icon adds to the set that must be kept consistent, so the set should grow only when there is a clear need.

> **Tip:** Before you draw a new icon, search the existing set. If a shared icon already matches the action, reuse it. A small set that everyone knows is easier to read than a large set full of near-duplicates.

## How do you make icons look like one family?

Consistency is the first goal. If one icon has thick rounded lines and the next has thin sharp lines, the screen looks messy, even when each icon is clear on its own. A design system fixes a few core choices and applies them to every icon in the set.

- **Shared grid:** Every icon is drawn inside the same square box. Keeping the box the same means the shapes line up when they sit side by side.
- **Shared size scale:** The system names a few sizes, not a random size for each use. The rules below show the common choices.
- **Shared stroke weight:** All the lines in the set share one thickness, so no icon looks heavier than its neighbors.
- **Shared corners and color tokens:** The corner style and the color come from the same named decisions, so the set reads as one style across light and dark screens.

The rules below explain each of these choices. Each one is a setting a designer can check, which is why a written guideline matters. Without written rules, the style slowly drifts as different people add icons over time.

Grid and size scale

Material Design draws its standard system icons at 24dp, the density-independent unit it uses for size. Some systems pick 16px as their default for interface icons. The exact number matters less than picking one scale and using only those sizes.

Inside the grid, designers usually leave a margin of padding. The margin stops icons from crowding the edges of the button or the next element.

Stroke weight and corners

Its guidance also asks for squared stroke ends and says to avoid mixing thicknesses. The lesson is that one value is chosen and kept.

Stroke size does not scale on its own in a fixed way. Teams that show icons at more than one size may adjust the stroke for each size, but they still keep the same weight across the set at each size.

> **Tip:** Place every line on the pixel grid where you can. Blurry edges are a common sign of a rushed icon.

Color tokens

Icons should take their color from named color tokens, not from a single hard-coded value. A token such as a primary text color or a danger color can change for dark mode or for a brand theme without redrawing any icon. This keeps the icon family consistent in every theme, and it stops one designer from picking a slightly different gray.

Keep one style for the whole set. Teams often choose outline or filled, and they may use filled shapes only for status icons. A team should write its choice down so that new icons match.

## How do you make icons understood?

A consistent icon is not automatically a clear icon. An icon must also say the right thing. Some people use a screen reader, some have low vision, some are new to the product, and some are rushing on a small phone. A good icon works for all of them, and a good system gives builders the rules to keep that true.

Choose familiar metaphors

A metaphor is the picture that stands for an idea. Use a picture that most people already read the same way. An envelope for mail, a magnifying glass for search, and a trash can for delete are common examples. If a rule makes a familiar picture unreadable, the picture should win and the rule should be adjusted.

Be careful with clever pictures. An icon that needs a long explanation is a weak icon. Test the picture with people who do not know the team's internal names. If they guess the wrong action, the icon needs a label or a new picture.

Pair icons with text

When the meaning could be unclear, add text next to the icon. A small label such as Archive beside a box picture removes guessing. Designers should also avoid using color or shape alone for important meaning. A red circle that means an error should also carry a word, so people who cannot see color still understand the message.

Decorative or meaningful

Every icon falls into one of two groups. A decorative icon adds no new meaning. It sits beside text that already says the same thing, or it adds only visual polish. A meaningful icon carries information that is not written anywhere else nearby, such as an icon-only button or a standalone warning.

- **Decorative icons are hidden:** The matching text already does the job.
- **Icon-only controls get a name on the control:** When a button shows only an icon, the name belongs on the button itself, such as Delete. The icon inside stays hidden. Screen readers should announce the action, not the drawing.
- **Meaningful standalone icons get a name:** A warning icon that stands alone needs a short accessible name, such as Warning, so that the meaning reaches everyone. Guides also warn that a file name such as warning.svg does not make a good name.

Critical states need visible words as well as a picture. If an icon shows a failed payment, the message should also say so in plain text on the screen. Relying only on a symbol leaves some people behind.

> **Tip:** Ask one question for every icon in a design: if I removed the picture, would the screen still make sense? If yes, the icon is probably decorative. If no, it needs a name for screen readers and often a visible label too.

## How do you ship icons as a component?

A design system does not hand out icons as a folder of random files. It ships them as a component, so each team uses the same icon in the same way. This is what keeps the family together after launch, when many products and many builders use the set.

Clear names and optimized SVGs

Each icon gets a clear name that says what it shows, such as trash or archive, not a vague name such as icon-47 or final-new. Clear names help designers search the set and help builders find the right icon without asking. Icons are usually exported as SVG files. Optimized means the file is cleaned of extra data so that it loads quickly.

One Icon component, many uses

Instead of pasting an image each time, product teams use one shared Icon component. The component takes a few props. The name prop picks the icon from the set. The size prop accepts only the agreed sizes. The color prop takes a color token, not a random color. Because every screen uses the same component, a fix or a new size reaches the whole product at once.

The component also sets the defaults for accessibility. If an icon is decorative, the component hides it. If an icon is meaningful, the builder must supply the name. This turns the rules from the previous section into a default that is hard to get wrong.

- **Name prop:** Chooses one icon from the shared set. A wrong name should show a clear error during building, not a broken picture on the live product.
- **Size prop:** Accepts only the named sizes in the scale, so no one invents a 30px icon by accident.
- **Color prop:** Takes a color token, so the icon follows the theme and matches the text beside it.

Icons also follow the sizing of their parent. A 24dp icon in a button needs a larger touch area around it so that a finger can press it. The icon may look small, but the tappable area must stay large enough.

## Worked Example: A Mail Toolbar Walk-Through

Here is a walk-through of a mail toolbar, similar to the one in Gmail. Use it as a teaching example. The steps show how the rules above combine on one real kind of screen. Check the live product yourself for the exact details, because a product can change its icons over time.

The toolbar has three actions shown only as icons: a trash can for delete, an archive box for archive, and an envelope for marking mail as read. Each icon is a button with no visible words. Follow the steps below to check the set against the system rules.

1. **Check the grid:** All three icons sit in the same 24 by 24 box. Their shapes fit the same keyline guides, so the trash can, the box, and the envelope look the same size even though their outlines differ.
2. **Check the stroke:** All three lines are drawn at one stroke weight with the same end style. None looks heavier than the others, which is why the row reads as a set.
3. **Check the size:** The toolbar uses one icon size from the scale. Nobody has placed a slightly bigger envelope in the middle of the row.
4. **Check the metaphors:** A trash can for delete and an envelope for mail are picture choices most people read the same way. The archive box is less common, so the team should test it with real users before shipping.
5. **Check the name:** Each icon-only button has an accessible name, such as Delete for the trash can. The name sits on the button, and the icon inside is hidden from screen readers.
6. **Check the hover help:** Each button shows a tooltip, a small box of text that appears when a mouse rests on the button. It helps sighted mouse users, but it does not replace the accessible name.
7. **Check the touch area:** Each icon has enough empty space around it to be pressed by a finger, even though the drawing itself is small.

> **Tip:** When you review a toolbar, step through each rule in order: grid, stroke, size, metaphor, name, and touch area. Writing down the result for each icon turns a vague feeling that something looks off into a list of specific fixes.

## Check Your Understanding

Try these two short scenarios. Each one needs the rules from this lesson, not just a memory of the sentences above.

**Quick check:** A teammate exports a new settings gear as a PNG at 30px with a thick stroke. They place it, with no label, as the only content of a button. Which change fixes the most problems against the system's icon rules?

A. Keep the PNG and make the stroke even thicker so the gear stands out more on the page.
B. Re-export the gear as an SVG on the agreed grid at a named size with the standard stroke, and give the button an accessible name such as Settings.
C. Leave the gear as it is and add only a tooltip, because people who can see the screen will understand it.
D. Keep the 30px size so it matches the new gear, and add a decorative label that screen readers skip.

**Answer:** B. The gear breaks several rules at once. A 30px size is not on the agreed scale, a PNG does not scale as cleanly as an SVG, and a thick stroke breaks the shared weight. Because the gear is the only content of the button, the button needs an accessible name. A tooltip helps people who can hover, but it does not replace the name.

**Quick check:** A payment screen shows a green check icon next to the words Payment saved. A designer wants to give the check icon the name Success so that screen readers announce it. What is the best choice?

A. Give the check icon the name Success so screen readers announce it twice, once with the words and once with the icon.
B. Hide the check icon from assistive technology, because the visible words already say what happened.
C. Make the check icon bigger and bolder so that the status is easier to see at a glance.
D. Remove the words and keep only the green check, so the screen looks cleaner and simpler.

**Answer:** B. The words already carry the meaning, so the icon is decorative. Hiding it stops repeated noise for screen reader users. Removing the words would leave a critical status relying on a picture and a color, which the rules warn against. Making the icon bigger does not add meaning.

## Key Takeaways

- **One grid and size scale:** Draw every icon inside the same box and use only the named sizes the system allows.
- **One stroke and corner style:** Keep one line weight and one end style across the set, and check each new icon against it.
- **Color from tokens:** Take icon colors from named tokens so the set follows every theme without redrawing.
- **Meaning first:** Pick familiar metaphors, add text when meaning could be unclear, and never rely on color or shape alone for critical meaning.
- **Right names:** Hide decorative icons. Name icon-only controls on the control itself, and give meaningful standalone icons a short accessible name.
- **Ship as one component:** Use clear icon names, optimized SVG files, and one Icon component whose props set the name, size, and color.

Icons look simple, but they carry many agreed choices. When a team writes those choices down and builds them into one component, a small symbol can serve every product screen clearly and consistently.

## Sources

- [Material Design 3, Icons (designing icons and keylines)](https://m3.material.io/styles/icons/designing-icons)
- [Material Design, System icons (stroke, grid, touch target)](https://m2.material.io/design/iconography/system-icons.html)
- [Material Design 1, Icons (dense layouts, SVG format)](https://www.mdui.org/en/design/1/style/icons.html)
- [Material Design 1, Icons (dense desktop sizing and SVG file format)](https://m1.material.io/style/icons.html)
- [GitLab Product Foundations, Iconography](https://design.gitlab.com/product-foundations/iconography)
- [Bold Design System, Iconography](https://bold.bridge.ufsc.tech/design-guidelines/iconography/)
- [Iconoop, Icon Sizes: Pixel Sizes, Grids and Stroke Weight](https://iconoop.com/icon-sizes.html)
- [Bigeye Agency, How to Design Icon Systems for Brand Consistency](https://www.bigeyeagency.com/insights/design-icon-systems-brand-consistency)
- [DEV Community, SVG Icon Accessibility: Decorative vs Meaningful Icons](https://dev.to/svgicons/svg-icon-accessibility-decorative-vs-meaningful-icons-2430)
- [Svg/icons, Accessible SVG Icons: Roles, Labels, and When to Hide Them](https://svgicons.com/articles/accessible-svg-icons-aria-roles-labels)
- [EqualWeb Academy, Accessible SVG and icons](https://www.equalweb.com/academy/learn/lessons/svg-icons.html)
- [AllSVGIcons, Accessible SVG Icons: aria-label and role](https://allsvgicons.com/blog/accessible-svg-icons-aria-label-role/)
