Famous brand colour palettes: exact hex values and how to use them

Every brand colour is a design decision you can borrow

A brand colour is a compressed design decision. The stripe next to Spotify's name is a specific green that survived years of designers, focus groups and legal trademark screens. Stripe's indigo reads as fintech before the logo is even legible. These values are not random — they were tuned to be recognised at a glance and to hold up in real products.

That makes them excellent starting colours for your own work. A brand palette is a hue that already passes the two tests your palette will eventually face: it is distinctive, and it performs on screen. Borrowing one as a seed is not copying a brand, it is starting from a colour that has already been battle-tested.

Where these hex values come from

Most brands publish official colour values in their press kits and brand guidelines — the same documents agencies use to build their decks. Our brand palettes dataset in /tools/brand-palettes collects 100+ of these widely published reference values, grouped by sector, so you can browse without tab-hopping through corporate PDFs.

Be aware of what the data is and is not. The values are widely published references rather than legal swatches, they cover only the primary brand colour (most brands have whole systems behind them), and using them does not mean the brand endorses your project. Treat them as starting points, not licences.

The exact values

Here are a handful with the numbers next to them, exactly as they appear in the dataset:

• Stripe — #635BFF, the indigo that owns modern fintech
• Spotify — #1DB954, a green that survives against dark and light backgrounds
• Netflix — #E50914, pure alarm red but restrained to a single surface
• Slack — #4A154B, a plum chosen for calm long-session software
• Instagram — #E4405F, the gradient core of the app icon
• Figma — #A259FF, a violet aimed squarely at the design audience

Start a design system from a brand colour

The workflow we built ChromaBrew around takes one hex and does the rest: banks of shades from 50 to 950, semantic tokens, light and dark themes, WCAG contrast checks and production exports. A brand colour is the perfect first input, because it anchors the whole system in a hue you already trust.

Open the generator, drop in the hex, and the scale, tokens and previews follow the hue end to end. From Stripe indigo, the mechanical result looks like this:

:root {
  --background: #f5f4ff;
  --surface: #ffffff;
  --primary: #635bff;
  --secondary: #7a6ff2;
  --accent: #7c3aed;
  --foreground: #1e1b2e;
}

Why a brand colour is such a good seed

A hue-anchored scale inherits the properties of its seed. If Spotify's green reads clearly in an app icon at 16 pixels, the 700 step of a scale derived from that same hue carries the same clarity. You skip the hardest part of palette design — picking a hue that is both distinctive and usable — and jump straight to the structural work of shades, roles and contrast.

The caveat is that a hue is not a palette. The perceptual distance between your brand hue and the neutrals, the darkness of your surface stack, and the exact ratio your typography needs against it are all decisions the generator still has to make. That is precisely what the seed workflow is for: the hue arrives ready, everything downstream is derived and checked.

Copy it exactly — then make it yours

Exactness matters more than people expect. #635BFF and #645CFF are different colours to the eye, and a hex value is a promise you either keep or quietly break. Copy the exact value from the brand palette entry, then regenerate the scale so every derived shade stays true to that hue. Your system can borrow the anchor while being entirely your own.