shadcn/ui v3 — Profile form

Forms & OnboardingSee it livev3.shadcn.com

A profile form keeps field explanations close to the controls they clarify.

Page excerpt · scroll inside to explore

Public demo · 2026-09-04Open full image ↗

Forms & onboarding Navigation

Why this pattern works

Constrain form width and use inline explanations instead of a separate help panel.

Design notes

Surface: Profile form
Navigation: A local settings list separates profile, account, appearance, notifications, and display.
Layout: Settings navigation sits beside a constrained single-column form for username, email, bio, and links.
Density: A constrained form column leaves room between groups while keeping labels and controls together.
Color: White surfaces, light input borders, and a dark update button.
Type: Use clear vertical rhythm between fields while keeping labels and helper text together.
Pattern: Constrain form width and use inline explanations instead of a separate help panel.
States: Public v3 settings demo with sample values; no profile was submitted.
Don't: Adapt the interaction pattern to your own product. Do not copy brand assets, sample identities, proprietary text, or assume unseen states. Specify keyboard behavior, loading, empty, error, and narrow-screen layouts for your implementation.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: shadcn/ui v3 — Profile form
Source: https://v3.shadcn.com/examples/forms
Swipefile reference: https://swipefile.design/ref/shadcn-profile/
Captured: 2026-09-04. This is a dated reference, not a claim about the current live product.
Capture scope: a page excerpt. Do not infer unseen sections or interactions.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Profile form
- nav: A local settings list separates profile, account, appearance, notifications, and display.
- layout: Settings navigation sits beside a constrained single-column form for username, email, bio, and links.
- density: A constrained form column leaves room between groups while keeping labels and controls together.
- color: White surfaces, light input borders, and a dark update button.
- typography: Use clear vertical rhythm between fields while keeping labels and helper text together.
- pattern: Constrain form width and use inline explanations instead of a separate help panel.
- states: Public v3 settings demo with sample values; no profile was submitted.
- dont: Adapt the interaction pattern to your own product. Do not copy brand assets, sample identities, proprietary text, or assume unseen states. Specify keyboard behavior, loading, empty, error, and narrow-screen layouts for your implementation.

Useful for: Constrain form width and use inline explanations instead of a separate help panel.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Constrain form width and use inline explanations instead of a separate help panel.

shadcn/ui v3 — Profile form

Make it your own

Keep exploring