Who this helps
- Designers styling cards and buttons
- Developers learning corner order
Developer Design Utility
Adjust CSS border-radius values for cards, buttons, images, and modals with a live preview, then generate shorthand CSS, individual properties, and inline style code.
Use the same value for all corners or adjust each corner separately to create the UI shape you want.
Uncheck this option to set each of the four corners separately.
Use px for general UI elements, and % for circular images or avatars.
The rounded corner values you set are reflected here in real time.
Quickly apply commonly used card, button, and image shapes.
Use the code below in a CSS file, component style, or inline style.
Select your settings, then click Generate CSS Code.
Adjust four corner radii together or separately, preview their shape and generate CSS. Choose px, rem or percent, then copy a uniform shorthand or a four-corner rule.
Choose px, rem or percent.
Keep linked corners enabled to adjust all four with any corner control.
Turn linking off to edit each corner independently.
Generate CSS; later edits update the output.
Copy or download and test on the actual component dimensions.
Equal corners use one value in the main rule.
Four values run clockwise from top-left; the output also shows individual corner declarations.
Controls use a 16px conversion basis. At a 20px root font, 1rem renders as 20px.
Equal corners become one value; other shapes use four values in top-left, top-right, bottom-right, bottom-left order. Controls range from 0 to 120 for px/rem mode and 0 to 50 for percent mode. In rem mode the number is divided by 16 and rounded to two decimal places.
Values are processed in the browser without upload or saved history. CSS files contain the selected radii.
Add depth around the same shape.
Make a radius change with viewport width.
With linked corners enabled, yes. Disable linking to give corners different values.
The tool divides the control value by 16: 16 produces 1rem. The actual size depends on the root font of the destination page.
Not necessarily. Apply the component's appropriate clipping or overflow rules separately.