Convert ring size between regions
See one ring size in all three systems at once: US size 7 is UK O and EU 54, an inner circumference of 54 mm. Enter a US number, a UK letter such as J1/2 or an EU size. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Size
- 7
- Region
- US
- Us size
- 7
- Uk size
- O
- Eu size
- 54
- Eu circumference mm
- 54
Ring labels are not universal: a familiar US number becomes a UK letter and a different EU number based on inner circumference. This converter accepts one recognized size in any of those three regional systems and returns the corresponding US, UK, and EU values together. It uses a fixed conversion table, so the same request always produces the same result. That makes it useful for international shopping, product catalogues, customer support, and any workflow that needs a practical regional equivalent without repeatedly consulting separate charts.
Choose the system printed beside the original size
Start by identifying the regional system attached to the size you already have. Select US for American numeric sizes such as 7 or 8.5, UK for British letter sizes such as O, Q, or J1/2, and EU for the circumference-based numbers commonly shown as 54 or 56.5. The region matters as much as the value: entering 7 as an EU size does not describe the same ring as US size 7, and a letter cannot be interpreted as a US or EU number.
Enter the label exactly enough to identify its standard table entry. UK half sizes may use forms such as J1/2 or the half symbol; the converter normalizes those common forms before matching. Numeric US and EU values may include a decimal point.
If a shop gives only a diameter in millimetres, first confirm its regional chart or measure the circumference, because this capability deliberately accepts regional sizes rather than guessing what an unlabeled measurement means. Clear source identification prevents the most common conversion mistake.
Understand what the returned equivalents mean
The result shows the matched US number, UK letter, and EU circumference size in one object. EU sizing is circumference-based, so the EU value also appears as the nominal inner circumference in millimetres. These are practical retail equivalents from a fixed regional table, not a promise that every manufacturer cuts rings to precisely identical dimensions.
Jewellery charts sometimes round a physical measurement differently, omit half sizes, or place a borderline diameter in the neighboring category. For that reason, treat the conversion as the best table match and keep the seller's own sizing instructions in view when they are available. The method field states that a fixed regional conversion table was used, making automated results easy to explain and audit.
No network request, current catalogue, or brand-specific rule influences the answer. Repeating the same input therefore yields the same conversion, which is important when a storefront, support agent, and order-processing system all need to agree on what was displayed to the customer.
Use conversions safely when fit has real consequences
A converted label is most useful for comparison, catalogue normalization, and narrowing down what to try. For an expensive ring, a surprise gift, a wide band, or a design that cannot be resized, verify the fit with a jeweller or the merchant's printable sizer before purchasing. Fingers change slightly with temperature and time of day, and wide bands can feel tighter than narrow rings even when their measured inner dimensions match.
In software, preserve the original size and region alongside the converted values instead of replacing the source data. That small choice lets customer support see what the shopper actually entered and protects against ambiguity if a vendor uses a different chart later. The converter rejects unknown regions and sizes outside its table rather than silently estimating them.
This behavior is intentional: a visible input error is safer than a plausible-looking but unsupported size.
What you can do with it
Shop across borders
Translate the size you know into the regional label used by an overseas jewellery store.
Normalize product catalogues
Store consistent US, UK, and EU equivalents for rings imported from suppliers using different systems.
Answer sizing questions
Give support teams a repeatable table match while retaining the customer's original size and region.
FAQ
Which regional systems are supported?
US numeric sizes, UK letter sizes, and EU circumference-based sizes are supported.
Does the EU result represent millimetres?
Yes. The EU size is also returned as the nominal inner circumference in millimetres.
Are conversions exact for every jewellery brand?
No. They are fixed practical table equivalents; individual manufacturers may round or size products differently.
What is a US size 7 ring in UK and EU sizes?
A US size 7 matches UK size O and EU size 54, which stands for a nominal inner circumference of 54 millimetres. Check the seller’s own chart before ordering, because some brands round their sizes differently.
Can I convert a ring diameter in millimetres?
Not directly. This converter accepts a size already labelled US, UK or EU. If a shop gives only a diameter, confirm its regional chart first or measure the circumference, because an unlabelled measurement could match more than one size.
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/ring-size-convert \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"size":"7","region":"US"}'const res = await fetch("https://api.kit.forhosting.com/misc2/ring-size-convert", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"size": "7",
"region": "US"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/misc2/ring-size-convert",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"size": "7",
"region": "US"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/misc2/ring-size-convert", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"size":"7","region":"US"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"size":"7","region":"US"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/misc2/ring-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": "7",
"region": "US"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "misc2.ring_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
Use conversions safely when fit has real consequences
API users can handle that typed error, request a corrected region, and avoid placing an order using an accidental conversion.
Technical questions
What happens if the region is not recognized?
The request returns an invalid input error naming the unsupported region and listing US, UK, and EU.
How much does an API conversion cost?
Each API request costs $0.002. The browser version can run locally on this page.