How to Choose a Color Palette for Your Website (Without a Design Background)
A good palette is a small, role-based system — primary, secondary, neutrals, semantic colours — not a collection of shades that happen to look nice alone. Here's the framework, plus the accessibility checks most sites skip.
TCTechToolsCenter TeamMost website colour disasters don't come from bad taste — they come from picking colours one at a time, in isolation, without a system tying them together. A genuinely good palette is a small, deliberate set of colours with clear roles, not a scattering of shades that happened to look nice individually in a colour picker.
The roles every website palette actually needs
- Primary — your main brand colour, used for key actions (buttons, links) and brand moments; should appear the least frequently but carry the most visual weight when it does.
- Secondary — a supporting colour that complements the primary, used for less critical UI elements or secondary calls to action.
- Neutral(s) — the greys, near-blacks and near-whites that make up the majority of any real interface — backgrounds, text, borders, dividers.
- Semantic colours — dedicated, conventional colours for success (green), error (red), warning (amber) and informational (blue) states, kept separate from your brand colours so meaning stays unambiguous.
Sponsored
The 60-30-10 rule
A classic, genuinely useful starting ratio: roughly 60% of a page's visual weight in your dominant neutral (usually a background colour), 30% in a secondary colour, and 10% in your primary accent colour used for the highest-priority actions and highlights. This isn't a rigid law, but it's a far better starting discipline than distributing colour evenly — an interface where every colour gets equal visual weight has no clear hierarchy telling the eye where to look first.
Step-by-step: build a palette with a free tool
- Start from one anchor colour — often your logo's primary colour, or a colour that reflects your brand's tone (calm blues for finance/health, energetic oranges for consumer/lifestyle brands, and so on).
- Use a Color Palette Generator to build a harmonious set from that anchor — complementary, analogous or triadic schemes each produce a different feel worth testing against your brand tone.
- Pick your neutrals separately and deliberately, rather than letting the generator's suggestion double as your text/background colours without a dedicated accessibility check.
- Check every foreground/background text combination with a Contrast Checker against WCAG AA (4.5:1 for normal text) before finalising anything.
- Document the final palette (hex codes, named roles) in a Brand Kit so every future page, ad and document uses the same, consistent set.
Color harmony schemes, in plain terms
- Complementary — two colours opposite each other on the colour wheel; high contrast, energetic, but risks feeling harsh in large areas if not balanced with plenty of neutral space.
- Analogous — colours next to each other on the wheel; naturally harmonious and calm, common in wellness, nature and lifestyle brands.
- Triadic — three colours evenly spaced around the wheel; vibrant and playful, but needs one colour to clearly dominate or the palette reads as chaotic rather than balanced.
- Monochromatic — different shades and tints of a single hue; the safest, most cohesive option, though it relies entirely on one accent colour to carry all visual interest.
Accessibility isn't optional — it's load-bearing
A palette that looks beautiful but fails contrast requirements actively excludes a meaningful share of visitors — including anyone with low vision, colour blindness, or simply using a phone screen in bright daylight. WCAG AA requires a 4.5:1 contrast ratio for normal text and 3:1 for large text and UI components; checking every text/background pairing your palette produces, not just the most obvious one, catches the specific combinations (a light secondary colour on a white card, for instance) that often slip through when only the primary brand colour gets checked. Our Color Blindness Simulator is worth running your palette through too, since roughly 8% of men have some form of colour vision deficiency — a palette that relies purely on a red/green distinction to convey meaning (success vs error, for instance) fails this group specifically, regardless of contrast ratio.
Cultural and industry context matters
Colour carries different associations across markets and industries — blue reads as trustworthy and calm in most Western and Indian business contexts (which is exactly why it dominates finance and healthcare branding), while red carries auspicious, celebratory associations in Indian cultural contexts that differ meaningfully from its more cautionary Western connotation (stop, error, danger). Researching how your specific industry and target audience read a candidate colour — not just personal preference — is worth the extra step before locking in a primary brand colour that'll appear on every page of the site.
How many colours is actually too many?
A genuinely disciplined website palette rarely needs more than 2-3 brand colours plus a neutral scale (typically 4-6 grey shades from near-white to near-black) and the 3-4 semantic colours for state feedback — somewhere in the range of 8-12 total colours covers the overwhelming majority of a real site's needs. A palette that's grown to 20+ colours almost always reflects colours added ad hoc, page by page, without anyone stepping back to check whether an existing palette colour could have served the same purpose — worth auditing and consolidating periodically rather than letting it grow unchecked.
Light and dark mode: two palettes, one system
A modern site supporting both light and dark modes needs its palette designed as a coordinated pair from the start, not a light palette with colours simply inverted for dark mode — a saturated primary colour that works beautifully on a white background can feel overly intense or even glow uncomfortably on a near-black background, and often needs its own, slightly desaturated dark-mode variant to feel equally premium rather than like an afterthought. Testing your palette's actual appearance in both modes, side by side, before considering it finished is worth the extra round of review.
A worked example
A small business chooses a deep teal as its primary brand colour (drawn from its existing logo), generates an analogous palette from it for a calm, cohesive feel appropriate to its wellness-adjacent positioning, picks a warm off-white and near-charcoal as its neutral pair rather than pure white/black (softer on the eyes for long reading sessions), and keeps standard green/red/amber for semantic states rather than trying to force its brand teal into a "success" role where it could be ambiguous. Every text/background combination is checked against WCAG AA before launch, and the same six-colour system — teal, its analogous support colour, two neutrals, and two semantic colours — is documented in a brand kit so a future landing page or a printed flyer never introduces an off-palette colour by accident.
The short version: a good website palette is a small, role-based system — primary, secondary, neutrals, semantic colours — not a collection of colours that individually look nice. Building it from one anchor colour using a genuine harmony scheme, checking every combination for accessibility, and documenting the final set for consistent reuse is what separates a palette that holds up across an entire site from one that starts falling apart the moment a second designer touches the project.
Tools beyond the generator: testing in context
A palette that looks right in a colour-picker swatch can behave differently once applied to real UI elements at their actual size — a button's accent colour, a thin link underline, a large hero background. Applying the candidate palette directly to a rough mockup of your actual homepage (even a simple one) before finalising it catches issues a swatch-only review misses, like a secondary colour that reads fine as a small dot but feels overwhelming across a full-width section.
Keeping the palette consistent as the site grows
The real test of a palette isn't the launch day — it's eighteen months later, when a new page, a new campaign or a new team member needs a colour and either reaches for the documented brand kit or picks something close-but-different from memory. A living, easily accessible brand kit (not a colour list buried in an old design file nobody opens anymore) is what actually keeps a palette disciplined over time, rather than slowly drifting into the 20-colour sprawl described earlier.
Seasonal and campaign palettes vs the core brand palette
A festive sale banner or a seasonal campaign page can reasonably introduce a temporary accent colour outside the core palette — a warm gold for a Diwali promotion, for instance — without diluting brand consistency, as long as it's clearly understood as a time-boxed exception layered on top of the permanent core palette, not a slow, undocumented expansion of the palette itself. Keeping campaign colours in a clearly separate, labelled section of the brand kit (rather than mixed in with the core set) preserves this distinction going forward.
A quick pre-launch palette checklist
- Every primary text/background pairing passes WCAG AA contrast.
- The palette has been tested in both light and dark mode, not designed for one and adapted for the other as an afterthought.
- No more than 2-3 true brand colours, with semantic colours kept clearly separate.
- The full palette (with hex codes and named roles) is documented somewhere the whole team can reference.
- The palette has been checked against a colour blindness simulator, not just a standard contrast checker.
When to hire a designer instead of DIY-ing the palette
The framework in this guide covers the fundamentals well enough for most small businesses and personal projects to build a genuinely solid, functional palette without professional help. A more complex brand — one spanning print, packaging, multiple product lines, or requiring genuine differentiation in a crowded, visually sophisticated market — benefits from a professional colour and brand strategy pass that goes deeper into competitive positioning and nuanced psychological association than a self-service tool and checklist can fully replace. Knowing which category your own project actually falls into is worth an honest assessment before committing significant marketing spend around a DIY palette.
One more accessibility angle: colour alone should never carry meaning
Beyond contrast ratios, a genuinely accessible palette avoids relying on colour as the *only* signal for something important — a form field outlined only in red to indicate an error, with no icon or text label alongside it, is invisible to a colour-blind user regardless of how strong the red/background contrast technically measures. Pairing every colour-coded state with a second, non-colour cue (an icon, a label, a pattern) is a small addition that meaningfully widens who can actually use your interface correctly.
Building a palette this deliberately takes an afternoon, not a week — and the payoff compounds every single time someone on your team, or a future version of you, needs to pick a colour and already knows exactly where to look.
Free vs paid palette tools: what actually differs
A free, browser-based palette generator covers genuine harmony-scheme generation, hex export and often built-in contrast checking — entirely sufficient for the vast majority of small business and personal sites. Paid, more advanced brand-design software adds features like automated accessible-palette suggestion across an entire design system, multi-brand palette management for agencies handling several clients, and deeper integration with design tools like Figma — genuinely useful at agency or larger-brand scale, but not something a single-site project needs to reach for by default.
Start from one anchor colour, build the system deliberately, and check it against real accessibility standards — everything else follows from getting that foundation right.
Palette inspiration without copying a competitor outright
Looking at competitors' and category leaders' palettes for inspiration is reasonable and common practice, but directly copying a specific competitor's exact hex codes crosses from inspiration into a genuine brand-differentiation problem — visitors who've seen both sites can end up confusing one brand for another, which works against the entire point of having a distinct visual identity in the first place. Use competitor research to understand category norms and expectations, then build your own genuinely distinct palette from your own anchor colour rather than reverse-engineering someone else's.
A distinct, accessible palette, built once and documented properly, is one of the highest-leverage design decisions a small site ever makes.
Tools used in this article
Sponsored
Frequently asked questions
Typically 8-12 total: 2-3 brand colors, 4-6 neutral shades, and 3-4 semantic colors for success/error/warning/info states.
TechToolsCenter Team
Product & Tools
The team behind TechToolsCenter — building fast, private, browser-based tools and writing practical guides on how to get the most out of them.
Related articles
SVG Blob Shapes Explained: How to Add Organic Backgrounds to Any Website
The soft, irregular blob shapes behind a hero section or testimonial card aren't drawn by hand — they're generated math, and understanding how gets you a shape that actually fits your design instead of a random download.
Border Radius Explained: From Rounded Corners to Pills and Blobs
One CSS property does everything from a subtle 4px card corner to a fully circular avatar — the difference is entirely in how far you push the same four numbers.
CSS Gradients Explained: linear-gradient vs radial-gradient vs conic-gradient
All three gradient functions paint a smooth color transition — the difference is entirely in the shape that transition follows, and picking the wrong one is the most common reason a gradient looks subtly off.