Vacuum leak rate converter
Convert vacuum leak rates between mbar·L/s, sccm, atm·cc/s, torr·L/s, Pa·m³/s and four more units: 1 mbar·L/s is 59.215396002961 sccm. Each result passes through Pa·m³/s and shows its steps for your helium leak-test report. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Numeric vacuum leak-rate
- 1
- From
- mbar_L_s
- To
- sccm
- Result
- 59.215396003 sccm
- Converted
- 59.215396003
- From
- mbar·L/s
- From id
- mbar_L_s
A vacuum leak rate converter turns one gas-throughput magnitude used in leak testing and vacuum system specifications into another without spreadsheet tables or mental approximations of millibar liters per second to sccm. Enter a finite value plus a source unit and a target unit among mbar·L/s, sccm, atm·cc/s, torr·L/s, Pa·m³/s, Pa·L/s, sccs, lusec, and mbar·m³/s; the tool returns the converted leak rate, the SI intermediate in pascal cubic metres per second, the exact unit factor applied, and step-by-step substitution lines you can paste into a helium leak-test report or pump specification review. Leak-test technicians reading mass-spectrometer reject limits, process engineers comparing European mbar·L/s specs to North American sccm flow meters, students converting homework throughput values, and automation authors mapping PLC tags between regional unit conventions all need the same deterministic path.
Which vacuum leak-rate units are supported and how conversion works
This capability converts among the gas-throughput units that dominate vacuum leak testing, residual gas analysis, and vacuum system acceptance work in industry and teaching laboratories. Throughput Q is pressure times volume flow rate (Q = p·V/t), not a bare volumetric flow without a reference pressure. The pascal cubic metre per second (Pa·m³/s) is the SI coherent unit and the internal hub: every conversion multiplies the input by how many Pa·m³/s equal one source unit, then divides by how many Pa·m³/s equal one target unit.
One millibar litre per second equals exactly one tenth of a Pa·m³/s because one millibar is one hundred pascals and one litre is one thousandth of a cubic metre. Torr litre per second uses the exact torr definition of one seven-hundred-sixtieth of a standard atmosphere times the litre-to-cubic-metre factor. Atmosphere cubic centimetre per second uses one hundred one thousand three hundred twenty-five pascals times one millionth of a cubic metre.
Standard cubic centimetres per second (sccs) share that same STP factor when standard pressure is one atmosphere; standard cubic centimetres per minute (sccm) are sccs divided by sixty. A lusec is one litre-micron per second, defined as one thousandth of a torr litre per second. 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 vacuum leak rates, pair classic examples such as one mbar·L/s to about fifty-nine point two sccm, one atm·cc/s to one point zero one three two five mbar·L/s, and one thousand lusec to one torr·L/s.
Stay inside the absolute range so intermediate SI values cannot overflow. This landing targets people searching for a vacuum leak rate converter, mbar L/s to sccm, atm cc/s converter, torr L/s to Pa m3/s, or lusec conversion online; it is not a vacuum pressure converter, not a pump-down time calculator, not a conductance tool, and not a general multi-quantity unit converter.
What you can do with it
Regional vacuum-spec translation
Process engineers map European mbar·L/s or torr·L/s acceptance values to sccm or Pa·m³/s tags used by North American flow meters and PLC displays.
Homework and training checks
Students convert lusec, torr·L/s, and sccm vacuum-homework values with deterministic steps they can compare against hand calculations before submission.
FAQ
How many sccm equal one mbar·L/s?
About 59.215 sccm using exact STP factors (101325 Pa standard pressure and one cubic centimetre per minute). The tool returns the full twelve-decimal rounded value.
Is atm·cc/s the same as sccs?
Yes for this converter: both use 101325×10⁻⁶ Pa·m³/s when standard pressure is one atmosphere. They remain separate display labels for client clarity.
Is the vacuum leak rate converter free?
The browser tool is free and runs locally.
What is a lusec?
A lusec is one liter-micron per second, defined as one thousandth of a torr liter per second. It appears in older vacuum and leak-test documents, and the converter handles it like any other unit.
Why is a leak rate not just a volume flow?
Because a leak rate is a throughput: pressure times volume flow. It always carries a pressure, which is why units such as mbar·L/s combine a pressure with liters per second.
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/leak-rate \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":1,"from":"mbar_L_s","to":"sccm"}'const res = await fetch("https://api.kit.forhosting.com/conv/leak-rate", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 1,
"from": "mbar_L_s",
"to": "sccm"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/leak-rate",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 1,
"from": "mbar_L_s",
"to": "sccm"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/leak-rate", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":1,"from":"mbar_L_s","to":"sccm"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":1,"from":"mbar_L_s","to":"sccm"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/leak-rate", 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": "mbar_L_s",
"to": "sccm"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.leak_rate",
"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 vacuum leak-rate units are supported and how conversion works
Common aliases are accepted case-insensitively: mbar L/s, mbar·L/s, millibar liter per second, atm cc/s, atm·cm³/s, and full words for sccm and sccs. 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. 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, mobile clients, or batch jobs that already hold a leak-rate reading and only need a second unit for display, recipe translation, or regulatory comparison without shipping floating conversion tables in every app binary. Send a JSON body with three required fields: value (aliases rate, amount, q, and leak_rate), 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, display from and to labels, from_id and to_id as canonical tokens, result and converted set to the same rounded target magnitude, value_si and value_pa_m3_s as the SI intermediate, unit as the target display 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 full list of 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 short canonical display tokens such as mbar·L/s, sccm, atm·cc/s, and torr·L/s so automated tests stay stable. Prefer this capability when both endpoints are among the supported throughput units and you need deterministic exact factors and step strings; if you need absolute vacuum pressure between torr and millibar without a volume-flow product, use the dedicated vacuum pressure converter instead. Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when clients deliberately probe unknown unit names.
Integration use cases
Helium leak-test reject limits
QA teams convert mass-spectrometer reject limits between mbar·L/s, atm·cc/s, and sccm so multi-vendor fixtures and written procedures share one throughput scale.
Technical questions
Which vacuum leak-rate units can I convert?
Pa·m³/s, Pa·L/s, mbar·L/s, mbar·m³/s, torr·L/s, atm·cc/s, sccs, sccm, and lusec, including common aliases such as millibar liter per second and atmosphere cc/s.
What happens if I send an unknown unit name?
The API returns invalid_input, names the bad field, and lists the supported units. The failed task is not charged.