1. Additive (RGB/HEX) vs. Subtractive (CMYK) Models
Displays and digital UI use the RGB Additive Color Model, combining Red, Green, and Blue light waves to emit colors. HEX codes represent hexadecimally encoded RGB values.
Physical printing uses the CMYK Subtractive Color Model (Cyan, Magenta, Yellow, Key/Black), absorbing light through layered inks.
2. Why UI Designers Prefer HSL / HSV
RGB values are unintuitive for human adjustment. HSL (Hue, Saturation, Lightness) and HSV (Hue, Saturation, Value) translate colors into intuitive parameters.
Designers can lock a base Hue value and shift parameters to build Hover, Active, or Disabled system UI components.
3. Understanding Tints (Lighter) and Shades (Darker)
In design system guidelines (e.g., Tailwind CSS), monochromatic swatches derive systematically from a base color:
- Tints (Lighter Tones): Mixes pure white into the base color (increasing Lightness) for card backgrounds, subtle container fills, and hover highlights.
- Shades (Darker Tones): Mixes pure black into the base color (decreasing Lightness) for text content, depth dropshadows, and structural borders.
Color Conversions FAQ
Q: Why do converted CMYK color codes look dull on digital RGB displays?
RGB and CMYK models possess different color gamut volumes. The RGB color space encompasses vibrant saturated neon blues and greens that fall outside printable CMYK gamuts.
Web CMYK values use mathematical approximations; consult physical Pantone spot-color books for production print proofing.
Q: Should I use HEX, RGB, or HSL formats in CSS/Tailwind?
Standard web development benefits from HEX codes due to concise syntax. When dynamic opacity adjustment is needed, use RGBA or 8-digit HEX syntax.
For design systems using native CSS variables, HSL allows dynamic generation of derivative color schemes using math expressions.