Sizes: The Fixed Set of Named Dimensions Each Component Comes In
Learn how a small, named scale of sizes keeps buttons and inputs consistent, and how to pick the right one for a finger on a phone or a mouse on a desktop.
In short
Sizes in a design system are a small, named scale of dimensions for components like buttons and inputs, so they stay consistent whether used by finger or mouse.
9 min readFree
What you will learn
Every button, text field and badge on a screen has a size. A designer could invent a new height each time, or choose from a short list the team already agreed on. In this course, Sizes means that short list: the small, fixed set of named dimensions that a component can come in, such as S, M and L. This lesson explains why teams use the list, how to build one, and how to pick the right entry for a given screen.
You will learn three things. First, why a component gets only a few sizes. Second, how to define a size scale so the sizes work as one set. Third, how to choose a size for the place it appears, including the minimum area a finger can reliably tap.
Key words
- Component
- A reusable piece of a screen, such as a button, input or badge. The team builds it once and reuses it on many screens.
- Size scale
- An ordered list of named sizes, such as S, M and L, where each name has a set measurement.
- Base size
- The starting size of a scale. The other sizes are built by stepping up or down from it.
- Density
- How tightly a layout packs its content. A dense layout fits more on screen by using smaller controls.
- Touch target
- The area that reacts when someone taps or clicks. It can be larger than the control you can see.
- dp, pt and px
- Units of length that design tools use to measure sizes. The Units lesson explains them, so here we only use the numbers.
Why do components get a fixed set of sizes?
A product often has dozens of screens. If each designer picks a height by eye, a button on one screen ends up a little taller than the same button on another. Users then see near-matches that do the same job, and they cannot tell whether the difference means anything. A fixed scale stops this drift, because every designer picks from the same named options.
Consistency
The same kind of control looks and behaves the same way on every screen. Users learn it once and reuse that knowledge.
Faster decisions
A designer chooses S, M or L from a list instead of measuring and debating a new size. Fewer choices mean quicker reviews.
Easier handoff
Designers and builders share the same names, so they need fewer questions when they pass work across.
How do you define a size scale?
A size scale is not a random set of sizes. It is built in a planned way, so that each step makes sense next to the others. Three steps are enough to build one.
- 1
Choose a base size
Pick the height that your most common control needs, and check that it meets your minimum touch area. This size usually becomes the default.
- 2
Step up in a steady pattern
Add the same amount at each step so the sizes rise evenly. Name them so the order is obvious, such as S, M and L.
- 3
Make the parts agree
At each size, check that height, text size and inside space work together. Padding, the space inside a component, follows rules covered in the Spacing lesson.
The next three sub-topics explain each step in more detail.
Pick the base size. Start from a height your product really needs. Material Design's button guidance has moved over time.
Tip
Names are local. Different guides use different words for the same height. One guide lists small as 32 px, default as 40 to 48 px and large as 48 px or more. Your team should write down what each name means in your own system, and then stick to it.
Step up in a steady pattern. Steady steps are easier to remember than random jumps. A set rule like this lets a designer predict the next size without measuring it.
Tip
A step of 8 is easy to remember, and it matches the 8-unit spacing that many layouts use. Pick one step size and use it for the whole scale.
Make the parts agree. A size is more than a height. When the height grows, the label text should grow with it, and the inside space should keep the label from crowding the edges. The text and the box change together.
Tip
Build the scale as a table with one row per size. Put the height, text size and padding side by side. If you change one column, check the other two before you publish the scale.
How do you choose the right size for the context?
Having a scale is only half the job. You still have to choose the right entry for each place a component appears. The choice depends on how people use the screen. A thumb on a phone needs more room than a mouse pointer on a desktop, and a crowded screen may need smaller controls. Ask three questions: how will people touch or click this, how much space is there, and how important is this action?
Touch targets: the 44 to 48 point floor. A touch target is the area that reacts to a tap. It can be larger than the visible control. Android's guidance gives an example: a 24 dp icon sits inside a 48 dp touch area, because the padding around the icon counts as part of the target. This means a small picture can still be easy to hit.
Apple (iOS)
Apple's Human Interface Guidelines suggest a tappable area of at least 44 points.
Material (Android)
Material Design asks for at least 48 dp in width and height, which the Android guidance says is about 9 mm on any screen.
Web standard (WCAG 2.2)
A web accessibility standard sets a minimum of 24 CSS px, with 44 px as the higher target. Its rules are covered in the Accessibility lesson.
Tip
Aim for 44 to 48 for any control a finger must hit. A 44 px target meets Apple's floor and most web targets, and 48 meets Material's floor. For most production work, 44 px is the practical minimum.
Leave space between targets too. Android's guidance suggests a gap of about 8dp between targets. Tight gaps cause mis-taps even when each target is large enough. Use the larger size for the actions that matter most, and for users who have larger thumbs or who may find small buttons hard to hit.
Dense desktop layouts. A desktop data table can hold many rows, and each row may carry a small action such as Edit. A compact size keeps the table readable.
Compact is not the same as tiny. Compact sizes are for mouse use and crowded screens, not for the main action on a phone.
Worked example: a checkout screen and a data table
Material Design's buttons come in set heights. Its touch area should be at least 48 dp. Imagine that you design two screens for one product: a mobile checkout and a desktop order table. Here is how you would pick the size for each.
- 1
Read the context
The checkout runs on a phone and people use their thumb. The Pay button is the main action on the screen.
- 2
Choose the large size for Pay
Pick the largest size, which is 48 px tall, so the tap area reaches the 44 to 48 range. Make the button full width if the layout allows, because full-width buttons are often the right choice in mobile apps.
- 3
Choose the compact size for the table
Each row has a small Edit button. The table holds many rows and sits on a desktop, so choose the compact size from the same scale, which can go down to 32 px tall.
- 4
Check the family
Both buttons use the same names, the same padding rules and the same text style. Anyone on the team can see they are one component at two sizes.
The result is that each screen gets the right size, and the team still uses one set of named sizes. The designer did not invent any new heights.
Mistakes to avoid
Shrinking the tap area to fit a small icon
A small icon can sit inside a larger touch area with padding. Keep the touch area large and let the icon stay small.
Adding too many sizes
Each extra size adds a choice and a chance for confusion.
Assuming one minimum fixes everything
Setting a minimum height for the scale does not fix a tight group of controls. Each option in a group, such as each segment of a segmented control, still needs its own clear size.
Making one-off sizes
A special size for one screen breaks the scale. Build a new size only when several screens need it, and add it to the scale on purpose.
Tip
Before you add a size, ask whether an existing size would work. If it would, use it.
Check yourself
Try these two short scenarios. Each one needs the ideas from this lesson to answer.
Quick check
Your team's mobile app has a 28 px tall Delete button that users often miss. The design system offers S at 28 px, M at 40 px and L at 48 px. Which size should you switch to?
Quick check
You design a web admin page with 200 rows. Each row has a small Edit action. People use a mouse on a large monitor, and space is tight. Which size fits best?
Sources
- Material Design 3: Buttons overview
- Material Design 1: Buttons
- Material Design 3: Segmented button specs
- Material Design 1: Metrics and keylines
- Android Accessibility Help: Touch target size
- Website Spec: Touch target size
- Cieden: What should be considered in app button design?
- Strynal: Sizing Touch Targets for Accessible, Tappable UI
Last updated on 17 November 2026
Related lessons
- Design systemsPlacement Guidance: Where Each Component Goes and Why
- Design systemsCreating Core Components: Build the Small Set of Parts Every Screen Uses
- Design systemsDesign System vs Component Library: What Each One Covers
- Design systemsSizing: The Agreed Dimensions Behind Consistent, Tappable Components
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.