Checkboxes

A checkbox is a control for one independent yes or no. Ticking one says nothing about its neighbours, which is the whole difference between a checkbox and a radio button, and the reason a column of them can be read in any order. The six blocks here run from a single choice on a card up to a table that selects every row at once.

The state people get wrong is the mixed one. Indeterminate is not a third answer anyone can pick. It is what a parent shows when its children disagree, and it exists so a select-all box can be honest about a partial selection. Decide what clicking it does before you draw it; usually it fills the set, and clicking again empties it. The other quiet failure is the hit area. The row or the card is the control, not the little square inside it, and a checkbox that only responds on the box is a miserable thing to tap on a phone.

18 blocks

Preferences list

Settings and notification screens: a titled list where each row is a choice

Preferences, channels

Notification settings where each topic can reach you in several places

Preferences, weekly load

Notification settings that show what each choice costs in a week

Selectable table

Bulk actions on records: select all, select some, act on the selection

Selectable table, selection bar

Tables where the actions should only appear once something is selected

Selectable table, running total

Money tables where the useful answer to "what did I select" is a sum

Permission groups

Roles and scopes: a parent box that follows its children and sets them

Permission groups, presets

Role editors where most people start from a standard role and tweak it

Permission groups, rings

Long permission lists where a glance should say how much is granted

Feature cards

Plan add-ons and option pickers: each choice is a card, with read-only and disabled states

Feature cards, receipt

Add-on pickers where the price must be clear before committing

Feature cards, configure

Add-ons that need a setting (how many, how much) the moment they are chosen

Logo cards

Integrations and connected apps: the same cards led by a brand logo

Logo cards, stack

Integration lists where the result of connecting should be visible at once

Logo cards, tiles

Directories of many apps: a grid of tiles where connecting takes a moment

Logo card

One connected-app choice on its own: the Checkbox Card component

Logo card, scopes

Connecting an app that asks for several permissions

Logo card, link

Connecting an app to your workspace with feedback on the link itself

01

Using Checkboxes

Reach for it when

  • Form values that a save commits, not settings that apply on the spot
  • Selecting rows in a table for an action taken on the selection
  • Nested scopes where a parent has to reflect and set its children
  • Optional extras drawn as cards, several of which can be on at once

Reach for something else when

  • A setting that takes effect the instant it is flipped: a switch reads as immediate
  • Choices that exclude one another: radio buttons make the exclusivity visible
  • Picking a few values out of a very long list: a searchable multi-select scales where a column of boxes stops
02

Where it shows up

01

Notification preferences

A settings screen where each row is its own yes or no (a channel, a digest, a mention alert) with a sub-label and a description doing the explaining the label has no room for.

02

Bulk table actions

Select some records, select them all from the header, then export or archive what is selected. The header box has to show the mixed state or the reader cannot tell a partial selection from none.

03

Permission groups

Roles and scopes, where a parent stands for a set of children. Ticking the parent grants the set, clearing one child drops the parent to mixed, and the indent is what makes the relationship readable.

04

Connected app pickers

Integrations presented as cards with the brand logo leading, where several are turned on at once and some are already fixed: read-only because an admin set them, or disabled because the plan excludes them.

03

Questions

When should I use a checkbox instead of a toggle switch?

A checkbox is for a value a form collects and a save commits, and it sits comfortably in a column with other checkboxes. A switch is for a setting that takes effect the moment it is flipped, with no save anywhere. If your checkbox applies instantly, people will still look for a save button; if your switch needs one, they will not.

What does an indeterminate checkbox mean?

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.