How does Poolors generate color palettes?

Poolors generates palettes by favoring colors that designers use least, and it shows the most-used colors as a contrast. You can generate combinations of 2, 3, 4, or 5 colors, and each color is expressed as a hex value such as #ffffff or #000000. This is useful when you want a palette that avoids the familiar designer defaults and looks less repetitive.

The core mechanism

The site's own description states it plainly: Poolors generates color palettes using the colors least-used by designers. That single rule drives the output.

Two lists sit behind the idea:

• Least used by designers — the pool the generator draws from.
• Most used by designers — shown alongside as a reference point.

So the tool is not random in the usual sense. Random selection would keep landing on the same popular colors simply because they are common. By inverting the preference — picking from the low-frequency end — the generator steers away from the colors you have already seen in countless templates, brand kits, and UI libraries.

The visible hex values in the interface (#ffffff, #000000, #3c3c3c, #787878, #b4b4b4) are the concrete output format. Each palette is a set of these codes, which you can copy directly into CSS, design tools, or a style guide.

Why "least used" changes the result

Most palette tools optimize for harmony, contrast ratios, or a mood you describe in words. Poolors optimizes for novelty relative to existing design practice.

That produces a different feel:

The trade-off is real. A palette built from underused colors may need more manual checking for contrast and accessibility than one built from a harmony model. The tool gives you the raw combination; judging whether it works for text, buttons, and backgrounds is still your job.

Palette sizes: 2, 3, 4, 5

Poolors supports combinations of 2, 3, 4, and 5 colors. The size you pick should match the job:

• 2 colors — simple pairs, useful for a background and a single accent, or a minimal two-tone brand mark.
• 3 colors — a common base for a small interface: one dominant, one secondary, one accent.
• 4 colors — enough for a fuller UI with states or a small illustration palette.
• 5 colors — the widest option here, suited to richer layouts or a broader brand system.

Larger palettes give more room but also more chances for two colors to clash. If you are unsure, start at 3 and expand only when you actually need another role filled.

How to use it in practice

1. Open Poolors and choose the number of colors you want (2, 3, 4, or 5).
2. Generate a palette and read the hex values it returns.
3. Compare against the "most used by designers" reference to see how far the result sits from the common range.
4. Copy the hex codes into your design tool or stylesheet.
5. Test the combination on real content — check text legibility and contrast before committing.

Step 5 is the one people skip. A palette can look striking as swatches and fail the moment you place body text on it.

Common sticking points

• Unfamiliar does not mean usable. Underused colors can sit in awkward lightness ranges. Verify contrast rather than trusting the novelty.
• Hex is the output, not a guarantee. The codes are standard, but how they render depends on the display and the surrounding colors.
• The "most used" list is context, not a target. It exists to show what you are moving away from, not as a palette to match.
• No single palette fits every role. You may still need separate choices for backgrounds, text, and accents even within one generated set.

If your goal is a palette that does not look like everything else, Poolors' least-used approach is the reason to use it. If your goal is guaranteed harmony or strict accessibility compliance out of the box, treat its output as a starting point and do the checking yourself.