What <input type="search"> actually gives you
Declaring an input as a search field changes rendering and behavior in a handful of ways. Some are genuinely useful; others are cosmetic or unreliable.
Rendering differences in Safari
- Safari draws the input with a rounded appearance that once matched the macOS search field look, but no longer does.
- Safari ignores any
font-sizeyou set on it, unless you remove the rounded styling with-webkit-appearance: none(expected to be unprefixed going forward). With that override,font-sizeapplies — likely why most sites take this route.
The clear button
When the field contains a value, browsers show a small × icon inside it that empties the input. It survives resetting appearance, which makes it the strongest practical argument for the type.
Semantics and autocomplete
The type is the semantically correct choice for a control that genuinely searches something. Browsers also store previously submitted search terms and offer them in an autocomplete menu — though the same behavior can be observed on non-search inputs, it fits search fields best.
Accessibility obligations
Search inputs do not remove any accessibility work:
- Add
role="search"to the parent form so assistive technology announces it as a search form. - Supply a real
<label>; a magnifying glass icon or aplaceholderalone is insufficient, regardless of what the design calls for.
The non-standard incremental attribute
The incremental attribute dispatches a debounced search event to the element itself, which could suit a live-search experience. It is non-standard and absent from Firefox, so it should not be relied upon.



