Tag Inputs

A tag input collects several short values in one field, committing each to a chip the reader can see and remove. It is the right control when the answer is a set rather than a value (recipients, labels, filters) and when the reader benefits from watching that set build. Four blocks cover people with faces on their chips, labels that fold into a counter when the row fills, free typing where a comma commits, and options that stack the field as it grows.

Real use of one of these usually starts with a paste. Someone copies a column of addresses out of a spreadsheet, or a list out of a mail header, and drops the whole thing in; a field that treats that as one tag has failed at the first genuine interaction. Split on commas and newlines, trim the pieces, drop the duplicates, and keep anything that does not parse visible rather than quietly swallowing it. A recipient that vanishes is worse than one flagged in red.

11 blocks

People picker

Sharing and assignment: pick a few people or groups, up to a limit

People picker, seats

Pickers with a hard limit that should read as seats filling up

People picker, roles

Sharing sheets: add people as rows and give each one an access level

Overflow tags

Narrow fields: chips fold into a counter that opens the folded ones

Overflow tags, fold

Narrow fields where seeing everything in place beats a second card: the counter unfolds the field

Overflow tags, tray

Narrow fields where the counter and the field open one card: what is in, or everything

Comma tags

Free-text tagging: type, a comma commits, suggestions match as you go

Comma tags, ghost

Free-text tagging without a floating menu: the best match is the grey completion

Comma tags, sorted

Tagging from a library whose tags have kinds: the menu groups, the chips tint

Stack picker

Long option lists that carry a count: swatch chips wrap, the field grows and the chevron keeps its own column

Stack swatches

Colour or avatar-like choices that read best as a stack: the picks overlap, the menu is a grid

01

Using Tag Inputs

Reach for it when

  • A recipient field taking a few people or groups, up to a stated cap
  • Free-text labelling where the vocabulary grows as people use it
  • Multi-select filters whose chosen values must stay on screen while the reader works
  • A narrow field where chips have to fold into a counter rather than push the layout around

Reach for something else when

  • The vocabulary is closed and known: a combobox tells the reader what the legal values are, while a tag input implies they can invent one
  • Order matters, or each entry carries more than a name such as a role or a date; a list of rows holds structure a chip cannot
  • There is only one value to collect: one chip in a field is a select in a costume, so use the select
02

Where it shows up

01

Invite fields

Sharing something with a few people or groups. Chips carry a face or a glyph so the reader recognises who is on the list, and once the cap is reached the remaining rows grey out instead of failing on submit.

02

Article tagging

A publishing tool where the vocabulary grows with use. Typing matches whole words first so a short query does not bury the obvious tag, a comma commits, and anything with no match can still be added as typed.

03

Saved filter sets

A view definition the reader builds and keeps. Each chip carries the colour dot its option had in the list, the list shows how many records sit behind each name, and the field stacks rather than scrolling as it fills.

04

Narrow recipient rows

A field in a sidebar or a compact form. Chips fill the row, then fold behind an ellipsis and a solid counter that states how many are hidden, so the layout holds while the full set stays one click away.

03

Questions

Which key should commit a tag?

Enter and comma both, and blur as well if the field can afford it. Enter is what people try first; comma is what mail clients taught them and what they will paste. Tab is the risky one, because it is also how people leave a field, and a tag committed on the way out surprises them. Say in the hint which keys work.

How should a tag input handle pasted text?

All blocks
The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.