Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is OKLCH?
OKLCH is a way of writing colors that tries to match how people actually perceive them. It encodes a color with three values — Lightness, Chroma, and Hue — plus an optional Alpha for transparency. The point is that changing one value produces a more predictable, even-looking change than it does in older formats like hex or HSL, where the same numeric tweak can look wildly different depending on the color.
What the three values mean
- Lightness — how bright or dark the color is, on a scale from black to white.
- Chroma — how vivid or muted it is. Low chroma is grayish; high chroma is saturated.
- Hue — the color family, expressed as an angle around a color wheel (reds, blues, greens, and so on).
- Alpha — optional transparency, as in RGBA.
Why designers and developers use it
The practical benefit is control. If you build a palette in OKLCH and keep hue and chroma fixed while stepping lightness, you get a set of shades that read as genuinely consistent rather than lurching in saturation. The same applies to hover states, dark-mode variants, and tint scales — adjust one axis and the rest of the color's character stays put.
Where it fits alongside other formats
| Format | Best thought of as | Main trade-off |
|---|---|---|
| Hex / RGB | Raw device values | Familiar and universally supported; not perceptually even |
| HSL | Hue, saturation, lightness | Intuitive but lightness changes are uneven across hues |
| OKLCH | Perceptual lightness, chroma, hue | More predictable editing; newer, so support and tooling vary |
OKLCH is not a replacement for hex in your stylesheet so much as a better space to design and reason in. A common workflow is to pick and tune colors in OKLCH, then output the hex or rgba values your project needs.
A concrete scenario
Suppose you are building a button component with five states. In HSL, darkening a yellow and darkening a blue by the same amount often leaves one looking muddy and the other barely changed. In OKLCH, you hold hue and chroma steady and step lightness down; the states stay recognizably the same color, just progressively darker.
Try it
Open OKLCH Color Picker & Converter, paste in a hex, RGB, or HSL value you already use, and read off its OKLCH equivalent. Then nudge only the Lightness value and watch how evenly the color shifts — that single experiment tells you quickly whether this model suits the way you work.
How do I convert a HEX, RGB, or HSL color to OKLCH?
Paste the color value into the picker's input field at OKLCH Color Picker & Converter. The tool accepts HEX, RGB, and HSL strings and converts them to OKLCH immediately, so the fastest path is copy the value from your stylesheet or design file, paste it, and read the resulting L, C, and H numbers.
What you get back
The interface exposes the three OKLCH components as separate controls, plus an alpha channel:
- Lightness (L) — perceived brightness, roughly 0–1, independent of hue.
- Chroma (C) — color intensity or saturation; higher values are more vivid.
- Hue (H) — the angle around the color wheel in degrees.
- Alpha — transparency, kept separate from the color itself.
There is also a 3D view, which is useful when you want to see how a color sits in the space rather than just read three numbers.
A practical workflow
If you are moving an existing palette into OKLCH, convert your current colors first, then adjust from there rather than starting from scratch. For example, a designer maintaining a brand palette in Figma can paste each HEX token, note the L and C values, and then build lighter or darker variants by changing only L. That keeps hue consistent across a ramp, which is the main reason people adopt OKLCH in the first place.
Watch the gamut
Not every OKLCH color is displayable in sRGB. The page includes a closest-fallback option (matched by chroma) and a P3 fallback setting, which matters if you are targeting both standard sRGB screens and wider-gamut P3 displays. If a converted color looks slightly flatter than expected in a browser, the fallback is likely doing its job. Test the final values in your actual target environment before committing them to a design system.
Next step
Convert your three or four most-used brand colors, write down their L, C, and H values, and compare the hue angles. Colors that should feel related but currently do not often reveal inconsistent hue angles — that is the first thing worth fixing.
What does the sRGB fallback for an OKLCH color mean and when should I use it?
The sRGB fallback is the closest color your sRGB screen can actually display when the OKLCH color you picked sits outside the sRGB gamut. OKLCH can describe colors that are more saturated than sRGB allows — especially in cyan, green and magenta ranges — so a browser or design tool must substitute a nearby in-gamut value. The fallback shown on OKLCH Color Picker & Converter is the closest sRGB match by chroma, meaning it keeps lightness and hue as close as possible and pulls saturation down until the color fits.
What the fallback changes
| Property | What usually happens |
|---|---|
| Lightness | Stays close to your OKLCH value |
| Hue | Stays close to your OKLCH value |
| Chroma | Reduced until the color fits inside sRGB |
| Appearance | Slightly less vivid, sometimes noticeably flatter in greens and cyans |
When to use it
- Shipping to sRGB-only displays or older browsers. If your CSS uses
oklch()without a fallback, some environments render a duller or unexpected color. Supplying the sRGB fallback gives you control over what those users see. - Designing for a mixed audience. Most phones and laptops are still sRGB or near-sRGB, so the fallback is what the majority will actually see.
- Print or brand work with strict color targets. If the brand color must match a physical or legacy reference, start from the sRGB value rather than the wider-gamut OKLCH one.
- You need predictable contrast. Fallbacks preserve lightness better than hue, so text and UI contrast is usually safe.
When to skip it
If you are targeting P3 displays — recent iPhones, many MacBooks, modern Android flagships — the wider-gamut OKLCH color will render more vividly, and the sRGB fallback is only a safety net. The picker also notes P3 fallback and an auto hex/rgba option, which is useful when you want the tool to handle the substitution for you.
A practical next step
Pick your OKLCH color, note the sRGB fallback value, then test both in a real browser on an sRGB monitor and a P3 device side by side. If the difference is unacceptable for your brand, choose a slightly lower-chroma OKLCH color that sits inside sRGB from the start — that way there is no visible shift between devices.
How do I use OKLCH colors in Figma with a P3 color profile?
You can use OKLCH colors in Figma by converting them to a P3-compatible value first, because Figma does not accept OKLCH directly. The OKLCH Color Picker & Converter is built for exactly this: it lets you pick in OKLCH and then copy the result in a form Figma can use, including a P3 fallback option.
A practical workflow
- Open the OKLCH Color Picker & Converter and set Lightness, Chroma and Hue, or paste an existing HEX/RGB/HSL value to convert it to OKLCH.
- Decide whether you need sRGB or P3 output. The tool shows a closest sRGB fallback by chroma, which matters when a vivid OKLCH color sits outside the sRGB gamut.
- If your Figma file uses a P3 color profile, copy the P3 value rather than the sRGB fallback, so the wider-gamut color survives into the design file.
- Paste into Figma as a fill or style. Keep the OKLCH numbers documented somewhere (a comment, a token name or a spec) so the color stays editable conceptually even though Figma stores it in another format.
Why P3 matters here
OKLCH and P3 solve different parts of the same problem. OKLCH is a perceptual color model: equal changes in Lightness or Chroma feel roughly equal to the eye, which makes it good for building palettes and ramps. P3 is a wider display gamut: it can show more saturated colors than sRGB on modern screens.
So the trade-off is:
| Choice | Best for | Risk |
|---|---|---|
| sRGB fallback | Broad compatibility, older displays, web CSS | Vivid OKLCH colors get clipped or dulled |
| P3 value | Modern Macs, iPhone, high-gamut displays, Figma P3 profile | May look different or clip on sRGB-only screens |
For a design system, a common approach is to define the palette in OKLCH for logic and consistency, then export both an sRGB fallback and a P3 value where saturation matters.
A concrete scenario
Suppose you are building a brand palette with a very saturated green. In OKLCH you set a high Chroma at a fixed Hue. The tool warns you that the color is outside sRGB and shows the closest sRGB fallback. If your Figma file is set to a P3 color profile, use the P3 output for the primary brand fill and keep the sRGB fallback for contexts that need it. That way the design looks vivid on a modern display and still degrades sensibly elsewhere.
Next step
Pick one color you already use, convert it to OKLCH, and compare the P3 and sRGB versions side by side in Figma on a high-gamut screen. If the difference is noticeable on your key brand colors, adopt a dual-value workflow; if not, the sRGB fallback alone may be simpler to maintain.
What do the Lightness, Chroma, and Hue values control in the OKLCH picker?
Lightness, Chroma, and Hue are the three axes of the OKLCH color model, and each slider controls a different property of the resulting color.
Lightness (L) sets how light or dark the color is, independent of its hue. In OKLCH, lightness is designed to be perceptually uniform, so moving the slider by the same amount should produce a similar visual change whether you're working with yellow or blue. This is a key difference from HSL, where the same lightness value can look very different across hues.
Chroma (C) controls colorfulness or saturation — how far the color sits from a neutral gray. At zero chroma, you get a gray; higher values produce more vivid colors. Chroma is not unlimited: each hue and lightness combination has a maximum chroma that can be displayed in a given color space, so pushing chroma too far may take the color out of gamut.
Hue (H) selects the color family — red, orange, yellow, green, blue, purple, and so on — as an angle on the color wheel. Changing hue rotates around the wheel while keeping lightness and chroma roughly constant.
| Value | Controls | Practical effect |
|---|---|---|
| Lightness | Perceived brightness | Makes the color lighter or darker without shifting hue |
| Chroma | Color intensity | Moves from gray to vivid; zero is neutral |
| Hue | Color angle | Picks the color family (red, blue, etc.) |
The page also lists an Alpha control, which adjusts transparency, and a 3D view for seeing how the three axes relate. Because OKLCH is designed for perceptual uniformity, it's often easier to build consistent palettes: you can hold lightness steady and vary hue for a set of equally bright colors, or hold hue and vary lightness for tints and shades.
For a concrete next step, try this: pick a base color, note its L, C, and H values, then create a lighter and darker version by changing only L while leaving C and H untouched. Compare that with the same experiment in HSL to see why OKLCH is often preferred for palette work. If you need to convert an existing hex, RGB, or HSL color, the page's converter can translate it into OKLCH values so you can start from something familiar.
How does OKLCH differ from LCH when picking or converting colors?
OKLCH is LCH with a perceptual correction applied to hue: it is designed so that a given hue angle looks the same across lightness and chroma levels, and so that equal numeric steps correspond more closely to equal visual steps. Classic LCH (CIELCh, derived from CIELAB) has a well-known blue-purple hue shift — a hue that reads as blue at high lightness can drift toward purple as you darken it. OKLCH avoids most of that drift, which is why it is the more practical choice for design systems where you generate tints and shades from one hue.
What changes in practice
| Aspect | LCH (CIELCh) | OKLCH |
|---|---|---|
| Hue stability | Hue can shift noticeably as lightness/chroma change, especially in blues and purples | Hue stays more consistent across the lightness range |
| Numeric intuition | Steps are less predictable relative to perceived change | Lightness and chroma behave more like the "expected" visual scale |
| Gamut handling | Values can fall outside sRGB; conversion is needed | Same issue, but the picker can show the closest sRGB fallback |
| Ecosystem | Common in print/color-science tools | Growing in CSS, design tools and dev workflows |
Both are polar spaces: lightness, chroma (colorfulness), hue. Neither is a device color space like sRGB or Display P3 — they describe colors abstractly, and you convert to hex, rgba or a wider gamut for output.
Concrete use cases
- Building a palette: pick one hue in OKLCH, then vary lightness for a scale. The hue stays recognizable, so a "blue 100–900" ramp looks like one family.
- Converting existing colors: paste a hex, RGB or HSL value and read off its OKLCH coordinates to understand why a color feels muddy or oversaturated.
- Cross-gamut work: if you target Display P3, OKLCH lets you define a color that is out of sRGB range and then choose a sensible sRGB fallback rather than discovering the clipping by accident.
On OKLCH Color Picker & Converter, the interface exposes Lightness, Chroma, Hue and Alpha, offers a 3D view, and lets you paste HEX/RGB/HSL to convert; it also indicates the closest sRGB fallback by chroma and points to using it in Figma with a P3 color profile. That fallback behavior is the practical difference from a plain LCH picker: you see what an sRGB-only browser or app will actually render.
How to decide
Use OKLCH when the color is part of a system you will adjust — themes, ramps, dark mode, accessible contrast tuning — because hue drift is the main thing that breaks generated palettes. Use LCH when you are matching an existing color-science or print workflow that already specifies CIELCh values, or when a downstream tool expects LCH input.
A good next step: take a color you already use, paste it into the picker, note its OKLCH lightness and chroma, then change only lightness and watch whether the hue holds. If it does, OKLCH is a safe basis for your scale.
User reviews (0)