OKLCH to hex converter

It follows an explicit numerical path from cylindrical OKLCH coordinates through OKLab and linear RGB, then clamps channels that fall outside the displayable sRGB gamut. The result is deterministic, easy to automate, and accompanied by RGB and OKLab values so you can inspect exactly what was converted instead of treating the final hex code as a black box.

Enter a valid OKLCH color

Provide the color using CSS functional notation, such as oklch(62.8% 0.258 29.23). Lightness may be written as a percentage from 0% through 100%, or as a unitless value from 0 through 1. Chroma must be zero or positive. Hue is interpreted as degrees when it has no suffix, while the standard deg, grad, rad, and turn suffixes are also accepted. Hue can be outside the usual 0-to-360 range because it is normalized to the equivalent angle. The converter deliberately requires all three coordinates and does not accept alpha, the CSS none keyword, commas, hex input, or another color function. Those rules keep the contract focused on producing a six-digit opaque hex color and make malformed data fail clearly rather than being guessed into a plausible-looking result. Every numeric component must be finite; values such as Infinity and NaN are rejected before conversion begins. This strict input boundary is useful in build tools and data pipelines, where silently accepting an unintended format can spread an incorrect brand color through many generated assets.

Understand the conversion path

OKLCH describes a color with perceptual lightness, chroma, and hue. The converter first normalizes the hue and resolves the cylindrical coordinates into the a and b axes of OKLab with cosine and sine. It then applies the published OKLab transform to obtain linear sRGB channels. Those linear channels are passed through the standard sRGB transfer curve and quantized to integer red, green, and blue values from 0 through 255. Each byte becomes exactly two hexadecimal characters, so the primary result always has the form #RRGGBB. The response also includes the resolved OKLab coordinates and integer RGB channels. These intermediate values make debugging easier when a design application and a code pipeline appear to disagree. Floating-point intermediate values are rounded only for the reported OKLab object; the full internal precision is retained until the final RGB bytes are calculated. The algorithm uses no network service, random source, current time, locale formatting, or mutable state, so identical input produces identical JSON in the API and browser implementation.

Handle colors outside sRGB

OKLCH can describe colors that ordinary sRGB screens and six-digit hex notation cannot represent. When any converted linear RGB channel is below zero or above one, this converter clips that channel to the nearest boundary before applying the sRGB transfer curve. The response sets clamped to true whenever this happens. Clipping is predictable and fast, but it is not a perceptual gamut-mapping strategy: a very vivid input can lose nuance, change apparent hue, or collapse onto a fully saturated channel. Treat the flag as a signal to review the color, especially for brand palettes, accessibility tokens, and gradients where relationships between neighboring colors matter. If clamped is false, all channels were already inside sRGB before encoding. If it is true and visual fidelity is important, consider reducing chroma in the source OKLCH value and converting again until the color fits. This explicit behavior avoids invalid channel math and guarantees a usable six-digit output while remaining honest about the compromise. The conversion preserves no alpha channel because six-digit hex represents an opaque color; use a separate workflow when transparency is part of the intended result.