CSS Animations

Introduction

Animations use @keyframes to define multi-step motion that runs continuously or on demand. Where transitions handle state changes, animations handle sequenced motion.

Business problem

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

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

Why this feature exists

Platform history: CSS added @keyframes animations 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 @keyframes animations as the single source of truth.

Browser rendering perspective

Rendering impact: @keyframes animations participates in style recalculation and may trigger layout, paint, or compositor work depending on which properties change.

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

Internal browser workflow

Workflow: Selector match → cascade → computed values → layout tree → paint layers → composite. Changes to @keyframes animations may invalidate earlier stages.

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

Syntax

Define keyframes, then apply them with animation:

@keyframes pulse {
  0%, 100% { transform: scale(1); }
  50%      { transform: scale(1.05); }
}
.dot { animation: pulse 1.5s ease-in-out infinite; }

Examples

A loading spinner — pure CSS:

@keyframes spin { to { transform: rotate(360deg); } }
.spinner {
  width: 32px; height: 32px;
  border: 3px solid #e2e8f0;
  border-top-color: #4f46e5;
  border-radius: 50%;
  animation: spin .8s linear infinite;
}

Real-world use

Notification bell badge bounces with @keyframes; loading spinners spin; tooltips fade in with a 150ms ease-out. Most micro-interactions are 5 lines of CSS.

Real production example

Production: Shopify codifies @keyframes animations 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 @keyframes animations drift across themes.
• Observability: RUM correlates CLS/LCP with @keyframes animations changes on hero surfaces.

Enterprise use case

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

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

Accessibility considerations

A11y: @keyframes animations must not remove focus visibility, break zoom, or convey state by color alone (WCAG 2.2).

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

Performance considerations

Performance: @keyframes animations can trigger reflow, expensive paint, or layer explosion — profile with DevTools Performance panel.

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

SEO considerations

SEO: @keyframes animations affects LCP, CLS, and mobile usability — ranking signals tied to Core Web Vitals.

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

Scalability considerations

Scale: @keyframes animations choices compound across micro-frontends, white-label tenants, and dark-mode variants.

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

Common production issues

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

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

Debugging guide

Debug: Chrome DevTools → Elements (computed styles), Layout panel, Rendering layers, Coverage for unused CSS affecting @keyframes animations.

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

/* DevTools console — inspect computed @keyframes animations */
const el = document.querySelector('.target');
console.log(getComputedStyle(el).getPropertyValue('/* property */'));

Best practices

• Respect prefers-reduced-motion.
• Use animation-fill-mode: both to keep end state.

Anti-patterns

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

Trade-offs

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

Architecture review questions

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

Interview questions

Hands-on exercise

Exercise: Implement @keyframes animations 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 @keyframes animations trade-offs vs alternatives.

Staff engineer notes

• @keyframes animations is an engineering decision — measure it with Web Vitals and a11y audits, not screenshots alone.
• Tokenize @keyframes animations early; retrofitting 200 components costs quarters.
• When @keyframes animations 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

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

Key takeaways

• @keyframes defines the motion; animation applies it.
• Loops, fills, delays — all configurable.
• Always honor reduced motion.