Glove size
A hand measuring 8.25 inches around the knuckles wears a size M, numeric 8. Enter that one measurement, thumb excluded, and get the letter to order and the number to check against a printed chart. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Circumference
- 8.25
- Size
- M
- Numeric size
- 8
Glove size is the circumference of the hand around the knuckles, not a guess from height, shoe size, or the faded tag in last winter’s pair. This calculator accepts that single positive length in inches — the measurement a flexible tape takes around the four knuckles, excluding the thumb — rounds it to the nearest whole inch, and returns the matching unisex label shoppers actually buy: XS, S, M, L, XL, XXL, or XXXL, together with the numeric size factories print on EN 420 and common US–UK charts. You get a letter you can order and a number you can compare with a printed chart.
How knuckle circumference becomes a matching glove size label
A glove size is a name for the circumference of the hand around the knuckles, not a style recommendation and not a conversion between centimetres and inches. The measurement the industry uses is taken with a flexible tape around the four knuckles — the metacarpophalangeal joints — excluding the thumb, with the hand relaxed and the tape snug but not tight. That length, in inches, is the only input.
The numeric glove size that factories and EN 420 charts print is that same circumference rounded to the nearest whole inch, because retail SKUs are 6, 7, 8, 9, 10, 11, and 12, not 8.37. The matching size label is then read from the common unisex letter chart that appears on winter, work, driving, and garden gloves: a numeric size of six or below is XS, seven is S, eight is M, nine is L, ten is XL, eleven is XXL, and twelve or above is XXXL.
Values that fall well below a child’s extra-small or well above a large adult still receive a label rather than a clamp error, because the contract is to fail only when the circumference is not a positive number. The algorithm is a single round and a seven-row table. There is no network chart, no brand vanity offset, and no clock.
How to measure, what to send, and how errors are reported
Measure the dominant hand at the end of the day when the hand is warm, not first thing in the morning. Wrap a flexible tape or a narrow paper strip around the four knuckles, skip the thumb, mark the overlap, and read inches on a ruler. Keep the tape level and snug; a loose wrap overstates the size and a tight wrap understates it.
If the knuckles and the palm differ a lot, record the knuckles — that is the dimension the glove must pass. A formula string restates the round-and-chart rule so a page can show the arithmetic next to the answer. A typical adult measurement of 8.25 inches returns M and numeric size 8.
Where a glove-size-from-inches calculator earns its keep
Online outdoor and workwear shops need an inches box on the size guide, not a lecture about centimetres versus letter charts. A shopper who has just wrapped a tape around the knuckles can type 7.5 or 9.2 and see the matching label before adding gloves to the cart, which cuts the returns that come from guessing between M and L. Gift buyers who cannot borrow the recipient’s pair can ask for a knuckle measurement in inches by text and convert it privately.
Warehouse and safety teams issuing one-size-per-person kits can turn a short list of tape readings into XS through XXXL without opening a printed wheel. Marketplaces that list the same SKU as both M and size 8 can fill those columns from one inch input, so a listing stays consistent when the catalogue is generated rather than typed.
What you can do with it
Gift buying without the pair
Convert an inches measurement sent by the recipient into a letter size so surprise gloves can be ordered without borrowing an existing pair.
Kit issue and marketplace listings
Turn a list of tape readings into consistent letter and numeric sizes for locker kits, or fill M and size-8 columns from one inch field.
FAQ
How do I find my glove size from hand circumference?
Send a positive finite number of inches in the circumference field, measured around the knuckles excluding the thumb.
How should I measure around the knuckles?
Wrap a flexible tape or a paper strip around the four knuckles of the dominant hand, skip the thumb, mark the overlap, and read inches. Measure at the end of a warm day with the tape snug but not tight.
What letter does each inch size map to?
Six inches or below is XS, seven is S, eight is M, nine is L, ten is XL, eleven is XXL, and twelve or above is XXXL. The numeric size is the circumference rounded to the nearest whole inch.
What if my measurement falls between two sizes?
Half-inches round toward the next whole size (7.5 becomes 8, which is M). If you are between sizes and want a looser work glove, choose the larger letter; for a close dress or driving glove, stay with the rounded result.
Which hand should I measure for gloves, and when?
Measure your dominant hand at the end of the day, when it is warm, rather than first thing in the morning. Keep the tape level and snug: a loose wrap gives a size too big, a tight one a size too small.
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/life/glove-size \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"circumference":8.25}'const res = await fetch("https://api.kit.forhosting.com/life/glove-size", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"circumference": 8.25
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/life/glove-size",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"circumference": 8.25
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/life/glove-size", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"circumference":8.25}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"circumference":8.25}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/life/glove-size", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"circumference": 8.25
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "life.glove_size",
"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
Zero, negative, missing, or non-finite values fail with invalid_input and are not billed.
How knuckle circumference becomes a matching glove size label
Half-inches round toward plus infinity, the same JavaScript Math.round rule on every call, so 7.5 becomes 8 and 8.4 stays 8; a product page and an API client therefore never disagree. The primary field size is the letter; numeric_size travels beside it so a chart that prints 8 instead of M can be read without a second conversion.
How to measure, what to send, and how errors are reported
POST a JSON body with one required field, circumference, a positive finite number of inches. The solver also accepts the aliases inches, in, value, hand, and knuckles, and it reports errors against the canonical name so a form can mark the right control. On success the body echoes the cleaned circumference, returns size as the matching letter label, and returns numeric_size as the nearest whole inch. Missing fields, empty strings, non-numeric tokens, NaN, Infinity, zero, and negative values all fail with invalid_input and a message that says the circumference must be a positive number; those failures are not billed. Successful API calls use the published base of $0.002 per item; the free browser path runs the same solve function without consuming prepaid balance.
Where a glove-size-from-inches calculator earns its keep
Keep the circumference positive and finite, pin size and numeric_size in your tests, and you get a reproducible label for a product page, a gift checklist, a locker-room intake form, or an edge worker without standing up a fit-lab stack for a one-number lookup.
Integration use cases
Product-page size guides
Let a shopper type knuckle circumference in inches and show the matching XS–XXXL label before checkout, using the same letter the catalogue API stores.
Technical questions
What does the glove size calculator cost?
The browser tool is free. API requests use prepaid balance at $0.002 per successful call; invalid input is not billed.