# Skeleton Screen

A skeleton screen reserves the shape of forthcoming content to signal progressive loading and reduce disruptive layout shifts during an initial fetch.

- Type: artifact
- Domain: Experience & interface
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/skeleton-screen/>)

## What it means

A skeleton screen is a simplified, noninteractive representation of the layout that will replace it. Blocks or lines approximate stable content structure while data loads. Unlike a spinner, it indicates where content will appear; unlike fake content, it should not be mistaken for usable information or controls.

## Why it matters

Skeletons can make an initial load feel continuous and reserve space that reduces movement when real content arrives. They work when final structure is predictable and data arrives soon. They do not improve network speed, so pair them with caching, streaming, and rendering optimization.

## When to use it

Use skeletons for initial loads of cards, lists, profiles, or dashboards whose geometry is known. Prefer retained content for refreshes, determinate progress for measurable operations, and a simple status indicator when final layout is unpredictable or the wait may be long.

## How it works

1. Model only stable structure and approximate text or media regions.
2. Reserve final dimensions to minimize layout shift and a second reflow.
3. Mark the region busy and hide meaningless placeholder shapes from the accessibility tree.
4. Use restrained animation, honor reduced motion, and avoid expensive paint effects.
5. Replace sections coherently and transition to empty, error, or loaded states without flashing.

## A practical example

A news feed renders fixed-height card shells with image and text regions matching loaded cards. The feed exposes loading status, but gray blocks are hidden from assistive technology. Reduced-motion users see static shapes, and an empty response becomes a proper empty state.

## Where it breaks

Skeletons mislead when layout is unknown, waits are long, or geometry differs from content. Shimmer can distract, trigger motion sensitivity, and increase rendering cost. A skeleton can also hide severe latency, so teams must still measure completion time and abandonment.

## Common mistakes

- Building a detailed fake interface that appears clickable
- Using skeletons on refresh when stable content could remain
- Animating shimmer without reduced-motion and performance safeguards

## Sources

1. [Skeleton](<https://atlassian.design/components/skeleton>) — Atlassian Design System · Institutional design system
2. [Loading pattern](<https://v10.carbondesignsystem.com/patterns/loading-pattern>) — Carbon Design System · Institutional design system

## Related topics

- [Loading State](<https://wiki.soroush.uk/topic/loading-state/>)
- [Empty State](<https://wiki.soroush.uk/topic/empty-state/>)
- [Reduced Motion](<https://wiki.soroush.uk/topic/reduced-motion/>)
