←back to thread

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

(meodai.github.io)
97 points meodai | 1 comments | 19 Jun 25 10:40 UTC | HN request time: 0.216s | 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/

Show context
magic_hamster ◴[21 Jun 25 08:58 UTC] No.44335894[source]▶
This is nicely done, but can you please explain why you need this? What is the use of the color names when you already know the actual color value and can use it?
replies(3): >>44335939 #>>44336037 #>>44336101 #
1. meodai ◴[21 Jun 25 09:27 UTC] No.44336037[source]▶
Thanks! Good question – it's mostly about readability and communication. Hex codes are precise but not intuitive. Names give context, like saying “salmon” instead of #fa8072. That’s helpful in design tools, UI previews, generative art, or even debugging.

Also, the API works the other way around too – you can search by name to get the matching color: https://api.color.pizza/v1/docs/#api-Default-getColorNames. I did not add it to the website yet, because I don't have good UI ideas for it yet.