Millimeters converter
Enter a length in millimetres and get inches, centimetres and metres at once: 25.4 mm is exactly 1 inch, 2.54 cm and 0.0254 m. It uses the exact inch definition, never a divide-by-25 shortcut. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Mm
- 25.4
- Inches
- 1
- Centimeters
- 2.54
- Meters
- 0.0254
- From unit
- mm
A millimeters converter turns a length written in millimeters into the three lengths people actually look up from a millimetre reading: inches, centimeters, and meters.
Why millimeters still convert to inches, centimeters, and meters
The meter is the SI base unit of length. A millimetre is the milli prefix applied to the meter: milli means one thousandth, so one millimetre is exactly one thousandth of a meter by definition, not by survey, historical treaty, or ruler manufacturing tolerance. That identity is why meters equal millimeters divided by one thousand, or equivalently millimeters times zero point zero zero one.
The same prefix family places the centimeter at one hundredth of a meter, which is why one millimetre equals one tenth of a centimetre exactly, or millimeters divided by ten. Inches remain the unit people still search from a millimetre reading because product drawings, screen thicknesses, fastener catalogues, and United States woodworking plans quote inches even when the source tape or CAD file is metric.
Since the 1959 international yard and pound agreement, one inch is defined as exactly twenty-five point four millimetres, so inches equal millimeters divided by twenty-five point four with no remaining survey-inch ambiguity. This capability never applies approximate mental shortcuts such as divide by twenty-five, nor does it mix unrelated units into the output. Zero millimeters maps cleanly to zero inches, zero centimeters, and zero meters.
Practical tips, checks, and related searches
Round-trip sanity checks are easy: convert twenty-five point four millimeters and confirm you receive exactly one inch, two point five four centimeters, and zero point zero two five four meters, or convert one thousand millimeters and confirm one meter, one hundred centimeters, and about thirty-nine point three seven inches under the same twelve-decimal rounding. If a drawing quotes centimeters, multiply by ten first to obtain millimeters, then call this tool; if it quotes meters, multiply by one thousand.
Stay inside the absolute range so the products cannot overflow into a non-finite result the solver must reject. When teaching SI prefixes alongside imperial units, pair a millimetre-marked ruler with a one-inch gauge block so students see both the decimal shift and the exact twenty-five point four definition rather than a kitchen estimate.
This landing targets people searching for mm to inches, convert millimeters to centimeters, or a millimeters to meters calculator; it is not a multi-unit length hub, not an inches-to-millimeters primary form, and not a wrench, ring, or shoe-size chart. Prefer this capability when the input is already a length in millimeters and you need inches, centimeters, and meters together; if you must convert among many unrelated units in one call, use a broader length converter instead.
Always keep the prefix labels separate: mm is one thousandth of a meter, cm is one hundredth, and m is the SI base, so mixing those symbols in one field is the most common avoidable error.
What you can do with it
Product drawings and fastener catalogues
Export millimetre CAD and hardware tables to inch, centimetre, and metre fields for mixed-unit catalogues, packing slips, and CNC jobs that still quote imperial thicknesses.
FAQ
How many inches, centimeters, and meters are in one millimeter?
Exactly 1/25.4 in (about 0.03937007874 in), 0.1 cm, and 0.001 m. One millimetre is the SI prefix milli applied to the metre, and one inch is defined as exactly 25.4 millimetres.
What formula converts millimeters to inches, centimeters, and meters?
in = mm ÷ 25.4, cm = mm ÷ 10, and m = mm ÷ 1000. The metric factors are exact by SI definition. This tool first reduces mm to metres for cm and m, then divides mm by 25.4 for inches.
Is 25.4 exact or approximate?
Exact. One inch equals 25.4 millimetres by the 1959 international yard and pound agreement. This tool does not use survey-inch variants or a rough divide-by-25 estimate.
Is the millimeters converter free?
The browser tool is free and runs locally.
Can I use it if my drawing is in centimetres?
Yes, but convert to millimetres first: multiply centimetres by 10, or metres by 1000, then enter the result. Entering centimetres directly would make every answer wrong by a power of ten.
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/mm-millimeters \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"mm":25.4}'const res = await fetch("https://api.kit.forhosting.com/conv/mm-millimeters", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"mm": 25.4
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/mm-millimeters",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"mm": 25.4
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/mm-millimeters", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"mm":25.4}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"mm":25.4}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/mm-millimeters", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"mm": 25.4
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.mm_millimeters",
"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, missing, or non-finite input fails with a clear invalid_input error instead of inventing a number.
Why millimeters still convert to inches, centimeters, and meters
It hard-codes the SI identities, routes centimetres through the metre so the two metric outputs stay consistent, divides by the exact twenty-five point four constant for inches, and rounds only so Worker and browser JSON stay byte-stable.
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, thousand separators, or currency symbols. Do not send centimeters, meters, or inches in this field: scale those to millimeters first, or the three outputs will be wrong by a power of ten or by the inch factor. Send a JSON body with one required finite number field named mm. Aliases millimeters, millimetres, value, length, and mm_value are accepted so SDK clients and form posts can use the name that fits the product. On success the response echoes rounded mm, sets inches, centimeters, and meters to the three converted magnitudes, from_unit to the token mm, inches_per_mm to the rounded reciprocal of twenty-five point four, centimeters_per_mm to one tenth, meters_per_mm to one thousandth, mm_per_inch to the exact constant twenty-five point four, formula to the string in equals mm divided by twenty-five point four with cm equals mm divided by ten and m equals mm divided by one thousand, message to a short English summary, and steps to an ordered array of substitution lines that show the inch divide and the metre as the SI base. 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 mm or pass text.
Integration use cases
Classroom SI and inch drills
Students convert textbook lengths in millimeters to inches, centimeters, and meters, then compare hand work against deterministic steps before submitting worksheets or coding kata fixtures.
Lab notebooks and API normalization
Instrument logs and science notebooks that record millimetres can be normalized to in, cm, and m for dashboards, API payloads, and unit tests without fragile hand-typed factor tables.
Technical questions
What happens if the millimeter value is missing or not a finite number?
Missing fields, non-finite values, non-numeric strings, or values outside the absolute limits return invalid_input and are never charged. Signed finite lengths are accepted.