Zero State

A zero state is the blank screen that greets every new user the first time they open your product. No projects. No documents. No history or prior activity. It is the highest stakes empty state because the user has zero context and zero investment yet. The zero state decides if they bother coming back for session two.

Teams often treat zero state and empty state as exact synonyms. They are close but not identical. Zero state refers to first run no data moments. Empty state is the broader category that also includes no results from a filter, no permission screens, no connection, and no AI output. The principles stay similar. The emotional stakes and required copy change.

The common trap is treating the zero state like an error page. It is not an error. The system works exactly as designed. The user simply has not added anything. Responding with sorry or vague illustrations trains users to expect weakness instead of confidence from your tool.

Cursor sets a high bar here. Open the app and you land inside a single editor window with a soft prompt and sample command already primed for the keyboard. No five step checklist. No tooltip parade. No welcome modal in the way. The user feels they are already inside the work. Figma follows the same logic with every new file. Clean infinite canvas, toolbar within immediate reach, cursor blinking exactly where you need it. Compare that to products that open with a Connect your workspace wall and a homework checklist. One feels like a tool. The other feels like setup theater.

Vercel before any deployments and a fresh Slack workspace before channels exist face identical zero state pressure. The best versions preview future content, offer one click paths to the first action, and remove every possible step. The worst versions stare back blank with a sad face illustration and three words that explain nothing. The difference appears in first hour activation rates.

Use a zero state when a brand new user opens your product for the first time or when they have cleared all existing data. Do not use one when you can redesign the onboarding flow to seed sample data or guide the user so the blank never appears. The tradeoff sits between authenticity and hand holding. Over explain the zero state and you patronize. Under explain it and you confuse. Most teams pick one extreme instead of finding the narrow path that respects the user.

Every zero state must sell the product in isolation. If a user saw only this screen would they understand the value and know exactly what to do next. Most zero states fail this test. The ones that pass become the reason users return before they ever see the populated dashboard.

Write zero state copy in two sentences maximum. The first names what the user sees and why it is empty. The second gives the next move in active voice with a clear verb. Cut every adjective. Cut every apology. Read it out loud. If it sounds like every other SaaS template rewrite it immediately.

The zero state is where retention curves are born or broken before the user even creates their first record.