UI Library for Design Engineers. Animated components and effects you can copy and paste into your apps. Free. Open Source.
Magic UI Component Reference
Purpose
Use this document to choose the right Magic UI component and avoid integration mistakes before implementation.
Install Contract
- Initialize shadcn once per project:
npx shadcn@latest init
- Add components via registry:
npx shadcn@latest add @magicui/<component-slug>
- Default import path is usually:
import { ComponentName } from "@/components/ui/<component-slug>"
If the project does not use @/ aliases, adapt import paths to local conventions.
Families
Layout And Social Proof
marqueeavatar-circlesbento-grid
Use for logo rails, testimonial movement, and feature grids.
Hero And Visual Anchors
globewarp-backgroundanimated-grid-patternretro-grid
Use one primary visual anchor per hero to keep hierarchy clear.
Text Motion
blur-fadetext-animateword-rotatesparkles-texttyping-animation
Use when product messaging needs motion emphasis.
Buttons And CTA Emphasis
shiny-buttonshimmer-buttonrainbow-buttonripple-button
Keep CTA style consistent within one page section.
Ambient Effects
particlesflickering-griddot-patterngrid-patternlight-rays
Use these as supporting layers, not primary content.
Integration Notes
- Some components require additional dependencies (for example
cobe,motionforglobepatterns). - Some components require global CSS keyframes (for example
marqueevariants). - Prefer prop-level customization before editing generated source.
- If customization grows large, wrap the component in a local section component rather than editing registry output directly.
Quality Checks
- Accessibility: interactive controls remain keyboard-accessible.
- Readability: animated backgrounds do not reduce text contrast.
- Responsiveness: no horizontal overflow on small screens.
- Performance: avoid stacking multiple expensive animated backgrounds in one viewport.