Convert clothing sizes between US, UK and EU regions
A women's US 8 is a UK 12 and an EU 38: enter a numeric size, its region and women or men, and get all three regional sizes from the same row of a standard chart. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Size
- 8
- Region
- US
- Category
- women
- Chart
- standard adult women's clothing
Clothing labels can become confusing as soon as a garment crosses a border. The same adult garment may carry a small American number, a larger British number, and a different European number, while men’s tailoring follows another scale entirely. This converter accepts a numeric size, its US, UK, or EU source region, and either the women or men category. It finds the corresponding row in a fixed standard chart and returns all three regional sizes. The calculation is deterministic, fast, and private because it uses no network service. Results are practical reference values, though an individual brand’s measurements and fit should always take priority.
Choose the right chart and describe the source size
Start with the label printed on the garment or shown by the retailer, then identify which regional system produced that number. Enter size as a numeric string or number, choose US, UK, or EU as region, and select women or men as category. Category is essential because adult women’s general clothing and men’s jackets do not share one numeric scale.
For example, a women’s US 8 belongs to a row with UK 12 and EU 38, whereas a men’s US 38 jacket belongs to a row with UK 38 and EU 48. A number can look plausible in several contexts, and a guess could produce a confident but misleading result. Children’s clothing, shoes, bras, jeans measured by waist and inseam, and letter sizes such as S or XL use different charts and are outside this capability’s scope.
Understand the conversion result and its limitations
A successful result contains an input block that reports the normalized size, uppercase source region, and canonical category. The sizes block then gives the matching US, UK, and EU values from the same chart row. The chart field states whether the lookup used standard adult women’s clothing or standard adult men’s jackets, and the note reminds consumers that regional equivalence is approximate.
This structure makes the result easy to show in a three-column comparison table or store as normalized catalog data. The method is table lookup, not arithmetic interpolation. That distinction matters because clothing systems are conventions rather than physical units: adding four may often relate a women’s US size to a UK size, but applying a formula blindly across categories and size ranges can be wrong.
Standard charts are most useful as a shopping starting point. Manufacturers may use vanity sizing, relaxed or slim cuts, stretch fabric, or their own measurement rules. When a retailer publishes bust, waist, hip, or chest measurements, compare those measurements before ordering.
Treat this conversion as a clear regional label cross-reference, not a guarantee that two garments will fit identically.
Clear checks and the same answer every time
Validation is strict so that automated workflows cannot silently mix incompatible charts. In particular, an unrecognized category such as kids, shoes, or unisex is rejected with a message listing the supported women and men categories. An exact numeric size that falls outside the chosen standard table is also rejected.
Correct the input or use a specialized chart instead of treating the failure as a converted value. Browser use can support quick checks while shopping or preparing a travel wardrobe. Because the implementation uses fixed tables and has no network calls, randomness, current-time dependency, or external model, identical input always produces identical output.
That repeatability is useful for tests and cached catalog transformations. Keep category and source region beside the original supplier value in stored data, rather than keeping only the converted number. Preserving provenance lets reviewers correct a supplier mapping later and prevents a bare number from being mistaken for a different regional scale.
What you can do with it
International online shopping
Convert a familiar home-region size into the regional label used by an overseas retailer before comparing its detailed measurement chart.
Marketplace catalog normalization
Transform supplier clothing sizes into consistent US, UK, and EU fields while retaining category and source-region provenance.
Customer support references
Give support agents a repeatable standard cross-reference when buyers ask how an adult women’s garment or men’s jacket size compares internationally.
FAQ
Which regional systems are supported?
The converter supports numeric US, UK, and EU clothing sizes.
Which clothing categories are supported?
It supports standard adult women’s general clothing and adult men’s jackets.
Does a converted size guarantee the same fit?
No. It is a standard chart equivalent; brand measurements, cut, and fabric can change real fit.
Why was my numeric size rejected?
The value must exactly match a row in the selected category and source-region chart. The converter does not interpolate unsupported sizes.
What is a women's US 8 in UK and EU sizes?
A UK 12 and an EU 38, from the same row of the standard women's chart. Men's jackets use a different scale: a US 38 jacket matches a UK 38 and an EU 48.
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/misc2/clothing-size-convert \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"size":"8","region":"US","category":"women"}'const res = await fetch("https://api.kit.forhosting.com/misc2/clothing-size-convert", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"size": "8",
"region": "US",
"category": "women"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/misc2/clothing-size-convert",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"size": "8",
"region": "US",
"category": "women"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/misc2/clothing-size-convert", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"size":"8","region":"US","category":"women"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"size":"8","region":"US","category":"women"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/misc2/clothing-size-convert", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"size": "8",
"region": "US",
"category": "women"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "misc2.clothing_size_convert",
"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
Choose the right chart and describe the source size
The converter also recognizes straightforward regional aliases such as USA, GB, and EUR, as well as women’s and men’s spelling variants. It deliberately requires a recognized category instead of guessing from the number. If the selected chart has no exact row for the supplied number, the request returns an input error rather than rounding to a nearby size.
Handle validation, API pricing, and repeatable workflows
Missing size, missing region, nonnumeric size, unknown region, and unknown category values produce invalid_input errors.
Technical questions
How much does API conversion cost?
Each successful API item costs $0.002. The deterministic browser experience can be used for quick interactive checks.