Paste a list of colours and export them as CSS variables, SCSS, a Tailwind theme or JSON, after checking which pairs converge under colour blindness.
Waiting for a list of colours
One per line, or comma separated. Hex, rgb(), hsl() and hwb() all work.
The palette appears here
Every colour, checked against four colour vision simulations for pairs that converge.
Paste some colours to export them.
Color Palette Generator runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
Paste the colours you have and get them back as something you can use: CSS custom properties, SCSS variables, a Tailwind theme object, plain JSON or W3C draft tokens, named with a prefix you choose and numbered or labelled as you prefer.
The collision check is the reason this page exists rather than being a formatter. A palette where the success green and the error red converge under deuteranopia is a palette that fails for roughly one man in twelve, and it is completely invisible while you are choosing the colours — they look nothing alike to you. Every pair is compared under four simulations and the ones that stay close are named.
It is phrased as "may be hard to tell apart" rather than as a verdict, because the distance measure behind it is a plain sRGB distance and that is a weak model of perception. The useful output is the pair, not the number: if those two colours carry different meanings in your interface, something other than colour needs to carry it too — a label, an icon, a shape.
Colours that fail to parse are listed with their line rather than silently dropped, so a typo in one entry does not quietly shrink the palette and leave you wondering why the export has five variables instead of six. Everything runs in your browser; nothing is uploaded.
That the two colours stay close to each other after one of the colour vision simulations, so they may be hard to tell apart for some readers. The useful output is which two, not the distance — the measure behind it is crude by design.
It clears one specific hazard. It says nothing about contrast against your backgrounds, nothing about whether colour is carrying meaning on its own, and the model covers dichromacy rather than the more common partial deficiencies.
If they never appear in the same context, nothing. If they carry different meanings — success and error, two series on a chart — the fix is not usually a different colour but a second cue: a label, an icon, a shape, a pattern.
CSS custom properties if the palette should be changeable at runtime, which is what themes need. A Tailwind theme if you are using Tailwind. JSON or W3C tokens if another tool will read it. SCSS only if your build is already there.
It is listed with its line number and the reason, rather than dropped. A silently shortened palette is worse than a visible error, because you find out later.