Why Design Tools Use HSL Instead of RGB

Contents
When you open the color picker in Figma or Photoshop, you'll often see Hue, Saturation, and Lightness sliders instead of three R, G, B sliders. Maybe you've tried to build a tone-on-tone palette that keeps the same blue but varies only the brightness, nudged the RGB values around, and gave up because the color itself kept shifting. That's not a designer's preference. It's because the two color models are built differently.
Summary ① RGB describes color as a mix of three channels — red, green, and blue — so there's no separate concept of "keep the hue, change only the brightness" ② HSL separates hue, saturation, and lightness, so holding hue (H) fixed and changing only lightness (L) produces a tone-on-tone palette in the same color family ③ Getting the same result from RGB values means calculating a different ratio for each channel, which is hard to do by hand
Why RGB sliders are bad at tone-on-tone
RGB describes a color by how much red, green, and blue — the three primary colors of light — you mix in. Those three values don't map one-to-one onto hue, saturation, and lightness; they're tangled together inside a single color. So "keep this color's hue and just lower the lightness" means adjusting all three values at once, each by a different ratio.
Take the sky blue HEX #2E9BE0: R:46, G:155, B:224 — three very different proportions. Even if you only want to make it "20% darker," subtracting the same number from all three channels changes the ratios and throws off the hue, and if one channel gets clipped below 0, the saturation collapses too.
HSL solves this by splitting color into three separate axes: hue (H), saturation (S), and lightness (L). Hue is the position on the color wheel, saturation is how vivid the color is, and lightness is how bright or dark it is — each independent. Move only the lightness (L) value and the brightness steps up or down while hue and saturation stay put.
Changing only lightness while keeping the same hue: how to check
To do this by hand without a design app or tool, you first need the HSL values of your base color. Most color pickers show HSL next to HEX, so write down the three numbers — H, S, and L — from there.
Then leave H (hue) and S (saturation) alone and raise or lower only L (lightness) by whatever unit you want (say, 10% each step). For example, if your base color is hsl(200, 80%, 50%), lowering only the lightness by 10% each time gives you hsl(200, 80%, 40%) and hsl(200, 80%, 30%) — a tone-on-tone palette with the same hue and saturation.
The catch is converting those HSL values back to HEX for your code. Converting HSL to HEX means working out the max and min from lightness and saturation, then applying a different formula depending on which 60-degree sector the hue falls into — so even one palette means running the math over and over.
Check it with our tool. Enter your base HSL values, the step size for lightness (or saturation), and how many steps you want, and it calculates and shows you the HEX and HSL code for each step.
Free · no sign-up · build a tone-on-tone palette right in your browser

Where people get stuck
| Situation | Why it happens |
|---|---|
| Adding or subtracting the same number from all three RGB channels | The per-channel ratios change, so the hue itself shifts |
| Changing hue (H) and saturation (S) along with lightness | You get a completely different color family, not tone-on-tone |
| Pushing lightness (L) close to 0% or 100% | The color approaches black or white and the hue information disappears |
| Stepping hue (H) while holding lightness fixed | You get colors cycling like a rainbow, not tone-on-tone |
As the table shows, tone-on-tone palettes usually fall apart when you move a value you should have left alone along with hue, saturation, or lightness. Move only lightness (or saturation) by a fixed step and you avoid the mistake.
The takeaway
Because RGB describes color by mixing red, green, and blue, the idea of "keep the hue, change only the brightness" doesn't exist separately inside the channel values. HSL separates hue, saturation, and lightness into independent axes, so stepping only lightness (L) gives you a tone-on-tone palette in the same color family.
Doing it by hand means reading the HSL values, calculating lightness step by step, and converting back to HEX — and that conversion is repeated math, so the more steps you need, the more tedious it gets.
Free · no sign-up · build a tone-on-tone palette right in your browser
FAQ
Can I make a tone-on-tone palette with RGB values alone?
Yes, but you have to calculate each of the three channels with a different ratio for every color, and if the math is even slightly off, the hue shifts or the saturation collapses. HSL, which holds hue fixed and moves only lightness, is simpler to calculate.
Should saturation (S) stay the same when I build a tone-on-tone palette?
To keep the sense of one color family, it feels more natural to fix saturation and step lightness (L) only. If saturation changes too, the same hue can look muddy in some steps and harsh in others, so it reads more like a mix of colors than tone-on-tone.
What step size for hue (H) feels natural?
Change the hue even a little and you no longer have tone-on-tone — you have a gradient that travels around the color wheel. If you want pure tone-on-tone, set the hue step to 0 and set only the lightness (or saturation) step.
This article was adapted from our Korean original. Read the Korean original