Developer & Web

HEX #FFB6C1: CSS LightPink, RGB and Readable Text

Convert #FFB6C1 to RGB 255, 182, 193, distinguish LightPink from Pink, and choose a legible foreground for an opaque pink background.

By Uddhav Gopani, FounderPublished 25 September 2026Reviewed 29 September 2026

HEX #FFB6C1: CSS LightPink, RGB and Readable Text

Identify the exact CSS colour

HEX #FFB6C1 is the CSS named colour lightpink. Its decimal channels are RGB 255, 182, 193. The byte FF is fifteen times sixteen plus fifteen, or 255; B6 is eleven times sixteen plus six, or 182; C1 is twelve times sixteen plus one, or 193. All three channels are fairly high, but red is strongest. This is an opaque sRGB value when written with six hexadecimal digits. The local HEX to RGB Converter can verify those three channel values from the code.

Distinguish LightPink from Pink

The CSS keyword pink refers to #FFC0CB, whose channels are RGB 255, 192, 203. That is a different specified colour: its green and blue channels are ten units higher than those of #FFB6C1. Therefore a design instruction saying only pink does not guarantee that a developer will choose the intended value. If the exact swatch matters, include #FFB6C1 or the keyword lightpink in the specification. Human descriptions such as pale pink are useful context but should not replace an exact identifier in a reproducible design handoff.

Use the converter in its supported direction

Enter #FFB6C1 and run the tool. It displays the normalized code #ffb6c1, RGB 255, 182, 193 and rounded HSL values. The change in case is only formatting. The input expects a three- or six-digit hexadecimal code, so entering lightpink itself is outside this local form's accepted format even though that keyword is valid in CSS. Likewise, entering the decimal RGB triplet belongs in the separate RGB to HEX Converter. A tool can support a useful subset of colour notation without implementing every syntax that a browser stylesheet accepts.

Interpret the hue and lightness calculation

For this colour, the maximum normalized channel is 1 and the minimum is 182/255. Their average gives lightness of approximately 85.686%. Saturation in HSL is 100%, because the highest channel has reached its endpoint while the other channels differ. The hue is approximately 350.959 degrees, so the tool displays HSL 351°, 100%, 86%. A high HSL saturation does not mean that the swatch will look as dark or intense as a fully saturated mid-lightness red. Lightness is an independent coordinate, and the high lightness here creates the pale appearance.

Calculate the text-pair contrast

Using the standard relative-luminance calculation for opaque sRGB colours, #FFB6C1 has luminance approximately 0.58566. Its contrast with black is approximately 12.71:1, and with white approximately 1.65:1. Black meets the WCAG minimum ratio for ordinary text on this background, while white does not. A white label may look stylistically consistent with a pastel theme but still be difficult to distinguish. These values are independent example calculations; the local converter does not perform a contrast assessment or determine whether an entire component or page satisfies accessibility requirements.

Keep transparency separate from the base swatch

The six-digit code specifies a fully opaque colour. If a designer adds opacity to a panel or places translucent white over it, the displayed result depends on the background and compositing. Do not reuse the opaque contrast result as though nothing changed. When a notification box uses this colour, preserve a solid, readable text treatment and identify the message with words such as Reminder or Error rather than relying only on its pink fill. Hover, selected and focus states should be checked separately when they alter the colours the user actually sees.

Verify a round trip before saving the token

To reconstruct the code from RGB 255, 182, 193, divide each channel into a multiple of sixteen and a remainder: 255 yields F and F, 182 yields B and 6, and 193 yields C and 1. Joining them gives FFB6C1. None of the last two pairs repeats its own digit, so this colour cannot be shortened exactly to a three-digit HEX value. Keep the six-digit token in the source file and record intentional alternatives separately. This avoids replacing a precise colour with an approximation when a palette is copied between systems.