←back to thread

Show HN: A color name API that maps hex to the closest human-readable name

(meodai.github.io)
97 points meodai | 2 comments | 19 Jun 25 10:40 UTC | HN request time: 0.425s | source

I built this API to return the closest named color for any hex value—using curated lists like my own [1], XKCD [2], and others.

I made it from scratch without Express or any frameworks because:

- I’m a frontend/interaction dev and wanted to learn how to build an API from the ground up. - Existing APIs didn’t guarantee unique names per color—mine does. - It also supports WebSocket updates, gzip responses, and multiple name sets.

I’ve been collecting color names for over 10 years [1]. With ~30,000 entries, bundling them into every color-related project became excessive. This API keeps things lightweight—for me and hopefully for others too.

GitHub: https://github.com/meodai/color-name-api

Would love feedback on naming logic, accuracy, performance, or backend best practices I might’ve missed.

[1] Large Color Name List: https://github.com/meodai/color-names [2] XKCD color survey results: https://xkcd.com/color/rgb/

1. Gys ◴[21 Jun 25 07:51 UTC] No.44335587[source]▶
Beautifully made! But I struggle a little for thinking of use cases? Maybe add some to the readme.

Also, I think adding a kind of ‘main color’ would be useful. For example ‘shore’ being in the category ‘blue’ or maybe even ‘light blue’. Because for ‘shore’ itself I personally would associate with sand and maybe yellow.

replies(1): >>44336018 #
2. meodai ◴[21 Jun 25 09:24 UTC] No.44336018[source]▶
Oh I mostly use it for my own apps – it just feels more human-readable than hex codes. But yeah, you're right, I should add some example use cases to the readme!

Like here:

https://farbvelo.elastiq.ch/ or https://meodai.github.io/poline/

Thanks a lot for the feedback, I really appreciate it!