How many brand colors do I need?

Usually one primary plus derived support — a neutral scale, functional colors, and perhaps one or two secondaries with named jobs. Most palettes that feel thin lack structure, not hues; most that feel chaotic have too many hues and no roles.

My brand color fails contrast on buttons — what now?

Move the fill one step darker on its own ramp rather than abandoning the color — the hue carries the recognition, and a darker step keeps it. Deriving the button text as a checked on-color prevents the failure from returning after the next brand tweak.

How do I convert Pantone or CMYK colors for screens?

Pick the closest perceptual match and accept that some inks — vivid oranges, deep teals — have no exact screen twin. What matters is committing to one screen value and deriving everything from it, rather than living with five approximations.

What is the difference between brand colors and UI colors?

Brand colors identify; UI colors function. In a working system they meet through derivation — the brand seed generates the ramps, and UI roles like borders, states and text pick contrast-checked steps from them.

Can we change our palette without losing recognition?

Usually, if you know what carries the recognition — most often the hue and its role, not the exact value. Audit what people actually see (the hue on the truck, the app icon), preserve that, and let the supporting values move.

Do black and white count as brand colors?

The neutral scale is a real brand decision — warm, cool or brand-tinted grays change how a product feels as much as the accent does — but it is chosen once as a temperature, not picked swatch by swatch.

Brand Colors: From One Color to a Working System

A brand color is a promise of recognition — and on its own it is not yet a system. The work of brand color is everything around the swatch: turning one approved value into the hundred related values a product needs, keeping it readable where the law asks, translating it between print and screen, and carrying it through rebrands without losing what people recognize. This hub collects our guides on that work; the fastest overview is to watch one color become a whole palette.

The gap every brand hits

Brand guidelines name a color; products consume systems. Between the two sits the derivation gap: hover states, borders, tints, text pairings, dark themes — none of which the guideline specifies and all of which someone must decide. The guides here treat that gap as the actual design problem: close it with rules and the brand stays coherent everywhere; close it with per-screen improvisation and the brand dissolves one hex at a time. From One Brand Color to a Full Design System walks the whole derivation once, and Brand Guidelines vs Design Tokens explains why the PDF and the product need different artifacts — one persuades people, the other instructs machines.

Recognition is specific

What people recognize is narrower than teams assume — usually a hue in a role, at a place they meet it repeatedly. That specificity is good news for every hard decision in this hub: a button can darken one step for contrast, a print orange can accept its closest screen twin, a rebrand can move supporting values freely — as long as the recognized thing survives. Several guides below are really about locating it before touching anything: Auditing an Existing Brand Palette finds what is actually in use and which of it people would notice changing, and Keeping Brand Equity Through a Redesign turns that finding into a preserve-versus-move decision. When the recognized color itself is the problem, When Your Brand Color Fails Accessibility shows the one-step-darker move that keeps the hue while passing the floor.

Where the craft connects

Brand color work stands on the scale machinery covered in our color scales guide — ramps, roles, derived states — and hands off downstream to design tokens, where brand decisions become values code and design files share. This hub is the strategic layer: which color, why it holds, how it survives contact with accessibility law, print production and redesigns. The derivation itself is what Scale Composer runs: a seed goes in, and the ramps, neutral scale, type and grid come out as one system with exportable tokens — the hundred related values produced by rule instead of improvised per screen.

Choosing, translating, scaling out

Before the system there is the choice. Choosing a Brand Color treats it as a positioning decision rather than color psychology, and Why Every Brand Ends Up Blue maps the gravitational pull that choice is made against. After the choice comes translation: Pantone to Screen for print-born brands, and Color Consistency Across Print, Web and Product for keeping the committed values aligned across media. At the far end sit the scale-out problems — Multi-Brand Token Architecture when several brands share one codebase, Rolling Out a Rebrand via Tokens when the values must change everywhere at once, and Brand Fonts on the Web for the identity asset that isn’t a color at all.

Guides in this hub

Auditing an Existing Brand Palette
How to run a brand color audit across every surface: what to collect, how to tell drift from deliberate forks, and the deliverable that ends the spread.
Brand Fonts on the Web: Licensing and Alternatives
Brand fonts, web licensing, and open alternatives: what the print license doesn't cover, the headings-only hedge, and how to judge a lookalike honestly.
Brand Guidelines vs Design Tokens
Do you need brand guidelines, design tokens, or both? Guidelines carry the intent humans need; tokens carry the exact values tools consume. Link them.
Choosing a Brand Color: Beyond Color Psychology
How to choose brand color without the psychology listicles: category distinctiveness first, then functional headroom — stress-tested before signing.
Color Consistency Across Print, Web and Product
Brand color consistency across print, web and product: one canonical value per color, one derived system per medium, and roles instead of raw values.
From One Brand Color to a Full Design System
A brand color palette that works is a system, not a swatch: what a complete one contains — ramps, roles, tokens — and why one hex plus tints dissolves.
Keeping Brand Equity Through a Redesign
The brand equity redesign discipline: name what people actually recognize, pin it before anything moves, and let the system around it change freely.
Multi-Brand Token Architecture
A multi-brand design system is a token-layering problem: share the semantic roles, give each brand its own primitives, and a brand switch touches no components.
Pantone to Screen: Translating Print Brands
Why pantone to hex is an approximation, not a formula — and the method that works: match by eye, commit to one screen twin, and derive the rest from it.
Rolling Out a Rebrand via Tokens
Rolling out a rebrand: design system tokens make it a values release — re-derive from the new seed, review the diff, re-verify contrast, stage behind flags.
When Your Brand Color Fails Accessibility
Brand color accessibility without a rebrand: why recognition survives a darker step, and the two-tier fix that keeps the vivid original for hero moments.
Why Every Brand Ends Up Blue (and How Not To)
Blue brand colors dominate through a safe-choice ratchet plus real functional merits. What blue costs in a blue category — and how to leave it safely.

Test the brand’s room to move

The questions in this hub — can the color darken for contrast? what does a rebrand cost? — share one experimental answer: swap the seed and watch the system re-derive. Everything that rebuilds automatically is what a rebrand no longer has to renegotiate; what you choose to pin is, by definition, your brand.