Force converter
Switch a force between newtons, kilonewtons, dynes, pounds-force, kilograms-force and poundals: 1 lbf is 4.4482216152605 N, worked out through newtons with exact standard gravity. Handy for load tables, tensile-test logs and homework. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Value
- 1
- Source unit
- kN
- Target unit
- N
- Result
- 1,000
- From label
- kilonewton
- To label
- newton
- Newtons
- 1,000
A force converter turns a quantity written in one force unit into another without hunting conversion tables or rewriting spreadsheet formulas.
Supported units and how the conversion is computed
The converter accepts six force families under stable canonical codes: N for the SI newton, kN for the kilonewton, dyn for the CGS dyne, lbf for pound-force, kgf for kilogram-force (also known as the kilopond), and pdl for the poundal.
Factors follow SI and conventional engineering standards: one kilonewton is one thousand newtons, one dyne is exactly ten to the minus five newtons, one kilogram-force is exactly nine point eight zero six six five newtons under standard gravity, one pound-force is zero point four five three five nine two three seven kilograms times that same standard gravity, and one poundal is one pound mass times one foot per second squared.
Because the intermediate is always newtons, converting A to B and B to A is consistent up to the published rounding of twelve decimal places, and there is no pairwise matrix that can drift out of sync. Mass units, pressure units, and torque units are intentionally out of scope so structural, mechanical, and lab users get predictable force-only results under one clear convention.
For load tables, lab tests and homework
Use the free in-browser force converter when you need a quick newtons-to-pounds-force, kilonewtons-to-kilograms-force, or dynes-to-newtons check while reading a lab procedure, structural drawing, materials datasheet, or homework problem. Open the page, enter the number and units, and copy the result without installing a spreadsheet, a unit library, or a desktop calculator pack. Source inputs follow the same retention rules as other KIT parse items, and results are safe to cache because the algorithm is fully deterministic.
Authors shipping mobile apps or chatbots can map the result and formula fields directly into cards that show both the number and the conversion path students, engineers, and technicians expect on paper.
What you can do with it
Structural and mechanical engineering
Convert kilonewtons and newtons to pounds-force (and back) so load tables, FEA exports, and bolt-spec sheets share one SI-or-customary view without hand-written factors.
Lab and materials testing
Normalize dynes, newtons, and kilograms-force in tensile-test logs and LIMS when instruments mix CGS, SI, and technical-atmosphere conventions.
FAQ
Which force units does this converter support?
Newtons (N), kilonewtons (kN), dynes (dyn), pounds-force (lbf), kilograms-force (kgf), and poundals (pdl).
How many newtons is one pound-force?
Exactly 4.4482216152605 N under the ISO definition that multiplies the avoirdupois pound mass by standard gravity 9.80665 m/s².
How do I convert 1 kilonewton to newtons?
The response result field is 1000, plus a newtons intermediate and a readable formula.
What happens if I send an unknown unit?
The message names the field and lists supported units. Validation failures are not charged.
Is the force converter free?
The browser tool runs free on your device.
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/force \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":1,"from":"N","to":"lbf"}'const res = await fetch("https://api.kit.forhosting.com/conv/force", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 1,
"from": "N",
"to": "lbf"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/force",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 1,
"from": "N",
"to": "lbf"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/force", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":1,"from":"N","to":"lbf"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":1,"from":"N","to":"lbf"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/force", 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": 1,
"from": "N",
"to": "lbf"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.force",
"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
The browser tool runs free on your device; the prepaid API charges $0.002 per successful item when pipelines need the same contract from servers and automation.
Supported units and how the conversion is computed
Friendly aliases such as newton, newtons, kilonewton, kilonewtons, dyne, dynes, pound-force, pounds-force, kilogram-force, kilograms-force, kilopond, poundal, and poundals are normalized case-insensitively so forms and APIs can pass either short codes or full names. Every request multiplies the input value by the exact newtons-per-unit factor for the source, then divides by the newtons-per-unit factor for the target.
Request shape, response fields, and unknown-unit errors
The error message names the bad field and lists the supported set so clients can correct forms without guessing. Negative values are allowed when you need signed force components in engineering pipelines; zero converts cleanly to zero in every target unit. Send a JSON body with three required fields: value as a finite number, from as the source unit string, and to as the target unit string. Aliases amount and quantity are accepted for value; unit_from and source for from; unit_to and target for to. On success the response echoes the canonical from and to codes, human-readable from_label and to_label strings, the converted result, the intermediate newtons quantity, the dimensionless factor from source to target, a short formula line suitable for UI display, the method tag force_si, and the fixed list of units_supported. Missing value, non-finite numbers such as NaN or Infinity, missing unit fields, and any token that does not map to a supported unit fail with invalid_input and are not charged after the engine rejects the request. Identical inputs always yield identical JSON because the path is pure arithmetic with no randomness, no remote lookup, and no dependence on the wall clock, which makes the endpoint safe to pin in continuous-integration goldens and SDK contract tests. Dyne-scale results and kilonewton-scale results share the same code path, so extreme magnitude pairs remain well-defined as long as IEEE double precision can represent the intermediate newtons product.
Browser use, API pricing, and everyday workflows
Switch to the prepaid API when a CAD plugin, structural-analysis pipeline, materials LIMS, robotics controller, physics homework checker, or load-cell calibration tool must convert force at scale under a stable KIT contract at $0.002 per successful item; validation failures that raise invalid_input do not consume balance after rejection. Pair this endpoint with mass or pressure converters when a product pipeline needs several measure families, or call it alone when search traffic is specifically for force conversion—newtons, kilonewtons, dynes, pounds-force, kilograms-force, and poundals—rather than a general unit switchboard.
Integration use cases
Homework and robotics pipelines
Convert poundals and pounds-force for class problems and servo force limits with a prepaid, deterministic API and clear invalid_input on unknown units.