Textarea

Use Textarea for content requiring multiple lines: comments, descriptions, messages, reviews, or any text over ~100 characters. Use Input for single-line data like names, emails, or short answers. Textarea signals "more space for writing."

Usually yes—auto-growing Textareas adapt to content, preventing scrolling within the field. Start with 3-4 rows, expand as users type. Set max height to prevent page overflow. Fixed height works for specific constraints like tweet composers (character limits).

Yes, when there's a limit! Display "50/280" or "230 characters remaining" so users know constraints before hitting them. Update in real-time. Without limits, counts add unnecessary pressure—let users write freely.

Use placeholders for examples or format guidance ("What's on your mind?" or "Describe the issue...") but never as label replacements. Labels should always be visible. Good placeholders inspire and guide; they don't replace proper labeling.

For rich text editing (bold, italic, links), use a rich text editor, not plain Textarea. Plain Textareas are for unformatted text. Adding formatting transforms it into a different component with different complexity and accessibility needs.

Yes, this Figma Textarea component matches the shadcn/ui implementation exactly, ensuring your multi-line inputs maintain consistent styling, states, and behavior from design to production.