Complete Hex Conversion Checklist for 2026

Updated 2026-03-27 · By SPUNK13 · Back to spunk.bet

Hex conversion covers two completely different jobs — colour values and raw bytes — and the mistakes are different in each. Work through this list and you will catch the ones that produce subtly wrong output rather than obvious errors.

Colour hex: the expansion rule

Three-digit hex expands by duplicating each digit, not by zero-padding. #F0F is #FF00FF, not #F00F0F and definitely not #0F0F0F. Four-digit hex works the same way with alpha: #F0F8 becomes #FF00FF88. Any converter that pads instead of duplicating is wrong, and the error is invisible until someone compares against a design file.

Colour hex: the checklist

• Accept both #-prefixed and bare input; normalise to lowercase for comparison, since #AABBCC and #aabbcc are the same colour.
• Support 8-digit hex with alpha — it is supported in every current browser. 80 is roughly 50% alpha, CC roughly 80%, FF opaque.
• Convert to RGB with parseInt(hex.slice(1,3), 16) per channel; convert back with value.toString(16).padStart(2, '0'). Forgetting the pad turns 10 into "a" and silently produces a five-character colour.
• Remember hex is sRGB only. There is no hex notation for Display P3 or wider gamuts — those need color(display-p3 ...) or oklch().
• For contrast checks, do not average the channels. Compute relative luminance with the WCAG formula, which linearises each channel before weighting them 0.2126, 0.7152, 0.0722.
• Lightening or darkening by adding to each channel produces muddy results. Convert to a perceptual space — oklch() is now usable directly in CSS — and change lightness there.

Byte hex: the checklist

• Decide on a representation before you start: xxd -p file gives continuous hex, xxd file gives an offset-plus-ASCII dump, hexdump -C gives the canonical form most tools expect.
• Reverse a hex string back to bytes with xxd -r -p. If it produces garbage, check for whitespace and newlines in the input first.
• Watch endianness. A 32-bit integer 0x0000002A appears as 2a 00 00 00 on a little-endian dump and 00 00 00 2a on a big-endian one. Network protocols are big-endian; your laptop is not.
• Hex has no notion of signedness. 0xFF is 255 or -1 depending on the type you decode into, and this is where checksum implementations usually go wrong.
• Two hex characters equal one byte, so a hex string is always even-length. An odd length means truncated input, not a value to left-pad.
• printf '%02x' 42 formats a single byte; od -An -tx1 is the portable alternative when xxd is missing.

Before you ship the conversion

Round-trip everything: hex to value to hex must give the original string, modulo case. Test the boundaries — 00, FF, #000, #FFFFFFFF — and test invalid input explicitly, because a converter that returns NaN for #GGG and then renders it into CSS produces a page with no styling and no error.