designmotionhq

visual

Border Radius

Same card. One looks off, one looks expensive. The gap is one CSS rule.

Watch on Instagram

Key insights

  • Nested corners follow math: inner radius = outer radius − padding. When the concentric curves line up, a card reads as intentional instead of "off."
  • Pull every value from one radius scale (4 · 8 · 12 · 16 · 24) instead of picking numbers per component — consistency is what makes UI look expensive.
  • Scale radius with element size: tooltips ~4px, inputs ~8px, cards ~12px, modals ~16px, panels ~24px. Bigger surfaces earn bigger corners.
  • Radius carries personality — small/sharp reads corporate, large/round reads friendly. Pick the range that matches your brand's tone.
  • The difference is subtle but felt: off-scale, mismatched corners are exactly what separates "something's wrong here" from polished.

Do / Don't

  • Do: Derive the inner radius from the outer radius minus padding so nested corners stay concentric.
  • Do: Commit to a single radius scale and reuse it across every component.
  • Do: Scale radius with element size — larger surfaces get larger corners.
  • Don't: Pick radius values at random for each component.
  • Don't: Nest a rounded card inside another without adjusting the inner corner.
  • Don't: Mix a playful, oversized radius into a brand meant to feel serious — or the reverse.

Want Claude to build this correctly?

UX Engine gives Claude Code the senior-designer reasoning behind every pattern.

The Design System Blueprint

An 11-page visual guide to consistent, scalable UI: colors, typography, spacing, components, motion.

Get the Blueprint — free

The PDF, plus emails about new patterns and my tools. Unsubscribe anytime.

Related patterns