Cups to grams converter
Two cups of all-purpose flour weigh 240 g, because flour is listed at 120 g per cup. Choose the ingredient, enter the cups, even as a fraction, and get the grams along with the density used. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Cups
- 2
- Ingredient
- all-purpose flour
- Ingredient
- all purpose flour g
- Ingredient key
- all_purpose_flour
- Grams per cup
- 120
- Grams
- 240
Volume is not weight. One cup of flour and one cup of honey occupy the same measuring cup but land on very different gram readings because their densities differ. This cups to grams converter multiplies the number of US cups you enter by a fixed grams-per-cup value for a chosen common ingredient, so recipe scaling, meal prep, and bakery batch sheets stay consistent. Pick an ingredient such as all-purpose flour, granulated sugar, butter, milk, cocoa powder, or rice, enter cups as a whole number or fraction, and receive grams plus the density factor used. Unknown ingredient names are rejected with a clear validation error instead of inventing a density.
How cups convert to grams with a density table
A US cup is a fixed volume. Culinary charts treat that cup as about two hundred forty milliliters when they publish grams per cup for pantry staples. Mass in grams is volume times density, so the practical kitchen formula is simply grams equals cups times the grams-per-cup value for the ingredient you chose.
All-purpose flour is often listed near one hundred twenty grams per cup when scooped and leveled the way many American recipes assume; granulated sugar sits near two hundred grams per cup; packed brown sugar is denser; butter is near two hundred twenty-seven grams per cup; water and milk sit close to the true mass of the cup of liquid. This capability stores those fixed values in a deterministic table and multiplies.
When you need a different packing style or a metric cup standard, treat that as a separate workflow; here the contract is one stable table so the same cups and ingredient always return the same grams. Coefficients and strings are validated first; invalid cups or unknown ingredient names fail with invalid input and are not charged.
Where a cups to grams converter shows up in real work
Home bakers scaling family recipes from US cups into gram-based kitchen scales avoid the classic flour-dump error when every cup has a published gram equivalent. Food bloggers and cookbook editors publish dual-unit recipes and need one oracle so cup lines and gram lines never drift between drafts. Meal-prep services and grocery apps convert user-entered cup quantities into purchase weights for shopping lists and cost estimates.
Culinary schools teach density awareness—why honey and flour disagree—and a deterministic table makes demos and quizzes reproducible. Small bakeries batch morning mise en place from cup-written formulas into scale-ready grams without opening a spreadsheet of ad-hoc constants. Nutrition and diet tools that already store foods by mass can accept cup inputs from consumers and convert before summing macros.
If you later need pure mass unit conversion without ingredients, temperature conversion, or a reverse grams-to-cups path with a different search intent, treat those as separate landings rather than overloading this ingredient density converter page.
What you can do with it
Scale a home baking recipe
Turn 2 cups of flour or ¾ cup of sugar into grams so a digital scale matches the written cup recipe without guesswork.
Dual-unit recipe publishing
Editors and bloggers generate consistent gram lines beside US cup lines from one fixed density table for every staple.
Meal prep and shopping lists
Convert cup-based prep sheets into purchase weights for flour, rice, oil, and dairy before you hit the store.
FAQ
How does the cups to grams converter work?
It multiplies the number of US cups by a fixed grams-per-cup density for the ingredient you choose.
Which cup standard is used?
US cup under the culinary 240 mL convention used by most American baking charts. Water is stored near true mass at 236.6 g per cup.
Can I use fractions of a cup?
Yes. Send any finite non-negative number such as 0.25, 0.5, 1.5, or 2.75. Negative values are rejected.
What does it cost?
The browser tool is free and runs locally.
Why does a cup of honey weigh more than a cup of flour?
Because volume is not weight. Both fill the same measuring cup, but honey is much denser than flour, so the same cup gives a far higher gram reading. That is why every ingredient has its own grams-per-cup value.
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/cups-grams \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"cups":2,"ingredient":"all-purpose flour"}'const res = await fetch("https://api.kit.forhosting.com/cook/cups-grams", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"cups": 2,
"ingredient": "all-purpose flour"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/cook/cups-grams",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"cups": 2,
"ingredient": "all-purpose flour"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/cook/cups-grams", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"cups":2,"ingredient":"all-purpose flour"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"cups":2,"ingredient":"all-purpose flour"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/cook/cups-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
{
"cups": 2,
"ingredient": "all-purpose flour"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "cook.cups_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
How cups convert to grams with a density table
It does not scrape the web, call a model, or adjust for humidity, altitude, or how firmly you packed the cup—those variables matter in competition baking, but product converters that change every request destroy trust.
What you send and what you get back
Send two fields. cups is a finite non-negative number of US cups—two, one half, one and a half, or any other finite value zero or greater. ingredient is a string naming a common kitchen staple: all-purpose flour, bread flour, cake flour, whole wheat flour, granulated sugar, brown sugar, powdered sugar, butter, milk, water, heavy cream, yogurt, honey, maple syrup, vegetable oil, olive oil, cocoa powder, cornstarch, rolled oats, uncooked rice, salt, baking powder, baking soda, peanut butter, sour cream, cream cheese, shredded cheese, chopped nuts, or breadcrumbs. Use the free browser form while scaling a single recipe on the counter, then call the same contract from scripts when you generate grocery lists or batch bakery sheets. Wire the returned grams into meal-planning tools, nutrition estimators that already work in mass, or label printers that expect grams rather than cup fractions. Matching is case-insensitive and accepts many everyday aliases such as flour, sugar, oil, oats, or rice. Missing fields, non-numeric cups, negative cups, NaN, Infinity, and names outside the table fail with invalid_input and are not charged. On success the response echoes cleaned cups, a human-readable ingredient label, the canonical ingredient_key, grams_per_cup from the table, grams as the product, unit set to g, the cup standard string, the formula string, and method fixed_density_table. Pricing for successful API calls is the published base of $0.002 per item; validation failures do not consume prepaid balance.
Where a cups 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 ingredient is unknown?
The request fails with invalid_input and a message that lists known ingredient names. No density is invented and the call is not charged.