Inductance converter
1 henry is 1000 millihenries: move an inductance between H, mH, µH, nH and pH while you read a coil datasheet, a PCB inductor catalog, an RF matching note or a homework problem, always through henries. 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
- H
- Target unit
- mH
- Result
- 1,000
- From label
- henry
- To label
- millihenry
- Henries
- 1
An inductance converter turns a quantity written in one inductance unit into another without hunting conversion tables or rewriting spreadsheet formulas.
Supported units and how the conversion is computed
The converter accepts five inductance families under stable canonical codes: H for the SI henry, mH for the millihenry, uH for the microhenry (ASCII form; Greek mu micro symbols are also accepted), nH for the nanohenry, and pH for the picohenry. Factors follow SI engineering standards: one millihenry is exactly one thousandth of a henry, one microhenry is exactly one millionth of a henry, one nanohenry is one billionth of a henry, and one picohenry is one trillionth of a henry.
Because the intermediate is always henries, 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. Capacitance, resistance, impedance, and inductive reactance units are intentionally out of scope so RF, power-electronics, and magnetics users get predictable inductance-only results under one clear convention.
Where inductance conversions come up
Use the free in-browser inductance converter when you need a quick henries-to-millihenries, microhenries-to-nanohenries, or nanohenries-to-picohenries check while reading a coil datasheet, PCB inductor catalog, RF matching note, filter design guide, 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, technicians, and engineers expect on paper.
What you can do with it
RF and PCB inductor selection
Convert microhenries and nanohenries to a common base so coil catalogs, matching networks, and layout notes share one SI view without hand-written factors.
Power electronics and filter design
Normalize millihenries and henries in boost, buck, and EMI filter specs when drawings mix SI multiples and legacy lab labels.
FAQ
Which inductance units does this converter support?
Henries (H), millihenries (mH), microhenries (uH or µH), nanohenries (nH), and picohenries (pH).
How do I convert 1 microhenry to nanohenries?
The response result field is 1000, plus a henries 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 inductance converter free?
The browser tool runs free on your device.
Can this convert inductive reactance or impedance?
No. It only changes the unit of an inductance, from henries down to picohenries. Reactance, impedance, capacitance and resistance are left out on purpose, so every result stays a plain inductance figure.
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/inductance \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":1,"from":"H","to":"mH"}'const res = await fetch("https://api.kit.forhosting.com/conv/inductance", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 1,
"from": "H",
"to": "mH"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/inductance",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 1,
"from": "H",
"to": "mH"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/inductance", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":1,"from":"H","to":"mH"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":1,"from":"H","to":"mH"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/inductance", 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": "H",
"to": "mH"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.inductance",
"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 henry, henries, millihenry, millihenries, microhenry, microhenries, nanohenry, nanohenries, picohenry, and picohenries 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 henries-per-unit factor for the source, then divides by the henries-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 inductance in modeling 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 henries quantity, the dimensionless factor from source to target, a short formula line suitable for UI display, the method tag inductance_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. Picohenry-scale results and henry-scale results share the same code path, so extreme magnitude pairs remain well-defined as long as IEEE double precision can represent the intermediate henries product.
Browser use, API pricing, and everyday workflows
Switch to the prepaid API when an electronics CAD plugin, magnetics design tool, power-converter simulator, EMI filter optimizer, physics homework checker, or instrumentation pipeline must convert inductance 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 capacitance or frequency converters when a product pipeline needs several passive-component measure families, or call it alone when search traffic is specifically for inductance conversion—henries, millihenries, microhenries, nanohenries, and picohenries—rather than a general unit switchboard.
Integration use cases
Lab metrology and homework checkers
Convert picohenries through henries for precision measurements and class problems with a prepaid, deterministic API and clear invalid_input on unknown units.
Technical questions
How many millihenries is one henry?
Exactly 1000 mH. Send value: 1, from: "H", to: "mH" to see it in the result field.