Cooking ounces to grams converter
One weight ounce is exactly 28.349523125 g, so 8 oz of chocolate is 226.796185 g: convert ounces to grams or back for recipes, prep sheets and dual-unit cards. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Weight magnitude to convert
- 8
- Conversion direction: oz_to_g
- Oz to g
- Result
- 226.796185
- From unit
- oz
- To unit
- g
- Factor g per oz
- 28.349523125
Kitchen scales and printed recipes rarely agree on the same unit. American cookbooks write dry and solid weights in ounces while metric bakers, food labels, and digital scales prefer grams. This cooking ounces to grams converter multiplies or divides your amount by the exact international avoirdupois factor—one ounce equals twenty-eight point three four nine five two three one two five grams—so batch sheets, meal-prep plans, and dual-unit recipe cards stay consistent. Choose a direction (ounces to grams or grams to ounces), enter any finite amount including fractions, and receive the converted weight plus the factor and formula used. Non-numeric amounts and unknown directions fail with a clear validation error instead of inventing a rounded guess.
How ounces convert to grams in the kitchen
An avoirdupois ounce is a fixed mass, not a fluid volume. The international pound is defined as exactly zero point four five three five nine two three seven kilograms, and sixteen ounces make one pound, so one ounce is exactly twenty-eight point three four nine five two three one two five grams. That constant is the same factor professional kitchen charts, nutrition databases, and shipping labels use for dry goods and solid weights.
Converting ounces to grams is therefore a single multiplication: grams equal ounces times the factor. Converting grams to ounces is the inverse division. This capability stores the exact factor once and applies it deterministically—no web scrapes, no language-model estimates, no humidity adjustments that change between calls.
Fluid ounces are a different unit of volume and are intentionally out of scope; if you need cups of flour to grams by density, use a cups-to-grams tool instead. When product pages round to twenty-eight point three five grams they introduce small drift on large bakery batches; keeping the full SI-derived constant keeps multi-kilogram prep sheets honest. Amounts and directions are validated first; non-numeric amounts and unknown directions fail with invalid input and are not charged.
Where a cooking ounces to grams converter shows up in real work
Home bakers translating American recipes onto metric kitchen scales avoid the classic half-cup-versus-four-ounce confusion when every solid weight has a published gram equivalent. Food bloggers and cookbook editors publish dual-unit recipes and need one oracle so ounce lines and gram lines never drift between drafts. Meal-prep services and grocery apps convert user-entered ounce quantities into purchase grams for shopping lists and cost estimates.
Culinary schools teach unit literacy—why fluid ounces are not the same as weight ounces—and a deterministic factor makes demos and quizzes reproducible. Small bakeries batch morning mise en place from ounce-written formulas into scale-ready grams without opening a spreadsheet of ad-hoc rounded constants. Nutrition and diet tools that already store foods by mass can accept ounce inputs from consumers and convert before summing macros.
If you later need multi-unit mass conversion across kilograms and pounds, cups-to-grams by ingredient density, or fluid-volume conversion with a different search intent, treat those as separate landings rather than overloading this kitchen ounces-to-grams converter page.
What you can do with it
Scale a home baking recipe
Turn 8 oz of chocolate or butter into grams so a metric digital scale matches the written ounce recipe without guesswork.
Dual-unit recipe publishing
Editors and bloggers generate consistent gram lines beside ounce lines from one exact avoirdupois factor for every solid weight.
Meal prep and shopping lists
Convert ounce-based prep sheets into purchase grams for proteins, chocolate, and dry goods before you hit the store.
FAQ
How does the cooking ounces to grams converter work?
It multiplies ounces by 28.349523125 to get grams, or divides grams by the same factor to get ounces. The factor is the exact international avoirdupois definition.
Is this fluid ounces or weight ounces?
Weight (avoirdupois) ounces only. Fluid ounces measure volume and are out of scope for this converter.
Can I convert fractions of an ounce?
Yes. Send any finite number such as 0.25, 0.5, 1.5, or 12.75. Both directions accept fractional amounts.
What does it cost?
The browser tool is free and runs locally.
Why keep every decimal of the ounce factor?
Because a rounded factor adds a small error to every line, and on large bakery batches that drift adds up. The exact 28.349523125 g keeps multi-kilogram prep sheets in line with the recipe.
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/cook/oz-grams \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"amount":8,"direction":"oz_to_g"}'const res = await fetch("https://api.kit.forhosting.com/cook/oz-grams", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"amount": 8,
"direction": "oz_to_g"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/cook/oz-grams",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"amount": 8,
"direction": "oz_to_g"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/cook/oz-grams", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"amount":8,"direction":"oz_to_g"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"amount":8,"direction":"oz_to_g"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/cook/oz-grams", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"amount": 8,
"direction": "oz_to_g"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "cook.oz_grams",
"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
What you send and what you get back
Classic kitchen checks include eight ounces of chocolate becoming two hundred twenty-six point seven nine six one eight five grams, one hundred grams of spice becoming about three point five two seven three nine six one nine five ounces, and one ounce mapping exactly to twenty-eight point three four nine five two three one two five grams. Use the free browser form while scaling a single recipe on the counter, then call the same contract from scripts when you generate dual-unit cards or import supplier packs marked only in ounces. Wire the returned result into meal-planning tools, label printers, and nutrition estimators that already work in mass. Send two fields. amount is a finite number of weight units—eight, one half, twelve point five, or any other finite value including negatives if you are modeling a delta. direction is either oz_to_g for ounces to grams or g_to_oz for grams to ounces; matching is case-insensitive and accepts everyday aliases such as ounces_to_grams, grams-to-oz, and oz-to-g. Missing fields, non-numeric strings, empty strings, NaN, Infinity, and directions outside the accepted set fail with invalid_input and are not charged. On success the response echoes the cleaned amount, the canonical direction, from_unit and to_unit as oz or g, result as the converted magnitude, factor_g_per_oz set to the exact constant, a printable formula string, and method avoirdupois_exact. Pricing for successful API calls is the published base of $0.002 per item; validation failures do not consume prepaid balance.
Where a cooking ounces to grams converter shows up in real work
Because this capability is a pure parse engine, API pricing is the published base of $0.002 per successful item and failed validation does not consume balance.
Technical questions
What happens if the amount is not a number?
The request fails with invalid_input. Missing, non-numeric, NaN, and Infinity amounts are rejected and the call is not charged.