US to metric cooking converter
One US cup is 236.59 ml and 8 ounces of weight are 226.80 g. Convert any line of an American recipe to milliliters, liters, grams or kilograms with one fixed kitchen table, so dual-unit recipe cards never drift. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Amount
- 1
- Source unit token
- cup
- Target unit token
- ml
- Result
- 236.5882365
- Dimension
- volume
- Factor
- 236.5882365
- Base unit
- ml
American recipes list cups, tablespoons, teaspoons, fluid ounces, and avoirdupois ounces while metric bakers, food labels, and digital scales expect milliliters, liters, grams, and kilograms. This US to metric cooking converter applies one fixed kitchen factor table so dual-unit cards, meal-prep sheets, and shopping lists stay consistent. Enter an amount plus a from unit and a to unit—one cup to milliliters, two tablespoons to milliliters, eight ounces to grams, or half a pound to kilograms—and receive the converted result, the dimensionless factor used, and the dimension (volume or mass). Unknown units and mixed-dimension pairs fail with a clear validation error instead of inventing a density guess.
How the fixed US–metric kitchen table works
Volume conversions route through a milliliter base using the US legal fluid-ounce chain (one US gallon equals three point seven eight five four one one seven eight four liters exactly under NIST definitions, so cups and spoons are exact subdivisions). Mass conversions route through a gram base using the international avoirdupois definitions (one pound equals zero point four five three five nine two three seven kilograms exactly, sixteen ounces to the pound).
Converting is a single multiplication of your amount by the ratio of the two table entries—no web scrapes, no language-model estimates, and no humidity or altitude adjustments that change between calls. Fluid volume units never silently become weight units: a cup is not a number of grams without an ingredient density, so cup-to-gram requests fail with invalid input rather than pretending flour equals water. Temperature is intentionally out of scope; oven gas marks and Fahrenheit–Celsius belong on a dedicated temperature tool.
Amounts and unit tokens are validated first; unknown units and non-numeric amounts fail with invalid input and are not charged.
Where a US to metric cooking converter shows up in real work
Home cooks translating American cookbooks onto metric kitchen scales avoid the classic cup-versus-milliliter confusion when every liquid line has a published milliliter equivalent and every solid weight has a gram line. Food bloggers and cookbook editors publish dual-unit recipes and need one oracle so US customary lines and metric lines never drift between drafts or localization passes. Meal-prep services and grocery apps convert user-entered cups and ounces into purchase milliliters and grams for shopping lists and cost estimates.
Culinary schools teach unit literacy—why fluid ounces are not the same as weight ounces—and a fixed table makes demos and quizzes reproducible. Small bakeries and cafés batch morning mise en place from cup-written formulas into scale-ready milliliters and grams without opening a spreadsheet of ad-hoc rounded constants. Recipe importers and CMS pipelines normalize legacy US-only content before storing metric fields for international audiences.
If you later need cups of a named ingredient converted by density, oven temperature marks, or a broad engineering unit picker across SI and imperial systems, treat those as separate landings rather than overloading this US-to-metric cooking converter page.
What you can do with it
Scale a liquid recipe line
Turn 1 cup or 2 tbsp of stock, milk, or oil into milliliters so a metric jug matches the written US customary recipe without guesswork.
Dual-unit recipe publishing
Editors and bloggers generate consistent metric lines beside cups, fluid ounces, and avoirdupois ounces from one fixed kitchen factor table.
Meal prep and shopping lists
Convert cup- and ounce-based prep sheets into purchase milliliters and grams before you hit a metric grocery aisle.
FAQ
How does the US to metric cooking converter work?
It multiplies your amount by a fixed table factor: volume units convert through milliliters, mass units through grams. One cup becomes about 236.59 ml; eight ounces become about 226.80 g.
Can I convert cups to grams?
No. Cups measure volume and grams measure mass. Cross-dimension pairs are rejected. Use an ingredient-density tool such as a cups-to-grams converter for flour or sugar by type.
What does it cost?
The browser tool is free and runs locally.
Is a fluid ounce the same as an ounce on the kitchen scale?
No. A fluid ounce measures volume and an ounce on the scale measures weight, so the converter keeps them apart. Eight ounces of weight are 226.80 grams, while fluid ounces convert to milliliters.
Can it convert oven temperatures from Fahrenheit to Celsius?
No. Temperature is deliberately left out, along with oven gas marks. This converter handles volume and weight only, so use a dedicated temperature tool for the oven setting.
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/us-metric \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"amount":1,"from":"cup","to":"ml"}'const res = await fetch("https://api.kit.forhosting.com/cook/us-metric", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"amount": 1,
"from": "cup",
"to": "ml"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/cook/us-metric",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"amount": 1,
"from": "cup",
"to": "ml"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/cook/us-metric", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"amount":1,"from":"cup","to":"ml"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"amount":1,"from":"cup","to":"ml"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/cook/us-metric", 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": 1,
"from": "cup",
"to": "ml"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "cook.us_metric",
"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
How the fixed US–metric kitchen table works
Kitchen conversion is only reliable when every call uses the same published factors. This capability stores a fixed table for common cooking measures: US teaspoons, tablespoons, fluid ounces, cups, pints, quarts, and gallons on the volume side, with milliliters and liters as metric partners; avoirdupois ounces and pounds on the mass side, with grams and kilograms as metric partners.
What you send and what you get back
Classic kitchen checks include one US cup becoming two hundred thirty-six point five eight eight two three six five milliliters, one tablespoon becoming fourteen point seven eight six seven six four seven eight one two five milliliters, eight avoirdupois ounces becoming two hundred twenty-six point seven nine six one eight five grams, and one liter becoming about four point two two six seven five two eight three seven cups. Use the free browser form while scaling a single recipe on the counter, then call the same contract from scripts when you generate bilingual recipe cards or import supplier packs marked only in customary units. Wire the returned result into meal-planning tools, label printers, and shopping-list builders that already work in metric mass or volume. Send three fields. amount is a finite number of kitchen units—one, one half, two point five, or any other finite value including negatives if you are modeling a delta. from is the source unit token such as cup, tbsp, tsp, fl_oz, pint, quart, gallon, ml, l, oz, lb, g, or kg; matching is case-insensitive and accepts everyday aliases like teaspoon, tablespoon, fluid_ounce, liter, ounce, and pound. to is the target unit and must share the same dimension as from: both volume or both mass. Missing fields, non-numeric strings, empty strings, NaN, Infinity, unknown unit spellings, and cross-dimension pairs such as cup to gram fail with invalid_input and are not charged. On success the response echoes the cleaned amount, canonical from and to labels, result as the converted magnitude, dimension as volume or mass, factor as the multiplier applied, base_unit as ml or g, a printable formula string, and method fixed_table. Pricing for successful API calls is the published base of $0.002 per item; validation failures do not consume prepaid balance.
Where a US to metric cooking 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 I enter an unknown unit?
The request fails with invalid_input. Only the documented kitchen tokens (tsp, tbsp, fl_oz, cup, pint, quart, gallon, ml, l, oz, lb, g, kg and common aliases) are accepted.
Are these fluid ounces or weight ounces?
Both are supported as separate units: fl_oz is volume (with ml and cups); oz is avoirdupois weight (with grams and pounds). They never share a conversion path.