Sugar cups to grams converter
One cup of granulated sugar is 200 grams, packed brown sugar 220 and powdered sugar 120. Pick the sugar, enter cups or grams, and get the other measure for your cookies, blondies or glaze, the same every time. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Amount
- 1
- Sugar type: granulated
- granulated
- Grams per cup
- 200 cups
- Cups
- 1
- Grams
- 200
- Cup standard
- US cup (240 mL culinary)
Home bakers, recipe developers, and meal-prep writers constantly need a reliable sugar cups to grams converter when a favorite cookie or cake formula lists volume while the kitchen scale only reads weight. Granulated white sugar, packed brown sugar, and powdered confectioners sugar do not weigh the same per cup, so a single generic cups-to-grams factor produces dry or gummy dough. Unknown sugar names fail with a clear validation error instead of inventing a density. Use it free in the browser for quick kitchen checks, or call the same contract from scripts when you scale batches and publish bilingual recipe cards that must stay numerically consistent.
Why sugar type changes cups-to-grams math
A US measuring cup holds a fixed culinary volume of about two hundred forty milliliters, but how much sugar fits that cup depends on crystal size, moisture, and how tightly the cook packs the spoon. Granulated white sugar is the usual baseline at about two hundred grams per cup in common baking charts. Packed brown sugar is denser because molasses clings to the crystals and recipes expect a firm pack, so many kitchen tables use about two hundred twenty grams per cup.
Powdered sugar, also called confectioners or icing sugar, is aerated and often contains a little starch, so the same cup is much lighter—about one hundred twenty grams. If you convert one cup of brown sugar with the granulated factor, you under-sugar the batter; if you treat powdered sugar like white sugar, frostings turn pasty. This converter locks those three densities so the same amount and type always produce the same grams and cups, with no weather, brand, or random seed in the path.
The formula is simple: grams equal cups times grams per cup for that type, and cups equal grams divided by the same factor when you start from weight. Fractions such as one half or one and one half cups are valid; zero is allowed and returns zero. Negative amounts and non-finite numbers are rejected.
The unit field defaults to cups because most search queries start from a volume measure, but setting unit to grams flips the direction without changing the density table. That bidirectionality helps when a European recipe lists grams and you only own cup measures, or when a US recipe lists cups and you want a scale-friendly target.
Where a sugar cups-to-grams converter shows up in real work
Home bakers translating viral US cup recipes for a kitchen scale need grams for granulated sugar in cookies, brown sugar in blondies, and powdered sugar in glazes without opening three different charts. Recipe site editors who publish metric and imperial side by side want one deterministic oracle so a cup figure and a gram figure never disagree after a CMS rewrite. Culinary schools grading mise-en-place worksheets can check student conversions against a fixed table instead of debating brand-specific scoop weight.
Food bloggers scaling a batch from twelve cookies to a hundred need linear density math that does not drift between draft and publish. Meal-kit and bakery production software stores inventory by weight but receives consumer-facing formulas in cups; converting sugar lines at ingest keeps pick lists accurate. If you later need a multi-ingredient cups-to-grams chart, oven temperature conversion, or ounces-to-grams for general cooking weight, treat those as separate search intents and landings rather than overloading this sugar-focused converter page.
Keep the type list intentionally small so the SEO page matches how people search—“sugar cups to grams,” “brown sugar grams per cup,” “powdered sugar cup to grams”—and so unknown types fail loudly instead of silently mapping to white sugar.
What you can do with it
Scale a cup-based cookie recipe to grams
Convert cups of granulated or brown sugar to grams so a kitchen scale can hit the same sweetness when you double or half a batch.
Publish metric and imperial recipe cards
Generate matching cup and gram lines for white, brown, and powdered sugar so bilingual posts never disagree on the sweetener amount.
Grade culinary conversion worksheets
Check student answers for sugar cups↔grams against a fixed density table instead of debating scoop packing styles.
FAQ
Which sugar types are supported?
Granulated (white), brown (packed), and powdered (confectioners / icing).
How many grams are in one cup of each sugar?
Using this tool’s fixed table: granulated 200 g, brown 220 g, powdered 120 g per US cup (240 mL culinary). These are standard baking approximations, not laboratory densities.
Why not one density for all sugar?
Crystal size, moisture, and packing differ. Using white-sugar density for brown or powdered sugar systematically mis-measures sweetness and texture in baked goods.
What does it cost?
The browser tool is free and runs locally.
Can I convert grams of sugar back to cups?
Yes. Set the unit to grams and the converter divides by the same factor for that sugar. It helps when a European recipe lists grams and you only own cup measures.
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/sugar \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"amount":1,"type":"granulated"}'const res = await fetch("https://api.kit.forhosting.com/cook/sugar", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"amount": 1,
"type": "granulated"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/cook/sugar",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"amount": 1,
"type": "granulated"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/cook/sugar", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"amount":1,"type":"granulated"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"amount":1,"type":"granulated"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/cook/sugar", 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,
"type": "granulated"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "cook.sugar",
"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
This tool accepts an amount, a sugar type, and optionally the unit of that amount, then returns both cups and grams using a fixed density table that never drifts between browser demos and API pipelines.
What you send and what you get back
Case does not matter. Do not expect this page to convert flour, butter, honey, or cocoa—those multi-ingredient conversions belong on a general cups-to-grams landing so sugar search intent stays focused and unambiguous. Send amount as a finite non-negative number, type as a sugar name or alias, and optionally unit as cups or grams. Type accepts granulated, brown, and powdered, plus everyday aliases such as white sugar, light brown sugar, packed brown sugar, confectioners sugar, and icing sugar. Missing amount, missing type, unknown sugar names, and unknown units fail with invalid_input and are not charged. On success the response echoes the cleaned amount and unit, the canonical type key, the grams_per_cup density used, both cups and grams for that quantity, the cup standard string, a short formula string showing which direction was applied, and method fixed_density_table. That dual output means a single request answers both “how many grams is one and a half cups of powdered sugar” and “how many cups is three hundred grams of brown sugar” depending on unit. Pricing for successful API calls is the published base of $0.002 per item; validation failures do not consume prepaid balance.
Where a sugar 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
Can I convert grams back to cups?
Yes. Set unit to grams and amount to the weight; the response includes cups = grams ÷ grams_per_cup for that type, plus the grams echoed back.