Stone to lbs converter
12 stone is exactly 168 pounds, because one stone is 14 lb. Turn a UK or Irish body weight in stone into the pounds that US apps, gym forms and shipping labels expect, decimals included. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Stone
- 12.5
- Pounds
- 175
- Lbs
- 175
- Factor
- 14
Stone is the everyday body-weight unit across the United Kingdom and Ireland: people say they weigh twelve stone, not one hundred sixty-eight pounds, yet gyms, medical charts, shipping labels, and many international apps still expect pounds. Converting by hand is simple in theory—one stone equals exactly fourteen pounds—but spreadsheet cells, rounded mental math, and mixed stone-plus-pounds notations introduce avoidable errors.
Why stone-to-pounds still needs a dedicated tool
The stone (abbreviated st) sits between the pound and the hundredweight in the British imperial mass system. By definition fixed in modern law and metrology references, one stone is exactly fourteen avoirdupois pounds, with no seasonal variation and no regional alternate factors for body weight. That exactness is what makes a dedicated stone to lbs page useful: searchers are not looking for a generic multi-unit converter with dozens of dropdowns; they type a single number and expect pounds back immediately.
Fitness trackers, NHS-style forms, boxing and rugby weight classes, and UK-to-US relocation paperwork all move data between stone-first and pound-first audiences. When a coach records 13.5 st and a US app stores pounds only, a wrong factor or a double conversion (stone to kilograms to pounds with intermediate rounding) can shift displayed weight by more than a pound. Separating this intent from a catch-all unit library also keeps SEO clear: people searching stone to lbs want that formula, that language, and that error behavior, not a lab multi-unit matrix.
This capability exists so browsers, scripts, and APIs share one audited multiplication and one failure mode when the input is empty, text garbage, or non-finite.
Where teams plug stone-to-lbs into real workflows
Consumer health apps that launch in the US and UK often store pounds or kilograms internally while UK users still think in stone; converting on ingest keeps dashboards consistent without teaching every user a new unit. Sports clubs publishing fighter or player weights for international listings can map stone entries to pound columns for partners that only accept lb. Education and exam platforms can grade stone-to-pounds questions with the same deterministic result students see on the free tool, so feedback matches the official factor.
Data-migration jobs that import legacy UK health records into systems standardized on pounds can quarantine only rows that fail validation while converting the rest.
What you can do with it
UK body-weight forms to pound databases
Convert user-entered stone values into pounds before storing them in a system that only accepts lb, keeping UI language local and storage consistent.
Sports and fitness listings
Map stone-based weigh-ins for boxing, rugby, or gym check-ins into pound columns for international partners and apps.
FAQ
How many pounds are in one stone?
Exactly 14. This converter multiplies stone by 14 with no approximate table or intermediate kilogram step.
Can I enter fractional stone?
Yes. Finite decimals such as 12.5 or 9.25 are accepted; 12.5 stone becomes 175 pounds.
Is the stone to lbs converter free?
The browser tool is free and runs locally.
Does this convert pounds back to stone?
No. This capability is stone → pounds only, matching the stone-to-lbs search intent. Use a dedicated reverse tool if you need pounds to stone.
How do I convert a weight like 12 stone 7 pounds?
The converter takes a single number of stone, so write the extra pounds as a fraction of 14. Seven pounds is half a stone, so 12 stone 7 pounds is 12.5 stone, which gives 175 pounds.
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/conv/stone-to-lbs \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"stone":12.5}'const res = await fetch("https://api.kit.forhosting.com/conv/stone-to-lbs", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"stone": 12.5
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/stone-to-lbs",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"stone": 12.5
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/stone-to-lbs", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"stone":12.5}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"stone":12.5}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/stone-to-lbs", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"stone": 12.5
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.stone_to_lbs",
"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
This stone to lbs converter applies that exact imperial factor on every run, rejects non-finite or missing input with a clear invalid_input error, and never calls a network or model.
How the conversion works and what you get back
The engine multiplies by the constant fourteen and returns stone (echoed), pounds, lbs (same number as pounds for clients that prefer the short name), factor (always 14), and formula (the human-readable identity pounds = stone × 14). There is no unit dropdown, no temperature-style offset, and no optional reverse mode in this landing: the SEO contract is stone in, pounds out. Overflow that would leave a non-finite product is likewise rejected. Send a single required field, stone (aliases include value, st, amount, n, and weight): a finite number of stone, including decimals such as 10.5 or 12.75. Missing stone, empty strings, Infinity, NaN, and non-numeric text raise invalid_input with a message that names the field; those tasks are not billed. At $0.002 per successful API item the charge matches a tiny edge parse; the free in-browser path uses the same lib so web and API never diverge.
Where teams plug stone-to-lbs into real workflows
Logistics and personal-effects shipping between the UK and North America sometimes list body or parcel estimates in stone on one side and pounds on the other—batch-converting a column with the KIT API avoids spreadsheet copy-paste drift. Whether you type one value on the free stone to lbs page or automate thousands of conversions through prepaid KIT balance, the contract stays the same: finite stone in, exact pounds out, hard fail on anything else—no silent zeros, no approximate lookup tables, no hidden rounding steps beyond ordinary IEEE floating-point multiplication of a small integer factor.
Integration use cases
Batch CSV migration
Run stone columns from UK export files through the API, fail bad rows with invalid_input, and write clean pound values for analytics.
Technical questions
What happens on invalid input?
Missing, empty, non-numeric, or non-finite values fail with invalid_input. Failed validation is not charged.