Mithqal mass converter
Convert mithqal to grams with a documented constant: one classic mithqal is 4.25 g, which is 4250 mg or about 0.1366 troy ounces, and an Ottoman option uses 4.8 g instead. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Mithqal
- 1
- Decimal places
- 4
- Variant
- classic_4_25g
- G
- 4.25
- Mg
- 4,250
- Troy oz
- 0.1366
Convert Islamic mithqal precious-metal mass with documented constant variants. Search intent: mithqal to grams. No network calls, no random seeds, and no server state are required for a correct answer. Failed jobs are not billed. Landings target the
What a mithqal is and which value to use
The mithqal is a traditional Islamic unit of mass for gold and other precious metals. Its value has not always been the same, so an honest conversion has to state which constant it uses. This converter offers two documented variants: the classic mithqal, also called modern, at 4.25 grams, and an Ottoman option at 4.8 grams. Pick the one that matches the source of your figure and the result appears in grams, milligrams and troy ounces, the ounce used for precious metals, all at once.
How the conversion works and the usual mistakes
The calculation is a single multiplication: the number of mithqals times the grams in one mithqal of the chosen variant. One classic mithqal is therefore 4.25 grams, or 4250 milligrams, and about 0.1366 troy ounces. The most common mistake is mixing variants, because a weight recorded with the Ottoman value of 4.8 grams will not match a figure worked out with 4.25 grams. Another is rounding too early. Here rounding happens only once, half up, at the very end and to the number of decimals you ask for. The same entry always gives the same answer.
How it works
Convert Islamic mithqal precious-metal mass with documented constant variants. classic/modern 4.25 g per mithqal; ottoman 4.8 g option. No network calls, no random seeds, and no server state are required for a correct answer. Failed jobs are not billed.
Landings target the stated search intent with precise keywords. Prefer explicit units and ranges over silent coercion of bad types. When a field is optional, defaults are documented in params and echoed in the output.
When to use it
Use when the search intent matches this tool. Convert Islamic mithqal precious-metal mass with documented constant variants. No network calls, no random seeds, and no server state are required for a correct answer.
Failed jobs are not billed. Landings target the stated search intent with precise keywords. Prefer explicit units and ranges over silent coercion of bad types.
When a field is optional, defaults are documented in params and echoed in the output.
FAQ
Locales?
EN-only delivery; Nitro hydrates the other seven languages.
How many grams are in one mithqal?
With the classic value, one mithqal is 4.25 grams, which is 4250 milligrams or about 0.1366 troy ounces. If you pick the Ottoman option, each mithqal counts as 4.8 grams instead.
Why are there different mithqal values?
Because the mithqal has not always been defined the same way. The converter documents its constants, the classic or modern value of 4.25 grams and an Ottoman option of 4.8 grams, so you can match the convention behind your figure.
Can I convert mithqal to troy ounces?
Yes. Every result shows grams, milligrams and troy ounces together. With the classic value, one mithqal comes to about 0.1366 troy ounces when rounded to four decimals.
How is the result rounded?
You choose how many decimals you want. Rounding is applied once, half up, to the unrounded result, so no rounding errors pile up along the way.
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/mithqal-mass \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"g":4.25}'const res = await fetch("https://api.kit.forhosting.com/conv/mithqal-mass", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"g": 4.25
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/mithqal-mass",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"g": 4.25
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/mithqal-mass", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"g":4.25}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"g":4.25}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/mithqal-mass", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"g": 4.25
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.mithqal_mass",
"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 calculator is free in the browser, deterministic, and identical in the API path. Inputs are validated before any arithmetic so invalid payloads fail with invalid_input. Half-up rounding is applied once from raw IEEE results when decimals are requested. Use the same JSON contract from spreadsheets, CMS hooks, automation, or teaching demos.
How it works
The calculator is free in the browser, deterministic, and identical in the API path. Inputs are validated before any arithmetic so invalid payloads fail with invalid_input. Half-up rounding is applied once from raw IEEE results when decimals are requested. Use the same JSON contract from spreadsheets, CMS hooks, automation, or teaching demos.
Inputs, limits and rounding
Outputs echo inputs for logging. No network calls, no random seeds, and no server state are required for a correct answer. Failed jobs are not billed. Landings target the stated search intent with precise keywords. Prefer explicit units and ranges over silent coercion of bad types. When a field is optional, defaults are documented in params and echoed in the output. Provide required JSON fields. Optional decimals use half-up once from raw IEEE values. Invalid types or ranges raise invalid_input. The calculator is free in the browser, deterministic, and identical in the API path. Inputs are validated before any arithmetic so invalid payloads fail with invalid_input. Half-up rounding is applied once from raw IEEE results when decimals are requested. Use the same JSON contract from spreadsheets, CMS hooks, automation, or teaching demos.
When to use it
The calculator is free in the browser, deterministic, and identical in the API path. Inputs are validated before any arithmetic so invalid payloads fail with invalid_input. Half-up rounding is applied once from raw IEEE results when decimals are requested. Use the same JSON contract from spreadsheets, CMS hooks, automation, or teaching demos.
Integration use cases
Quick check
Use the free widget to verify a formula before production.
Automation
Call the API with the same JSON contract from scripts or CMS.
Teaching
Show pinned golden examples without proprietary software.
Technical questions
Is the browser widget free?
Yes. Tier A is free client-side with the same core as the API.
Does it use the network?
No. Computation is local and deterministic.
What on bad input?
invalid_input is thrown; failed jobs are not billed.
API compatible?
Yes — same JSON fields as params.json.