UI Components

Avatar

User avatar with image support, initials fallback, multiple sizes, and AvatarGroup for overlapping stacks

Quick Preview

XSSMMDLGXL

Installation

// Copy the Avatar component from
src/components/ui/Avatar.tsx

Usage

import { Avatar, AvatarGroup } from '@/components/ui/Avatar'

// With initials fallback
<Avatar initials="JD" size="md" />

// With image
<Avatar
  src="https://example.com/photo.jpg"
  alt="Jane Doe"
  size="lg"
/>

// Grouped avatars
<AvatarGroup
  avatars={[
    { initials: "A" },
    { initials: "B" },
    { initials: "C" },
    { initials: "D" },
  ]}
  max={3}
/>

Examples

With Image (broken image shows initials)

With image

Initials fallback

AvatarGroup — Overlapping Stack

ABCD+1

In Context — User Row

Jane Doe

jane@example.com

Prompt Preview

Copy a prompt that recreates this UI

Paste this into your AI coding assistant to generate code that closely matches the reference, including color, size, shape, typography, spacing, and polish.

Copy-ready AI prompt

Starts from the current visual reference and project constraints.

Build a ui component named Avatar in React/Next.js.
Goal: recreate the same overall UI and behavior as the Avatar reference from a component gallery.
What it needs to communicate: User avatar with image support, initials fallback, multiple sizes, and AvatarGroup for overlapping stacks.

Project constraints:
- Use Next.js 16.2.6 with the App Router, React 19, TypeScript strict mode, and Tailwind CSS v4.
- Do not create a tailwind.config.js file. Use Tailwind v4 utilities and CSS variables where design tokens are needed.
- If you are implementing this inside the same project, use the Prompt font via next/font/google. If not, use the closest equivalent typeface.
- Return production-ready code with imports, responsive behavior, keyboard accessibility, and polished empty, hover, focus, active, and disabled states where relevant.
- Match the reference closely: color palette, spacing scale, border radius, shadows, icon scale, typography hierarchy, and motion timing.

Component-specific expectations:
- Keep the API concise and reusable.
- Make visual states feel polished and consistent across variants and sizes.
- Avoid unnecessary dependencies unless the behavior truly requires them.
- No explicit color literals were found in the examples. Match the live reference and the project accent color when appropriate.

Props to support:
- src: string — Image URL
- alt: string — Alt text for the image
- initials: string — Fallback text when no image (max 2 chars)
- size: "xs" | "sm" | "md" | "lg" | "xl" — default "md" — Avatar size
- className: string — Additional CSS classes

Reference usage patterns:
- With Initials

```tsx
<Avatar initials="JD" size="lg" />
```

- Avatar Group

```tsx
<AvatarGroup avatars={[{initials:"A"},{initials:"B"},{initials:"C"}]} max={3} />
```

Feature expectations:
- 5 sizes: xs, sm, md, lg, xl
- Image with broken-image fallback
- Initials fallback with primary color
- AvatarGroup with overlap + overflow counter
- Server Component

Output requirements:
- Return complete code, not pseudocode.
- Include all necessary imports and helper types.
- Keep the implementation accessible, responsive, and visually finished.
- Match the reference for color, size, shape, typography, spacing, and interaction states as closely as possible.
- If multiple files are needed, organize them cleanly and explain the file structure briefly.

Tweak only product-specific copy or data after the first generation pass.

Props

Prop	Type	Default	Description
`src`	`string`	-	Image URL
`alt`	`string`	-	Alt text for the image
`initials`	`string`	-	Fallback text when no image (max 2 chars)
`size`	`"xs" \| "sm" \| "md" \| "lg" \| "xl"`	`"md"`	Avatar size
`className`	`string`	-	Additional CSS classes

Features

✓5 sizes: xs, sm, md, lg, xl
✓Image with broken-image fallback
✓Initials fallback with primary color
✓AvatarGroup with overlap + overflow counter
✓Server Component