Particle fluence converter
One particle per square centimetre is 10000 per square metre. Convert fluence between nine units, from per barn and per square fermi to per square inch, always through the per-square-metre value, so a round trip lands where it started. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Value
- 1
- From
- cm-2
- To
- m-2
- Result
- 10,000
- From label
- per square centimetre
- To label
- per square metre
- Si
- 10,000
A particle fluence converter turns a particle-count-per-area quantity written in one unit into another without hunting handbook tables or rewriting spreadsheet formulas by hand.
Supported units and how the conversion is computed
The converter accepts nine particle fluence families under stable canonical codes: m-2 for particles per square metre (the SI base), cm-2 for per square centimetre, mm-2 for per square millimetre, km-2 for per square kilometre, barn-1 for per barn, mb-1 for per millibarn, fm-2 for per square fermi, plus in-2 and ft-2 for customary inverse square measures.
Factors follow SI and nuclear-data convention: one square centimetre is exactly ten to the minus four square metres so one per centimetre squared equals ten thousand per metre squared; one barn is exactly one times ten to the minus twenty-eight square metres so one per barn equals one times ten to the twenty-eight per metre squared; millibarn and square fermi apply the usual metric area scales; inch and foot use the exact SI metre definitions zero point zero two five four metres and zero point three zero four eight metres.
Because the intermediate is always SI inverse square metres, 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. Nuclear cross section as area alone, dose, activity, or flux integrated over time by a separate model are intentionally out of scope so reactor physics, radiation-transport, and lab users get predictable fluence-only results under one clear convention.
Where it helps in everyday lab and report work
Use the free in-browser particle fluence converter when you need a quick n/cm² to m⁻² check, a per-barn to per-square-metre normalization, or a square-inch to square-centimetre switch while reading a reactor physics homework set, neutron-transport memo, radiation-hardness report, detector paper, or irradiation log. 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, engineers, and technicians expect on paper.
What you can do with it
Reactor physics and neutron transport notes
Normalize fluence tallies between n/cm² and m⁻² before comparing transport outputs, homework answers, or irradiation logs under one deterministic contract.
Radiation hardness and space environments
Convert mission particle fluences between per square metre and per barn so cross-section products stay dimensionless and publication tables stay consistent.
Lab instruments and teaching labs
Students and technicians convert n/cm² to m⁻² or per barn while reading detector notes, without guessing handbook factors or retyping spreadsheet cells.
FAQ
Which particle fluence units does this converter support?
m-2, cm-2, mm-2, km-2, barn-1, mb-1, fm-2, in-2, and ft-2.
How do I convert 1 per barn to m⁻²?
The response result is 1e28, plus an si intermediate in m⁻² 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 particle fluence converter free?
The browser tool runs free on your device.
Does the converter handle radiation dose or flux too?
No. It converts fluence only, a count of particles per area. Dose, activity, a cross section on its own and flux integrated over time need a separate model and are left out on purpose.
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/particle-fluence \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":1000000000000,"from":"cm-2","to":"m-2"}'const res = await fetch("https://api.kit.forhosting.com/conv/particle-fluence", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 1000000000000,
"from": "cm-2",
"to": "m-2"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/particle-fluence",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 1000000000000,
"from": "cm-2",
"to": "m-2"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/particle-fluence", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":1000000000000,"from":"cm-2","to":"m-2"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":1000000000000,"from":"cm-2","to":"m-2"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/particle-fluence", 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": 1000000000000,
"from": "cm-2",
"to": "m-2"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.particle_fluence",
"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 n/cm2, n/m2, /barn, per square centimetre, particles per barn, cm⁻², m⁻², and common symbols like b⁻¹ are normalized so forms and APIs can pass either short codes or full names. Every request multiplies the input value by the exact inverse-square-metre factor for the source, then divides by the 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 residual or delta-fluence workflows; 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, quantity, fluence, and phi 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 si quantity in inverse square metres with si_unit set to m-2, the dimensionless factor from source to target, a short formula line suitable for UI display, the method tag particle_fluence_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. Extreme magnitude pairs such as per barn to per square metre remain well-defined as long as IEEE double precision can represent the intermediate SI product.
Browser use, API pricing, and everyday workflows
Switch to the prepaid API when a nuclear-data pipeline, Monte Carlo post-processor, laboratory LIMS, space-radiation analysis chain, or education platform must convert fluences 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 nuclear cross-section or radiation-exposure converters when a product pipeline needs several nuclear measure families, or call it alone when search traffic is specifically for particle fluence conversion—per square metre, per square centimetre, per barn, per millibarn, and related inverse areas—rather than a general unit switchboard.
Technical questions
How many per square metre is one per square centimetre?
Exactly 10⁴ m⁻². Send value: 1, from: "cm-2", to: "m-2" to see result 10000 with the SI intermediate path.