Surface tension converter
72.8 mN/m is exactly 72.8 dyn/cm and 0.0728 N/m. Convert surface tension between N/m, mN/m, dyn/cm and lbf/ft when water-like values near 72 mN/m meet older dyne tables or imperial process sheets. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Value
- 72.8
- From
- mN/m
- To
- dyn/cm
- Result
- 72.8 dyn/cm
- Converted
- 72.8
- Value nm
- 0.0728
- Factor
- 1
A surface tension converter turns one interfacial force-per-length magnitude into another everyday unit without spreadsheet factors or mental decade tables. Enter a finite value plus a source unit and a target unit among newtons per metre, millinewtons per metre, dynes per centimetre, and pounds-force per foot; the tool returns the converted surface tension, the SI intermediate in N/m, the exact unit factor applied, and step-by-step substitution lines you can paste into a lab notebook or design review. Colloids and coatings engineers comparing water-like values near seventy-two millinewtons per metre, petroleum labs reading dynes per centimetre tables, process safety notes using imperial lbf per foot, and students converting homework interfacial tension all need the same deterministic path.
Which surface-tension units are supported and how conversion works
This capability converts among four everyday surface-tension units that dominate laboratory tables, process engineering data sheets, coatings specifications, and undergraduate fluid-mechanics coursework. The newton per metre (N/m) is the SI coherent unit of force per unit length and the internal hub: every conversion multiplies the input by how many newtons per metre equal one source unit, then divides by how many newtons per metre equal one target unit.
Millinewtons per metre use the exact SI milli prefix of one thousandth of a newton per metre and are the unit most often quoted for pure water near room temperature. Dynes per centimetre are exactly equal to millinewtons per metre because one dyne is ten to the minus five newtons and one centimetre is one hundredth of a metre, so the ratio is exactly one thousandth of a newton per metre; many older capillary and pendant-drop tables still print dyn/cm even when modern sheets prefer mN/m.
Pounds-force per foot use the international pound-force of four point four four eight two two one six one five two six zero five newtons divided by the exact international foot of zero point three zero four eight metres, matching sibling imperial force conversions in the catalogue. 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, pair classic examples such as seventy-two point eight millinewtons per metre to seventy-two point eight dynes per centimetre (identity under the exact CGS–SI milli equivalence), zero point zero seven two eight newtons per metre to seventy-two point eight millinewtons per metre, and one millinewton per metre into pounds-force per foot for imperial process notes. Stay inside the absolute range so intermediate N/m values cannot overflow.
This landing targets people searching for a surface tension converter, N/m to mN/m, dynes per centimeter to newtons per meter, or lbf/ft surface tension online; it is not a general multi-quantity unit converter, not a capillary-rise calculator, not a Young–Laplace delta-P tool, and not a contact-angle solver.
What you can do with it
Lab tables and pendant-drop notes
Coatings and colloids labs convert mN/m instrument readouts to dyn/cm literature tables so historical capillary data and modern tensiometers stay on one scale.
Process sheets with mixed SI and imperial units
Plant engineers convert N/m or mN/m interfacial values into lbf/ft for mixed-unit P&ID notes, training packs, and vendor data sheets.
Homework and fluid-mechanics checks
Students convert N/m, mN/m, and dyn/cm homework values with deterministic steps they can compare against hand calculations before submission.
FAQ
Is dyn/cm the same as mN/m?
Yes. One dyne per centimetre equals exactly one millinewton per metre (both are 0.001 N/m). Converting between them yields the same numeric magnitude.
Is the surface tension converter free?
The browser tool is free and runs locally.
How is lbf/ft converted to N/m?
One pound-force per foot uses the international pound-force of 4.4482216152605 newtons divided by the exact foot of 0.3048 metres. Pick lbf/ft as the source and N/m as the target to get the SI value.
Which surface tension units can I convert?
Four: newtons per metre, millinewtons per metre, dynes per centimetre and pounds-force per foot. Any of them can be the starting unit or the target.
Can I enter a negative value?
Yes, for signed differences between two measurements. Negative values convert with exactly the same factors as positive ones, so a difference keeps its sign in every unit.
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/surface-tension \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":72.8,"from":"mN/m","to":"dyn/cm"}'const res = await fetch("https://api.kit.forhosting.com/conv/surface-tension", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 72.8,
"from": "mN/m",
"to": "dyn/cm"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/surface-tension",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 72.8,
"from": "mN/m",
"to": "dyn/cm"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/surface-tension", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":72.8,"from":"mN/m","to":"dyn/cm"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":72.8,"from":"mN/m","to":"dyn/cm"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/surface-tension", 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": 72.8,
"from": "mN/m",
"to": "dyn/cm"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.surface_tension",
"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 surface-tension units are supported and how conversion works
Common aliases are accepted case-insensitively: newton per meter and newtons per metre for N/m, millinewton per meter and mN/m for the milli form, dyne per centimeter and dynes per centimetre for dyn/cm, and pound-force per foot or lbf/ft for the imperial form. 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 values are allowed for signed difference contexts; 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 surface-tension reading and only need a second unit for display, regulatory comparison, or mixed SI–CGS reports without shipping floating conversion tables in every app binary. Send a JSON body with three required fields: value (aliases amount, gamma, sigma, and st), 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 newtons per metre, 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 four 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, mN/m, dyn/cm, and lbf/ft so automated tests stay stable. Prefer this capability when both endpoints are among the four supported interfacial-tension units and you need deterministic factors and step strings; if you need meniscus height or pressure jump across a curved interface, use the dedicated fluid-mechanics calculators 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 surface-tension units can I convert?
Newtons per metre (N/m), millinewtons per metre (mN/m), dynes per centimetre (dyn/cm), and pounds-force per foot (lbf/ft), including common full-word aliases such as dyne per centimeter and newton per meter.
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.
Are results deterministic across browser and API?
Yes. Handler and widget share the same lib.js solve path with fixed SI factors and twelve-decimal rounding, so golden examples match production.