# Avatar and Avatar Group

An avatar visually represents a person or entity, while an avatar group compacts several representations into a recognizable set.

- Type: framework
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-10-07
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/avatar-and-avatar-group/>)

## What it means

An avatar is a small image, illustration, initials treatment, or fallback used to represent a person, team, agent, or other product entity. An avatar group displays several avatars together, often with overlap and an overflow count, to communicate membership or participation rather than full identity details.

## Why it matters

Avatars support rapid recognition in collaborative and account-oriented interfaces, but images and initials are not reliable unique identifiers. A consistent component provides fallbacks, accessible naming, privacy handling, presence separation, and predictable behavior at constrained sizes.

## When to use it

Use an avatar when entity recognition or ownership is relevant, normally alongside a visible name when identification matters. Use a group for a compact preview of participants; use a textual list or dedicated people view when users must identify, compare, or act on every member.

## How it works

1. Define which entity types the system represents and whether shape or treatment distinguishes them.
2. Select an image, approved illustration, initials, or neutral fallback with predictable priority.
3. Provide a name when the avatar conveys identity and hide it from assistive technology when adjacent text already does so.
4. Separate presence, status, and actions from the identity image and expose their meanings in text.
5. For groups, set a visible limit, preserve a stable order, and provide access to the complete membership.

## A practical example

A project header shows three collaborator avatars followed by “+8.” Selecting the group opens a named member list, failed profile images fall back to initials, and screen readers do not hear each identity twice because visible names provide context.

## Where it breaks

Photos may be unavailable, sensitive, culturally unsuitable, or hard to distinguish at small sizes. Initials collide, generated colors are not identities, overlap hides detail, and presence indicators can imply certainty that the underlying status cannot provide.

## Common mistakes

- Using an avatar alone where users must distinguish people with similar images or initials.
- Omitting a fallback for missing or failed images.
- Giving decorative avatars redundant accessible names beside visible identity text.
- Showing an avatar group without a way to discover hidden members.

## Sources

1. [Avatar](<https://atlassian.design/components/avatar>) — Atlassian Design System · Institutional design system
2. [Avatar](<https://fluent2.microsoft.design/components/web/react/core/avatar/usage>) — Fluent 2 Design System · Institutional design system

## Related topics

- [Badge, Chip, and Tag](<https://wiki.soroush.uk/topic/badge-chip-and-tag/>)
- [Component Library](<https://wiki.soroush.uk/topic/component-library/>)
- [Accessibility](<https://wiki.soroush.uk/topic/accessibility/>)
