Blood glucose converter
100 mg/dL is 5.5499439456 mmol/L: the converter divides or multiplies by the clinical constant 18.0182, so a reading from a US meter and a European lab report line up. It converts only and never diagnoses. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Value
- 100
- Source unit of 'value'
- mg_dl
- To
- mmol_l
- Result
- 5.5499439456
- From label
- milligrams per deciliter
- To label
- millimoles per liter
- Value mg dl
- 100
This blood glucose unit converter turns a numeric glucose concentration from milligrams per deciliter into millimoles per liter or the reverse, and returns the converted magnitude with canonical unit labels. The only conversion factor used is the fixed clinical constant 18.0182: one millimole per liter equals 18.0182 milligrams per deciliter, so milligrams per deciliter divide by that factor to become millimoles per liter, and millimoles per liter multiply by it to become milligrams per deciliter. Conversion always bridges through milligrams per deciliter with no network calls, no sampling, and no date-dependent shortcuts. Typical checks include one hundred milligrams per deciliter to millimoles per liter and five point five millimoles per liter back to milligrams per deciliter.
Where blood glucose unit conversion fits in labs, travel, and software
Clinical and consumer glucose reporting often mixes United States style milligrams per deciliter with SI millimoles per liter used in Canada, the United Kingdom, Australia, and much of Europe, so a single deterministic converter prevents hand-calculator drift when a patient, nurse, student, or developer compares readings across devices and papers.
Lab reports convert meter exports into the SI unit the electronic health record expects; travelers map home meter readings into the unit on a foreign care plan; teachers assign homework that needs a fast, offline check of the 18.0182 factor without trusting opaque apps that silently change precision. Developers call the same contract from scripts to seed deterministic test vectors for health-tech UIs, to normalize user-entered glucose before charting demos, or to satisfy programming-challenge statements that demand exact factors rather than a hand-waved estimate.
Product tools use the rewrite when a learner or agent types one hundred milligrams per deciliter and the UI must show millimoles per liter side by side. Pair it with general concentration converters when you need molarity for other solutes, and remember this tool does not diagnose, interpret clinical ranges, or recommend treatment.
What you can do with it
Lab and meter unit alignment
Convert meter exports and lab printouts between mg/dL and mmol/L so records, charts, and handoffs share one reporting unit.
Travel and dual-system care
Map home meter readings into the SI or US unit used on a foreign care plan, prescription note, or patient education sheet.
FAQ
What does the blood glucose converter cost?
It is free in your browser on this page.
What happens if I send a negative value?
Blood glucose concentration cannot be negative; zero is allowed and converts to zero.
Does this tool interpret clinical ranges or diagnose diabetes?
No. It only converts units between mg/dL and mmol/L. It does not provide medical advice, A1C conversion, or treatment recommendations.
Which countries use mmol/L and which use mg/dL?
mg/dL is the usual unit in the United States, while mmol/L is used in Canada, the United Kingdom, Australia and much of Europe. That is why travelers and patients with a foreign care plan often need both.
How many decimals does the result show?
Ten by default, and you can choose anywhere from 0 to 15. The underlying value stays the same; only the rounding of the number you see changes.
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/blood-glucose \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":100,"from":"mg_dl","to":"mmol_l"}'const res = await fetch("https://api.kit.forhosting.com/conv/blood-glucose", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 100,
"from": "mg_dl",
"to": "mmol_l"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/blood-glucose",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 100,
"from": "mg_dl",
"to": "mmol_l"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/blood-glucose", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":100,"from":"mg_dl","to":"mmol_l"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":100,"from":"mg_dl","to":"mmol_l"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/blood-glucose", 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": 100,
"from": "mg_dl",
"to": "mmol_l"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.blood_glucose",
"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_value | 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
Everyday aliases such as mg/dL, mg/dl, mmol/L, mmol/l, and mmol are accepted so lab printouts, meter exports, and spreadsheet cells can share one contract.
What the blood glucose converter returns and which units it understands
A blood glucose unit conversion answers a narrow question: given a concentration in one common reporting unit, what is the equivalent magnitude in the other unit that clinics, meters, and journals actually use. This calculator accepts a numeric value, a source unit, and a target unit, then returns the converted result rounded to a stable precision, the canonical from and to identifiers, human-readable labels, the intermediate value in milligrams per deciliter, and the fixed factor 18.0182 used for the bridge. Everyday spellings such as mg/dL, mg/dl, mgdl, milligrams per deciliter, mmol/L, mmol/l, mmol, and millimoles per liter normalize to those ids so forms, query strings, and spreadsheets can reuse the same contract without inventing private enums. Canonical ids are mg_dl for milligrams per deciliter and mmol_l for millimoles per liter. There is no approximate molecular-weight table path and no lab-specific correction factor: the engine either multiplies and divides by 18.0182 inside the supported magnitude range or rejects the input with invalid_input. Rejected cases include missing value, from, or to; non-finite numbers; magnitudes above the documented ceiling; negative concentrations; and any unit string that is not on the supported list.
How the 18.0182 factor is applied and how results stay reproducible
Optional scientific notation on the value string is allowed when it parses as a finite decimal; embedded spaces, hex prefixes, and non-numeric tokens are rejected with a clear message so a bad cell does not become a wrong lab number. Zero is a valid value and simply yields zero in the target unit. Computation multiplies value by the source factor in milligrams per deciliter, then divides by the target factor: one millimole per liter is exactly 18.0182 milligrams per deciliter, so one hundred milligrams per deciliter becomes one hundred divided by 18.0182 millimoles per liter, and five millimoles per liter becomes five times 18.0182 milligrams per deciliter. The preferred fields are value for the glucose magnitude, from for the source unit, and to for the target unit, with aliases amount, glucose, n, quantity, and level for the value, unit, from_unit, source, and input_unit for from, and target, to_unit, output_unit, and into for to so heterogeneous clients can share one contract. Negative values fail with invalid_input because a physical concentration cannot be negative. An optional precision field, with aliases decimals and dp, chooses how many decimal places to expose for value, result, and value_mg_dl, defaulting to ten and capped at fifteen so JSON goldens stay stable. Pair the free browser run on this page with the priced API when you need the identical mathematical result inside an automated pipeline without re-implementing unit tables yourself.
Where blood glucose unit conversion fits in labs, travel, and software
On this page the work runs entirely in your browser; through the API each successful lookup costs $0.002, failed validation is not charged, and nothing is stored after the response returns. That split — free interactive exploration and a priced, identical API — matches the rest of the KIT tier-A catalog and lets you move from a classroom demo to an automated pipeline without changing the mathematical result.
Integration use cases
Homework and CI fixtures
Generate reproducible blood glucose conversions for worksheets, tutoring software, and unit tests that assert the fixed 18.0182 factor.
Technical questions
Which blood glucose units are supported?
Milligrams per deciliter (mg_dl, aliases mg/dL, mg/dl, mgdl) and millimoles per liter (mmol_l, aliases mmol/L, mmol/l, mmol).
What conversion factor is used?
The fixed clinical factor 18.0182: 1 mmol/L = 18.0182 mg/dL. mg/dL ÷ 18.0182 = mmol/L; mmol/L × 18.0182 = mg/dL.