
Set 12px card corners, pill buttons and a chat bubble with one sharp corner, then copy the CSS values into shared design tokens.
A design review turns up three different corner styles in one product: cards at 8px, buttons at 6px, and a modal at something that looks like 14px. Nobody chose it, it accumulated. Before you write the next component, settle a short list of radius values and name them. The Border Radius Generator gives you four sliders and a live preview so you can compare values by eye, then copy a ready line of CSS.
The result for this example is a small token set: 12px for cards, a pill value for buttons, 12px on the top corners only for tabs, and 16px with one 4px corner for chat bubbles.
There is a "Link all corners" switch and four sliders labelled Top Left, Top Right, Bottom Left and Bottom Right, each from 0 to 200 px. With linking on, moving one slider moves all four. A preview square about 192 pixels wide shows the shape as you drag, and a code box shows a single line such as border-radius: 12px 12px 12px 12px; with a Copy CSS button underneath.
The output order follows CSS shorthand: top-left, top-right, bottom-right, bottom-left. Note that the sliders are laid out with bottom-left before bottom-right, but the generated line is always in the CSS order, so read the code box rather than the slider position. Values are always in pixels, and every corner is a simple circular curve.
Keep the set tiny: perhaps four to six tokens in total. Every extra value is another thing someone will use slightly wrongly.
When a rounded element sits inside another with padding, the inner radius should be the outer radius minus the padding. A 12px card with 4px padding around an image wants an 8px image radius. A card with 16px padding can use a small inner radius such as 0 to 4px. When the inner and outer corners use equal values, the gap looks fatter at the corners than along the sides, and the nested shape feels slightly off.
You can check this in the generator by building the outer and inner values separately and holding the preview next to your layout.
The preview is a fixed square, not your component. A radius of 12px on a 192px square is gentle, while the same 12px on a 40px chip is nearly a pill. Always judge a value against the real element size. Browsers also scale radii down automatically if two neighbouring corners together exceed the side length, which is why a very large value on a small box looks like a full pill or circle, not an error.
The slider stops at 200 px. That is plenty for anything under 400 px tall. For a full pill on any size, edit the copied number by hand.
Uneven radii are not only for decoration. A dropdown that opens beneath a button can carry square top corners and rounded bottom ones, so it looks attached. A notification stack can use rounded top corners on the first item and rounded bottom corners on the last. An image on the edge of the screen can round only the inner side. Each of these is a four-number line the generator can produce.
The tool's own tip points to a more organic look from deliberately uneven corners. If you try that for a hero shape, remember that the generator makes circular corners only, so more complex blob outlines need custom CSS.
Reading slider positions instead of the code box. The order is top-left, top-right, bottom-right, bottom-left.
Picking radii at the preview size and never testing them on a small button or a large card.
Using different values for the same role in different files. Put the value in a token or a CSS variable once.
Copying a 200px value into a button and calling it a pill. It works on short elements, but a 9999px value is more robust.
Forgetting that images need the radius too, or an overflow-hidden wrapper, otherwise the image corners poke through a rounded card.
Radius rarely travels alone. The Box Shadow Generator pairs with it for card elevation, and our post on shadows that stay subtle gives a restrained starting point. The Gradient Generator covers button fills, and the Color Converter turns hex values into the formats a token file expects. More utilities are in the design tools category.
The generator runs in your browser, and each use counts toward your 10 trial usages a day. Ten minutes spent settling radius values once is cheaper than a review comment on every pull request.
Which part of your design system needs a worked example next, spacing, shadows or colour tokens? Tell us on the contact page.