Metric tons to US tons converter
1 metric ton is 1.102311310924 US short tons, because a short ton is exactly 907.18474 kg. Turn tonnes from a manifest or a European freight label into the short tons American rail bills, grain elevators and scrap buyers quote. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Mass in metric tons
- 1
- Result
- 1.1023113109
- Converted
- 1.1023113109
- Us tons
- 1.1023113109
- Us short tons
- 1.1023113109
A metric-tons-to-US-tons converter turns SI tonne masses used on shipping manifests, commodity contracts, and European freight labels into the US short ton still quoted on American rail bills, grain elevators, and industrial inventory systems. Approximate mental shortcuts such as multiply by one point one zero two are rejected in favour of the composed international constants, so logistics records and homework checks match engineering tables.
Why metric tons and US short tons still need an exact bridge
Metric tons, also called tonnes, belong to the SI-derived mass family used on international bills of lading, European product labels, and most scientific and customs declarations: one metric ton is exactly one thousand kilograms. The United States still prices many bulk commodities, scrap metal, and rail freight in short tons of two thousand avoirdupois pounds each. Those two ton systems are not interchangeable; treating a metric ton as a short ton understates mass by roughly ten percent and can skew quotes, duties, and inventory.
The bridge is exact by composition, not a survey approximation. One US short ton is defined as two thousand avoirdupois pounds, and since the nineteen fifty-nine international yard and pound agreement one international pound is exactly zero point four five three five nine two three seven kilograms. Multiplying those constants yields nine hundred seven point one eight four seven four kilograms per short ton with no leftover uncertainty.
That makes the conversion a single exact multiply: US short tons equal metric tons times one thousand divided by nine hundred seven point one eight four seven four. Rough rules of thumb such as multiply by one point one zero two introduce scale error that shows up on multi-thousand-tonne shipments.
Practical tips, checks, and related searches
Prefer sending bare numbers when you control the client; string numbers are accepted only when they match a strict finite numeric pattern without units, thousand separators, or currency symbols.
Round-trip sanity checks are easy: convert one metric ton and confirm you receive approximately one point one zero two three one one three one zero nine two four US short tons after rounding, or convert nine hundred seven point one eight four seven four kilograms worth of mass expressed as zero point nine zero seven one eight four seven four metric tons and confirm you receive exactly one short ton after rounding.
When teaching, pair the exact path with a rough mental shortcut so students see the drift on larger cargos. Stay inside the absolute range so the multiply cannot overflow into a non-finite result the solver must reject. This landing targets people searching for metric tons to US tons, convert tonnes to short tons, or an exact nine hundred seven point one eight four seven four calculator; it is not a general multi-unit mass hub, not a short-tons-to-metric primary form, not a UK long-ton converter, and not a kilograms-only tool.
Prefer this capability when the input is already in metric tons and you only need US short tons; if you must convert among many mass units in one call, use a broader unit converter instead.
What you can do with it
Freight and shipping manifests
Turn SI tonne bill-of-lading totals into US short tons for American rail and truck quotes with the same exact factor every row.
Commodity and scrap pricing
Traders convert metric cargo masses to short tons for US elevator, scrap-yard, and industrial price sheets before publishing offers.
FAQ
What formula converts metric tons to US short tons?
US short tons = metric tons × (1000 ÷ 907.18474).
Is 907.18474 exact or approximate?
Exact by composition. This tool uses 2000 lb per US short ton and the 1959 international pound (0.45359237 kg), not a rough multiply-by-1.102 estimate.
Can I convert US short tons back to metric tons?
This capability is metric tons → US short tons only. Multiply short tons by 0.90718474 on your side, or use a bidirectional mass converter for other units.
Is the metric tons to US tons converter free?
The browser tool is free and runs locally.
Why does 1 metric ton give more than 1 US ton?
Because a US short ton is lighter: 2000 pounds of 0.45359237 kg each make 907.18474 kg, while a metric ton is 1000 kg. So 1 metric ton is 1.102311310924 short tons.
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/metric-tons-to-us-tons \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"metric_tons":1}'const res = await fetch("https://api.kit.forhosting.com/conv/metric-tons-to-us-tons", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"metric_tons": 1
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/metric-tons-to-us-tons",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"metric_tons": 1
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/metric-tons-to-us-tons", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"metric_tons":1}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"metric_tons":1}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/metric-tons-to-us-tons", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"metric_tons": 1
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.metric_tons_to_us_tons",
"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. Send a JSON body with one required finite number field named metric_tons. Aliases metric_ton, tonnes, tonne, mt, value, mass, and weight are accepted so SDK clients and form posts can use the name that fits the product. On success the response echoes rounded metric_tons, sets us_tons, us_short_tons, result, and converted to the same rounded short-ton magnitude, unit and to_unit to the token US short ton, from_unit to t, factor to the rounded ratio one thousand over nine hundred seven point one eight four seven four, kg_per_short_ton to the exact constant nine hundred seven point one eight four seven four, kg_per_metric_ton to one thousand, pounds_per_short_ton to two thousand, formula to the string us_short_tons equals metric_tons times one thousand divided by nine hundred seven point one eight four seven four, message to a short English summary, and steps to an ordered array of substitution lines that show the two-thousand-pound definition. 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 metric_tons or pass text.
Integration use cases
Homework and unit-test fixtures
Students and engineers convert classroom metric-ton masses to US short tons and pin golden JSON so browser and API arithmetic never drift.
Technical questions
What happens on missing or non-numeric input?
The API returns invalid_input naming the problem (for example a missing metric_tons field). Failed tasks are not charged.