Conductance converter
1 millisiemens is 1,000 microsiemens: convert electrical conductance between siemens, millisiemens, microsiemens and mhos, and see the same value in all four units at once, for water meter readings, circuit homework and older manuals. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Conductance magnitude to convert
- 1
- Input unit
- millisiemens
- Output unit
- microsiemens
- Result
- 1,000
- Siemens
- 0.001
- Millisiemens
- 1
- Microsiemens
- 1,000
Electrical conductance conversion between siemens and the everyday engineering prefixes is a recurring task in electronics labs, water-quality instrumentation, secondary-school circuit homework, and industrial process notes. People search for an electrical conductance converter when they need millisiemens next to microsiemens, mhos next to siemens, or a quick SI-prefix hop, not a general multi-unit toolbox that also handles length and temperature. This capability accepts one finite amount plus from and to unit labels among siemens, millisiemens, microsiemens, and mho, bridges every conversion through the siemens so results stay consistent, and returns the target value together with the same conductance expressed in all four units. Unrecognized unit names are rejected with a clear validation error instead of silently guessing a nearby symbol.
How the electrical conductance converter maps units through the siemens
Start from the siemens as the SI coherent unit of electrical conductance G, the reciprocal of resistance in ohms, and express every other supported unit as a fixed factor into siemens. One millisiemens is exactly one thousandth of a siemens, which is why conductivity meters for natural water and many process instruments print readings such as 250 mS or 1.5 mS on their front panels. One microsiemens is exactly one millionth of a siemens and is the scale of high-purity water and dilute laboratory standards.
The historical mho is defined as the reciprocal of the ohm and is therefore identical to the siemens; older textbooks, military manuals, and some legacy sensor firmware still label conductance in mhos rather than siemens. This calculator never mixes those paths ad hoc. It multiplies the input amount by the factor of the source unit to reach siemens, then divides by the factor of the target unit to produce the result.
Because every path shares the same intermediate, converting one millisiemens to one thousand microsiemens and back, or equating one mho with one siemens, stays numerically consistent within ordinary floating-point precision. The tool does not convert resistance, does not compute complex admittance for AC networks, does not convert conductivity in siemens per metre, and does not fetch live instrument telemetry. It answers only the algebraic electrical conductance unit conversion people mean when they type electrical conductance converter into a search bar and expect siemens, millisiemens, microsiemens, and mhos with exact factors.
Where dedicated conductance conversion shows up in real work
Secondary-school and college electronics courses constantly assign problems that give a conductance value on one scale and ask for another, often mixing millisiemens with microsiemens and still using mhos in older problem sets. Water-quality and process-control teams quote sensor ranges in mS or µS while design documents and SI reports prefer siemens, so a single conversion pass keeps calibration logs, SCADA tags, and lab notebooks aligned. RF and DC circuit designers normalize admittance magnitudes between S and mS before comparing filter tables.
Procurement scripts that scrape mixed instrument CSV rows with S, mS, uS, and mho tags can call this capability once per line instead of reimplementing the factors in every service. If you later need electrical resistance conversion, conductivity in siemens per metre, complex admittance solvers, or general multi-category unit conversion alone, treat those as separate search intents and landings rather than overloading this electrical conductance converter page.
What you can do with it
Instrument and datasheet normalization
Normalize conductance values among siemens, millisiemens, microsiemens, and mhos so lab logs, SCADA exports, and SI reports stay consistent.
Water quality and process control
Convert sensor readings in mS or µS into siemens or mhos for calibration sheets and regulatory tables without hand-written factors.
FAQ
Which electrical conductance units does this converter support?
Siemens (S), millisiemens (mS), microsiemens (µS, uS), and mho/mhos.
What happens if I send an unrecognized unit?
The error message includes Unrecognized unit and lists the supported families so you can correct the label.
How many microsiemens are in one millisiemens?
Exactly 1_000 microsiemens. One millisiemens is 1×10⁻³ S and one microsiemens is 1×10⁻⁶ S.
Are mhos and siemens the same?
Yes. The mho is the reciprocal of the ohm and is exactly equal to the siemens. This converter treats 1 mho as 1 S so legacy labels convert cleanly.
What does it cost?
The browser tool is free and runs locally.
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/conductance \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"amount":1,"from":"millisiemens","to":"microsiemens"}'const res = await fetch("https://api.kit.forhosting.com/conv/conductance", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"amount": 1,
"from": "millisiemens",
"to": "microsiemens"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/conductance",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"amount": 1,
"from": "millisiemens",
"to": "microsiemens"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/conductance", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"amount":1,"from":"millisiemens","to":"microsiemens"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"amount":1,"from":"millisiemens","to":"microsiemens"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/conductance", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"amount": 1,
"from": "millisiemens",
"to": "microsiemens"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.conductance",
"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
What you send and what you get back from the API and browser form
Send three fields: amount, a finite number for the conductance magnitude; from, a string naming the input unit; and to, a string naming the output unit. When a unit string is unknown the error message includes Unrecognized unit and lists the four supported families so clients can fix the label rather than guessing. Classic checks include one millisiemens becoming one thousand microsiemens, one siemens matching one thousand millisiemens exactly, one mho equaling one siemens, and one microsiemens becoming one millionth of a siemens. Both unit fields accept short keys and everyday words in any common casing, including siemens or S, millisiemens or mS or milli_siemens, microsiemens or uS or µS or micro_siemens, and mho or mhos. Missing fields, non-numeric amount strings, NaN, Infinity, and unrecognized unit labels fail with invalid_input and are not charged. On success the response echoes the cleaned amount, normalized from and to keys, the primary result in the target unit, the same conductance as siemens, millisiemens, microsiemens, and mho with twelve significant digits of stable precision, the SI factors used, the formula string, and method siemens_bridge. Pricing for successful API calls is the published base of $0.002 per item; validation failures do not consume prepaid balance.
Where dedicated conductance conversion shows up in real work
Data pipelines that ingest mixed IoT or lab payloads with conductance unit tags normalize those readings into one SI key before stacking with simulation models. Because this capability is a pure parse engine, API pricing is the published base of $0.002 per successful item and failed validation does not consume balance.
Integration use cases
Homework and curriculum tools
Map exam values between S, mS, µS, and mhos for answer keys, auto-graders, and interactive electronics demos that share one JSON contract.