Electron mobility converter
1400 cm²/(V·s), roughly the electron mobility of silicon, is 0.14 m²/(V·s). Convert carrier mobility between square metres, centimetres and millimetres per volt second and the per-volt-hour units of older tables, for datasheets, Hall-effect results and homework. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Value
- 1,400
- Source unit: m²/
- cm²/(V·s)
- Target unit: m²/
- m²/(V·s)
- Result
- 0.14 m²/(V·s)
- Converted
- 0.14
- Value si
- 0.14
- Factor
- 0.0001
An electron mobility converter turns one charge carrier mobility magnitude into another common semiconductor and SI unit without spreadsheet formulas or mental scale tables. Enter a finite value plus a source unit and a target unit among square meters per volt second, square centimeters per volt second, square meters per volt hour, square centimeters per volt hour, and square millimeters per volt second; the tool returns the converted mobility, the SI intermediate in m²/(V·s), the exact unit factor applied, and step-by-step substitution lines you can paste into a device datasheet, lab notebook, or homework check. Device physicists comparing Hall-effect results, process engineers scaling process-control limits between cm²/(V·s) and SI, students converting textbook mobility values, and simulation authors mapping legacy hour-based tables to SI all need the same deterministic path.
Which mobility units are supported and how conversion works
This capability converts among five everyday charge carrier mobility units that dominate semiconductor device physics, Hall-effect metrology, materials datasheets, and SI-facing engineering reports. The square meter per volt second, written m²/(V·s), is the SI coherent unit and the internal hub: every conversion multiplies the input by how many m²/(V·s) equal one source unit, then divides by how many m²/(V·s) equal one target unit.
Square centimeters per volt second use the exact geometric factor of ten to the minus four: one square centimeter is one ten-thousandth of a square meter, so one cm²/(V·s) equals 0.0001 m²/(V·s). That is the unit most silicon and compound-semiconductor literature quotes for electron and hole mobility.
Square meters per volt hour and square centimeters per volt hour divide by the exact definition of the hour as three thousand six hundred seconds, so one m²/(V·h) equals one over three thousand six hundred m²/(V·s) and one cm²/(V·h) equals ten to the minus four over three thousand six hundred m²/(V·s). Square millimeters per volt second use the exact millimeter-to-meter area factor of ten to the minus six. Same-unit requests succeed and return the input magnitude with a short message that no change of unit was required.
Practical tips, limits, and when to use this landing
Prefer sending bare numbers for value when you control the client; string numbers are accepted only when they match a strict finite numeric pattern without currency symbols or thousand separators. Round-trip checks are straightforward: convert A to B and B back to A and confirm you recover the original within the published twelve-decimal rounding.
When teaching scale, pair classic examples such as one thousand four hundred cm²/(V·s) to zero point one four m²/(V·s) for approximate silicon electron mobility, one m²/(V·s) to ten thousand cm²/(V·s), and hour-based tables that multiply by three thousand six hundred when moving from per-hour to per-second denominators. Stay inside the absolute range so intermediate SI values cannot overflow.
This landing targets people searching for an electron mobility converter, charge carrier mobility unit conversion, cm2/Vs to m2/Vs, or square meters per volt second online; it is not a Hall-effect mobility calculator that derives mu from voltage and current, not a general multi-quantity unit converter, not a conductivity or resistivity tool, and not a band-structure simulator.
What you can do with it
Semiconductor datasheet unit alignment
Device and process teams convert published cm²/(V·s) electron and hole mobility figures into SI m²/(V·s) so global specs, PDK notes, and mixed-unit standards stay consistent.
Hall-effect lab notebooks
Metrology labs convert measured carrier mobility between cm²/(V·s), mm²/(V·s), and SI for instrument software, lab reports, and round-robin comparisons.
Homework and textbook checks
Students convert m²/(V·s) and cm²/(V·s) homework values with deterministic steps they can compare against hand calculations before submission.
FAQ
How do I convert cm²/(V·s) to m²/(V·s)?
Multiply by 10⁻⁴. One square centimeter is 10⁻⁴ square meters, so 1400 cm²/(V·s) equals 0.14 m²/(V·s).
What about per-volt-hour mobility units?
m²/(V·h) and cm²/(V·h) use the exact hour definition of 3600 seconds. Conversion multiplies or divides by 3600 when changing between per-second and per-hour denominators.
Does this compute mobility from Hall measurements?
No. It only converts a known mobility magnitude between supported units. It does not derive μ from voltage, current, magnetic field, or thickness.
Is the electron mobility converter free?
The browser tool is free and runs locally.
Which unit do semiconductor papers usually use?
Square centimetres per volt second. Most silicon and compound-semiconductor literature quotes electron and hole mobility that way, while SI reports and simulations expect square metres per volt second, where one unit equals ten thousand of the smaller ones.
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/electron-mobility \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":1400,"from":"cm²/(V·s)","to":"m²/(V·s)"}'const res = await fetch("https://api.kit.forhosting.com/conv/electron-mobility", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 1400,
"from": "cm²/(V·s)",
"to": "m²/(V·s)"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/electron-mobility",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 1400,
"from": "cm²/(V·s)",
"to": "m²/(V·s)"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/electron-mobility", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":1400,"from":"cm²/(V·s)","to":"m²/(V·s)"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":1400,"from":"cm²/(V·s)","to":"m²/(V·s)"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/electron-mobility", 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": 1400,
"from": "cm²/(V·s)",
"to": "m²/(V·s)"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.electron_mobility",
"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
Unknown unit names fail with a clear invalid_input error instead of silent wrong factors.
Which mobility units are supported and how conversion works
Common aliases are accepted case-insensitively: m2/Vs, m²/(V·s), square meters per volt second; cm2/Vs, cm²/(V·s); m2/Vh, m²/(V·h); cm2/Vh, cm²/(V·h); mm2/Vs, mm²/(V·s), and related slash or word forms. If the name is not on that list the solver rejects the request with invalid_input naming the bad field and listing supported units, so clients never guess whether a typo produced a wrong number. Negative values are allowed for signed bookkeeping contexts; absolute magnitude must stay within the published one-trillion limit so intermediate products remain finite in IEEE double precision on the Worker and in the browser.
How to call the API and read the response
Value must be a finite number or a strict numeric string within absolute limits of one trillion. Wire this into dashboards, process-control systems, or batch jobs that already hold a mobility reading and only need a second unit for display, standards comparison, or homework checking without shipping floating conversion tables in every app binary. Send a JSON body with three required fields: value (aliases mobility, amount, mu, and the Greek letter mu), from (aliases from_unit, unit_from, and source), and to (aliases to_unit, unit_to, and target). From and to must resolve to supported unit names after alias normalization. On success the response echoes the rounded input value, canonical from and to labels, result and converted set to the same rounded target magnitude, value_si as the SI intermediate in square meters per volt second, unit as the target label, factor as the from-to multiplier, formula as the short equation string, message as an English summary, steps as ordered substitution lines, and supported_units as the five canonical identifiers. Failed validation—missing fields, non-finite numbers, values outside absolute limits, or an unknown unit name—returns invalid_input and is never charged. Pricing is a flat $0.002 per successful request with unit item and zero marginal unit price.
Practical tips, limits, and when to use this landing
Normalize display labels on your side if you need locale-specific spellings—this API always returns the short canonical tokens m²/(V·s), cm²/(V·s), m²/(V·h), cm²/(V·h), and mm²/(V·s) so automated tests stay stable. Prefer this capability when both endpoints are among the five supported mobility units and you need deterministic factors and step strings; if you need mobility from measured Hall data, use a dedicated Hall mobility calculator instead. Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when clients deliberately probe unknown unit names.
Technical questions
What units does the electron mobility converter support?
m²/(V·s), cm²/(V·s), m²/(V·h), cm²/(V·h), and mm²/(V·s), including common aliases such as m2/Vs and cm2/Vs. Unknown names return invalid_input.