Estimate CMYK from a Pantone-style color name lookup
Pantone 186 C comes back as an estimate of cyan 2 %, magenta 100 %, yellow 85 % and black 6 %, marked as approximate and for screen previews only. Keep an early layout moving before the printer's swatch book arrives. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Name
- pAnToNe 186 c
- Name
- Pantone 186 C percent
- Purpose
- screen_preview_only
This Pantone-name to CMYK estimate lookup returns a practical screen-preview value for a supported color in a small, transparent reference set. Enter a familiar Pantone-style name, such as Pantone 186 C, and receive cyan, magenta, yellow, and black percentages. The result is deliberately marked as approximate and is not an official Pantone specification, a color-managed conversion, or a substitute for a printer's swatch, proof, ink recipe, substrate test, or ICC workflow.
Use the lookup for early visual planning
A named spot color often appears in a brand brief long before a production printer, proofing profile, or physical swatch book is available. This lookup gives designers, developers, content teams, and project managers a stable CMYK-shaped estimate they can place in a mockup, design token, spreadsheet, or implementation note while work is still being reviewed on screens. Enter one supported Pantone-style name and the result reports four integer percentages: cyan, magenta, yellow, and black.
It also returns the canonical name from the table, a percent unit, an approximate flag, and a screen-preview-only purpose marker. Matching ignores capitalization and extra whitespace, which makes copied names easier to use without weakening the actual lookup. The table remains intentionally small.
That limited scope is useful because a recognized name produces the same deterministic answer every time, while an unknown name produces an explicit error instead of a fabricated conversion that merely looks authoritative. Use the estimate to keep an early layout moving, communicate a rough direction, or populate a non-production preview where exact press behavior is not being promised.
Understand what the CMYK percentages mean
CMYK values describe nominal amounts of cyan, magenta, yellow, and key black, but the same four numbers do not guarantee the same visible color everywhere. A screen emits RGB light, while print combines inks that interact with paper, coating, screening, press calibration, viewing illumination, and a chosen color profile. For that reason, this capability does not calculate a colorimetric match and does not claim that its percentages reproduce a proprietary spot ink.
It performs a reference lookup only. The returned integers are convenient for approximate UI previews, draft documents, and handoff conversations because they are compact and easy to compare. They should not be treated as an official formula or silently promoted into production artwork.
If exact output matters, ask the print provider which CMYK profile, press condition, stock, and proofing method apply. Then use approved color-management tools and a physical or contract proof rather than relying on a generic percentage set viewed through an uncalibrated display.
What you can do with it
Prepare a draft brand mockup
Insert a rough CMYK-shaped value into an on-screen layout while clearly retaining the approximate preview status.
Annotate an early design handoff
Give developers and project managers consistent preview percentages alongside a supported Pantone-style name.
FAQ
Is this an official Pantone conversion?
No. It is an independent, approximate reference lookup for screen-preview purposes and does not provide official Pantone data or formulas.
Can I use the result for production printing?
Not as a final specification. Confirm the color with your printer, the required ICC profile, the actual substrate, and an appropriate physical or contract proof.
Does capitalization matter?
No. Letter case, surrounding whitespace, and repeated internal spaces are normalized before the exact table lookup.
Why can printed output differ from the preview?
Ink, paper, press conditions, profiles, lighting, and display calibration all affect appearance; a generic screen preview cannot model those production variables.
What CMYK values does Pantone 186 C give?
The estimate is cyan 2 %, magenta 100 %, yellow 85 % and black 6 %. Use it for on-screen mockups and draft notes, and ask your printer for the approved values before production.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/color/pantone-cmyk-estimate \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"name":"Pantone 186 C"}'const res = await fetch("https://api.kit.forhosting.com/color/pantone-cmyk-estimate", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"name": "Pantone 186 C"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/color/pantone-cmyk-estimate",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"name": "Pantone 186 C"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/color/pantone-cmyk-estimate", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"name":"Pantone 186 C"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"name":"Pantone 186 C"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/color/pantone-cmyk-estimate", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"name": "Pantone 186 C"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "color.pantone_cmyk_estimate",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Understand what the CMYK percentages mean
The `approximate` field is always true, and `purpose` is always `screen_preview_only`, making that limitation machine-readable as well as visible to a person.
Handle supported and unsupported names safely
Normalization helps with ordinary typing variation, but it does not guess missing suffixes, reinterpret numbers, accept arbitrary color descriptions, or search an external catalog. Applications should show the error, ask the user to choose a supported name, or route the task to a qualified color workflow. Successful results can be cached safely because the algorithm has no network, random value, current date, user state, or changing external source. The input must contain a non-empty `name` string. A value such as `Pantone 186 C` is normalized by trimming its edges, reducing repeated spaces to one, and comparing without letter-case differences. If the normalized name is absent from the bundled reference table, the request fails with an `invalid_input` error that says the color is not in the table. That failure is an important product behavior: invented fallback values could enter brand documentation and later be mistaken for approved specifications. The API price is $0.002 per request, while the browser execution can use the same pure lookup logic.
Integration use cases
Validate a controlled color-name field
Accept only names covered by the small reference set and surface a typed error for anything else.
Technical questions
What happens when a name is not supported?
The request returns an `invalid_input` error instead of estimating, guessing, or selecting a similarly named color.
What does an API request cost?
Each API request costs $0.002. The result covers one submitted color name.