Torque converter
50 N·m is 36.878107463863 lbf·ft. Convert torque between newton-metres, newton-centimetres, pound-force feet, pound-force inches and kilogram-force metres, with the factor and steps, so a service-manual figure matches the scale on your wrench. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Value
- 50
- From
- N·m
- To
- lbf·ft
- Result
- 36.8781074639 lbf·ft
- Converted
- 36.8781074639
- Value nm
- 50
- Factor
- 0.7375621493
A torque converter turns one moment-of-force magnitude into another unit without spreadsheet formulas or mental factor tables. Enter a finite value plus a source unit and a target unit among newton-metres, newton-centimetres, pound-force feet, pound-force inches, and kilogram-force metres; the tool returns the converted torque, the SI intermediate in N·m, the exact unit factor applied, and step-by-step substitution lines you can paste into a report. Mechanics comparing fastener specs, automotive techs reading wrench scales in mixed units, design engineers checking motor nameplates, and students converting homework values all need the same deterministic path.
Which torque units are supported and how conversion works
This capability converts among five everyday torque units that dominate mechanical design, fastener tables, automotive service manuals, and laboratory work. Newton-metres (N·m) are the SI coherent unit of torque and the internal hub: every conversion multiplies the input by how many newton-metres equal one source unit, then divides by how many newton-metres equal one target unit. Newton-centimetres use the exact factor of one hundredth of a newton-metre.
Pound-force feet use the international pound-force of four point four four eight two two one six one five two six zero five newtons times the international foot of zero point three zero four eight metres. Pound-force inches use the same pound-force times the international inch of zero point zero two five four metres. Kilogram-force metres use standard gravity nine point eight zero six six five newtons per kilogram-force times one metre.
Same-unit requests succeed and return the input magnitude with a short message that no change of unit was required.
Practical tips, limits, and when to use this landing
Prefer sending bare numbers for value when you control the client; string numbers are accepted only when they match a strict finite numeric pattern without currency symbols or thousand separators. Round-trip checks are straightforward: convert A to B and B back to A and confirm you recover the original within the published twelve-decimal rounding. When teaching unit analysis, pair classic examples such as fifty newton-metres to roughly thirty-six point eight eight pound-force feet, one hundred newton-centimetres to one newton-metre, and twelve pound-force inches to one pound-force foot.
Stay inside the absolute range so intermediate newton-metre values cannot overflow. This landing targets people searching for a torque converter, N·m to lbf·ft, newton-metre to pound-foot, or kgf·m to N·m online; it is not a general length-weight-temperature unit converter, not a power or force-only calculator, and not a fastener torque-spec database.
What you can do with it
Fastener and wrench scale conversion
Service manuals list torque in N·m while shop wrenches show lbf·ft or lbf·in; techs convert specs once and torque fasteners correctly without mental factor tables.
Motor and gearbox nameplate checks
Designers convert motor torque ratings between N·m and kgf·m (or pound-feet) when comparing supplier datasheets written in mixed regional unit systems.
Lab and homework moment checks
Students and technicians convert experiment moments between SI and customary units and compare deterministic steps against hand calculations before submission.
FAQ
Is the torque converter free?
The browser tool is free and runs locally.
How many lbf·ft is 50 N·m?
50 N·m equals 36.878107463863 lbf·ft, roughly 36.88. Each newton-metre is 0.737562149277 lbf·ft, and one lbf·ft is 1.355817948331 N·m.
How do I convert lbf·in to lbf·ft?
Divide by 12, because a foot holds twelve inches: 12 lbf·in equal 1 lbf·ft. Shop wrenches show either scale, so this is the step to check before tightening.
What is one kgf·m in N·m?
One kgf·m is 9.80665 N·m. It is standard gravity, 9.80665 newtons per kilogram-force, multiplied by one metre, so the factor is fixed and exact.
Does it tell me the tightening torque for a bolt?
No. It converts a torque you already have, such as a figure from a service manual. It is not a database of fastener torque specs, and it does not convert power or force alone.
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/torque \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":50,"from":"N·m","to":"lbf·ft"}'const res = await fetch("https://api.kit.forhosting.com/conv/torque", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 50,
"from": "N·m",
"to": "lbf·ft"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/torque",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 50,
"from": "N·m",
"to": "lbf·ft"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/torque", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":50,"from":"N·m","to":"lbf·ft"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":50,"from":"N·m","to":"lbf·ft"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/torque", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"value": 50,
"from": "N·m",
"to": "lbf·ft"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.torque",
"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
Unknown unit names fail with a clear invalid_input error instead of silent wrong factors.
Which torque units are supported and how conversion works
Common aliases are accepted case-insensitively: Nm, N.m, and newton-meter for N·m; Ncm and newton-centimeter for N·cm; lb-ft, ft-lb, ft-lbs, and pound-feet for lbf·ft; lb-in, in-lb, and pound-inches for lbf·in; and kgfm, kgf.m, and kilogram-force meter for kgf·m. If the name is not on that list the solver rejects the request with invalid_input naming the bad field and listing supported units, so clients never guess whether a typo produced a wrong number. Negative torques are allowed for signed direction conventions; absolute magnitude must stay within the published one-trillion limit so intermediate products remain finite in IEEE double precision on the Worker and in the browser.
How to call the API and read the response
Value must be a finite number or a strict numeric string within absolute limits of one trillion. Wire this into dashboards, mobile clients, or batch jobs that already hold a torque reading and only need a second unit for display, wrench selection, or regulatory comparison without shipping floating conversion tables in every app binary. Send a JSON body with three required fields: value (aliases torque, amount, and n), from (aliases from_unit, unit_from, and source), and to (aliases to_unit, unit_to, and target). From and to must resolve to supported unit names after alias normalization. On success the response echoes the rounded input value, canonical from and to labels, result and converted set to the same rounded target magnitude, value_nm as the SI intermediate in newton-metres, unit as the target label, factor as the from-to multiplier, formula as the short equation string, message as an English summary, steps as ordered substitution lines, and supported_units as the five canonical identifiers. Failed validation—missing fields, non-finite numbers, values outside absolute limits, or an unknown unit name—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, limits, and when to use this landing
Normalize display labels on your side if you need locale-specific spellings—this API always returns the short canonical tokens N·m, N·cm, lbf·ft, lbf·in, and kgf·m so automated tests stay stable. Prefer this capability when both endpoints are among the five supported torque units and you need deterministic factors and step strings; if you only need to reformat a number for a locale without changing physical unit, use a number-format capability instead. Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when clients deliberately probe unknown unit names.
Technical questions
Which torque units can I convert?
Newton-metres (N·m), newton-centimetres (N·cm), pound-force feet (lbf·ft), pound-force inches (lbf·in), and kilogram-force metres (kgf·m), including common aliases such as Nm, ft-lb, lb-in, and kgfm.
What happens if I send an unknown unit name?
The API returns invalid_input, names the bad field, and lists the supported units. The failed task is not charged.
How is a kilogram-force metre defined here?
One kgf·m equals exactly 9.80665 N·m, using standard gravity g_n as the conversion from kilogram-force to newtons.
Are results deterministic across browser and API?
Yes. Handler and widget share the same lib.js solve path with fixed conversion factors and twelve-decimal rounding, so golden examples match production.