Brand colour palette: how to build one properly

Nearly every amateur palette has the same fault: five colours of equal importance. The result is that no colour ever repeats often enough to become yours, and every new material looks like it belongs to somebody else.

Palettes that work have a strict hierarchy, and most of the surface is taken up by neutrals.

The structure: one colour does 10% of the work and all of the meaning

Choosing the accent

Three criteria, in order of practical importance:

1. 01Differentiation from competitors. Put five competitors' logos on one screen. If four are blue, a fifth blue will be remembered by nobody. Colour is the cheapest differentiation tool you have.
2. 02Fit with your [personality](/guides/brand-strategy). Not in the sense of colour-psychology folklore, but in saturation and lightness: a highly saturated colour reads as energy and urgency, a desaturated one as restraint, whatever the hue.
3. 03Technical behaviour. It has to work as a button fill with white text on it, survive CMYK printing without shifting, and not disappear on a cheap screen. Pure yellow and cyan fail these tests regularly.

On colour psychology, briefly: the associations are real but weak and heavily dependent on culture and context. Consistency matters far more, an ordinary colour used with discipline beats a “correct” colour used haphazardly.

Neutrals: where quality is won or lost

Neutrals cover most of any material, so they decide the overall impression. Two things make them look expensive:

• Do not use pure black (#000000) and pure white (#FFFFFF) as your main pair. The contrast is harsh on screen. A near-black around #0E0E10 and a near-white around #FAFAFA immediately look better.
• Give the neutrals a trace of the accent. A grey with a tiny amount of the accent hue in it ties the whole palette together. The difference is almost imperceptible on a swatch and very visible across a full page.

You need steps, not one value: primary text, secondary text, muted text, divider, surface. Five steps cover nearly everything.

Contrast: the non-optional part

Contrast is not an aesthetic preference, it is the condition for text being readable, including by a 55-year-old customer, on a phone, outdoors. The WCAG thresholds are a reasonable minimum:

Checking takes seconds with any contrast tool. The most common real defect: light grey text on white, because it “looks airier”, it looks airy on the designer's monitor and is illegible on everyone else's.

Dark mode

If your product is digital you need palettes for both modes, and you do not get one by inverting the other. Two things must change: the accent has to be lightened, because a saturated colour on a dark background reads darker than it is, and surfaces are raised with lightness, not shadow, shadows are close to invisible on black.

What to fix in the guidelines

• Every code: HEX, RGB, CMYK, Pantone if you print often.
• The proportions: what share of a typical material each role covers.
• The permitted pairs: which text on which background, with contrast verified.
• The prohibitions: which combinations are never used.
• Tokens, if you have a digital product: semantic names (`background`, `text-primary`, `accent`) instead of colour names. When the hue changes you change one value, not three hundred places.

All of that belongs in the brand guidelines, next to typography and the logo rules.

Common mistakes

• Colours pulled from a moodboard photograph. They look good in context and collapse out of it.
• A gradient instead of a colour. A gradient cannot be printed consistently, cannot be embroidered, and cannot be a colour code.
• A palette with no neutrals. Five vivid colours and no grey means you cannot set a readable paragraph anywhere.
• Checking only on your own screen. Test on a cheap phone and, if you print, on real paper.
• Different colours in different files. The most common real defect in small companies: three near-identical shades all claiming to be the official one.

A fast route to a coherent palette

If you want to see several colour directions built correctly (with steps, matched neutrals and verified contrast) starting from your own brief, RHAM generates the palette alongside the rest of the identity and exports it as CSS tokens, ready to use. It stays editable: the structure is generated, the final call is yours.