Micrometer conversion
1000 µm is 1 mm, 0.001 m, 0.03937007874 in and 1000000 nm. Enter a coating thickness, a feature size or a filter pore in micrometers and get all four lengths together, with the exact international inch. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Micrometers
- 1,000
- Millimeters
- 1
- Meters
- 0.001
- Inches
- 0.0393700787
- Nanometers
- 1,000,000
A dedicated micrometer conversion is the search people type when a drawing, microscope scale, coating thickness, semiconductor feature, or filter pore size is already in micrometers and they need millimeters, meters, inches, and nanometers without opening a general unit hub. Enter a non-negative finite length in micrometers. This calculator applies the exact SI prefix identities that one millimeter equals one thousand micrometers, one meter equals one million micrometers, and one micrometer equals one thousand nanometers, together with the international inch of twenty-five point four millimeters so one inch equals twenty-five thousand four hundred micrometers. The path is pure deterministic arithmetic: no network, no random seeds, and no wall-clock dependence.
Why micrometers convert with exact SI prefixes and the international inch
The micrometer, also spelled micrometre and still called a micron in many shops, is one millionth of a meter. That single SI definition is enough to derive every millimeter, meter, and nanometer result this capability returns, because those three names are also decimal prefixes of the meter rather than independent length units. Milli means one thousandth, so one millimeter is one thousand micrometers and millimeters equal micrometers divided by one thousand.
The meter itself is one million micrometers, so meters equal micrometers divided by one million. Nano means one billionth, so one micrometer is one thousand nanometers and nanometers equal micrometers times one thousand. Inches are the only non-SI column: since 1959 the international inch is exactly twenty-five point four millimeters, therefore one inch is exactly twenty-five thousand four hundred micrometers and inches equal micrometers divided by twenty-five thousand four hundred.
There is no US survey inch here, no approximate twenty-five-point-four-ish rule of thumb, and no route through feet unless you divide the inch result by twelve on your side. Zero micrometers maps to zero in every column. Negative lengths are rejected: a length converter is not a signed-delta calculator, and a minus sign on a form is almost always a typo rather than a physical length.
What you can do with it
Thin films, coatings, and plating thickness
Labs that record coating thickness in micrometers can emit millimeters, meters, inches, and nanometers for drawings, BOMs, and mixed-unit customer reports.
Semiconductor, MEMS, and microscopy scale bars
Feature sizes and scale bars stored in micrometers convert to nanometers for process notes and to millimeters or inches for mixed-unit figures.
Precision machining and filter pore sizes
Shop tolerances and filter pores quoted in microns (micrometers) become millimeters and inches for prints, catalogs, and inspection sheets.
FAQ
Are negative lengths allowed?
Zero is allowed and converts to zero in every column. Failed tasks are not charged.
Is the micrometer conversion free?
The browser tool is free and runs locally.
How do I convert micrometers to millimeters?
Divide by 1000. So 1000 µm is 1 mm, which is also 0.001 m and 1000000 nm, and the converter shows all of these together with the inch value.
Is a micron the same as a micrometer?
Yes. Micron is the shop name for the micrometer, one millionth of a meter, so a tolerance or filter pore quoted in microns can be entered as it is.
How many micrometers are in one inch?
Exactly 25400. Since 1959 the international inch measures 25.4 mm, and each millimeter holds 1000 micrometers, so 25400 µm make one inch.
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/micrometer-conversion \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"micrometers":1000}'const res = await fetch("https://api.kit.forhosting.com/conv/micrometer-conversion", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"micrometers": 1000
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/micrometer-conversion",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"micrometers": 1000
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/micrometer-conversion", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"micrometers":1000}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"micrometers":1000}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/micrometer-conversion", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"micrometers": 1000
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.micrometer_conversion",
"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
Negative lengths, missing fields, and non-finite numbers fail with invalid_input instead of inventing a signed length.
Why micrometers convert with exact SI prefixes and the international inch
Results are rounded only to keep JSON stable across runtimes, not because the factors themselves are approximate.
Input contract, response shape, and error behaviour
Prefer sending bare numbers when you control the client. Round-trip sanity checks are easy: convert one thousand micrometers and confirm you receive one millimeter, one thousandth of a meter, one million nanometers, and one thousand divided by twenty-five thousand four hundred inches; or convert twenty-five thousand four hundred micrometers and confirm exactly one international inch together with twenty-five point four millimeters. Send a JSON body with one required finite number field named micrometers. Aliases um, micron, microns, micrometer, value, and length are accepted so SDK clients and form posts can use the name that fits the product. The value must be a JSON number or a strict numeric string without units, thousand separators, or currency symbols. On success the response echoes rounded micrometers and returns millimeters, meters, inches, and nanometers as four finite numbers, plus formula, method, from_unit, a short English message, and an ordered steps array that shows each identity. Failed validation—missing fields, non-finite numbers, bare plus or minus signs, non-numeric strings, negative lengths, 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.
Where a dedicated micrometer-conversion landing earns its keep
Prefer this landing when the search intent is specifically micrometer conversion, not a general multi-unit hub, not a centimetre-to-millimetre school step, and not a mesh-to-micron particle chart. Thin-film and coating labs that record micrometer thicknesses but ship millimeter drawings, semiconductor and MEMS notes that mix nanometer gates with micrometer pitches, microscopy scale bars that must also print inches for mixed-unit reports, filtration data that started in microns, and machining tolerances quoted in micrometers on a print that also lists millimeters all need the same deterministic four-column contract. Stay inside the published range so the nanometer multiply cannot overflow. Pair the exact path with a mental check: divide by one thousand for millimeters, divide by one million for meters, multiply by one thousand for nanometers, and divide by twenty-five thousand four hundred for inches; if the API disagrees, the input was not a finite non-negative micrometer value. Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when learners deliberately omit micrometers or pass text. Successful conversions bill as one item at $0.002; validation failures are free.
Technical questions
How do I convert micrometers to millimeters, meters, inches, and nanometers?
Send JSON with micrometers set to a non-negative finite number (for example micrometers: 1000). The response returns millimeters, meters, inches, and nanometers from the exact identities mm = μm/1000, m = μm/1e6, in = μm/25400, and nm = μm×1000.
Why is one inch exactly 25400 micrometers?
The international inch has been exactly 25.4 millimeters since 1959, and one millimeter is exactly 1000 micrometers, so 1 in = 25400 μm. There is no survey-inch mode.
What happens on missing or non-numeric input?
The API returns invalid_input naming the problem (for example a missing micrometers field or a non-finite number). Failed tasks are not charged.