Six component archetypes
Design a familiar pill, an explicit two-way segment, a radial power control, a drawn checkbox, a day-night horizon, or a favorite bloom.
Components & state
Give a binary choice the clarity it deserves. Test six genuinely different toggle systems with pointer, touch, and keyboard input—all built around a real checkbox.
State you can feel
Good toggle motion explains where a control came from and where it landed. Shape that transition without compromising native input behavior, focus visibility, touch ergonomics, or reduced-motion preferences.
Design a familiar pill, an explicit two-way segment, a radial power control, a drawn checkbox, a day-night horizon, or a favorite bloom.
Every live and exported control contains a native checkbox, so click, tap, Space, focus, checked state, and form behavior remain dependable.
Tune the copy, state labels, scale, timing, overshoot, canvas, card, text, off state, on state, and fine detail independently.
Three-step workflow
Use a pill for familiar settings, a segment for explicit alternatives, or a more expressive control where context supports it.
Click or tap the card, then tab to its checkbox and press Space. Pause and replay the transition while tuning its timing and overshoot.
Copy the scoped HTML and CSS or download a standalone file; the current preview state becomes the exported default.
It is a native checkbox wrapped by a label, with a visible focus treatment. That preserves browser keyboard, pointer, touch, and checked-state semantics.
Yes. The exported transition is driven by the checkbox checked state and scoped CSS, so no script or animation package is required.
State changes remain immediate and clear, but transitions collapse to an effectively instant duration and decorative motion is removed.
Yes. Add the name and value attributes your form requires to the generated checkbox; its native checked behavior is already intact.