Visual Forms: The Shape and Depth Rules That Give Components One Family Look
Corner radius, borders, elevation, and fill versus outline: a small set of named style rules that make buttons, cards, and inputs feel related.
In short
Visual forms are a small set of named rules for corner radius, borders, elevation, and fill versus outline that make buttons, cards and inputs feel related.
13 min readFree
What you will learn
Every button, card, and text box on a screen has a shape. Some corners are round and some are square. Some parts sit flat on the page, and others seem to float above it. When each team picks these values on its own, a product can look like it was built by several different groups. Visual forms are the small set of shared shape and depth rules that stop this. In this lesson you will learn what visual forms are, how to limit them to a short named scale, how to match each shape to its job, and how to store the rules so they stay the same over time.
This lesson does not cover color, type, spacing, icons, or sizes. Those topics have their own lessons in this course.
Key words
- Design system
- A shared set of parts and rules that a product team uses to build its screens.
- Component
- One reusable piece of an interface, such as a button, a card, or a text input.
- Visual form
- The basic shape and style of a component: how round its corners are, whether it has a border, how deep it looks, and whether it is filled or outlined.
- Corner radius
- How round a corner is. A bigger radius makes a rounder corner. A radius of zero makes a sharp corner.
- Border
- A line drawn around the edge of a shape. It has a width and a style, such as solid or dashed.
- Elevation
- How high a surface appears to sit above the surface beneath it. Designers think of it as distance along an imaginary line that points out of the screen toward the viewer.
- Shadow
- A soft dark area drawn under a raised surface to make it look lifted.
- Fill and outline
- A filled shape has a solid background. An outlined shape has only a border, so the page shows through the inside.
- Scale
- A short, ordered list of named values, such as small, medium, and large.
- Token
- A named design value saved in one place so that every part of the product can reuse it.
What are the four visual form decisions?
Visual forms are not one setting. They are a group of style decisions that work together. Most design systems make the same four choices for their components.
Corner radius
How round each corner is. It can be none, a little rounded, quite rounded, or fully rounded like a pill.
Border
The outline around a shape. The team decides how thick it is and what style it uses, and then it uses that same border everywhere it is needed.
Elevation and shadow
How high a surface sits and how strong its shadow is. A higher level usually means the surface is in front of the content around it.
Fill or outline
Whether a component is solid or open. A filled button is a strong call to action. An outlined button is usually a quieter choice.
These four choices are small on their own. Together they decide whether a screen looks like one product or a set of unrelated parts. They also help a user tell at a glance which items can be pressed and which items are just content.
How does shape set the personality?
Shape carries mood. A soft rounded corner tends to look friendly and easy to approach. A sharp square corner tends to look exact and serious. Neither is better. The right choice depends on the product and the people who use it.
Fluent 2 makes a similar point: shapes help a screen feel personal and let people recognize parts quickly.
Tip
Before you pick any numbers, write down one or two personality words for your product, such as calm and precise, or playful and warm. Then check every shape decision against those words.
Why build a short, named scale?
The key idea is to limit the choices. Instead of letting each designer type any corner value they like, the team creates a scale: a small list of named steps. A designer picks a step by name, not by number.
Material Design 3 is a useful model. Its corner radius scale runs from none, at 0dp, through extra small, small, medium, large, and extra large, up to full, which means fully rounded corners. dp stands for density-independent pixel, a unit that keeps its size across different screens. Material also adds a few in-between steps in its newer version. A student team can start with four or five steps and add more only when a real need appears.
For elevation, a scale is just as useful. Material 3 describes elevation with levels rather than with free-form shadow settings. Higher levels are kept for states such as hover or drag.
Why does a short list matter so much? Fewer choices mean fewer near-duplicate values. One guide says it is always good to have a clear and limited set of sizes.
- 1
List the components
Write down every component that has a visible corner, border, or shadow. Buttons, cards, inputs, menus, and dialogs are common ones.
- 2
Group by size and job
Put small controls in one group and large containers in another. A small button and a big panel do not need the same rounding.
- 3
Name the steps
Give each group a name such as none, small, medium, and full. Use the same names across the whole product.
- 4
Give each step a value
Set one value per step. If your spacing grid uses 4px or 8px steps, choose radius values that fit the same grid so they come out as clean numbers.
Tip
Keep the names about the role, not the number. A name like medium stays useful even if you later change its value from 8px to 10px.
Why give each shape a job?
A scale is only useful when each step is used for a clear purpose. The shape of a component should tell the user what role it plays. Here are the common rules.
Small controls get smaller rounding
Lightning Design System notes that dense controls, such as buttons and input fields, work better with a smaller radius.
Large containers get larger rounding
Cards and modal windows take up more space, so they can use a larger radius. Material uses a medium step for cards and a larger step for dialogs.
Flat for page content, raised for overlays
Use elevation to separate things that float above the page, such as pop-up menus, from the content beneath them. Plain page content should usually stay flat.
Full rounding for pills and round buttons
Pill shapes and round icon buttons use the full step. Material maps its buttons to the full radius by default.
Elevation has a rule of its own. Do not add a shadow just to make something look nice.
Keep similar components at the same level. If every card sits at one elevation level, a user learns that cards behave the same way. If one card has a heavy shadow and the next has none, the user has to guess.
Nested shapes need extra care. When a rounded box sits inside another rounded box, the inner corner should be a little less round than the outer one. Telerik adds that a nested element should be smaller than its parent and should follow the parent's border style.
Tip
If a screen looks slightly off, check the nested corners first. Mismatched outer and inner corners are one of the most common causes of a shape that looks wrong, even when every value is in the scale.
How do you store the choices as tokens and write the rules down?
A scale on paper is not enough. Designers and developers need to use the same values in their own tools. The usual method is to save each step as a token. A token is a named value in one shared place. Components point to the token instead of holding a copy of the number.
Material 3 works this way. It has shape tokens for each corner step, and each component is mapped to one of them. Buttons map to the full step by default. If a product needs less rounding, the team can change the mapping to small or medium. The component stays the same, but its shape follows the new mapping.
This is why tokens matter. When a team changes the value behind one token, every component that uses that token updates. Without tokens, the same change has to be made by hand in every place, and some places will be missed.
- 1
Name each step once
Create one token for each radius and elevation step. Use the names from your scale.
- 2
Map each component to a step
Decide which step buttons, cards, inputs, menus, and dialogs use. Write the mapping in one table that everyone can find.
- 3
Write a usage rule
Add a short sentence for each step, such as use small for text inputs and use the raised level only for overlays.
- 4
Test a change
Change one token in a test file and check that the right components update. Then undo the change.
Tokens need rules, or people will still invent new values. Lightning Design System advises against mixing sharp and rounded corners inside one component.
Worked example: Material Design 3 shape and elevation
Material Design 3 is one of the clearest real examples of visual forms in use. Follow the steps below to see how one shape scale and one elevation scale are applied to real components. The values come from the official Material pages and from the Material cards specification.
- 1
Start with the shape scale
Material's corner radius scale includes none at 0dp, extra small at 4dp, small at 8dp, medium at 12dp, large at 16dp, extra large at 28dp, and full, which means fully rounded corners. The scale is shared by every component.
- 2
Map buttons to full rounding
Material's default mapping gives buttons the full step, so their ends look like pills. A product that wants less rounding can remap buttons to small or medium instead.
- 3
Map cards to medium rounding
The Material cards specification lists a 12dp corner radius. That is the medium step, so cards look softer than sharp boxes but less round than a pill button.
- 4
Map dialogs to a larger step with higher elevation
Dialogs sit in front of everything else on the screen, so they use a larger step. An unofficial Material reference lists dialogs at extra large, which is 28dp. Another community guide lists dialogs at medium. The two disagree, so check the official Material component page before you copy the value into your own system.
- 5
Set the elevation levels
Material 3 uses levels 0 to 3 for resting elements. Higher levels are reserved for interaction states.
- 6
Check the result
Look at the screen and ask whether the shape tells the user the role of each part. Buttons look like pills, cards look like soft panels, and dialogs look lifted above the page. That is the goal of the system.
Material also reminds designers that elevation is shown mainly through surface tone in its newer version. A higher level uses a slightly different surface color, and shadows are used only when extra separation is needed. That detail belongs to the Color lesson, but it shows that visual forms work together with other style rules.
Tip
When you study a real system, do not copy every value. Copy the logic: a small set of named steps, a clear purpose for each step, and one place where the mapping is stored.
Common mistakes to avoid
Picking values one component at a time
This is how a product ends up with 4px buttons, 12px cards, and 8px inputs. Each value may look fine alone, but together they feel unrelated.
Adding shadows for decoration
A shadow should show that something sits above the page. A shadow added only for looks makes the screen busy and blurs the meaning of elevation.
Mixing sharp and rounded corners
A component with one rounded corner and one sharp corner looks unfinished. Keep one radius style per component unless a special shape is intended.
Using the same radius for nested shapes
An inner box with the same radius as its outer box can look cramped at the corner. Subtract the padding to get the inner value.
Check your understanding
Read each scenario and pick the best answer. Think about the rules in this lesson, not just the first idea that comes to mind.
Quick check
Your team's app has buttons with 4px corners, cards with 12px corners, inputs with 8px corners, and three different shadow styles. Each was picked by a different designer. What is the best way to fix this using visual forms, and why?
Quick check
A settings page lists several content sections. A pop-up asking Delete this account? appears on top of the page. A new designer makes the sections raised with heavy shadows and makes the pop-up flat so it matches the page. Which change is the best fix?
Recap
Visual forms are shared style rules
They cover corner radius, borders, elevation and shadow, and fill versus outline. Together they give components one family look.
Limit the choices
Build a short named scale for each form decision, and use the names everywhere.
Match shape to role
Small controls get smaller rounding, containers get more, and only overlays get raised.
Store and document
Save each step as a token, map components to tokens, and write usage rules. Then a single change updates the whole product.
Next, you can study how the same kind of rule applies to components such as cards, inputs, and buttons in their own lessons. Each of those lessons builds on the idea that a shape should tell a user what a part does.
Sources
- Material Design 3: Shape corner radius scale
- Material Design 3: Shape overview and principles
- Material Design 3: Elevation overview
- Material Design 3: Applying elevation
- Material Design 3: Cards specifications
- Material Design 3: Introducing tone-based surfaces
- Android Developers: Material Design 3 in Compose
- Design for Native: The Basics of Elevation on Android
- Material 3 shape tokens reference (community GitHub skill, unofficial)
- Lightning Design System: Borders and Radius
- Telerik Design System: Guidelines for Using Border Radius
- Microsoft Fluent 2 Design System: Shapes
- Massachusetts Design System: Corner radius and elevation
- Utah Design System: Shape (rounded corners)
- Design Bootcamp (Medium): Building a consistent corner radius system in UI
- 92Learns: Border Radius Rules Every Designer Must Know
Last updated on 17 November 2026
Related lessons
- Design systemsPerforming a Visual Audit: Finding Where Your Interface Repeats and Differs
- Design systemsForms: The Shared Pattern for Collecting User Input Consistently
- Design systemsStyle in Design Systems: Repeatable Visual Choices That Give a Product One Look
- Design systemsCode Style: Shared Rules That Make Every Component Look Like One Hand Wrote It
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.