Why are we still using HEX and RGB for design work in 2025?
Both are device-dependent, non-perceptual color spaces created for old hardware. They don’t reflect how humans actually see color, and they make tasks like “adjust the color a bit” or “make this lighter” behave unpredictably.
Modern color spaces like OKLCH (and even LCH) give:
predictable lightness changes perceptual uniformity more accurate contrast control easier palette generation fewer surprises when colors shift between devices
Browsers support OKLCH now, CSS supports it, and most modern tools are catching up. Yet most workflows still start with HEX → HSL → guessing.
What’s keeping teams, frameworks, and designers tied to HEX/RGB at this point? Legacy tools? Inertia? Lack of education? Curious to hear other people’s experiences.
mustafaiste•2mo ago
Both are device-dependent, non-perceptual color spaces created for old hardware. They don’t reflect how humans actually see color, and they make tasks like “adjust the color a bit” or “make this lighter” behave unpredictably.
Modern color spaces like OKLCH (and even LCH) give: predictable lightness changes perceptual uniformity more accurate contrast control easier palette generation fewer surprises when colors shift between devices
Browsers support OKLCH now, CSS supports it, and most modern tools are catching up. Yet most workflows still start with HEX → HSL → guessing.
What’s keeping teams, frameworks, and designers tied to HEX/RGB at this point? Legacy tools? Inertia? Lack of education? Curious to hear other people’s experiences.