Rest API that returns a bunch of color names for a given color-value.
Introducing a comprehensive and easy to use color-naming API! Easily retrieve the color name for any hexadecimal color value, using a variety of different color name lists. Whether you're working on a design project or building a color-themed application, our API has you covered.
While hex codes are precise, they're not intuitive for humans. Color names bridge the gap between technical accuracy and human understanding. Instead of saying "#fa8072", you can say "Salmon" – which immediately conveys meaning and context.
This API solves real-world problems across various domains:
- Design Software: Show human-readable color names in color pickers and palettes
- Generative Art: Poline gradient generator uses named colors for more intuitive palette creation
- Color Palette Tools: Farbvelo demonstrates real-time color naming for palette exploration
- Screen Reader Support: Provide meaningful color descriptions instead of just RGB values
- Color Blind Users: Offer descriptive names alongside visual color representations
- Voice Interfaces: Enable color selection through spoken color names
- CSS Development: Generate human-readable color variable names automatically
- Debug Logs: Make color values in logs more readable ("Midnight Blue" vs "#191970")
- API Documentation: Auto-generate color examples with intuitive names
- Chart Libraries: Automatically name data series colors for legends
- Dashboard Tools: Provide accessible color descriptions for data points
- Reporting: Generate color-coded reports with named color categories
- E-commerce: Name product colors automatically from uploaded images
- Brand Guidelines: Maintain consistent color naming across teams
- Customization Systems: Let users describe and share custom color schemes
- World Generation: Procedurally name environmental colors
- UI Themes: Provide descriptive names for theme variations
- Color Picker Widgets: Enhance user experience with named color feedback
- Theme Builders: Help users understand and communicate color choices
- Content Management: Auto-tag content based on dominant colors
The API also works in reverse – you can search by color name to get hex values, making it perfect for natural language color interfaces. This enables users to say "I want salmon pink" instead of having to know "#fa8072".
# Search for colors by name
$ curl 'https://api.color.pizza/v1/names/?name=red'
This reverse functionality is particularly useful for:
- Voice-controlled design applications
- Conversational interfaces for color selection
- Natural language processing in creative tools
- Accessibility features where users describe colors verbally
- Distance Metric: Uses CIEDE2000 ΔE for perceptually accurate color matching
- Multiple Lists: Choose from various color naming systems (Wikipedia, RAL, Pantone, etc.)
- Unique Names: Optional
noduplicates
parameter ensures each color gets a distinct name - Real-time Updates: WebSocket support for live color naming applications
Let's start by testing the API. Open up a command prompt and enter the following command:
$ curl https://api.color.pizza/v1/?values=aaffcc
➜ {
➜ "colors":
➜ [
➜ {
➜ "name":"Neo Mint",
➜ "hex":"#aaffcc",
➜ "rgb":{"r":170,"g":255,"b":204},
➜ "hsl":{"h":144,"s":100,"l":83.33333},
➜ "lab":{"l":93.57729,"a":-34.63514,"b":15.94209},
➜ "luminance":159.78151,
➜ "luminanceWCAG":0.84426,
➜ "requestedHex":"#aaffcc",
➜ "distance":0
➜ }
➜ ],
➜ "paletteTitle":"Neo Mint"
➜ }
The response will be a JSON Object containing two keys: colors
and paletteTitle
colors will contain an array of all the colors you have asked for, with some useful information like name
or hsl
.
Now, let's GET
the names for multiple colors:
$ curl 'https://api.color.pizza/v1/?values=0d0d0f,f39d91,d4d4d7'
➜
{
"paletteTitle":"Ruined Amber",
"colors":[
{
"name":"Ruined Smores",
"hex":"#0f1012",
"rgb":{
"r":15,
"g":16,
"b":18
},
"hsl":{
"h":220,
"s":9.09091,
"l":6.47059
},
"lab":{
"l":4.64662,
"a":-0.0655,
"b":-1.21669
},
"luminance":10.60828,
"luminanceWCAG":0.00516,
"requestedHex":"#0d0d0f",
"distance":0.7732
},
{
"name":"Peach Amber",
"hex":"#fb9f93",
"rgb":{
"r":251,
"g":159,
"b":147
},
"hsl":{
"h":7,
"s":92.85714,
"l":78.03922
},
"lab":{
"l":74.88027,
"a":34.17564,
"b":21.39099
},
"luminance":120.93069,
"luminanceWCAG":0.47412,
"requestedHex":"#f39d91",
"distance":1.39432
},
{
"name":"Nimbus Cloud",
"hex":"#d5d5d8",
"rgb":{
"r":213,
"g":213,
"b":216
},
"hsl":{
"h":240,
"s":3.7037,
"l":84.11765
},
"lab":{
"l":85.33592,
"a":0.40788,
"b":-1.48475
},
"luminance":142.46096,
"luminanceWCAG":0.66693,
"requestedHex":"#d4d4d7",
"distance":0.23432
}
]
}
The response now contains 3 objects in the colors
array. The API will return the closest color names if can find for each requested color.
The come from a large collection. If for some reason you don't like the names, there are several other lists to choose from. So lets get the same names from a differet list
.
$ curl 'https://api.color.pizza/v1/?values=0d0d0f,f39d91,d4d4d7&list=wikipedia'
The API serves static HTML documentation at the /docs/
endpoint:
$ curl https://api.color.pizza/v1/docs/
$ curl 'https://api.color.pizza/v1/lists/'
➜
{
availableColorNameLists: [
"defaults",
"colors",
"bestOf",
"basic"
// ... //
],
listDescriptions: {
"basic": {
"title": "Basic",
"description": "A set of basic colors. Red, Green, Blue...",
"source": "https://github.com/colorjs/color-namer/tree/master/lib/colors",
"key": "basic"
"colorCount": 21,
"url": "/v1/?list=basic"
},
// ... //
}
}
The response contains two keys: availableColorNameLists
and listDescriptions
.
availableColorNameLists
is an array of all the color name lists currently supported by Color Names, such as Wikipedia, HTML color lists, traditional Japanese colors etc.
listdescriptions
is an object whose keys are the name of the color lists with values containing useful information such as title
, description
, source
etc.
In this demo, you can preview names of common colors given by each list. You can also change the input colors and the corresponding names in each list will be updated on the spot.
Now when some of the requested colors are very similar you might get some duplicate names:
$ curl 'https://api.color.pizza/v1/?values=1b2b11,1c2f11,2e3f24&list=wikipedia'
Notice how Phthalo Green
was returned twice.
What makes this API unique is that you can ask to return a color name only once. So if you ask for similar colors the api will make sure to return a unique color name per requested color.
$ curl 'https://api.color.pizza/v1/?values=1b2b11,1c2f11,2e3f24&list=wikipedia&noduplicates=true'
The noduplicates=true
parameter is a powerful feature that ensures each requested color receives a unique name, even when colors are similar. When enabled:
- The API will never return the same color name twice in a single response
- Each color in your request will receive the closest available unique name
- Names are assigned in the order colors appear in your request
- The algorithm intelligently selects alternative names with minimal perceptual distance
This is particularly useful for:
- Generating diverse color palettes with distinct names
- Creating color legends where each item needs a unique identifier
- Building accessible interfaces where similar colors need distinguishable names
- Naming elements in data visualizations
The API uses an efficient Vantage Point Tree (VPTree) spatial data structure to find the nearest unique color names. When noduplicates=true
, each assigned name is temporarily removed from future consideration within that request.
For optimal results with noduplicates=true
:
- Use with larger color name lists:
default
,bestOf
,wikipedia
,ntc
,ral
,ridgway
orxkcd
- Order your most important colors first in the request, as they'll receive the closest name matches
- Be aware that with very small color lists or many similar colors, later colors might receive less ideal name matches
In smaller color name lists, this can lead to unexpected results as the algorithm must choose increasingly distant color names. We suggest using this feature with some of the larger lists mentioned above.
When using noduplicates=true
, if you request more colors than are available in the selected list, the API will:
- Return as many uniquely named colors as possible (up to the size of the selected list)
- Drop any additional colors that can't be assigned unique names
- Return a response with fewer color objects than requested
For example, if you use the "basic" list (which has only 21 colors) and request 30 colors with noduplicates=true
, the response will contain only 21 color objects.
This behavior ensures the API maintains its promise of providing truly unique names for each color, even in edge cases. If you need to name a large number of colors uniquely, make sure to use one of the larger color lists mentioned above.
The Color Name API also supports real-time color updates via WebSocket connections. It broadcasts whenever new color names are requested through the API. If you're interested in using WebSockets with the API, please create an issue with your use case and domain.
Codepen is allowed by default. See the demo for an example of how to use the WebSocket connection.
To use WebSockets with the API:
-
First, make sure your domain is on the allowed origins list. Currently, WebSocket connections are restricted to approved origins for security purposes. If you need access, please create an issue with your use case and domain.
-
Connect to the WebSocket endpoint using a WebSocket client:
const socket = io('https://api.color.pizza', { transports: ['websocket'] }); // Listen for color updates socket.on('colors', (data) => { console.log('Received color data:', data); // { // paletteTitle: "Neo Mint", // colors: [{ // name: "Neo Mint", // hex: "#aaffcc", // // ... other color properties // }], // list: "default" // } });
-
The WebSocket connection will automatically receive updates whenever new colors are requested through the API. The data format matches the REST API response structure, containing the
paletteTitle
,colors
array, and thelist
used.
If you're self-hosting the API, you can enable WebSocket support by setting the following environment variables:
SOCKET=true
ALLOWED_SOCKET_ORIGINS=https://yourdomain.com,https://otherdomain.com
Note that WebSocket support is optional and disabled by default. The REST API endpoints will continue to work regardless of WebSocket configuration.
The API supports custom referrer tracking via the X-Referrer
header. This is useful when:
- The standard
Referer
header is stripped by privacy settings - You want to explicitly identify your application or service
- You're making server-to-server requests where standard referrer information isn't available
To use this feature, simply include the X-Referrer
header in your requests:
$ curl -H "X-Referrer: my-awesome-app" 'https://api.color.pizza/v1/?values=aaffcc'
or
fetch('https://api.color.pizza/v1/?values=aaffcc', {
headers: {
"X-Referrer": "your-app-name",
},
}).then((response) => response.json())
When the API is configured with WebSockets enabled, this referrer information is included in the broadcasted socket events, allowing for tracking and analytics of color requests across different applications or domains.
This header is especially useful for:
- Attribution in multi-platform scenarios
- Tracking API usage from different client applications
- Understanding where color lookups are being performed
Please include the X-Referrer header in your requests to help us understand how the API is being used. This information helps us improve the service and justify continued development and maintenance of this free API. Your support is greatly appreciated!
The Color Name API uses the CIEDE2000 ΔE (Delta E) distance metric for perceptually accurate color matching. This advanced algorithm ensures that the color names returned are as close as possible to human visual perception.
- Input colors are converted to the LAB color space (a perceptually uniform color space)
- Distance calculation uses the CIEDE2000 formula to compute the ΔE between the input color and each color in our database
- Closest matches are returned based on the smallest ΔE values
- Distance values in the API response represent the calculated ΔE difference
The distance
field in API responses represents the CIEDE2000 ΔE value:
- 0.0: Perfect match (identical colors)
- < 1.0: Differences not perceptible to most people
- 1.0 - 2.0: Perceptible under ideal viewing conditions
- 2.0 - 10.0: Perceptible at a glance
- > 10.0: Colors appear quite different
The API leverages the excellent Culori library for color space conversions and CIEDE2000 calculations, combined with a custom Vantage Point Tree (VP-tree) data structure for efficient nearest-neighbor searches across our extensive color database.
This ensures both accuracy and performance when matching colors to their closest named equivalents.