Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Colorscales?
Colorscales is a web app for building color palettes in OKLCH, a color space designed to match how people perceive lightness and hue. Rather than picking colors by eye in hex, you adjust lightness, chroma and hue directly, which makes it easier to produce even, predictable gradations across a palette. It is developed by Zeix and currently carries a 2.0.0-beta version label.
What you can do with it
- Create a free account, then build and save palettes made of named colors.
- Tune each color with sliders for lightness, chroma and hue, and read the resulting OKLCH, RGB and HSL values.
- Copy CSS values straight into a stylesheet.
- Mark a palette public so it appears on your profile alongside other public palettes.
- Manage account details: avatar, nickname, email, password and username, plus language and accent-color preferences.
Who it suits
Designers and front-end developers who need a systematic scale — for example, a ten-step button or surface ramp — will get more out of OKLCH than from a hex picker, because equal slider steps correspond more closely to equal visual steps. If you only need one or two ad-hoc colors, a general-purpose picker is lighter weight.
A practical next step
Before committing to an account, open the palette editor and build a five-step ramp from one hue: hold hue fixed, drop lightness in even increments, and adjust chroma down at the light and dark ends to avoid oversaturation. Then check the CSS output against your existing brand colors.
Related tools
If you want to compare approaches, OKLCH Color Picker converts between OKLCH and other formats, and Culori is the color library Colorscales itself lists as a dependency.
How does Colorscales use OKLCH for perceptually uniform color gradations?
Colorscales builds its palette editor around OKLCH, a color space designed so that equal numeric steps look like equal visual steps. Instead of nudging hex codes and guessing, you adjust three perceptual controls — Lightness, Chroma and Hue — and the app derives the corresponding OKLCH, RGB and HSL values for each color. That is the core of its "perceptually uniform" approach: a lightness ramp should look evenly spaced to the eye, not just be evenly spaced in code.
What that means in practice
- Lightness controls how light or dark a color reads. Because OKLCH lightness tracks human perception, a series of swatches from low to high lightness should appear to brighten at a steady rate — useful for building UI scales (backgrounds, borders, text) that stay balanced.
- Chroma controls colorfulness. Keeping chroma constant while varying lightness is what stops mid-tones from looking washed out or oversaturated compared with the ends of a ramp.
- Hue stays stable in OKLCH in a way it often does not in HSL, where a "blue" at different lightnesses can drift toward purple or cyan. That makes OKLCH ramps more predictable for brand colors.
Who it suits
A designer building a design system gets the most value: define a hue, then produce a light-to-dark scale where each step is a deliberate perceptual increment. A developer benefits from the exact CSS output — each color shows its oklch(...), RGB and HSL values with a copy control, so the ramp goes straight into stylesheets without conversion tools.
Trade-offs to weigh
OKLCH is newer than hex or HSL, so older browsers and some design tools may not support oklch() directly; you may need fallbacks. Fully saturated colors can also fall outside the sRGB gamut, so an OKLCH value that looks right in the editor may clip when rendered on a standard display. If your audience is on legacy browsers, treat OKLCH as the source of truth and export RGB/HSL for output.
A concrete next step
Pick one brand hue, fix the chroma at a comfortable level, then step lightness in even increments to build a 9- or 10-stop scale. Copy the CSS values into your tokens file, and check the result on a real screen rather than trusting the numbers alone. If you want to compare how other tools handle perceptual color, OKLCH Color Picker is a focused reference for the same space.
What are the differences between OKLCH, RGB, and HSL values when editing a color in Colorscales?
In Colorscales, all three notations describe the same color you are editing, but they expose different controls and behave differently when you adjust them.
OKLCH is the model the editor is built around. It splits a color into Lightness, Chroma, and Hue, and it is designed to match human perception. That means changing Lightness or Chroma produces a more even, predictable shift across hues than you get in RGB or HSL. The editor gives you sliders for each of these three values, so it is the most direct way to make controlled gradations.
RGB is the raw screen representation: red, green, and blue channels. It is useful when you need to hand a value to a tool or developer that expects RGB, but it is a poor model for reasoning about light and dark. Moving a single RGB channel often changes both apparent brightness and hue at once.
HSL is closer to how people describe color (hue, saturation, lightness), but its lightness is not perceptually uniform. Two HSL colors with the same lightness value can look very different in brightness, especially between yellows and blues. It remains widely supported in CSS and design tools, so it is handy for compatibility.
| Value | What it controls | Best for | Trade-off |
|---|---|---|---|
| OKLCH | Lightness, Chroma, Hue | Building even color scales and gradations | Less familiar; not universally supported in older tools |
| RGB | Red, Green, Blue channels | Exporting exact screen values | Hard to adjust brightness without shifting hue |
| HSL | Hue, Saturation, Lightness | Quick, familiar CSS-friendly tweaks | Lightness is not perceptually even across hues |
If your goal is a consistent palette, start in OKLCH and use the Lightness and Chroma sliders, then check the RGB or HSL readout only when you need to paste a value somewhere else. If you are matching an existing brand color that was defined in HSL or RGB, enter that value and use the OKLCH readout to understand how it sits perceptually before building lighter or darker steps around it.
The editor shows the OKLCH, RGB, and HSL strings together for the selected color, so you can compare them side by side as you drag. For a practical test, pick a yellow and a blue at the same OKLCH Lightness and compare their HSL lightness values — the difference is the clearest demonstration of why the model matters.
How do I create, save, and share a public palette on Colorscales?
On Colorscales, palettes live in your account, so signing in first is the practical starting point; public sharing is controlled by a Public switch on the palette itself.
Create and save a palette
- Sign in or create a free account.
- Open My Palettes and choose + Edit Palette.
- Give the palette a name.
- Add or edit colors. Each color can be adjusted with Lightness, Chroma, and Hue, with values shown in OKLCH, RGB, and HSL. You can also paste or set a CSS value.
- Save, then repeat + Edit Color for the rest of the palette.
Make it public Turn on the Public option for the palette. Public palettes appear in the public palette listing, and your profile shows your public palettes. If a palette is not marked public, it stays in My Palettes only.
Share it
Once public, share the palette page or your profile URL. Colorscales warns that changing your username breaks existing /user/:username links and public palette attributions, so choose your username before you circulate links widely.
A practical decision criterion Keep a palette private while you are still testing contrast and ordering; switch it to public when the colors are stable and you are ready for others to cite or reuse them. If you only need to hand colors to one collaborator, sharing CSS/OKLCH values may be simpler than making the palette public.
For broader color work, compare with OKLCH Color Picker for quick OKLCH picking or Coolors for fast palette generation.
What happens to my shared links and palette attributions if I change my Colorscales username?
Changing your username on Colorscales breaks every existing /user/:username link and all public palette attributions tied to your old name. The account settings page states this directly: the old URLs stop resolving, and palettes that credited you under the previous username no longer point to your current profile.
That means anyone who bookmarked your profile, linked to your palettes from a blog post, or referenced your username in a shared palette will hit a dead end. Your palettes themselves are not deleted — only the username-based paths and attribution labels change.
If you rely on inbound links or want to keep credit intact, either keep your username or update the places where you've shared those links after the change. If you just want a different display name, check whether the optional nickname field covers your need, since it doesn't affect URLs or attributions the same way.
A practical next step: before changing it, list where your profile URL appears — portfolio, social posts, team docs — so you can fix them afterward.
How do I permanently delete my Colorscales account and all my palettes?
Sign in to Colorscales, open Account Settings, scroll to the Danger Zone, and use Delete account. You must confirm with your current password; the page states this permanently deletes your account and all your palettes. There is no public “delete” link and no email-based cancellation flow shown, so the password confirmation is the only step described.
Before you delete, note two things:
- Palettes go with the account. The wording is explicit that all your palettes are deleted, so export or copy any palette values you want to keep first. Because Colorscales works in OKLCH and shows CSS, RGB and HSL values, you can save those strings in a text file or design tool.
- Public links stop working. If you shared palette URLs, those will break along with the account.
If you only want to stop using the site or change your identity, Change username is a separate option in the same Danger Zone. It warns that changing your username breaks all existing /user/:username links and public palette attributions, so it is not a substitute for deletion if your goal is to remove your data.
For a quick check on how other tools handle this, compare with a service that separates account deletion from data export, such as GitHub. The practical test is whether the settings page offers an export before the delete button; Colorscales' page evidence does not show one, so collect your palette values manually first.
User reviews (0)