Skip to content

shadcn.io is an independent project built on shadcn/ui

Free

Controlled Tabs for Svelte

Step 1, Step 2 and Step 3 as equal tabs. Step 1 shows Basic Information, and Previous and Next sit under the panel.

UI library: Ark UI

Three equal tabs labeled Step 1, Step 2 and Step 3. Step 1 is selected and shows Basic Information, with Project Name and Description as labeled hints. Previous is disabled. Next sits beside it.

Use stepped tabs for a setup people can also jump by clicking a step. If steps must not be skipped, a Dialog with one step at a time is stricter. Ark UI in Svelte does not move Previous and Next.

Preview

Preview width

Installation

MCP · Pro
Make your AI a shadcn expert
Your agent installs components, builds pages and restyles your app from one prompt, in Claude Code, Cursor or VS Code.
Get MCPSee plans
Part of Pro

Anatomy

Tabs anatomy: root, list, indicator, trigger, content

Usage

<div class="flex w-full max-w-2xl flex-col gap-4"><Tabs onValueChange={handleValueChange} value={activeTab}><TabsList class="grid w-full grid-cols-3">{#each steps as step (step.value)}<TabsTrigger value={step.value}>{step.label}</TabsTrigger>{/each}</TabsList>{#each steps as step (step.value)}<TabsContent value={step.value}><div class="rounded-lg border bg-card p-6 text-card-foreground shadow-sm"><h3 class="mb-2 font-semibold text-lg">{step.title}</h3><p class="mb-4 text-muted-foreground text-sm">{step.description}</p><div class="flex flex-col gap-4">{#each step.fields as field (field.label)}<div class="rounded-md border p-4"><p class="font-medium text-sm">{field.label}</p><p class="mt-1 text-muted-foreground text-sm">{field.hint}</p></div>{/each}</div></div></TabsContent>{/each}</Tabs><div class="flex justify-between"><Button disabled={index === 0} onclick={handlePrevious} variant="outline">Previous</Button><Button disabled={index === steps.length - 1} onclick={handleNext}>Next</Button></div></div>

FAQ

How does this demo control the selected tab?

The selected value is kept in state, starting at step1, and passed back to Tabs. Clicking a trigger or a button writes the same state. Tabs gets value, and onValueChange stores details.value.

When are Previous and Next disabled?

Previous is disabled on the first step and Next on the last. Each button moves one place in the steps array.

Can the reader still click a step?

Yes. The three triggers are not disabled. Clicking one updates the same state the buttons write, so the buttons stay in sync.

Why are the three steps equal width?

TabsList has grid w-full grid-cols-3, so each of Step 1, Step 2 and Step 3 fills a column. The group is w-full max-w-2xl.

Does Next wait for the step to be filled in?

No. The handlers only look at the current step. The panels show labels and hints, not inputs, so nothing is checked before the tab changes. Add your check in the Next handler before you move on.

Would inputs in a step survive switching away?

Not with this file. Inactive panels unmount, so input state inside a step resets on the way back. Set lazyMount and unmountOnExit to false on Tabs to keep a step mounted.

API Reference

Tabs

Sets onValueChange={handleValueChange}, value={activeTab} and value={step.value}. The rest is on the Tabs page.

Button

Sets disabled={index === 0}, onclick={handlePrevious}, variant="outline", disabled={index === steps.length - 1} and onclick={handleNext}. The rest is on the Button page.

All 11 tabs examples