CSS corner-shape lets you draw squircles, bevels, notches and scoops instead of only round corners. The catch so far: you always needed two declarations, one for the radius and one for the shape. Chrome 160 fixes that with a set of corner shorthand properties that set border-radius and corner-shape together, per corner or per edge, in a single line.
This guide explains the new properties, shows practical examples, and covers how to ship them safely while other browsers catch up. Sources: the Chrome Platform Status entry, the Chrome 160 feature list and the CSS Borders and Box Decorations Level 4 draft.
The problem with two properties
Today, a squircle in the top-left corner looks like this:
.card {
border-top-left-radius: 20px;
corner-shape: squircle round round round;
}
That works, but it splits one design decision across two properties, and per-corner shapes are easy to get wrong. The CSS Working Group resolved to add a shorthand that combines both, and Chrome 160 implements it.
What ships in Chrome 160
According to the Chrome Platform Status entry, Chrome 160 implements:
- the
cornershorthand for all four corners, - per-corner sub-shorthands:
corner-top-left,corner-top-right,corner-bottom-left,corner-bottom-right, - physical edge shorthands such as
corner-topandcorner-bottom, - logical edge shorthands such as
corner-block-startandcorner-block-end, - and
cornersas a compatibility alias forcorner.
In the spec, corner accepts a corner-shape value and a border-radius value in either order, and each per-corner property accepts one shape and one radius.
Basic usage
/* one corner, one line */
.badge {
corner-top-left: 20px squircle;
}
/* all four corners */
.card {
corner: 24px squircle;
}
/* order doesn't matter */
.card-alt {
corner: squircle 24px;
}
The Chrome entry gives exactly this before/after for a single corner: two declarations become corner-top-left: 20px squircle;.
Practical patterns
A ticket with notched edges
.ticket {
background: #fff7e6;
padding: 1.5rem 2rem;
corner: 16px round; /* base: rounded */
corner-top-right: 24px notch; /* override one corner */
corner-bottom-right: 24px notch;
}
Because the per-corner properties are shorthands too, the usual cascade rules apply: set a base with corner, then override individual corners.
Edge shorthands for tabs
Tabs usually shape only the top edge:
.tab {
corner-top: 12px squircle; /* top-left and top-right together */
}
Logical properties for international layouts
If your UI supports vertical writing modes or right-to-left languages, logical edge shorthands follow the writing direction:
.callout {
corner-block-start: 18px bevel;
}
Design tokens with custom properties
Shorthands make tokens simpler because a single variable can hold both values:
:root {
--corner-card: 20px squircle;
--corner-button: 999px round;
}
.card { corner: var(--corner-card); }
.button { corner: var(--corner-button); }
Ship it safely: progressive enhancement
At the time of writing, Chrome 160 is not yet on stable. The Chromium release schedule lists its earliest beta for 2 December 2026. The Chrome Platform Status entry describes Firefox’s position as positive and WebKit as in development, so for now treat the shorthand as an enhancement.
The safest approach is three layers:
.card {
/* 1. everyone: plain rounded corners */
border-radius: 20px;
}
/* 2. browsers with corner-shape but not the shorthand */
@supports (corner-shape: squircle) {
.card {
corner-shape: squircle;
}
}
/* 3. browsers with the new shorthand */
@supports (corner: 20px squircle) {
.card {
corner: 20px squircle;
}
}
Browsers without corner-shape just render a rounded rectangle, which is the right fallback for almost every design. Layer 3 is optional; layer 2 already gives the shape. The shorthand mostly pays off in new code where you want readable, per-corner styling.
Watch out for reset order
Like border-radius, a shorthand resets its longhands. If you write a per-corner border-*-radius before corner, the corner declaration wins. Put the shorthand first and overrides after it.
Testing in Chrome
- Install Chrome Canary or Dev (or Beta once 160 reaches it).
- Open DevTools, select an element and type
corner: 20px squirclein the Styles pane. If it is not crossed out, the property is supported. - Check
CSS.supports('corner', '20px squircle')in the console for a quick yes/no.
console.log(CSS.supports('corner', '20px squircle')) // shorthand
console.log(CSS.supports('corner-shape', 'squircle')) // underlying feature
The Chrome entry also links a sampler page showing the shorthands in action.
Other front-end items in Chrome 160
The same release lists a few features worth knowing if you build UI:
CSSPseudoElement.selectorTextreturns the selector string for a pseudo-element from script.- View Transitions
shadowRootsoption:startViewTransition()can now find participating elements inside specified shadow roots, which helps web component libraries. - SVG Path Data API:
getPathData(),setPathData()andgetPathSegmentAtLength()give structured access to an SVG path without parsing thedattribute yourself. - Case-sensitive anchor matching in quirks mode, aligning Chrome with Safari, Firefox and the HTML spec.
Each is documented in the Chrome 160 feature list.
Accessibility and design notes
- Corner shapes are visual only; they don’t change the element’s box or hit area. Keep focus outlines visible and test them with your new shapes.
notchandscoopshapes cut into the box. Make sure padding keeps text clear of the cut-out.- Keep shapes consistent across a component family. A token per role (card, button, chip) avoids mixing styles.
Takeaway
The new corner shorthands don’t add new rendering abilities, but they make shaped corners far easier to write and maintain: corner: 20px squircle instead of two properties, plus per-corner and per-edge versions. Start using them behind @supports with a plain border-radius fallback, and they will light up as Chrome 160 and other browsers ship. Read the spec draft for the full grammar.
