Baking soda teaspoons to grams converter
One level US teaspoon of baking soda weighs 4.6 grams, and half a teaspoon 2.3. Enter teaspoons, fractions included, and weigh the soda for cookies, cakes or pretzels instead of trusting a heaped spoon. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Teaspoons
- 1
- Grams
- 4.6 g
- Grams per teaspoon
- 4.6
- Ingredient
- baking soda
- Teaspoon standard
- US customary teaspoon
This baking soda teaspoons to grams converter turns a teaspoon measure of sodium bicarbonate into grams with one fixed kitchen mass so cookies, cakes, pretzels, and quick breads stay chemically consistent. Volume marks on a measuring spoon are convenient at the bench, but leavening is a mass-sensitive reaction: too little baking soda leaves a dense crumb, and too much leaves a soapy aftertaste and a metallic bite. Enter a finite non-negative number of teaspoons and the engine multiplies by a documented four-point-six grams per teaspoon mass constant.
What the converter returns and which mass constant it uses
Baking soda is sodium bicarbonate, a dry alkaline powder, not a liquid, so a teaspoon of it does not weigh the same as a teaspoon of water, salt, baking powder, or cream of tartar. Kitchen charts that treat every white powder as interchangeable send bakers off by grams, which is enough to wreck a batch of cookies or leave a soapy aftertaste in a cake. This tool uses a single documented mass constant: four point six grams of baking soda in one leveled US customary teaspoon.
That figure is the conventional USDA kitchen row for a spooned-and-leveled teaspoon rather than a packed heap or a scant dip. There is no baking-powder path, no yeast path, no tablespoon-only shortcut, and no brand-specific aluminum-free table: those searches belong on their own landings. Zero teaspoons is a valid input and returns zero grams.
The mass is fixed on purpose so two clients that share this contract never disagree about how many grams sit in a teaspoon of baking soda.
How teaspoons are read so the gram result stays reproducible
The required field is teaspoons, a finite non-negative number of US customary teaspoons. Optional leading plus signs, a leading decimal point such as point two five, and scientific notation are parsed when they are well-formed finite decimals. Embedded spaces, hex prefixes, empty strings, objects, arrays, Infinity, and NaN are rejected so a bad cell does not become a silent wrong batch size.
Missing teaspoons fails by naming the field. Computation is a single multiply: grams equals teaspoons times four point six. Results are rounded to ten decimal places with half-away-from-zero rounding, and negative zero is collapsed to plain zero so goldens compare byte for byte.
Where baking-soda teaspoon conversion earns its keep
Home bakers meet this conversion when a US family recipe says one teaspoon of baking soda for cookies and the only scale in the kitchen shows grams, or when a European formula in grams must be followed with an American measuring spoon. Bakery production sheets convert teaspoon marks on a dry scoop into gram targets so sodium bicarbonate is dosed the same on every shift.
Culinary students use a fixed mass for worksheet keys instead of opaque calculator apps that silently round a teaspoon of baking soda to five grams one day and four the next. Product teams call the same contract from scripts to seed deterministic test vectors for recipe importers, to normalize user-entered baking-soda fields before scaling a batch, or to satisfy programming-challenge statements that demand a documented mass rather than a hand-waved spoon weight.
Do not confuse this page with baking powder, cream of tartar, or yeast converters: those ingredients have different chemistry and different grams per teaspoon.
What you can do with it
Scale a US teaspoon recipe onto a gram scale
Convert teaspoon and fraction-of-a-teaspoon baking soda lines in family recipes to grams so a digital scale can dose leavener without a measuring spoon.
Bakery and catering production sheets
Normalize baking-soda lines from teaspoon scoops to gram targets so large cookie, pretzel, and pancake batches stay consistent across staff.
FAQ
How many grams is one teaspoon of baking soda?
Under the fixed mass constant used here, one US customary teaspoon of baking soda is 4.6 grams.
What mass constant does this converter use?
It multiplies US teaspoons by 4.6 grams per teaspoon. That is a conventional leveled-teaspoon kitchen figure for baking soda (the USDA row), not a brand-specific lab assay and not the mass of baking powder or salt.
What happens if I enter a negative or non-numeric value?
Negative teaspoons, missing teaspoons, Infinity, NaN, and non-numeric tokens are rejected and are not billed.
Is baking soda the same as baking powder?
No. Baking soda is sodium bicarbonate alone; baking powder already contains an acid and a base and weighs a different number of grams per spoon. Use a dedicated baking-powder tool when that is the ingredient.
What does the baking soda teaspoons to grams converter cost?
It is free in your browser on this page.
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/baking-soda-tsp-to-grams \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"teaspoons":1}'const res = await fetch("https://api.kit.forhosting.com/cook/baking-soda-tsp-to-grams", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"teaspoons": 1
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/cook/baking-soda-tsp-to-grams",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"teaspoons": 1
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/cook/baking-soda-tsp-to-grams", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"teaspoons":1}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"teaspoons":1}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/cook/baking-soda-tsp-to-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
{
"teaspoons": 1
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "cook.baking_soda_tsp_to_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.
Limits
max_abs_teaspoons | 1000000000000 |
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
Fractions such as one half teaspoon or one and a half teaspoons are accepted; negative values and non-numeric tokens fail with invalid_input and are not billed.
What the converter returns and which mass constant it uses
You send teaspoons; the response echoes the cleaned teaspoon amount, the gram mass, the grams_per_teaspoon factor of four point six, an ingredient label of baking soda, the teaspoon_standard string US customary teaspoon, the unit g, a method tag fixed_baking_soda_mass, and the formula grams equals teaspoons times four point six.
How teaspoons are read so the gram result stays reproducible
Aliases tsp, amount, value, quantity, and qty map to the same field so spreadsheets, query strings, and typed forms can reuse the contract without renaming columns. A JSON number, a numeric string, or a bigint inside the safe integer range is accepted. Negative teaspoons fail with invalid_input and a message that baking soda volume cannot be negative, because a kitchen quantity cannot go below zero. Amounts above the documented ceiling of one trillion teaspoons are rejected so a typo cannot overflow the Worker. Pair the free browser run on this page with the priced API when a pipeline must convert baking soda teaspoons without re-implementing the mass.
Where baking-soda teaspoon conversion earns its keep
On this page the work runs entirely in your browser; through the API each successful lookup costs $0.002, failed validation is not charged, and nothing is stored after the response returns. That split — free interactive exploration and a priced, identical API — lets you move from a kitchen demo to an automated pipeline without changing the mathematical result.
Integration use cases
Deterministic recipe-importer fixtures
Generate reproducible baking-soda teaspoon-to-gram equivalents for unit tests, recipe importers, and CI assertions without re-coding the mass constant.