Border radius utilities round an element's corners, from subtly softened edges to fully circular shapes. This lesson covers the full radius scale and per-corner rounding for more complex shapes.
What Are Border Radius Utilities?
rounded-* utilities map to the CSS border-radius property, offering a scale from rounded-sm (barely rounded) to rounded-full (fully circular or pill-shaped, depending on the element's aspect ratio).
Rounded corners are one of the fastest ways to make an interface feel modern and approachable, and Tailwind's consistent scale keeps rounding uniform across buttons, cards, and inputs.
rounded-* sets radius on all four corners at once.
Side variants (rounded-t-*, rounded-r-*) round both corners on one side.
Corner variants (rounded-tl-*, rounded-br-*) round a single specific corner.
rounded-full creates a perfect circle on square elements, or fully pill-shaped edges on rectangles.
Border Radius Cheatsheet
The full rounding scale and common shape patterns.
Class
Radius
Typical Use
rounded-none
0
Sharp, squared-off corners
rounded-sm
0.125rem
Subtle softening for tables or inputs
rounded
0.25rem
Default light rounding
rounded-md
0.375rem
Standard button/card rounding
rounded-lg
0.5rem
Popular card and modal rounding
rounded-xl
0.75rem
More pronounced rounding for hero cards
rounded-2xl
1rem
Large, soft rounding for feature panels
rounded-full
9999px
Circles (avatars) or pill shapes (badges)
rounded-t-lg
Top corners only
Rounding a card's top above a flat footer
Circles vs Pill Shapes
rounded-full produces different visual results depending on the element's shape: on a square element (equal width and height), it creates a perfect circle. On a wide rectangular element, it creates a pill/capsule shape instead.
When combining elements visually, like a search input attached to a button, or a card with a flat-bottomed image and rounded card corners, per-corner rounding utilities let you round exactly the corners that need it.
The input rounds only its left corners and the button rounds only its right corners, so together they look like one seamless control.
Rounded Images Need overflow-hidden
As covered in the Overflow lesson, applying rounded-* directly to an <img> works fine, but if the image is wrapped in a container div that also needs rounding (for a border or overlay), remember to add overflow-hidden to the wrapper.
Applying rounded-full to a non-square element expecting a circle, and getting a pill shape instead.
Forgetting overflow-hidden on a rounded wrapper div, so its child image ignores the rounded corners.
Mixing inconsistent radius values across similar components (some rounded-md, others rounded-lg) without a clear system.
Not adjusting per-corner rounding when merging two adjacent elements into a single visual control.
Using excessive rounding (rounded-2xl or higher) on small UI elements like checkboxes, which can look disproportionate.
Key Takeaways
Border radius utilities scale from rounded-none to rounded-full, matching a consistent design scale.
rounded-full creates circles on square elements and pills on rectangular elements.
Per-side and per-corner utilities allow precise rounding for merged or adjacent UI elements.
Rounded wrapper containers need overflow-hidden to properly clip rounded child content.
Standardizing radius values (e.g. always rounded-lg for cards) keeps a design system visually consistent.
Pro Tip
Pick two or three radius values maximum for your entire design system, for example rounded-md for inputs/buttons and rounded-xl for cards, and apply them consistently instead of picking a new radius per component.
You now understand Tailwind's border-radius utilities. Next, learn ring utilities for building accessible focus indicators.