Building Color Palettes
Need a palette fast? Generate a base palette, lock the colors you like, keep hitting generate for the rest:
1. Go to coolors.co/generate
2. Press spacebar to generate random palettes
3. Click the lock icon on colors you want to keep
4. Keep pressing spacebar until the unlocked slots feel right
5. Click each color to fine-tune hex/HSB values
6. Export (PNG, PDF, SVG, CSS vars, Tailwind config, SCSS)
Progress:
- Define the goal (branding, UI, illustration, data viz, etc.)
- Choose a starting method (generate from scratch, extract from image, or search explore/palettes)
- Build/refine the palette (lock, shuffle, adjust)
- Validate accessibility (contrast checker)
- Preview in context (visualizer)
- Export in the right format for the target platform
1. Define the goal Ask: is this for a UI (needs semantic colors — primary/secondary/success/error/neutral grays), a brand identity (needs 2-5 core + accent colors), an illustration (broader harmonious set), or data visualization (needs distinguishable, colorblind-safe hues)?
2. Choose a starting method
- From scratch:
/generate— spacebar-driven random generation with lock/unlock per swatch. - From an image:
/image-picker— upload a photo, auto-extract dominant colors, adjust the number of swatches and selection points. - From existing inspiration:
/palettes/explore— browse curated/trending palettes, filter by hue, tag (branding, pastel, vintage, etc.), or search keywords. - From a URL/screenshot:
/palettes/urlor/palettes/camera— pull colors from a live webpage or camera capture.
3. Build and refine
- Lock colors you're committed to; regenerate the rest to see new combinations without losing what works.
- Adjust each color's hue/saturation/brightness individually rather than regenerating everything — preserves palette "mood" while fixing one bad swatch.
- Use harmony rules as a mental check: monochromatic (single hue, varied lightness), analogous (adjacent hues), complementary (opposite hues), triadic (3 evenly spaced hues). Most logo/brand work wants analogous + one complementary accent.
- For UI work, ensure the palette includes: a neutral/gray scale (at least 3 steps), one primary action color, and semantic colors (success=green-ish, warning=amber, error=red) — don't let these clash with the brand hue.
4. Validate accessibility
Run foreground/background pairs through /contrast-checker. Target WCAG AA minimum: 4.5:1 for normal text, 3:1 for large text/UI components. If a pairing fails, darken/lighten rather than changing hue, to preserve brand consistency.
5. Preview in context
Use /visualizer to see the palette applied to a real mockup (website, poster, app) before committing — flat swatches often look different once applied to actual layouts.
6. Export Match format to destination:
- Code/dev handoff → CSS variables, SCSS, or Tailwind config (
/tailwind) - Design handoff → PDF/PNG swatch sheet, or Figma plugin import
- Quick share → palette URL (
coolors.co/{hex1}-{hex2}-{hex3}...)
Example 1:
Input: "I need a palette for a fintech app — trustworthy but modern, needs dark mode support."
Output: Base: a deep navy (#0B1D3A) as primary, a bright teal/cyan accent (#2DD4BF) for CTAs, neutral gray scale from #0F172A (dark bg) to #F8FAFC (light bg), semantic green (#22C55E)/red (#EF4444)/amber (#F59E0B). Verify navy-on-white and white-on-navy both pass 4.5:1 contrast. Export as CSS custom properties with --color-primary, --color-accent, --color-bg-dark, etc.
Example 2: Input: "Extract a palette from this product photo for marketing materials." Output: Use image-picker, upload photo, pull 5 dominant swatches (e.g., background, product color, shadow tone, highlight, accent). Drop near-duplicate grays, keep the most saturated color as the accent, generate a neutral pairing for text using the contrast checker.
- Lock first, generate second — don't regenerate a whole palette just to fix one color.
- Always include at least one near-black and near-white (or off-black/off-white) for text/background use, even in "colorful" palettes.
- Check contrast early, not after the design is finalized — hue shifts to fix contrast can break brand consistency if done late.
- Keep UI palettes small (5-7 core colors + tints/shades); keep brand palettes smaller still (2-4 core).
- Name colors semantically in exports (
primary,surface,danger) rather than only hex, so dev handoff is unambiguous.
- Don't pick palettes purely on aesthetic appeal without running contrast checks — a gorgeous pastel-on-pastel palette can be unusable for text.
- Don't use more than ~2 saturated/loud colors in one palette — pair bold accents with muted neutrals.
- Don't ignore colorblindness — check how the palette collapses under deuteranopia/protanopia simulation if it's for data viz or status indicators (red/green alone is a common failure).
- Don't export only PNG swatches for a dev handoff — always provide a code-usable format (CSS vars, Tailwind, SCSS).