Skip to content

Now in the official shadcn registry directory.

Start free

Range sliders

Five two-thumb range sliders that keep a real minimum and maximum in state: a plain dual, a live min/max readout, a stepped track, a labelled scale and a gradient fill. The thumbs clamp against each other so they never cross, and each thumb has its own role slider, label and keyboard control.

SliderRange

Installation

The styled layer is free and installs like any other ai2 component.

Run the following command

npx shadcn@latest add @ai2/slider-range

Dependencies, the @ai2/tokens theme and the component file are installed together.

Variations

5 takes on the same idea. Each is its own export, and every one accepts a size prop (sm, md, lg, xl) aligned to the base Button scale.

Dual

Two thumbs with a solid fill between them.

sm
md
lg
xl

Min max

Live minimum and maximum readouts follow each thumb.

sm
md
lg
xl

Steps range

Both thumbs snap to a ten unit step over a ticked track.

sm
md
lg
xl

Labels range

A scale of min, mid and max labels sits under the track.

sm
md
lg
xl

Fill range

A thick track whose selected span is a token gradient.

sm
md
lg
xl

ai2 Range sliders: 5 styled variations on the token system

The ai2 Range sliders are a set of 5 decorative button variations from the styled layer of the @ai2 design system, built around two-thumb range sliders with a clamped minimum and maximum. They are free and MIT licensed, and every color comes from a semantic token, so they theme with the rest of ai2 in light and dark.

Motion runs on framer-motion: framer-motion springs the active thumb; pointer drag and keyboard both work. The styled layer is opt-in, so the dependency only lands if you use it; the base components stay lean. Under reduced motion, the thumb spring is disabled and the thumbs move directly.

What is in the ai2 Range sliders?

5 exports in one file: Dual, Min max, Steps range, Labels range and Fill range. Each renders a native button and takes a size prop (sm, md, lg, xl) aligned to the base Button. They are separate from the base Button on purpose: the base keeps its clean variant, tone and size axes, while the styled layer carries the effects.

You own the file. Copy the one category file and you have all 5 variations, with no runtime dependency on ai2 itself.

Why use it

  • On-system by construction: Every color resolves to an ai2 semantic token, so the buttons follow your theme in light and dark with no extra work.
  • Effect without the sprawl: The decorations live in a dedicated styled file, so the base Button keeps its clean, predictable API.
  • Accessible and honest: Each renders a real button element, keeps a visible focus ring, and respects prefers-reduced-motion.

Features

  • Token-driven color: No hardcoded hex or oklch; the look recolors with your theme tokens.
  • framer-motion: framer-motion springs the active thumb; pointer drag and keyboard both work.
  • Reduced-motion aware: Under prefers-reduced-motion, the thumb spring is disabled and the thumbs move directly.
  • Size aligned to the base: Every variation takes sm, md, lg and xl matching the base Button height scale, so styled and base buttons line up in a row.

Production tips

  • Use it for emphasis, not everywhere: Styled buttons draw the eye. Reserve them for the one action you want people to take on a screen, and use the base Button for the rest.
  • Keep labels as verbs: The decoration adds weight, so a clear action label keeps the button scannable.
  • Pick one variation per surface: The variations share a family; using two different ones in the same view competes for attention.

Works with the rest of ai2

The Range sliders sit alongside the base Button and the rest of the @ai2 registry. They share the same token file, so a styled action next to a base button or a badge stays visually consistent in both modes.

FAQs

Get new components in your inbox

Component drops, new themes and release notes. No spam, and you can unsubscribe from any email.

© 2026 ai2 design system · MIT licensed · Built with its own components