pattern-library checked
Carbon Design System Empty States Pattern
Distinguishes no-data, user-action, and error-management empty states, including no-results feedback after search and filter actions.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Dead-end empty state | Flag dead-end empty state when a blank area lacks a specific object name, cause, and reachable next action. | A blank or actionless content region is not a valid terminal state. | Carbon distinguishes no-data, user-action no-results, and error-management empty states, which helps diagnose dead-end blanks. |
| Empty state | Choose empty state only after the system knows the area is legitimately empty rather than loading, filtered, or failed. | The empty state identifies what is absent and why the absence is expected. | Carbon distinguishes no-data, user-action no-results, and error-management empty states and describes matching the state to cause. |
| No-results recovery | Choose no-results recovery whenever search or filters can produce an empty set. | The UI must explain that no matches were found and identify the active constraints. | Carbon distinguishes user-action empty states such as no search results from first-use empty states and system issue states. |
Evidence Role
This source is treated as pattern-library evidence. Use it to validate the decision rules above, not as a visual style reference.
Publisher: IBM Carbon Design System. Last checked: .