Lbs to stone converter
Divide pounds by exactly 14 and get stone: 168 lb is 12 stone, the way body weight is still said in the UK and Ireland. For fitness apps, health forms and boxing or rugby weigh-ins. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Lbs
- 168
- Pounds
- 168
- Stone
- 12
- Factor
- 14
Pounds are the everyday mass unit across the United States and many international trade contexts, yet body weight across the United Kingdom and Ireland is still spoken and written in stone. People say they weigh twelve stone, not one hundred sixty-eight pounds, while US fitness apps, shipping scales, and export forms often store only pounds. Converting by hand is simple in theory—one stone equals exactly fourteen pounds, so stone equals pounds divided by fourteen—but spreadsheet cells, rounded mental math, and mixed stone-plus-pounds notations introduce avoidable errors.
Why pounds-to-stone 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 lbs to stone page useful: searchers are not looking for a generic multi-unit converter with dozens of dropdowns; they type a single number in pounds and expect stone back immediately.
Fitness trackers, NHS-style forms, boxing and rugby weight classes, and UK-to-US relocation paperwork all move data between pound-first and stone-first audiences. When a US app records one hundred seventy-five pounds and a UK coach thinks in stone, a wrong factor or a double conversion (pounds to kilograms to stone with intermediate rounding) can shift displayed weight by more than a tenth of a stone.
Separating this intent from a catch-all unit library also keeps SEO clear: people searching lbs to stone 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 division and one failure mode when the input is empty, text garbage, or non-finite. Reverse-direction pages such as stone to pounds answer the opposite query; this landing stays pounds in, stone out.
Where teams plug lbs-to-stone 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 display keeps dashboards familiar without teaching every user a new unit. Sports clubs publishing fighter or player weights for UK listings can map pound entries from international partners into stone columns for local fans and coaches. Education and exam platforms can grade pounds-to-stone questions with the same deterministic result students see on the free tool, so feedback matches the official factor.
Data-migration jobs that import legacy US health records into systems that surface stone for UK clinicians can quarantine only rows that fail validation while converting the rest.
What you can do with it
US pound databases to UK stone displays
Convert stored pound values into stone before showing them to UK users, keeping storage consistent and UI language local.
Sports and fitness listings
Map pound-based weigh-ins for boxing, rugby, or gym check-ins into stone columns for UK partners, fans, and coach reports.
FAQ
How many pounds are in one stone?
Exactly 14. This converter divides pounds by 14 with no approximate table or intermediate kilogram step.
Can I enter fractional pounds?
Yes. Finite decimals such as 175 or 182.5 are accepted; 175 pounds becomes 12.5 stone.
Is the lbs to stone converter free?
The browser tool is free and runs locally.
Does this convert stone back to pounds?
No. This capability is pounds → stone only, matching the lbs-to-stone search intent. Use a dedicated reverse tool if you need stone to pounds.
How many stone is 175 pounds?
175 pounds are 12.5 stone. The converter simply divides by 14, so a weight recorded in a US app reads straight away in the stone a UK coach or clinician expects.
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/lbs-to-stone \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"lbs":168}'const res = await fetch("https://api.kit.forhosting.com/conv/lbs-to-stone", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"lbs": 168
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/lbs-to-stone",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"lbs": 168
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/lbs-to-stone", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"lbs":168}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"lbs":168}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/lbs-to-stone", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"lbs": 168
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.lbs_to_stone",
"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 lbs to stone 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 divides by the constant fourteen and returns lbs (echoed), pounds (same number as lbs for clients that prefer the long name), stone, factor (always 14), and formula (the human-readable identity stone = pounds ÷ 14). There is no unit dropdown, no temperature-style offset, and no optional reverse mode in this landing: the SEO contract is pounds in, stone out. Overflow that would leave a non-finite quotient is likewise rejected. Send a single required field, lbs (aliases include pounds, pound, lb, value, amount, n, weight, and mass): a finite number of pounds, including decimals such as 154 or 182.5. Missing lbs, 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 lbs-to-stone into real workflows
Logistics and personal-effects shipping between North America and the UK sometimes list body or parcel estimates in pounds on one side and stone on the other—batch-converting a column with the KIT API avoids spreadsheet copy-paste drift. Whether you type one value on the free lbs to stone page or automate thousands of conversions through prepaid KIT balance, the contract stays the same: finite pounds in, exact stone out, hard fail on anything else—no silent zeros, no approximate lookup tables, no hidden rounding steps beyond ordinary IEEE floating-point division by a small integer factor.
Integration use cases
Batch CSV migration
Run pound columns from US export files through the API, fail bad rows with invalid_input, and write clean stone values for UK 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.