Usage statistics for hwb() show a steep decline, which raises the question of why adoption never took off despite the function's stated goal of being easier to work with than hsl().

How hwb() works
hwb() lives in the sRGB color space — the same one used by rgb(), hsl() and hexadecimal notation such as #f8a100. It takes three values: a hue between 0deg and 360deg, followed by a whiteness value and a blackness value, each between 0 and 100.
hwb()accepts three values, and similar tohsl(), the first value specifies the color's hue (between0deg–360deg), while the second and third values add whiteness (0–100) and blackness (0–100) to the mix, respectively.
The pitch for hwb() is that specifying how much black or white to add to a color is more instinctive than working with saturation and lightness. The trade-off appears once you compare equivalent colors side by side.
/* light orange */
.element {
color: hsl(34deg 100% 65%);
}
.element {
color: hwb(34deg 30% 0%);
}
/* light orange in hsl */
.element-1 {
color: hsl(30deg 100% 75%);
}
/* light orange in hwb() */
.element-2 {
color: hwb(30deg 50% 0%);
}
Why hsl() feels more natural
Both declarations above produce the same light orange, but they divide the work differently. hsl() controls lightness with a single argument and leaves another for saturation, whereas hwb() splits lightness across two arguments — whiteness and blackness. The consequence is that hwb() has no clear, intuitive way to set saturation alone, which arguably makes it the less intuitive of the two.
Familiarity compounds this. HSL as a color model dates to the 1970s; HWB was created in 1996. Browsers shipped hsl() support as far back as 2008, with Safari leading and others following. hwb() did not gain support until 2021 — a gap of more than a decade in which developers could use and get comfortable with one function but not the other.
Competing functions also raise the bar. lab(), lch(), oklab() and oklch() represent colors in other color spaces and bring advantages such as access to more colors in the gamut and perceptual uniformity. Intuitiveness may simply come at the expense of a more robust feature set, which would explain choosing a less intuitive, non-sRGB function instead.
An sRGB function without a clear niche
There is a case for controlling how white or black a color looks according to personal preference — for designers, mixing colors that way may come more easily. Even so, hsl() is a stronger default in the sRGB space: it works from the same hue but exposes saturation and lightness as parameters, which is far more intuitive than what hwb() offers. Stefan Judis reaches a similar conclusion, preferring hsl() over hwb() in his writing on the topic.
The spec itself has been questioned. Lea Verou raised the idea of removing hwb() from the spec in 2022, but a decision was made to keep it as it was, since browsers were already implementing the function. Walking something back is hard once it has shipped, and backwards compatibility is a core tenet of the web.
Meanwhile lab(), lch(), oklab() and oklch() are already available and are better color functions than hwb(), supporting many more colors than are present in hsl() and hwb(). That makes them the functions worth reaching for ahead of hwb().



