:in-range CSS pseudo-class

Baseline Widely available

This feature is well established and works across many devices and browser versions. It’s been available across browsers since November 2015.

The :in-range CSS pseudo-class represents an <input> element whose current value is within the range limits specified by the min and max attributes.

Try it

label {
  display: block;
  margin-top: 1em;
}

input:in-range {
  background-color: palegreen;
}
<form>
  <label for="amount">How many tickets? (You can buy 2-6 tickets)</label>
  <input id="amount" name="amount" type="number" min="2" max="6" value="4">

  <label for="dep">Departure Date: (Whole year 2022 is acceptable)</label>
  <input id="dep" name="dep" type="date" min="2022-01-01" max="2022-12-31" value="2025-05-05">

  <label for="ret">Return Date: (Whole year 2022 is acceptable)</label>
  <input id="ret" name="ret" type="date" min="2022-01-01" max="2022-12-31">
</form>

This pseudo-class is useful for giving the user a visual indication that a field's current value is within the permitted limits.

Note: This pseudo-class only applies to elements that have (and can take) a range limitation. In the absence of such a limitation, the element can neither be "in-range" nor "out-of-range."

Syntax

css
:in-range {
  /* ... */
}

Examples

HTML

html
<form action="" id="form1">
  <ul>
    Values between 1 and 10 are valid.
    <li>
      <input
        id="value1"
        name="value1"
        type="number"
        placeholder="1 to 10"
        min="1"
        max="10"
        value="12"
        required />
      <label for="value1">Your value is </label>
    </li>
  </ul>
</form>

CSS

css
li {
  list-style: none;
  margin-bottom: 1em;
}

input {
  border: 1px solid black;
}

input:in-range {
  background-color: rgb(0 255 0 / 25%);
}

input:out-of-range {
  background-color: rgb(255 0 0 / 25%);
  border: 2px solid red;
}

input:in-range + label::after {
  content: "okay.";
}

input:out-of-range + label::after {
  content: "out of range!";
}

Result

Note: An empty <input> does not count as out of range, and will not be selected using the :out-of-range pseudo-class selector. The :blank pseudo-class exists to select blank inputs, although at the time of writing this is experimental and not well-supported. You could also use the required attribute and the :invalid pseudo-class to provide more general logic and styling for making inputs mandatory (:invalid will style blank and out-of-range inputs).

Specifications

Specification
HTML
# selector-in-range
Selectors Level 4
# in-range-pseudo

Browser compatibility

desktop mobile
Chrome
Edge
Firefox
Opera
Safari
Chrome Android
Firefox for Android
Opera Android
Safari on iOS
Samsung Internet
WebView Android
WebView on iOS
:in-range
Chrome – Full support
Chrome 10 (Release date: 2011-03-08)
footnote
footnote Before Chrome 52, :in-range matched disabled and read-only inputs (see bug 41248615). In Chrome 52, it was changed to only match enabled read-write inputs.
Edge – Full support
Edge 13 (Release date: 2015-11-12)
footnote Full support
Firefox – Full support
Firefox 29 (Release date: 2014-04-29)
footnote
footnote Before Firefox 50, :in-range matched disabled and read-only inputs (see bug 1264157). In Firefox 50, it was changed to only match enabled read-write inputs.
Opera – Full support
Opera 11 (Release date: 2010-12-16)
footnote
footnote Before Opera 39, :in-range matched disabled and read-only inputs (see bug 41248615). In Opera 39, it was changed to only match enabled read-write inputs.
Safari – Full support
Safari 5.1 (Release date: 2011-07-20)
footnote
footnote In Safari, :in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs.
Chrome Android – Full support
Chrome Android 18 (Release date: 2012-06-27)
footnote
footnote Before Chrome Android 52, :in-range matched disabled and read-only inputs (see bug 41248615). In Chrome Android 52, it was changed to only match enabled read-write inputs.
Firefox for Android – Full support
Firefox for Android 16 (Release date: 2012-10-09)
footnote Full support
Opera Android – Full support
Opera Android 11 (Release date: 2011-03-22)
footnote
footnote Before Opera 39, :in-range matched disabled and read-only inputs (see bug 41248615). In Opera 39, it was changed to only match enabled read-write inputs.
Safari on iOS – Full support
Safari on iOS 5 (Release date: 2011-10-12)
footnote
footnote In Safari on iOS, :in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs.
Samsung Internet – Full support
Samsung Internet 1 (Release date: 2013-04-27)
footnote
footnote Before version 6.0, :in-range matched disabled and read-only inputs (see bug 41248615). In version 6.0, it was changed to only match enabled read-write inputs.
WebView Android – Full support
WebView Android 2.2 (Release date: 2010-05-20)
footnote
footnote Before version 52, :in-range matched disabled and read-only inputs (see bug 41248615). In version 52, it was changed to only match enabled read-write inputs.
WebView on iOS – Full support
WebView on iOS 5 (Release date: 2011-10-12)
footnote
footnote In WebView on iOS, :in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs.

Legend

Tip: you can click/tap on a cell for more information.

Full support
Full support
See implementation notes.

See also