Sizing: The Agreed Dimensions Behind Consistent, Tappable Components
Learn how a design system picks sizes from a shared scale, names size variants, and keeps buttons and icons easy to tap on every screen.
In short
Sizing in a design system means picking sizes from a shared scale and naming size variants, so buttons and icons stay consistent and easy to tap on every screen.
11 min readFree
What Does Sizing Mean in a Design System?
Sizing is the set of agreed dimensions that a design system uses. A dimension is how tall or how wide something is. In a design system, the heights, widths, icon sizes, and touch areas are chosen once, written down, and reused. This keeps the product consistent, and it helps the product work across phones, tablets, laptops, and different ways of pressing, such as a finger, a mouse, or a stylus.
Why does it matter? Imagine one button is 34 units tall on the login page and 41 units tall on the checkout page. Users may not name the difference, but they feel that the app is a little off, and some of them miss taps. A sizing rule gives the whole team one set of numbers to choose from.
Key words
- Sizing
- The agreed set of heights, widths, and tap areas that a design system uses again and again.
- Component
- A reusable part, such as a button, that designers place on many screens.
- Element
- A smaller piece inside a component, such as an icon or a text label.
- Scale
- An ordered list of allowed sizes. Teams pick from the list instead of inventing new numbers.
- Base unit
- The small step that a scale is built from, such as 4 or 8.
- Pixel (px)
- A tiny dot on a screen. Its real size varies by device, so it is a loose unit.
- Density-independent pixel (dp)
- An Android unit that is meant to look about the same size on screens with different densities.
- Point (pt)
- The unit Apple uses for layout. It is close to a pixel on a standard screen.
- Touch target
- The area that responds when someone taps or clicks. It can be bigger than the picture of the control.
- Variant
- A named version of one component, such as small, medium, or large.
- Responsive
- A size or layout that changes when the screen gets wider or narrower.
Why Start From a Defined Scale?
Some teams pick sizes by eye. One button is set to 34, another to 37, and a third to 41, because each looked right on its own screen. This works for one screen. It falls apart across a whole product, because nobody can tell which number is the right one.
A defined scale fixes this. It is a short list of allowed values, all built from one base unit. Many teams use 4 or 8 as the base. Material Design uses an 8 dp baseline grid for components and a 4 dp baseline grid for toolbar iconography, which is a good example of a grid used in a real system.
Predictable
Every value can be traced back to the base unit, so a designer can guess a sensible size before checking a chart.
Reusable
A new button or card uses a value that already exists, so the team does not drift into new numbers.
Easy to check
A reviewer can spot a value that is off the grid, such as 37 when the scale uses multiples of 4, and fix it quickly.
The next block shows how a team can build its own scale. It takes a few decisions, but the decisions are made once.
- 1
Pick one base unit
Choose 4 or 8 and stick with it. Do not mix both in the same set of sizes unless the rules say when each is used.
- 2
List the sizes you need
Write the heights and widths your components need, such as a compact row, a standard control, and a large action.
- 3
Express each size as a multiple
Every value should be the base unit times a whole number. Use small steps for fine tuning and bigger steps for major sizes.
- 4
Write down what each step is for
Put the list in the design system guidelines, with a short note on where each size is used.
- 5
Add new steps only when needed
Before adding a value, check whether an existing step already fits. A new step should solve a real problem, not a one-off screen.
Tip
Keep the scale short. A long list of near-identical sizes looks thorough, but it gives designers too many choices and brings back the problem you started with.
What Are Named Size Variants?
Many components come in more than one size. A system does not let each screen invent its own version. Instead, it gives each size a name, such as small, medium, and large. Each name points to a fixed set of dimensions from the scale. A designer then chooses a name, not a number.
Names make the choice easier to explain. A teammate who reads 'use the large button for the main action' knows what to do without measuring anything.
Give Each Variant a Clear Job
Small
Used where space is tight, such as a dense toolbar or a compact row of actions. It must still meet the touch rules covered below.
Medium
The default for most screens. Most designers reach for this size first, so it should look right in the most common places.
Large
Used for the main action on a screen, or where the action must be easy to find and easy to press.
Tip
Name variants by role or by relative step, not by one screen. A name such as 'checkout button' breaks as soon as the same control is used somewhere else.
Each variant should have a rule for where it belongs. If a designer cannot say when to use a size, the size is probably not needed. This is also a good moment to write a short note in the guidelines, so future designers do not guess.
Sizes That Support Usability and Access
A size that looks fine on a large monitor can be too small for a thumb on a phone. Platform guides set minimum tap sizes so that people with larger fingers, tremors, or motor difficulties can still press the right control. Sizing rules should follow these minimums.
Android (Material Design)
Touch targets should be at least 48 by 48 dp, according to Google's guidance. The guidance applies to devices that take both touch and other kinds of input.
iPhone and iPad (Apple)
Apple recommends a minimum of 44 by 44 points for buttons, links, and icons.
Web (WCAG 2.2, Level AA)
Pointer targets should be at least 24 by 24 CSS pixels, or have enough empty space around them. This is the AA target size for pointer targets.
Web (WCAG 2.5.5, Level AAA)
The stricter enhanced rule asks for 44 by 44 CSS pixels. Teams that aim high can use this number as their standard.
Notice that the numbers differ. Use the platform your product runs on, and when you build one system for many platforms, choose a rule that meets the strictest one you support.
Keep Space Between Targets
A large tap area is not enough on its own. If two targets sit too close together, a tap on one can land on the other.
What Is the Difference Between Visible Size and Tap Area?
The picture you see is not always the area that responds. A small icon can sit in a larger, invisible tap area. Material's icon examples show a 24 dp icon inside a 48 dp target. In web guidance, a small icon gets extra padding, so its clickable area grows without changing how it looks.
Tip
Grow the tap area with padding, not the artwork. The icon can stay small and tidy while the hit area still reaches the minimum.
Sizes also have to leave room for readable text. The size of the text itself is covered in the typography lesson, but a component that is too tight for its label will fail, whatever its tap area.
Should Sizing Be Fixed, Flexible, or Responsive?
Not every component should behave the same way when the screen changes. A good system says which of three behaviors each component uses.
Fixed
The size never changes. This suits icons, avatars, and small controls whose shape must stay exact.
Flexible
The size stretches to fill the space it is given, such as a full-width button on a narrow phone.
Responsive
The size or layout changes at set screen widths, so a page can move from phone to tablet to desktop. Material keylines can change at each breakpoint range, which is one way to plan this.
Tip
Decide the behavior in the guidelines for each component. A full-width primary button may stretch, while an icon button should stay fixed, so its tap area is never lost.
Whatever the behavior, the minimum touch area still applies. A flexible button can grow wider, but it should never shrink below the minimum height. Test on real devices with real people, because a rule that looks right on a design file can feel wrong in a hand.
How Do You Apply Sizing to a Real Screen?
Now try the idea on a short case. Read the scenario, then choose the answer that uses the rules from this lesson, not the first answer that sounds quick.
Quick check
Your team's app has three buttons on one screen. Their heights are 34, 37, and 41 px. Phone users often miss the smallest one. How should the design system fix this?
Here is a second case, about an icon. A web team has a close icon that is 16 px across, with no padding, in a tight row of other icons. A reviewer says it fails the Level AA target rule.
Quick check
What is the best fix for the close icon in the web product?
A Quick Sizing Checklist
Use a scale
Build sizes from one base unit, and keep the list short and written down.
Name the variants
Give each size a name and a clear purpose, such as small for tight spaces and large for main actions.
Protect the tap area
Meet the platform minimum, use padding for small visuals, and keep space between targets.
Decide the behavior
Mark each component as fixed, flexible, or responsive, and test it on real devices.
Sizing is a small topic that does a lot of work. When every button, icon, and target follows one clear set of agreed numbers, the product feels steady, and people can press what they mean to press.
Sources
- Material Design: Spacing methods (touch targets, padding increments, keylines)
- Material Design: Metrics and keylines (button and touch target heights)
- LogRocket: All accessible touch target sizes
- TetraLogical: Foundations, target sizes
- Evelance: Fitts's Law and touch target sizing on mobile
- Equal Web: WCAG 2.5.8 Target Size (Minimum)
- Accessibility.build: WCAG 2.5.8 Target Size (Minimum), Level AA
- uxcel: iOS App Design, minimum tap target size
- UX Patterns glossary: Touch Targets
- Interaction Design Foundation: How to Use Tappability Affordances
- Mobile Viewer: Touch Target Size, Google's Guidelines for Mobile Buttons
- WCAG rules: 2.5.8 Target Size (Minimum)
Last updated on 17 November 2026
Related lessons
Learn with me
Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.