Shadcn Empty State Blocks

Empty state blocks built with shadcn/ui: no results, no data, first run, syncing, access denied, offline and verification screens with soft illustrations, skeleton previews and clear next actions.

Empty State 1 Pro

Survey responses card with title and description, containing a centered empty state with a round chart icon, a no responses message and an outline Create survey button.

Empty State 2 Pro

No search results state under a soft radial glow, showing three overlapping avatars, a no engineers found title, the searched name with an invite link, and a Clear search button that shows a toast.

Empty State 3 Pro

All files view with type tabs, a search field and Filters button above a bordered empty state with orbiting file icons on rings, a message that follows the search, Clear search and New document buttons.

Empty State 4 Pro

Contact import progress state with three skeleton contact cards, floating avatars on concentric rings, an importing message, and Notify me and Refresh page buttons that show toasts.

Empty State 5 Pro

Orders header with Filters, Export and Add order buttons over a table column row, followed by a folder and search illustration, a no orders match message and a Search again button.

Empty State 6 Pro

Centered no data state with a dashed square database icon, a two line message, and Learn more and Add new item buttons that stack full width on mobile.

Empty State 7 Pro

Access denied state with a red lock icon inside two rings, a billing workspace permission message, a Back to dashboard button and a Request access button that switches to a disabled Request sent state.

Empty State 8 Pro

Account setup prompt with a badge icon, a verification message and a Complete registration button, followed by a muted card listing three numbered activation steps.

Empty State 9 Pro

Minimal reports state with two tilted document outlines in a muted circle and a two line message explaining that reports appear after the first billing cycle closes, with no buttons.

Empty State 10 Pro

AI agents first run state with three skeleton agent cards, the side cards faded and hidden on mobile, a Build your AI workforce title, description and an Add agent button.

Empty State 11 Pro

No files found state on a faded grid background with three tilted file cards labeled DOC, PDF and XLS, a message naming the search term and a Clear filters button.

Empty State 12 Pro

Domains first run state on a grid background with two skeleton domain rows, a no domains yet title, a short benefit message, and Add domain and See tutorial buttons.

Empty State 13 Pro

Waitlist empty state with two stacked placeholder member rows showing decline and approve slots, a no one is waiting title, an explanation and a View Products button.

Empty State 14 Pro

Command style search card with a prefilled search input and shortcut keys, a dotted no tools found area with Browse all tools button, and two footer actions with keyboard shortcuts.

Empty State 15 Pro

Compact no projects state with a folder code icon, a short workspace message and small Create project and Import project buttons side by side.

About Shadcn UI Empty State Blocks

An empty state is what a screen shows before there is any data, when a search returns nothing, or when something blocks the content, such as a missing permission or a lost connection. Instead of a blank area, it tells people what belongs there and what to do next. These 22 shadcn empty state blocks cover first run screens, no results views, access and offline errors, setup prompts and illustrated feature cards.

Like the rest of our shadcn blocks, they are built with React, TypeScript and Tailwind CSS on top of shadcn ui components, mainly the Empty component together with Button, Card, Skeleton, Avatar, Tabs and InputGroup. Illustrations are drawn with Tailwind classes and lucide-react icons instead of image files, so they follow your theme tokens in light and dark mode and sit naturally next to other shadcn components in your dashboard.

Key Elements of an Empty State

  • Clear title: names the situation in a few words, such as “No projects yet” or “You are offline”.
  • Helpful description: one or two sentences on why the area is empty and what will appear once the user acts.
  • Visual cue: an icon, avatar stack or small illustration that makes the state recognizable at a glance.
  • Primary action: the one step that fills the screen, like Create project, Add domain or Try again.
  • Recovery path: a Clear search, Clear filters or Go back button when the emptiness comes from the user’s own query or access level.

Where and Why to Use Empty State Blocks

Every list, table and widget in an app has a moment where it has no data. If that moment is a blank box, users assume something is broken. A well designed empty state keeps them oriented, explains the feature and moves them toward the action that makes the product useful. Because these blocks are standard shadcn components styled with Tailwind CSS, you can drop them into cards, tables and pages without fighting the rest of your shadcn ui layout.

  • First run and onboarding: invite new users to create their first project, agent or domain.
  • Search and filters: explain that nothing matched and offer a quick way to reset the query.
  • Dashboard widgets: fill a chart or report card that has no data yet with a message and a call to action.
  • Permissions and errors: show access denied or offline screens that tell users how to recover.
  • Background jobs: keep users informed while an import or sync is still running.
  • Feature promotion: use an illustrated card to describe a feature before the user has turned it on.

Empty State Blocks in This Collection

First run and no data

  • Empty State 1: Use it for a chart card that has no data yet, keeping the card title visible so the layout of the dashboard does not jump.
  • Empty State 6: A neutral fallback for any list or data view, with a learn more link next to the add action.
  • Empty State 9: Fits places where the user cannot act yet, because it shows only an illustration and a message about when reports will arrive.
  • Empty State 10: Suits products where the user builds a set of items, since the skeleton cards preview what the filled page will look like.
  • Empty State 12: Good for settings pages such as custom domains, where a tutorial link helps users who have never done the setup before.
  • Empty State 13: Works for approval queues like waitlists or requests, previewing the approve and decline rows that will appear later.
  • Empty State 15: The simplest workspace starter, for apps where users either create something new or import it from another tool.
  • Empty State 16: Choose it when you offer templates, because each template row is a link that skips the blank page entirely.
  • Empty State 22: A landing view for analytics tools that offer several starting points, each explained in its own card.

No results

  • Empty State 2: Use it in a team or people search, where an invite link turns a failed lookup into a new member.
  • Empty State 3: Built for file managers, with a message that changes between “no results” and “nothing here yet” depending on the search field.
  • Empty State 5: Keeps the toolbar and column headers of an orders table in place, so users still see what they were filtering.
  • Empty State 11: A document search result screen that names the query and offers to clear the active filters.
  • Empty State 14: Fits command palettes and integration pickers, with keyboard shortcut hints for the follow up actions.

Access, errors and progress

  • Empty State 4: Shows that work is in progress during an import or sync, and lets the user ask for a notification instead of waiting.
  • Empty State 7: A permission screen where users can request access without leaving the page.
  • Empty State 8: Use it when an account needs verification or setup before a feature unlocks, with the remaining steps listed below.
  • Empty State 17: An admin only page guard that hints at the hidden content behind a blurred preview.
  • Empty State 18: A connection error screen with a retry button that shows progress while it reconnects.

Feature cards

  • Empty State 19: Explains an automated workflow in one picture, useful before a user schedules their first job.
  • Empty State 20: Presents an integrations hub before any app is connected.
  • Empty State 21: A growth or upgrade card that uses a faded chart to hint at the results a feature can bring.

Similar Block Categories

  • Tables: most data tables need a no rows state, and several table blocks already render one inside the table body.
  • Onboarding Screens: guide new users through setup before they reach an empty dashboard.
  • Stat Cards: pair a card level empty state with KPI cards that have no data yet.
  • Modal Dialogs: open a create dialog from the primary action of an empty state.
  • Page Layouts: place an empty state inside a full page with header and navigation.

Accessibility

The blocks rely on real buttons and visible text, so every action is reachable with the keyboard and has a readable label. Avatars in Empty State 2 carry the person’s name as alt text, decorative avatars in Empty State 4 use an empty alt, the search field in Empty State 14 has an aria-label, and the retry button in Empty State 18 is disabled while its Spinner, which has role=“status”, is shown. Empty State 7 also disables its button after a request so it cannot be sent twice.

A few improvements are worth considering. EmptyTitle renders a div, so you may want to render the title as a heading that fits your page outline. The search input in Empty State 3 relies on its placeholder and would benefit from an aria-label. The app icons in Empty State 20 put aria-label on plain divs, where a visually hidden text label is more reliable. For the ping animation in Empty State 19 and the cursor pulse in Empty State 22, consider the motion-safe variant so users who prefer reduced motion see a still version.

Empty State FAQ

An empty state is the screen a user sees when a page, list, table or widget has nothing to show yet. It replaces a blank area with a short explanation of why it is empty and a clear next step, such as creating the first item or clearing a filter.

They are ready-made empty state layouts built with shadcn ui and Tailwind CSS. Most of them compose the shadcn Empty component (EmptyHeader, EmptyMedia, EmptyTitle, EmptyDescription and EmptyContent) with Button, Card, Skeleton or Avatar, so they drop into any dashboard that already uses shadcn components.

An empty screen is often the first thing a new user sees. A good empty state explains what will appear there, sets expectations and gives one obvious action. It also turns dead ends, such as a search with no results or a missing permission, into a recoverable moment instead of a confusing blank page.

A short title that names the situation, one or two sentences that explain why and what happens next, a visual cue such as an icon or illustration, and one primary action. Add a secondary action only when there is a real alternative, like importing instead of creating, or clearing a search.

Empty State 3 shows a file browser with type tabs and a working search that switches the message and adds a Clear search button. Empty State 5 sits below an orders table header, Empty State 11 covers a folder search, Empty State 14 sits inside a command style search panel and Empty State 2 handles a people search with an invite link.

Empty State 7 and Empty State 17 cover pages a user is not allowed to see. Empty State 7 turns its Request access button into a disabled “Request sent” state after a click. Empty State 18 is an offline screen whose Try again button shows a spinner and “Reconnecting” for 1.5 seconds.

Empty State 3 (file type tabs, live search text and Clear search), Empty State 7 (request access toggle), Empty State 18 (retry with spinner) and the toast based buttons in Empty State 2 and Empty State 4. The other blocks render static buttons that you connect to your own handlers or links.

Empty State 2 and Empty State 4 import toast from sonner and render the shadcn Toaster component. Empty State 21 draws its bar chart with recharts through the shadcn ChartContainer. Empty State 16 uses next/link for its template rows. Everything else needs only shadcn ui components and lucide-react icons.

Most action buttons, like Create survey, Add new item or Create project, are plain shadcn Buttons without a handler. Add an onClick that opens your create dialog, or use the Button with asChild around a Link. Empty State 16 already uses Link with a placeholder href for its template rows and Create blank project button, so you only replace the href.

Titles and descriptions are written inline in each block. Blocks with repeated visuals keep them in small arrays at the top of the file: fileTypes and orbitIcons in Empty State 3, avatars and rings in Empty State 4, columns in Empty State 5, steps in Empty State 8, files in Empty State 11, templates in Empty State 16, apps in Empty State 20, data in Empty State 21 and options in Empty State 22.

Only a few use motion. Empty State 19 pulses a ring around its sparkle icon with animate-ping, Empty State 22 blinks a text cursor with animate-pulse, and the Skeleton bars in Empty State 4, Empty State 10 and Empty State 12 use the default Skeleton pulse. Empty State 21 renders its chart with animation turned off.

They are centered single column layouts that shrink with the screen. Empty State 6 stacks its two buttons full width below the sm breakpoint, Empty State 10 hides the two side agent cards on phones, Empty State 3 turns its tabs into a horizontally scrollable list, and Empty State 22 moves each card illustration above the text on small screens.

Yes. Empty State 1 already sits inside a Card with its own header, Empty State 5 sits under a Table header row and Empty State 14 sits between a search input and a footer inside one Card. The Empty component is a plain flex container, so you can also render it inside a TableCell with colSpan when a data table returns no rows.

No. All 22 empty state blocks are part of All Access, the one-time license that also unlocks every other block, admin dashboard and template with lifetime updates.
shadcn empty state blocks
Unlock Premium Blocks & Sections
Premium blocks are part of All Access. One license unlocks the whole Shadcn UI Kit, so you can build complete pages and products instead of single sections.
  • 550+ blocks for landing pages, stores, dashboards and apps
  • 16 admin dashboards and 17 ready-made apps
  • 5 premium Next.js website templates
  • 560+ component variants and 70+ examples
  • Install with the shadcn CLI or from your AI editor through the MCP server
  • Lifetime updates, including every new block we release
Unlock Now

One-time payment, no subscription.