HSL to OKLAB
Color Convert Engine
Enter a color in any supported format; the engine outputs every other color space.
Input Mode
Accepts #RGB or #RRGGBB, with or without #.
Preview
#1E40AF
Preview uses the sRGB color space.
Output — all color spaces
How to use
- Provide hue as degrees and saturation/lightness as percentages, then check that the hue wheel direction matches your design intent.
- Hue wraps at
360°; small hue edits can jump across the spectrum if you are not watching the numeric field. - Confirm lightness shifts read correctly on both light and dark UI backgrounds.
FAQ
What is HSL to OKLAB used for?
HSL to OKLAB is used when your source color is expressed as hue, saturation, and lightness (`hsl()` / `hsla()` style angles and percentages) but your destination expects OKLAB coordinates—a perceptually uniform space popular for resilient gradients and interpolation—common when aligning design tools, CSS, print specs, or APIs.
Is my data uploaded?
No. Processing runs locally in your browser.
Does HSL match CSS `hsl()` exactly?
Values align with the usual CSS mental model; always validate critical brand colors in the browser because surrounding contrast changes perception.
Introduction
HSL splits color into a hue angle (degrees), saturation (how vivid it is), and lightness (blend toward white or black)—the same mental model as CSS hsl(). That is what we treat as the from (HSL) color encoding on this page.
OKLAB is a newer perceptually uniform space built for predictable interpolation and distance judgments—common when blending gradients or evaluating pairs mathematically. That is the to (OKLAB) encoding you get after conversion.
A HSL to OKLAB converter bridges them when your pipeline outputs HSL but the next step expects OKLAB—without redoing the coordinate math by hand.
What is HSL to OKLAB?
HSL to OKLAB maps colors described in hue, saturation, and lightness (hsl() / hsla() style angles and percentages) into OKLAB coordinates—a perceptually uniform space popular for resilient gradients and interpolation. The perceptual aim is the same color expressed with different coordinates—ideal when downstream systems disagree on notation.
Key Features
Fast conversion helps when you are juggling HSL inputs against OKLAB consumers in the same sprint.
Live preview catches transcription mistakes early, especially when channels have different ranges or units.
Copy-ready output reduces slack-and-paste errors moving from spreadsheets or PDF specs into code.
Common Use Cases
- Shipping UI tokens where APIs expose HSL but theme files require OKLAB.
- Preparing brand palettes for mixed pipelines—web RGB alongside print CMYK or perceptual LAB QA.
- Debugging divergent pickers by exporting one canonical mix and re-importing it elsewhere.
Best Practices
- Normalize inputs (confirm units and ranges) before trusting downstream diffs.
- Compare previews on both light and dark chrome when contrast ratios matter for accessibility.
- Bookmark the inverse OKLAB to HSL when you frequently round-trip edits.
Related tools
These complement HSL to OKLAB when you are iterating palettes under real UI constraints:
- Color Converter — Jump to any supported pair from the suite hub.
- OKLAB to HSL — Reverse direction when edits bounce between teams.
- HSL to HEX — Nearby conversion from the same HSL source when you need another output format.
- Color Picker — Dial or sample a color visually, then route it through the converter chain.