UIArchives
Journal
Journal

5 min readEngineering

How to Style a Native Select with appearance: base-select (2026 Guide)

A practical guide to customizable select: opting in with appearance: base-select, styling the button, picker and options, rich option content, positioning, animation, browser support and fallbacks.

Author Malay Patel

UIArchivesJournal

How to Style a Native Select with appearance: base-select (2026 Guide)

Engineering

Short answer: add appearance: base-select to both select and ::picker(select). The browser then lets you style the button, the dropdown, every option, the checkmark and the arrow, and even put images and rich HTML inside options, while keeping native keyboard support, screen reader semantics and form submission. It works in Chrome and Edge 135+ and in Safari 27. Firefox ignores it and shows a normal select, so it's safe to ship today.

Why this is a bigger deal than it looks

The select element has been the most-rebuilt component on the web. Because it couldn't be styled, design systems shipped their own: a div button, a ul listbox, and hundreds of lines of JavaScript for keyboard handling, typeahead, scroll-into-view and ARIA. Most got at least one of those wrong.

Customizable select means the native element now matches your design, and you get everything the browser already does well for free: typeahead, Escape to close, correct roles, mobile behaviour, autofill and form validation.

Step 1: Opt in

css
1select,
2::picker(select) {
3 appearance: base-select;
4}

Both selectors matter. Setting it only on select restyles the closed button but leaves the dropdown native. With both, you get a minimal, unstyled-but-functional base to design from.

Step 2: Know the parts

Customizable select exposes new pieces you can target:

SelectorWhat it is
selectThe closed button
select buttonAn optional custom button you write yourself
selectedcontentMirrors the chosen option inside your custom button
::picker(select)The dropdown surface
optionEach item, now able to hold any phrasing content
option::checkmarkThe tick next to the selected option
::picker-iconThe arrow on the closed button
select:openThe select while its picker is open

Step 3: Style the button and picker

css
1select {
2 display: flex;
3 align-items: center;
4 gap: 8px;
5 padding: 8px 12px;
6 border: 1px solid var(--line);
7 border-radius: 10px;
8 background: var(--bg);
9 font: inherit;
10}
11
12select::picker-icon {
13 transition: rotate 0.2s;
14}
15
16select:open::picker-icon {
17 rotate: 180deg;
18}
19
20::picker(select) {
21 margin-top: 4px;
22 padding: 4px;
23 border: 1px solid var(--line);
24 border-radius: 12px;
25 background: var(--bg);
26 box-shadow: 0 12px 32px rgb(0 0 0 / 0.12);
27}
28
29option {
30 padding: 8px 10px;
31 border-radius: 8px;
32}
33
34option:hover,
35option:focus-visible {
36 background: var(--hover);
37}
38
39option:checked {
40 font-weight: 500;
41}

Step 4: Put rich content inside options

This is the part that used to be impossible. Options can contain images, icons and secondary text:

html
1<select name="country">
2 <button>
3 <selectedcontent></selectedcontent>
4 </button>
5 <option value="in">
6 <img src="/flags/in.svg" alt="" width="20" height="14" />
7 <span>India</span>
8 </option>
9 <option value="jp">
10 <img src="/flags/jp.svg" alt="" width="20" height="14" />
11 <span>Japan</span>
12 </option>
13</select>

selectedcontent clones the chosen option's content into the button, so the flag shows there too. Keep decorative images at alt="" so screen readers only announce the country name.

Step 5: Position it with anchor positioning

The picker is anchored to the select automatically, which means anchor positioning properties work on it. To align it to the right edge, or flip it above when there's no room:

css
1::picker(select) {
2 position-area: block-end span-inline-start;
3 position-try-fallbacks: flip-block;
4}

Step 6: Animate opening and closing

The picker is a popover in the top layer, so @starting-style and discrete transitions work:

css
1::picker(select) {
2 opacity: 1;
3 translate: 0 0;
4 transition: opacity 0.15s, translate 0.15s, display 0.15s allow-discrete, overlay 0.15s allow-discrete;
5}
6
7@starting-style {
8 ::picker(select):popover-open {
9 opacity: 0;
10 translate: 0 -4px;
11 }
12}
13
14@media (prefers-reduced-motion: reduce) {
15 ::picker(select) { transition: none; }
16}

Browser support and fallbacks

As of November 2026:

  • Chrome and Edge: supported since version 135.
  • Safari: supported in Safari 27.
  • Firefox: in development, not yet on by default.

Unsupported browsers ignore appearance: base-select and the extra markup degrades cleanly: the custom button is dropped and options render their text. To keep your fallback styles from leaking into the new mode, scope the fancy parts:

css
1@supports (appearance: base-select) {
2 select, ::picker(select) { appearance: base-select; }
3 /* rich styles here */
4}

Mistakes to avoid

  • Interactive content inside options. Links or buttons inside an option are not allowed and confuse assistive tech. Options are for content, not controls.
  • Dropping the visible label. A styled select still needs a <label>.
  • Hiding the focus ring. Restyle :focus-visible instead of removing it.
  • Tiny hit targets. Keep options at least 24 × 24 px to meet WCAG 2.2's target size rule. Our accessibility checklist covers the rest.
  • Rebuilding multi-select. multiple selects aren't part of the first release. Keep your existing component for those for now.

Should you delete your custom select component?

Not yet, if Firefox users must see the full design. But you can change its implementation: render a native select with base-select styles in supporting browsers and keep the old component only as a fallback. When Firefox ships, delete the fallback. That path ends with less code and better accessibility than any library.

FAQ

It's a CSS value that switches the select element into a new, fully stylable mode. The browser keeps the native behaviour (keyboard, typeahead, accessibility, forms) but lets you style every part and put rich content inside options.

Not by default as of November 2026. Firefox ignores the property and shows a normal native select, so the page still works.

Yes, in supporting browsers. Options can contain images, icons and text, and the selectedcontent element mirrors the chosen option inside the button.

It keeps the native select's roles, keyboard support and screen reader behaviour, which is far more reliable than most custom dropdowns. You still need a visible label, a visible focus style and sufficient contrast.

#CSS#HTML#Forms#Customizable Select#Accessibility#Safari 27