# Icons: Small Shared Pictures That Make Actions Easy to Recognize

> Learn why a design system keeps one icon set, how icons are built on a grid, and how to use them so everyone can understand them.

**In short:** Icons are small shared pictures that make actions easy to recognize, and a design system keeps one icon set built on a grid so everyone can understand them.

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

## What You Will Learn

This lesson explains icons as they are used in a design system. An icon is a small picture that stands for an action, an object, or a status. A magnifying glass can mean search, a bin can mean delete, and a warning triangle can mean a problem. In a design system, icons are not loose drawings. They form a shared set with agreed rules for style, size, and use, and every team picks from that set.

By the end, you should be able to explain why a system keeps one icon family, how icons are built on a grid and delivered for reuse, and how to use icons so that more people can understand them, including people who use screen readers.

- **Icon:** A small picture that shows an action, an object, or a status in a product.
- **Icon set:** The full group of icons a design system provides, drawn in one shared style.
- **Grid:** An invisible square frame that each icon is drawn inside, so icons line up and take up similar space.
- **Stroke:** The line that draws the edge of an icon. Stroke weight means how thick that line is.
- **Metaphor:** A picture that stands for an idea, such as a bin for delete.
- **SVG:** A picture file made of lines and shapes. It stays sharp at any size.
- **Screen reader:** Software that reads the screen out loud for people who cannot see it well.
- **Touch target:** The area on a screen that a finger can tap. It should be big enough to hit easily.

> **Tip:** Keep a daily app open next to this lesson. Find five icons and guess what each one does before you keep reading.

## What Do Icons Do in a Product?

Icons do three main jobs. They show an action the user can take, such as save or share. They show an object, such as a folder, a person, or a photo. They also show a status, such as success, an error, or an upload that is still running. A good icon helps the eye understand the screen faster than words alone.

- **Action icons:** Tell the user what will happen when they press. Examples are save, share, add, and delete.
- **Object icons:** Name a thing in the product. Examples are a folder, a calendar, a user, or a file.
- **Status icons:** Show the state of something. Examples are a check for done, a warning for a problem, and a spinning mark for waiting.

## Why Does a Design System Need One Icon Set?

Imagine three screens made by three people. One uses thin lines with sharp corners, one uses thick rounded lines, and one uses solid filled shapes. Each icon might be clear by itself, but together they look like three different products. Users must learn each style again. A design system solves this problem by giving every team one set to draw from.

### Style That Holds the Set Together

Style is what makes icons read as one family. Design teams write down a few settings and then follow them for every icon. These settings are the main ones to know.

- **Stroke weight:** How thick the lines are. Every icon in the set should use the same thickness unless there is a strong reason not to.
- **Corner radius:** How round the corners are. A set should use one corner style so the shapes feel related.
- **Grid and padding:** The frame each icon sits in and the empty space kept around its edge. This keeps icons the same visual size.
- **Optical alignment:** Small hand adjustments so an icon looks centred and balanced to the eye, even when the maths says it is not.

Other icon guides add that sharper or more detailed icons often need more space inside the grid to look balanced.

### Recognition Comes Before Reading

Most people scan a screen instead of reading every word. When a save icon looks like the other icons in the app, the eye learns it quickly and reuses that knowledge on the next screen. This is the real reason a system bothers with style rules: the goal is fast recognition, not beauty alone.

## How Are Icons Built and Shared?

Icons are built once in a design file and then reused across many screens. Before drawing, the team sets a few fixed rules. These rules make a new icon look like it belongs with the old ones, and they make reuse simple.

### The Base Grid and Size Scale

Most teams start every icon on the same square grid. A 24 by 24 grid is very common for interface icons. Material Design gives its system icons a 24dp size. Other systems use 32 by 32 for larger icons. Whatever size is chosen, the same frame applies to all icons in that family.

A size scale is a short list of allowed sizes, such as 16, 20, 24, and 32 pixels. The scale stops anyone from making a new size on a whim. Some guides suggest picking sizes that fit a common spacing system, such as multiples of 8.

> **Tip:** Write the allowed sizes in the design system and say which size goes with which place, such as small icons inside buttons and larger icons on empty screens.

### Clear Names and SVG Files

Each icon needs a clear name, so designers and engineers can find it. Good names describe the picture or the action in plain words and follow one pattern across the whole set. A team that names icons well can search for a 'trash' icon and find only one.

Most teams deliver icons as SVG files. SVG is a picture format made of lines and shapes, so it scales without going blurry. SVG also works well for color changes. Icon guides note that SVG suits icons that need to scale or change color. A useful next step is making icons take their color from the text or button around them. That one file can then work in a normal state, a selected state, and a dark theme. Choosing the actual colors belongs to the color lesson.

> **Tip:** Ask for the SVG file, not a screenshot. A screenshot cannot change color or scale cleanly.

## Worked Example: Google's Material Symbols

Google publishes Material Symbols, a free icon library. Its guide says the set has over 2,500 icons in one font file, with four adjustable settings. Follow these steps to see how one icon, such as a search or settings icon, is set up so it matches the rest of the family.

1. **Start on the 24 pixel grid:** A third-party review notes that only the 20 and 24 pixel versions are drawn for exact pixel alignment.
2. **Choose a style:** Material Symbols comes in three styles: outlined, rounded, and sharp. The outlined style is light and clean, and it works well in dense screens with a lot of content.
3. **Set the weight:** Weight runs from 100, which is thin, to 700, which is bold. The regular setting is 400. Many teams match the icon weight to the weight of the text beside it.
4. **Set the fill for state:** Fill runs from 0, which is an outline, to 1, which is solid. Designers often use fill to show a selected or active state, such as a filled star for a saved item.
5. **Request by name:** Google's guide shows icons requested by a name, such as home, palette, or settings.

The lesson for a design team is clear. The set fixes the grid, the style, and the names once. Each screen then uses the same settings, so a settings icon on one screen matches a settings icon on another. Keep in mind that this set has no two-tone icons, so a team that needs two-tone style must plan for that gap.

## How Do You Use Icons Well?

A set can be perfect and still confuse people if icons are used badly. Three habits keep icons clear: add text when needed, keep one picture for one idea, and build in accessibility from the start.

### Pair Icons With Text When Meaning Is Unclear

An icon alone can be read in several ways. Three dots might mean more options, sharing, or settings. When the meaning is not obvious, add a short text label next to the picture. Accessibility guides also advise against relying on color or shape alone for information that really matters.

### Keep One Picture for One Idea

Pick one metaphor for each concept and reuse it everywhere. If save is a floppy disk on one screen, a download arrow on another, and a check mark on a third, users must learn the action again each time. The design system should name the one picture for save and record it in the set, so every screen uses it.

### Accessibility Basics for Icons

Some people use screen readers, and some have low vision or limited motor control. These rules help every icon work for them.

- **Decorative icons:** An icon that repeats a label or adds no meaning should be hidden from screen readers. Guides call this marking it as decorative.
- **Icon-only buttons:** Put the spoken label on the button, not on the picture. The label should describe the action, such as 'Close dialog', not the shape of the X.
- **Meaningful standalone icons:** An icon that stands alone and carries meaning needs a short accessible name that a screen reader can announce.
- **Contrast:** The icon must stand out from its background.
- **Touch target:** On mobile, the tappable area should be at least 44 by 44 pixels, even if the picture inside is smaller.

## What Rules Apply for Adding New Icons?

A design system should not grow by accident. Each new icon should follow a clear path. Design guides suggest documenting grid size, stroke width, corner radius, spacing, and export settings, so new icons can be made without breaking the family.

1. **Search the set first:** Check whether an icon with the same meaning already exists. Most duplicate icons come from people who did not look.
2. **Confirm a picture is needed:** If the idea is rare or hard to draw clearly, a text label may serve users better than a new icon.
3. **Draw on the shared grid:** Use the same grid, stroke weight, corner radius, and padding as the rest of the set.
4. **Test on real screens:** Place the new icon in an actual screen at its real size. A good drawing on a blank board can still look wrong in a button.
5. **Name it and document it:** Give it a clear name, record its meaning and its accessible label, and publish it with a short note on when to use it.

> **Tip:** Mixing icons from different sources often breaks the style. Only mix them when their design language clearly matches.

## Check Your Understanding

Try these three short scenarios. Each one needs an idea from this lesson to answer.

**Quick check:** Your team's app draws 'save' as a floppy disk on one screen, a download arrow on another, and a check mark on a third. Users keep hesitating. What is the main icon problem, and what should the design system do?

A. The icons are too small, so the system should set every icon to a larger size.
B. The same action has three different pictures, so the system should name one agreed save icon and require every screen to use it.
C. The icons need more color, so each screen should use a different color for its save icon.

**Answer:** B. The problem is inconsistent metaphor. One action should have one picture, recorded in the system and used everywhere.

**Quick check:** A teammate adds a new trash icon with thick, rounded strokes to a set where every icon uses thin, square-cornered lines. What should happen before it goes into the library?

A. Add it as it is, because the teammate thinks it is clearer.
B. Redraw it on the set's grid with the agreed stroke weight and corner radius, then test it on real screens.
C. Give it a bright color so users can tell it apart from the other icons.

**Answer:** B. New icons must follow the set's shared style rules. A color change does not fix a mismatch in stroke and shape.

**Quick check:** A phone screen has a close button shown as a small X with no text. A developer asks what a screen reader should say. Which answer is best?

A. The screen reader should say 'X', because that is what sighted users see.
B. The button should carry a label that describes the action, such as 'Close dialog', and the picture itself should be hidden from screen readers.
C. No label is needed, because sighted users can see the X and know what it does.

**Answer:** B. Screen readers should announce the action the button performs, not the shape of the picture.

## Sources

- [Google Fonts: Material Symbols guide](https://developers.google.com/fonts/docs/material_symbols)
- [Google material-design-icons GitHub repository](https://github.com/google/material-design-icons)
- [Material Web: Icon component documentation](https://material-web.dev/components/icon/)
- [Material Design: Icons style guidance](https://m1.material.io/style/icons.html)
- [Hysen Labs: Material Design Icons review](https://hysenlabs.com/projects/google-material-design-icons)
- [Iconoop: Material Symbols axes explained](https://iconoop.com/material-icons.html)
- [Uxcel: Guide to iconography design](https://uxcel.com/blog/beginners-guide-to-iconography)
- [Upslide Design Studio: Design principles for perfect icons](https://upslidedesignstudio.com/blogs/design-principles-for-perfect-icons-a-complete-ui-ux-guide)
- [Bigeye Agency: How to design icon systems for brand consistency](https://www.bigeyeagency.com/insights/design-icon-systems-brand-consistency)
- [DEV Community: How to maintain visual consistency across your app icons](https://dev.to/albert_nahas_cdc8469a6ae8/how-to-maintain-visual-consistency-across-your-app-icons-14ac)
- [Colorpark: Practical icon size guidelines for UI/UX design](https://www.colorpark.io/blog/practical-icon-size-guidelines-for-ui-ux-design)
- [Memorable Design: Icon system design guide](https://memorable.design/icon-system-design/)
- [Svg/icons: Accessible SVG icons, roles, labels, and when to hide them](https://svgicons.com/articles/accessible-svg-icons-aria-roles-labels)
- [Icojoy: Accessible icon design, ARIA labels, contrast and screen-reader support](https://icojoy.com/blog/accessible-icon-design-aria-contrast-screen-reader-support/)
- [AllSVGIcons: Accessible SVG icons, aria-label and role](https://allsvgicons.com/blog/accessible-svg-icons-aria-label-role/)
- [Toolsmonk: Icon design for the web with SVG best practices](https://toolsmonk.com/blog/icon-design-web-svg-best-practices)
- [10Web: Icon accessibility guidelines](https://10web.io/blog/icon-accessibility-guidelines/)
