CSS Rounded Corners

Introduction

border-radius rounds the corners of any element. Use a single value for all four corners, or up to four for individual corners. Use 50% to make squares into circles, 999px for pill buttons.

Business problem

Business pressure: Product teams ship border-radius across dozens of surfaces — marketing, checkout, admin dashboards — and expect pixel parity without layout regressions that hurt conversion or trigger accessibility complaints.

• Conversion: Linear-style polish depends on consistent border-radius tokens; one-off CSS breaks trust on high-value flows.
• Velocity: Without a shared border-radius contract, every squad reinvents spacing, states, and responsive behavior.
• Risk: Visual debt compounds — refactors cost more than getting border-radius right in the design system.

Why this feature exists

Platform history: CSS added border-radius so authors could express layout and visual intent declaratively instead of table hacks, image slices, or JavaScript layout engines.

• Problem solved: Separates presentation from document structure while staying cacheable and themeable.
• Rejected alternative: Inline styles and per-page one-offs — unmaintainable at enterprise scale.
• Today: Design tokens and component APIs expose border-radius as the single source of truth.

Browser rendering perspective

Rendering impact: border-radius participates in style recalculation and may trigger layout, paint, or compositor work depending on which properties change.

• Chrome (Blink): WebKit GridNG resolves border-radius during style → layout → paint → composite.
• Firefox (Gecko): Servo-based stylo computes values; WebRender composites promoted layers.
• Safari (WebKit): Style resolver + GPU layer rules — test border-radius on real iOS devices, not just desktop Safari.

Internal browser workflow

Workflow: Selector match → cascade → computed values → layout tree → paint layers → composite. Changes to border-radius may invalidate earlier stages.

• DevTools: Elements panel → Computed → trace which rule won the cascade for border-radius.
• Layout: Toggle "Layout" badge in Rendering tab when debugging border-radius shifts.
• Layers: Check whether border-radius promoted a compositor layer unnecessarily.

Examples

Here's a focused example you can experiment with:

.card   { border-radius: 12px; }
.pill   { border-radius: 999px; padding: .25rem 1rem; }
.avatar { border-radius: 50%; width: 48px; height: 48px; }
.fancy  { border-radius: 12px 32px 12px 32px; }

Real production example

Production: Linear codifies border-radius in design tokens, Stylelint rules, and visual-regression CI so PRs cannot ship ad-hoc overrides.

• Pattern: Token pipeline emits CSS custom properties consumed by components.
• CI: Percy/Chromatic snapshots catch border-radius drift across themes.
• Observability: RUM correlates CLS/LCP with border-radius changes on hero surfaces.

Enterprise use case

Enterprise: Polaris, Carbon, and Atlassian Design System document border-radius in component APIs — not in page-level CSS.

• Multi-brand: White-label tenants override tokens, not raw border-radius rules.
• Dark mode: Scoped variable overrides propagate border-radius consistently.
• Governance: Architecture review for new border-radius patterns outside the system.

Accessibility considerations

A11y: border-radius must not remove focus visibility, break zoom, or convey state by color alone (WCAG 2.2).

• Focus: :focus-visible outlines survive border-radius resets — never outline: none without replacement.
• Motion: Honor prefers-reduced-motion when border-radius includes animation.
• Contrast: Visual effects from border-radius cannot be the only error indicator.

Performance considerations

Performance: border-radius can trigger reflow, expensive paint, or layer explosion — profile with DevTools Performance panel.

• CLS: Reserve space before border-radius loads or animates into place.
• Paint: Prefer transform/opacity over properties that repaint large regions.
• Selectors: Deep selectors targeting border-radius slow style recalc on large DOMs.

SEO considerations

SEO: border-radius affects LCP, CLS, and mobile usability — ranking signals tied to Core Web Vitals.

• LCP: Hero border-radius must not delay largest content paint.
• Mobile: Google mobile-first indexing sees the same border-radius as users on phones.
• Legibility: Text effects from border-radius must stay readable without zoom.

Scalability considerations

Scale: border-radius choices compound across micro-frontends, white-label tenants, and dark-mode variants.

• Tokens: Centralize border-radius values — avoid 47 slightly different radii.
• Micro-frontends: Shadow DOM and CSS modules isolate border-radius per team.
• Migration: Document deprecation path when border-radius API changes.

Common production issues

Production failures: Specificity wars, z-index stacks, and responsive rules that work in Chrome but break Safari — common border-radius incident patterns.

• Regression: Global reset broke border-radius on legacy iframe embeds.
• Theme leak: Dark-mode border-radius overrode light admin shell.
• Print: border-radius hid critical content in PDF exports.

Debugging guide

Debug: Chrome DevTools → Elements (computed styles), Layout panel, Rendering layers, Coverage for unused CSS affecting border-radius.

• Cascade: Find which stylesheet wins for border-radius.
• Forced state: :hov / :cls toggles in DevTools for hover/focus border-radius.
• Diff: Compare computed border-radius values across browsers in BrowserStack.

/* DevTools console — inspect computed border-radius */
const el = document.querySelector('.target');
console.log(getComputedStyle(el).getPropertyValue('/* property */'));

Anti-patterns

• Magic numbers: Hard-coded border-radius values instead of design tokens.
• !important escalation: Fighting specificity instead of fixing cascade order.
• Global overrides: Page CSS rewriting component border-radius from outside.

Trade-offs

• Benefit: Declarative border-radius keeps UI consistent and testable.
• Cost: Learning curve and cross-browser edge cases for advanced border-radius.
• Trade-off: Pure CSS border-radius vs JS libraries — simpler CSS wins until a11y/complexity demands JS.

Architecture review questions

• Are border-radius values sourced from design tokens, not one-off literals?
• Does border-radius pass axe and keyboard navigation on interactive targets?
• What is the CLS impact if border-radius assets load late?
• How does border-radius behave at 200% zoom and in high-contrast mode?
• Is there a Safari/iOS verification checklist for border-radius?
• Can we remove unused border-radius rules flagged by Coverage?

Interview questions

Hands-on exercise

Exercise: Implement border-radius in a component that passes axe, Lighthouse performance ≥ 90, and a visual-regression snapshot on light/dark themes.

• Deliverable: Component + token definitions + Try It demo.
• Verify: Safari iOS + Firefox + Chrome computed style parity.
• Stretch: ADR documenting border-radius trade-offs vs alternatives.

Staff engineer notes

• border-radius is an engineering decision — measure it with Web Vitals and a11y audits, not screenshots alone.
• Tokenize border-radius early; retrofitting 200 components costs quarters.
• When border-radius breaks in Safari, check prefixes, stacking contexts, and subpixel rounding — not just syntax.

Try it yourself

Edit the CSS panel — the preview updates live. Use DevTools Performance and Accessibility panels to validate.

Summary

Rounded Corners separates tutorial demos from production engineering: tokenized values, cross-browser verification, Web Vitals-safe animation, and WCAG-compliant states — the patterns Linear and peers enforce via design systems and CI.

Key takeaways

• border-radius works on any element, including images.
• 50% turns squares into circles.
• 999px (or 9999px) creates perfect pill shapes regardless of size.