# Small Use Guidance: Keeping Icons, Logos, and Text Clear at Tiny Sizes

> How design systems set minimum sizes and allowed simplifications, and what to do when an element still will not fit.

**In short:** Small use guidance sets minimum sizes and allowed simplifications so icons, logos and text stay clear at tiny sizes, and says what to do when one still will not fit.

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

## What You Will Learn

A design system is a shared set of parts and rules. Each single piece in it is called an element: an icon, a logo, a label, or a button. On a wide desktop screen, elements have room to breathe. On a small phone screen or in a crowded table row, they often do not. Small use guidance is the part of a system's rules that says how far an element may shrink, what you may simplify, and what to do when it still will not fit. In this lesson you will learn to read and write minimum sizes, choose allowed simplifications, and pick the right fix when space runs out.

- **Small use guidance:** The written rules for how an element may be shown and changed at its smallest size or in a tight space.
- **Element:** Any single piece of a design, such as an icon, a logo, a label, or a button.
- **Minimum size:** The smallest size an element may be shown at before it stops being clear. Some people call this the floor.
- **Legible:** Easy to read, or easy to see and understand.
- **Compact variant:** A separate, simpler version of an element that is made for small spaces.
- **Submark:** A very simple version of a logo, often just a symbol or a monogram.
- **Touch target:** The area on a screen that a finger can tap. It can be larger than the small shape you see.
- **dp (density-independent pixel):** A unit used on Android screens. It keeps the size of an element about the same on screens with different pixel densities.

> **Tip:** Read a minimum size as a floor, not a target. Design at the normal size first, and drop toward the floor only when the space forces you to.

## Why Do Small Sizes Need Their Own Rules?

Shrinking a design is not the same as shrinking a photo. Thin lines, small letters, and fine details fail first. Once they fail, the element stops doing its job. Small use guidance exists so that no designer has to guess where that line is.

- **Detail disappears:** Logos lose their fine parts below a certain size, and the effect is worse on a small screen.
- **Icons go muddy:** An icon that looks clear at a large size can turn into a smudge at a small one. Test icons at their smallest realistic size before you judge them.
- **Vague advice fails:** A line such as 'use plenty of space' gives no answer. A measured rule, such as keeping a clear zone equal to the height of the logo's icon, gives a designer something to check.

## What Are the Minimum Sizes for Each Element?

Every element type needs its own floor. Write the number, then write the reason beside it. A rule with a reason is kept and followed. A bare number gets ignored or argued about.

### Icon Minimums

Icons are the most common small element. Michelin's guidance is stricter at the bottom end. It rejects the 12px size outright because the icon cannot be read at that size, and it adds a 20px step between 16px and 24px, which it says is needed at small scale. Atlassian makes 16px its default and reserves its 12px size for rare use, since the smaller icon is harder to read.

> **Tip:** Write the icon floor with its reason. For example: no icon below the smallest size on the scale, because the detail of a smaller icon blurs.

### Logo Minimums

A logo minimum is the smallest width or height at which the mark still reads clearly. For screens, the number is usually in pixels. For print, it is given in millimeters or inches. Good guides also add a proportion rule, so the logo is never stretched or squashed just to hit a size. A brand's own guide sets the real number. This lesson does not give a figure for any real brand.

Each version can have its own minimum, so the simple mark may be shown smaller than the full logo.

### Text and Tap Area Minimums

For text, your guidance should name the smallest text size the system allows. This lesson does not supply that figure. Take it from your own type scale and test it on a real screen at the narrowest width you support. For tap areas, the visible icon can stay small while the tappable zone is larger. Michelin asks for a clickable zone of at least 48px and works out that a 32px icon needs 8px of extra padding on each side to reach it. The Accessibility lesson covers that floor in depth.

## What May Change at Small Sizes?

Small use guidance does not say make everything smaller. It names the changes that are allowed. Every allowed change passes one test: the element must still be recognizable afterward. If a person cannot tell what it is, the change is not allowed.

- **Simplified icons:** Draw a small-size version with simple shapes and only the detail needed to carry the meaning. Remove fine lines and tiny gaps first, and keep the main shape.
- **Compact logo marks:** A compact mark is a simpler version of the logo, often just the symbol or a monogram.
- **Shortened labels:** A label may be shortened only if the short form still says what the action does. Trim filler words and extra detail. Never cut the word that names the action.
- **Hidden secondary parts:** A tagline or subtitle is the usual part to hide.

## Do and Do Not Rules

Write the guidance as short rules. Each rule below pairs a do with a don't, so a designer can see where the allowed zone ends. Picture each pair as two versions side by side: the one that is allowed and the one that is not.

- **Do: set a floor for each element:** Give every element type its own minimum. Use pixels for screens and millimeters or inches for print.
- **Don't: shrink a full logo to make it fit:** Most brand guides do not allow a full logo below its minimum, even when the space is only slightly short. Use the compact mark instead.
- **Do: keep the shape recognizable:** After any simplification, a person should still identify the element at a glance. Check the result at the smallest size first.
- **Don't: distort or tilt:** Never stretch, squash, rotate, or add depth to fit a gap. Atlassian's icon rules ask that icons face forward and do not look three-dimensional.
- **Do: give an icon a bigger size than its label:** When an icon sits beside text, Michelin's guidance says to use an icon one size higher than the text it sits with. Never pair a smaller or equal-size icon with a label.
- **Don't: crowd the breathing room:** Leave clear space around a small element so neighbors do not overlap it. Michelin calls this the safe area, and it is separate from the tap area.

## What Should You Do When an Element Will Not Fit?

Sometimes the space is smaller than every allowed size. The guidance then gives an order of fixes. Shrinking further is never the first fix, and it is never the last one either.

1. **Confirm the space is really too small:** Measure the space and the element at the same scale. Make sure the element is not already below its own floor before you change anything.
2. **Try the approved compact variant:** Swap to the simplified version that the guidance lists for tight spaces. Logo guides often keep a set of approved alternates, each with a stated use.
3. **Hide only the secondary parts:** Remove a tagline, subtitle, or extra text. Keep the part that names or identifies the element.
4. **Rethink the layout:** If the element still cannot fit, give it more room by changing the arrangement around it. Detailed layout rules belong to other lessons. The point here is that room is the fix, not a smaller element.
5. **Stop at the floor:** Never shrink an element below its minimum to make it fit.

> **Tip:** A compact variant is a different design, not a smaller copy of the full one. Draw it as its own asset, with its own minimum size.

**Quick check:** You are placing a brand logo with fine detail and a tagline in a 32px-high mobile app header. The tagline is now unreadable. According to small use guidance, what should you do, and what should you avoid?

A. Shrink the tagline and the full logo together until both fit inside the 32px header
B. Stretch the logo sideways so its detail has more width to show
C. Swap to a simplified version with no tagline, and keep the mark recognizable
D. Hide the logo entirely and show the company name in plain text instead

**Answer:** C. The approved fix is the simplified version without the tagline, because it keeps the mark recognizable at header height. Shrinking the text below its floor, stretching the logo, or removing the logo all break the rules.

## Worked Example: Merchant Logos in a Transaction List

This example is a teaching case, not the real rules of any app. Imagine a mobile banking app whose transaction list shows each merchant's full logo at the start of every row. The full logo has fine detail and a small name line. At row height, that detail becomes an unreadable blur. The guidance sets a minimum for the full logo and forbids shrinking it below that minimum.

1. **Spot the problem:** The row has less height than the full logo needs. Shrinking the full logo to fit would make the blur worse, so the full logo cannot be used in this row.
2. **Check the rule:** The guidance forbids showing the full logo below its minimum. The list row is therefore not a place for the full logo.
3. **Choose the compact mark:** The guidance provides a simplified compact mark for list rows. In this app, the mark is shown at 24px, the size the guidance sets for that variant.
4. **Keep it recognizable:** The compact mark keeps the main shape and the brand color. The fine lines and the small name text are removed, because they cannot survive at 24px.
5. **Check the tap area:** The whole row is the tap target, so the 24px mark does not need its own button. The clickable zone stays large enough even though the mark is small.
6. **Bring back the full logo where there is room:** On the merchant's detail screen, the full logo returns at its normal size, because that screen has room for the detail.

## Common Mistakes

- **Shrinking first:** Reducing the size is the reflex fix, and it often breaks the element fastest. Try the allowed changes before you make anything smaller.
- **Dropping the identity:** Hiding the only part that identifies an item removes the reason for showing it. Hide secondary parts, not the identity.
- **Stretching to fit:** Changing the proportions makes a logo or icon look wrong. Keep the shape, and use a compact variant instead.
- **Inventing a new size:** A size that is not on the system's scale creates a one-off that no one else can match. Use only the sizes the guidance lists.

## Quick Check

Try these two new scenarios. Each one needs the rules in this lesson to answer.

**Quick check:** In a dense table, an icon-only edit button uses a 12px icon, and the icon looks fuzzy. What does the guidance point you toward?

A. Keep the 12px icon, since it is the smallest size and fits the row
B. Move to the smallest size on the system's scale that still reads clearly, and keep the clickable area large enough
C. Stretch the 12px icon wider so that its shape is easier to see
D. Add a thin line drawing with extra detail so the icon looks sharper

**Answer:** B. A 12px icon is too small to read well, so the fix is a size on the scale that stays clear. Stretching distorts the icon, and adding detail makes it harder to read at small sizes.

**Quick check:** A transaction row on a phone has room for a merchant name, a 24px compact mark, and a grey subtitle with the date. The subtitle does not fit at the row's width. What should you do?

A. Shrink the subtitle below the text floor so that it fits on the same line
B. Hide the subtitle as a secondary element, and keep the name and the mark
C. Remove the merchant mark and keep the subtitle, since the date matters more
D. Stretch the mark to the same width as the name so the row looks balanced

**Answer:** B. The subtitle is secondary, so it can be hidden while the name and the mark keep the row recognizable. Shrinking below the floor, removing the identity, and stretching the mark all break the rules.

## Sources

- [Michelin Design System: Icons, Usage](https://designsystem.michelin.com/icons/brand/icons-pictograms/icons/usage)
- [Material Design: System icons](https://m2.material.io/design/iconography/system-icons.html)
- [Atlassian Design: Iconography](https://atlassian.design/foundations/iconography)
- [Sanjay Shrestha: Choosing an Icon Style That Scales](https://sanjayshrestha.com/blog/icons-design-systems)
- [Icojoy: Icons in Design Systems](https://icojoy.com/articles/53/)
- [Vistaprint: Logo usage guidelines](https://www.vistaprint.com/hub/logo-usage-guidelines)
- [Branding Toolbox: Logo Usage Guidelines](https://brandingtoolbox.ca/topics/logo-design/logo-usage-guidelines)
- [Customer Impact: Logo usage guidelines, clear space and don'ts](https://www.customerimpact.be/en/blog/logo-usage-guidelines/)
- [Ficonica: Logo Brand Guidelines That Small Teams Use](https://ficonica.com/blog/logo-brand-guidelines-small-teams)
- [RV Tech Solutions: Master Logo and Brand Usage](https://rvtechsolutions.com/logo-usage-guidelines-for-consistent-branding/)
- [Brand VM: Iconography in Web Design](https://www.brandvm.com/post/iconography-web-design-size-style-icons)
