Hex to CMYK Converter

About HEX and CMYK color

Screens and printers describe color in fundamentally different ways. A HEX code like #FF6699 is an RGB value: it tells a display how much red, green, and blue light to emit. RGB is an additive model, because adding all three at full strength makes white. CMYK is the model of print: cyan, magenta, yellow, and key (black) inks sit on paper and subtract wavelengths from reflected light. Layering all the inks moves toward black. This tool converts a HEX/RGB code into CMYK percentages so you can take a screen color toward print.

The catch is that the two systems cover different ranges of color, called gamuts. RGB screens can show vivid, glowing colors (electric blues, neon greens) that no combination of CMYK inks can reproduce. So conversion is always an approximation: the formula maps a HEX value to the nearest CMYK recipe, but the printed result can look duller than the screen, especially for saturated hues.

The K in CMYK stands for "key," the key plate that historically held the black detail. Printers use a dedicated black ink rather than mixing full cyan, magenta, and yellow because it is cheaper, dries faster, and keeps text and fine lines crisp. That is why CMYK has four channels while RGB has three.

How it works: the formula

The tool parses the hex into red, green, and blue (0 to 255), normalises each to a 0 to 1 fraction, then applies the standard RGB-to-CMYK equations:

r, g, b = hex_to_rgb(input) / 255      // each 0..1
K = 1 - max(r, g, b)                    // black
C = (1 - r - K) / (1 - K)               // cyan
M = (1 - g - K) / (1 - K)               // magenta
Y = (1 - b - K) / (1 - K)               // yellow
// multiply each by 100 for percentages; if K = 1 (pure black), C=M=Y=0

• max(r, g, b) finds the brightest channel, which sets how little black is needed.
• Pure white (#FFFFFF) gives K = 0 and C = M = Y = 0 (no ink).
• Pure black (#000000) gives K = 100 percent and C = M = Y = 0.
• This is the naive formula; it ignores ICC profiles, ink, and paper.

Worked example: converting #FF6699

1. Split the hex. FF = 255 (red), 66 = 102 (green), 99 = 153 (blue).
2. Normalise. r = 1.0, g = 0.4, b = 0.6.
3. Black: K = 1 - max(1.0, 0.4, 0.6) = 1 - 1.0 = 0, so K = 0 percent.
4. Cyan: (1 - 1.0 - 0) / (1 - 0) = 0, so C = 0 percent.
5. Magenta: (1 - 0.4 - 0) / 1 = 0.6, so M = 60 percent.
6. Yellow: (1 - 0.6 - 0) / 1 = 0.4, so Y = 40 percent.

The result is cmyk(0%, 60%, 40%, 0%), a bright pink built entirely from magenta and yellow ink with no black. That high saturation is exactly the kind of color that may shift slightly when actually printed.

Reference: common HEX colors in CMYK

Common pitfalls

• Trusting the formula for production print. The naive conversion ignores ICC profiles, paper, and ink. For final files, convert through a color-managed app using your printer's profile (such as SWOP or FOGRA).
• Expecting screen-perfect color. Saturated RGB colors often fall outside the CMYK gamut and will print duller. Always proof before a run.
• Forgetting black generation choices. The simple formula uses maximum black removal (GCR). Real print workflows tune how much black replaces CMY, which changes ink usage and richness.
• Entering an invalid hex. The tool accepts 3- or 6-digit hex with or without the leading #. Other formats (rgb(), hsl(), color names) will not parse.
• Treating percentages as exact ink coverage. CMYK percentages are a target; dot gain on press means printed coverage often differs from the nominal value.

Related tools

Common mistakes and pitfalls

• Pasting input that includes extra whitespace or quotes the encoding does not allow - clean the input first.
• Expecting reversed conversion to give byte-identical original when the encoding is lossy (some text -> binary -> text round-trips can lose multibyte chars if encoding is wrong).
• Mixing encodings (e.g., URL-encoded text inside a base64 string) - decode in the right order.
• Forgetting that some encodings have multiple valid forms (uppercase vs lowercase hex, padded vs unpadded base64).

Frequently asked questions