Inch-lbs to newton-meters converter
1 inch-pound is 0.11298482902761668 N·m: turn the in-lb torque on a North American wrench, a bicycle spec or an electronics assembly chart into the newton-metres of modern fastener specs, with no truncated constant. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Inch lbs
- 1
- Result
- 0.112984829 N·m
- Converted
- 0.112984829
- Newton meters
- 0.112984829
- From unit
- in·lbf
An inch-pounds-to-newton-meters converter turns a US customary inch-pound torque reading into the SI newton-metre value used in modern fastener specs, small-motor nameplates, and international mechanical datasheets. Approximate mental shortcuts such as zero point one one three newton-meters per inch-pound are rejected in favour of the full exact constant, so homework checks and lab exports match standard conversion tables.
Why inch-pounds and newton-meters meet at an exact SI factor
The newton-metre is the SI coherent unit of torque and of work: one newton of force through one metre of lever arm, and the common reporting unit for fastener torque, moment of force, and energy in modern science. Inch-pounds remain common on North American inch-pound torque wrenches, electronics assembly charts, bicycle component specs, firearm and optics mounts, and many small-fastener tables that still quote in-lb rather than N·m.
The bridge between them is exact for the international definitions: one inch is exactly zero point zero two five four metres, and the pound-force is defined from standard gravity acting on the international pound-mass, which yields one pound-force of four point four four eight two two one six one five two six zero five newtons. Multiplying those two exact pieces gives one inch-pound-force equal to zero point one one two nine eight four eight two nine zero two seven six one six seven newton-meters.
That makes the conversion a single exact multiplication: newton-meters equals inch-pounds times that constant. Teachers can contrast the exact path with a rough zero-point-one-one-three rule of thumb so students see the small relative error that accumulates on large torque tables when the truncated constant is reused row after row. Twelve inch-pounds equal one foot-pound, so this landing is the dedicated search page for the smaller customary unit rather than a foot-pound form.
Practical tips, checks, and related searches
Round-trip sanity checks are easy: convert one inch-pound and confirm you receive about zero point one one two nine eight four eight two nine zero two eight newton-meters after twelve-decimal rounding, convert twelve inch-pounds and confirm about one point three five five eight one seven nine four eight three three one newton-meters (one foot-pound of torque), or convert zero and confirm zero. If your source table quotes foot-pounds or kilonewton-metres, scale to inch-pounds or interpret the SI result carefully before treating it as N·m from in·lbf alone.
Stay inside the absolute range so the product 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 pure conversion so students see that one inch-pound is much smaller than one newton-metre and that twelve of them recover one foot-pound.
This landing targets people searching for inch lbs to nm, convert inch-pounds to newton-meters, in-lb to N·m, or an exact inch-pound to newton-metre calculator; it is not a multi-unit torque hub, not a newton-meters-to-inch-pounds primary form, not a foot-pounds landing, and not a kinetic-energy or power calculator. Prefer this capability when the input is already in inch-pounds and you only need newton-meters; if you must convert among many torque units in one call, use a broader torque unit converter instead.
What you can do with it
Small-fastener and electronics torque charts
Convert US customary inch-pound wrench settings into N·m for SI datasheets, metric driver tools, and international assembly instructions with the same exact factor every row.
FAQ
How many newton-meters are in one inch-pound?
Exactly the product of the international pound-force and the international inch: 4.4482216152605 N × 0.0254 m, about 0.1129848290276167 N·m.
Is this torque or energy?
Inch-pound and newton-metre can name either a moment of force (torque) or energy (work). This tool applies the exact unit factor between in·lbf and N·m; interpret the physical quantity from your problem context.
Why not use 0.113 N·m per inch-pound?
0.113 is a rounded rule of thumb. This converter hard-codes the exact international product of pound-force and the inch used in precise tables and unit-conversion references.
Is the inch-lbs to newton-meters converter free?
The browser tool is free and runs locally.
How many inch-pounds make one foot-pound?
Twelve inch-pounds make one foot-pound, so the inch-pound is the smaller unit used for light fasteners. If your table is in foot-pounds, multiply by twelve first or use a foot-pound converter instead.
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-lbs-to-nm \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"inch_lbs":1}'const res = await fetch("https://api.kit.forhosting.com/conv/inch-lbs-to-nm", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"inch_lbs": 1
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/inch-lbs-to-nm",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"inch_lbs": 1
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/inch-lbs-to-nm", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"inch_lbs":1}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"inch_lbs":1}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/inch-lbs-to-nm", 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_lbs": 1
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.inch_lbs_to_nm",
"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. Do not send mixed unit strings such as twelve in-lb in the number field; convert the magnitude only and keep the unit implied by the contract. Send a JSON body with one required finite number field named inch_lbs. Aliases inch_pounds, in_lbf, in_lb, inlb, value, inlbs, inch_pound, 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_lbs, sets newton_meters, result, and converted to the same rounded newton-metre magnitude, unit to the token N·m, from_unit to in·lbf and to_unit to N·m, factor to the rounded multiplier, newton_meters_per_inch_pound to the exact IEEE product of pound-force and the international inch, formula to the string newton_meters equals inch_lbs times that constant, 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.
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_lbs or pass text.
Integration use cases
Homework and exam checks
Students convert classroom inch-pound readings to newton-meters and compare hand work against deterministic steps before submitting worksheets or coding kata fixtures.
Workshop unit alignment
Service notes that mix inch-pounds and newton-meters can be normalized for SI exports, control logic, and API payloads without fragile hand-typed factor tables.
Technical questions
What happens on invalid input?
Missing fields, non-finite values, non-numeric strings, or values outside the absolute limits return invalid_input and are never charged.