Inch-pounds to foot-pounds converter
12 inch-pounds is exactly 1 foot-pound: turn an in-lb reading from a small-fastener chart or a click wrench into the ft-lb used on lug-nut charts and engine notes, with an exact divide-by-twelve. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Inch pounds
- 12
- Result
- 1 ft·lbf
- Converted
- 1
- Foot pounds
- 1
- From unit
- in·lbf
An inch-pounds-to-foot-pounds converter turns a US customary torque or moment reading quoted in inch-pounds into the foot-pound value used on wrench charts, fastener specs, and engineering datasheets. Mental shortcuts and mixed-unit guesses are rejected in favour of the exact divide-by-twelve identity, so homework checks and torque tables match the international foot definition.
Why inch-pounds and foot-pounds still meet at twelve
Inch-pounds remain the everyday unit on small-fastener charts, bicycle and electronics torque specs, and the inch-pound click wrenches used on laptop screws, rifle scopes, and instrument panels. Foot-pounds remain the reporting unit on automotive lug-nut charts, engine-assembly notes, and most North American wrench settings once the fastener is large enough that an inch-pound scale would read in the hundreds.
The bridge between them is not an approximation: by definition one international foot equals exactly twelve inches, so a one-pound-force acting at a one-foot lever arm is exactly twelve times a one-pound-force acting at a one-inch lever arm. That identity makes the conversion a single exact division—foot-pounds equals inch-pounds divided by twelve, or equivalently inch-pounds times the reciprocal factor one twelfth.
Teachers and technicians often still teach mixed-unit display such as twenty-four inch-pounds shown as two foot-pounds, but the pure unit conversion itself must stay exact so a one-hundred-forty-four inch-pound reading always maps to twelve foot-pounds and a six inch-pound instrument spec always maps to one half of a foot-pound.
Practical tips, checks, and related searches
Round-trip sanity checks are easy: convert twelve inch-pounds and confirm you receive exactly one foot-pound after rounding, or convert one hundred forty-four inch-pounds and confirm exactly twelve foot-pounds. If your source table quotes newton-metres or kilogram-force metres, convert those to inch-pounds first or use a dedicated SI torque converter rather than treating this landing as a multi-unit hub. Stay inside the absolute range so the division cannot overflow into a non-finite result the solver must reject.
When teaching unit analysis, pair a torque example such as a one-pound-force at a one-inch lever arm with the same force at a one-foot lever arm so students see why the factor is exactly twelve and why an inch-pound is smaller than a foot-pound. This landing targets people searching for inch pounds to foot pounds, convert in-lb to ft-lb, or an exact divide-by-twelve torque calculator; it is not a general multi-unit torque hub, not a foot-pounds-to-inch-pounds primary form, not a newton-metres converter, and not a kinetic-energy or power calculator.
Prefer this capability when the input is already in inch-pounds and you only need foot-pounds; if you must convert among many torque units in one call, use a broader torque unit converter instead.
What you can do with it
Wrench and fastener torque charts
Convert inch-pound tool readings into foot-pounds for automotive specs, assembly instructions, and wrench settings that quote ft·lbf instead of in·lbf.
Homework and exam checks
Students convert classroom inch-pound torque problems to foot-pounds and compare hand work against deterministic steps before submitting worksheets.
FAQ
How many foot-pounds are in twelve inch-pounds?
Exactly one. Foot-pounds = inch-pounds ÷ 12, because one foot-pound-force equals twelve inch-pounds-force by the international foot definition.
Is the divide-by-12 factor exact or approximate?
Exact. One international foot is twelve inches, so one foot-pound-force is twelve inch-pounds-force. This tool hard-codes that identity.
Is this torque or energy?
Inch-pound and foot-pound can name either a moment of force (torque) or energy (work). This tool applies the exact unit factor between in·lbf and ft·lbf; interpret the physical quantity from your problem context.
Is the inch-pounds to foot-pounds converter free?
The browser tool is free and runs locally.
When are foot-pounds used instead of inch-pounds?
Foot-pounds take over once a fastener is large enough that an inch-pound scale would read in the hundreds, as on lug nuts and engine assembly. Inch-pounds stay on laptop screws, rifle scopes and instrument panels.
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/inch-pounds-to-foot-pounds \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"inch_pounds":12}'const res = await fetch("https://api.kit.forhosting.com/conv/inch-pounds-to-foot-pounds", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"inch_pounds": 12
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/inch-pounds-to-foot-pounds",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"inch_pounds": 12
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/inch-pounds-to-foot-pounds", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"inch_pounds":12}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"inch_pounds":12}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/inch-pounds-to-foot-pounds", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"inch_pounds": 12
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.inch_pounds_to_foot_pounds",
"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.
Limits
max_abs | 1000000000000 |
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
Invalid or missing input fails with a clear invalid_input error instead of inventing a number.
How to call the API and what comes back
Absolute values must stay within the published limit of one trillion. Prefer bare numbers when you control the client; string numbers are accepted only when they match a strict finite numeric pattern without unit suffixes or thousand separators. Send a JSON body with one required finite number field named inch_pounds. Aliases in_lb, in_lbf, inlb, value, inch_pound, inlbs, and in_lbs are accepted so SDK clients and form posts can use the name that fits the product. On success the response echoes rounded inch_pounds, sets foot_pounds, result, and converted to the same rounded foot-pound magnitude, unit to the token ft·lbf, from_unit to in·lbf and to_unit to ft·lbf, factor to the rounded reciprocal one twelfth, inch_pounds_per_foot_pound to the exact constant twelve, formula to the string foot_pounds equals inch_pounds divided by twelve, message to a short English summary, and steps to an ordered array of substitution lines. Failed validation—missing fields, non-finite numbers, bare plus or minus signs, non-numeric strings, values outside absolute limits, or a non-finite converted result—returns invalid_input and is never charged. Pricing is a flat $0.002 per successful request with unit item and zero marginal unit price.
Practical tips, checks, and related searches
Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when learners deliberately omit inch_pounds or pass text.
Integration use cases
Engineering unit alignment
Process notes that mix inch-pounds and foot-pounds can be normalized for exports, control logic, and API payloads without fragile hand-typed factor tables.
Technical questions
What happens on missing or non-numeric input?
The API returns invalid_input naming the problem (for example a missing inch_pounds field or a non-finite number). Failed tasks are not charged.