Radioactivity converter
Move an activity reading between becquerels, curies and rutherfords with every common prefix: one curie is exactly 3.7 × 10¹⁰ becquerels, so assay certificates, administered activities and soil reports share one unit. 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
- Ci
- To
- Bq
- Result
- 37,000,000,000 Bq
- Converted
- 37,000,000,000
- Value bq
- 37,000,000,000
- Factor
- 37,000,000,000
A radioactivity converter turns one nuclear activity magnitude into another unit without spreadsheet factors or mental powers of ten. Enter a finite value plus a source unit and a target unit among becquerels, curies, rutherfords, and their common SI multiples such as kilobecquerel, megabecquerel, gigabecquerel, millicurie, microcurie, nanocurie, and kilorutherford; the tool returns the converted activity, the SI intermediate in becquerels, the exact unit factor applied, and step-by-step substitution lines you can paste into a lab notebook or report. Health-physics technicians comparing assay certificates, nuclear medicine staff converting administered activities between mCi and MBq, environmental labs reporting soil samples in Bq and pCi, and students checking textbook examples all need the same deterministic path.
Which activity units are supported and how conversion works
This capability converts among three activity families that dominate nuclear science, radiation protection, nuclear medicine, and environmental monitoring. Becquerels (Bq) are the SI coherent unit of activity—one disintegration per second—and the internal hub: every conversion multiplies the input by how many becquerels equal one source unit, then divides by how many becquerels equal one target unit. Curies use the exact modern definition of three point seven times ten to the ten becquerels per curie, fixed so that historical inventories remain comparable after the SI adoption of the becquerel.
Rutherfords use the exact historical definition of one million becquerels per rutherford, still seen in older literature and some teaching materials. Common SI multiples are first-class units: for becquerels the table includes picobecquerel through petabecquerel with the usual symbols pBq, nBq, µBq, mBq, Bq, kBq, MBq, GBq, TBq, and PBq; for curies it includes pCi, nCi, µCi, mCi, Ci, kCi, and MCi; for rutherfords it includes µRd, mRd, Rd, kRd, MRd, and GRd. English names such as megabecquerel, millicurie, and kilorutherford resolve to the same canonical symbols.
Prefix case matters for mega versus milli: MBq is one million becquerels while mBq is one thousandth of a becquerel. Micro accepts both the Greek mu and the Latin u spelling, so uCi and µCi both mean microcurie. 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. Classic teaching pairs include one curie equals three point seven times ten to the ten becquerels, one rutherford equals one megabecquerel, thirty-seven megabecquerels equals one millicurie, and one gigabecquerel equals about twenty-seven millicuries.
Stay inside the absolute range so intermediate becquerel values cannot overflow; for very large inventories choose a larger target unit such as TBq or PBq instead of expanding everything to plain Bq. This landing targets people searching for a radioactivity converter, becquerel to curie, mCi to MBq, Ci to Bq, or rutherford conversion online; it is not a general length-weight-temperature unit converter, not an absorbed-dose or sievert calculator, and not a decay-chain solver.
What you can do with it
Nuclear medicine activity labels
Clinics receive vials labeled in mCi while dose calibrators and protocols use MBq; staff convert administered activities once with exact Ci–Bq factors before patient administration.
Environmental lab reporting
Laboratories measure samples in Bq or Bq per mass but clients and older standards still request pCi; analysts convert assay results for certificates without spreadsheet drift.
Teaching and inventory checks
Students and source custodians convert textbook problems and sealed-source inventories between Ci, Bq, and historical rutherford units with deterministic step strings for audit.
FAQ
Which radioactivity units can I convert?
Becquerels, curies, and rutherfords with common SI multiples (for example Bq, kBq, MBq, GBq, TBq, mCi, µCi, nCi, pCi, Ci, Rd, kRd). English names such as megabecquerel and millicurie are accepted.
How is one curie defined here?
One Ci equals exactly 3.7×10¹⁰ Bq. One rutherford equals exactly 10⁶ Bq (one megabecquerel).
Is the radioactivity converter free?
The browser tool is free and runs locally.
How many MBq is 1 mCi?
1 mCi is 37 MBq. A curie is 3.7 × 10¹⁰ becquerels, so a thousandth of it is 37 million becquerels, the figure nuclear medicine staff use when switching between millicuries and megabecquerels.
Is MBq the same as mBq?
No. Capital M means mega, so 1 MBq is one million becquerels, while lowercase m means milli, a thousandth of a becquerel. For micro, both µCi and uCi are read as microcurie.
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/radioactivity \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":1,"from":"Ci","to":"Bq"}'const res = await fetch("https://api.kit.forhosting.com/conv/radioactivity", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 1,
"from": "Ci",
"to": "Bq"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/radioactivity",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 1,
"from": "Ci",
"to": "Bq"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/radioactivity", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":1,"from":"Ci","to":"Bq"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":1,"from":"Ci","to":"Bq"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/radioactivity", 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": "Ci",
"to": "Bq"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.radioactivity",
"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 | 1000000000000000000 |
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 activity units are supported and how conversion works
If the name is not on the supported list the solver rejects the request with invalid_input naming the bad field and listing example units, so clients never guess whether a typo produced a wrong number. Absolute magnitude must stay within the published one-quintillion 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 quintillion. Wire this into lab information systems, nuclear medicine calculators, environmental reporting pipelines, or batch jobs that already hold an activity reading and only need a second unit for display, regulatory comparison, or inventory transfer without shipping floating conversion tables in every app binary. Send a JSON body with three required fields: value (aliases activity, amount, and n), 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_bq as the SI intermediate in becquerels, 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 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 tokens such as Bq, kBq, MBq, GBq, mCi, µCi, and Rd so automated tests stay stable. Prefer this capability when both endpoints are among the supported activity units and you need deterministic factors and step strings; if you only need to reformat a number for a locale without changing physical unit, use a number-format capability 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 happens if I send an unknown unit name?
The API returns invalid_input, names the bad field, and lists example supported units. The failed task is not charged.
Are results deterministic across browser and API?
Yes. Handler and widget share the same lib.js solve path with fixed conversion factors and twelve-decimal rounding, so golden examples match production.