Electrical conductivity converter
1.5 S/m is 0.015 S/cm, and confusing the two shifts a reading by a factor of 100. Convert conductivity between siemens or mho per metre, centimetre and millimetre and their prefixed forms, for water, soil and lab readings. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Value
- 1.5
- From
- S/m
- To
- S/cm
- Result
- 0.015
- Si S per m
- 1.5
- Factor
- 0.01
Electrical conductivity measures how readily a material or solution carries electric current. Labs, water-quality programs, soil salinity surveys, and materials datasheets report it in siemens per meter, siemens per centimeter, millisiemens or microsiemens scales, and sometimes the older mho family. This electrical conductivity converter applies exact SI relationships so a reading in one unit becomes the correct value in another without spreadsheet formulas, rounded lookup tables, or silent unit mix-ups.
Why conductivity units differ across industries
Siemens per meter (S/m) is the SI coherent unit for electrical conductivity: the reciprocal of ohm-meter resistivity. Materials science and physics references often quote pure metals and semiconductors in S/m or larger multiples, while electrochemistry and analytical chemistry prefer siemens per centimeter because a centimeter-scale cell constant keeps numbers readable for laboratory samples. Water-quality instruments and aquarium controllers commonly display microsiemens per centimeter (µS/cm), so that drinking water and dilute solutions stay in three or four digit ranges instead of scientific notation.
Soil science and irrigation management lean on decisiemens per meter (dS/m) for salinity classes that farmers and agronomists already memorize. The historical mho—ohm spelled backward—is numerically identical to the siemens, so mho per meter equals S/m and mho per centimeter equals S/cm, yet both spellings still appear on older meters, textbooks, and regulatory annexes.
Mixing those families without a fixed conversion path is a frequent source of order-of-magnitude errors: treating 1.5 S/cm as if it were 1.5 S/m understates conductivity by a factor of one hundred, which can invalidate a materials comparison or a compliance check.
How the conversion works and what you get back
Provide three fields: value (a finite number), from (source unit), and to (target unit). The engine normalizes the unit strings, multiplies the input by the exact factor that maps the source unit into siemens per meter, then divides by the factor for the target unit. Because every factor is a pure power-of-ten scale relative to S/m, the arithmetic is deterministic and free of iterative solvers, network lookups, or floating randomness.
Use the structured output to populate lab notebooks, normalize multi-instrument CSVs, or assert unit contracts in automated tests without re-implementing SI tables in every service.
Where teams plug it into real workflows
Water utilities and environmental labs often receive probe logs in µS/cm while reporting standards or partner APIs expect mS/cm or S/m; converting at ingest keeps dashboards and regulatory exports consistent. Materials characterization teams compare literature values published in S/cm against simulation outputs in S/m and need a single audited conversion step rather than ad-hoc spreadsheet cells. Agronomy platforms map soil EC sensors that speak dS/m into analytics pipelines standardized on S/m so salinity thresholds stay comparable across vendors.
Education platforms and exam systems use a strict converter so students see immediate feedback when they type an unknown unit instead of a quietly wrong grade. Hardware reverse-engineering notes may still list conductivity in mho; mapping those strings to siemens before storage avoids dual columns that drift apart. Because unknown units fail fast with a message that names the bad token and lists supported options, bulk jobs can quarantine only bad rows and reprocess the rest.
What you can do with it
Water-quality log normalization
Convert probe readings from µS/cm or mS/cm into S/m (or the reverse) so multi-site dashboards and compliance exports share one unit column.
Materials and semiconductor datasheets
Translate literature values in S/cm or mho/cm into S/m for simulation inputs, design reviews, and side-by-side material comparisons.
Soil salinity and irrigation analytics
Map field EC sensors reporting dS/m into a pipeline standardized on S/m or mS/cm without hand-written factor tables.
FAQ
Is mho the same as siemens?
Yes. The mho is the historical name for the siemens. This converter treats 1 mho/m as exactly 1 S/m and 1 mho/cm as exactly 1 S/cm.
Is the electrical conductivity converter free?
The browser tool is free and runs locally.
Why do water meters show µS/cm?
Microsiemens per centimetre keep drinking water and dilute solutions in three- or four-digit ranges instead of scientific notation. That is why water-quality instruments and aquarium controllers use it.
Which unit is used for soil salinity?
Decisiemens per metre, dS/m. Soil science and irrigation use it for the salinity classes that farmers and agronomists already know, so sensor readings stay comparable with those thresholds.
Why do chemistry labs use siemens per centimetre?
Electrochemistry and analytical chemistry work with cells on a centimetre scale, so S/cm keeps laboratory numbers readable, while physics and materials references prefer the SI unit, S/m.
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/electrical-conductivity \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":1.5,"from":"S/m","to":"S/cm"}'const res = await fetch("https://api.kit.forhosting.com/conv/electrical-conductivity", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 1.5,
"from": "S/m",
"to": "S/cm"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/electrical-conductivity",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 1.5,
"from": "S/m",
"to": "S/cm"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/electrical-conductivity", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":1.5,"from":"S/m","to":"S/cm"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":1.5,"from":"S/m","to":"S/cm"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/electrical-conductivity", 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.5,
"from": "S/m",
"to": "S/cm"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.electrical_conductivity",
"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
Unknown units fail with a clear invalid_input error instead of inventing a factor.
Why conductivity units differ across industries
A dedicated electrical conductivity converter exists so every pipeline—browser paste, batch API job, or teaching demo—uses the same exact factors and the same failure mode when a token is not recognized.
How the conversion works and what you get back
Supported tokens include S/m, S/cm, S/mm, mS/m, mS/cm, uS/m, uS/cm (also µS forms), dS/m, kS/m, nS/m, mho/m, and mho/cm, plus common aliases such as siemens per meter or microsiemens per centimeter. The response returns the original value, the normalized from and to unit ids, the converted result, the intermediate value in S/m (si_S_per_m), the combined multiplicative factor applied, and the list of supported units for client validation. Empty fields, non-finite numbers, and unknown unit tokens raise invalid_input and are not billed.
Where teams plug it into real workflows
Whether you paste one reading into the free electrical conductivity converter page or automate thousands of conversions through the KIT API with prepaid balance, the contract stays the same: finite number in, recognized units in, exact SI scale out, hard fail on anything else.
Technical questions
Which electrical conductivity units are supported?
S/m, S/cm, S/mm, mS/m, mS/cm, uS/m, uS/cm (including µS spellings), dS/m, kS/m, nS/m, mho/m, and mho/cm, plus common word aliases such as siemens per meter.
What happens if I pass an unknown unit?
The task fails with invalid_input, names the unknown token, and lists supported units. Failed validation is not charged.
Are the conversion factors exact?
Yes. All scales are exact SI relationships relative to siemens per meter (for example 1 S/cm = 100 S/m, 1 µS/cm = 1e-4 S/m). No approximate lookup tables are used.