Salt teaspoons to grams converter
One level teaspoon of salt counts as 6 grams, so 1.5 teaspoons come to 9 grams. Type the teaspoons from your recipe and get the weight with the factor shown, ready to scale or note down. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Teaspoons
- 1.5
- Grams
- 9 g
- Grams per teaspoon
- 6
- Ingredient
- salt
This salt teaspoons to grams converter turns a volume measurement into a mass measurement by using one clear, fixed assumption: one level teaspoon of salt equals 6 grams. Enter any finite, non-negative number of teaspoons and receive the corresponding gram weight, the conversion factor, and the formula used. The calculator is designed for recipes, meal planning, kitchen scaling, and repeatable software workflows where a stable answer matters more than estimating differences among salt crystal sizes, brands, or packing methods.
Convert a salt measurement in one step
Enter the number of level teaspoons shown in your recipe, then run the converter. The result multiplies that quantity by the fixed factor of 6 grams per teaspoon. For example, two teaspoons become twelve grams, while half a teaspoon becomes three grams.
Zero is accepted and returns zero grams. The response also includes the original teaspoon value, the factor, the ingredient name, the output unit, and a readable formula, making the calculation easy to audit when it is used inside an application or saved with recipe notes. Input must be an actual finite number and cannot be negative.
Text such as "two", numeric strings, blank values, infinity, and not-a-number values are rejected instead of being guessed or silently converted. That strict behavior prevents ambiguous data from entering automated cooking, nutrition, or purchasing workflows and ensures the same valid input always produces exactly the same structured result.
Understand the fixed 6-gram assumption
Salt is not a perfectly uniform ingredient by volume. Fine table salt, coarse kosher salt, flakes, and crystals can place different masses into the same spoon because their grain sizes and empty spaces differ. This calculator deliberately does not identify a salt style or estimate packing density.
It applies a published product assumption of 6 grams for every level teaspoon, every time. That makes it useful when a recipe or internal standard already relies on this factor and when consistency is the main requirement. Treat the answer as a conversion based on that convention, not as a laboratory measurement of an unknown salt.
If exact dietary sodium, commercial formulation, fermentation percentage, or regulatory labeling depends on the mass, weigh the salt with a calibrated kitchen scale and consult the product label. For ordinary recipe conversion, keeping the factor visible helps cooks compare the calculated amount with their own ingredient and decide whether the convention suits the task.
Scale recipes and automate repeatable calculations
A gram measurement is often easier to scale than a spoon measurement, especially when a recipe is multiplied, divided, or prepared repeatedly. Convert the original teaspoons first, then apply your serving or batch multiplier to the gram result, or submit the already-scaled teaspoon quantity directly. Because the function uses only fixed arithmetic, it has no network dependency, random choice, changing lookup table, or time-sensitive behavior.
Keep the returned factor and formula with stored results so future users know which convention produced them.
What you can do with it
Scale a home recipe
Turn fractional or multiple level teaspoons into grams before increasing or reducing a batch.
Standardize prep instructions
Give kitchen staff a repeatable gram target based on one documented conversion convention.
Add conversion to recipe software
Use a deterministic structured response in calculators, recipe databases, or automated tests.
FAQ
How many grams are in one teaspoon of salt?
This converter uses the fixed convention that one level teaspoon of salt equals 6 grams.
Does the result change for kosher or flaky salt?
No. It always uses 6 grams per teaspoon, although real salt styles can have different masses by volume. Weigh specialty salt when exact mass matters.
Can I enter a fractional teaspoon?
Yes. Any finite non-negative numeric value is accepted, including decimals such as 0.25 or 1.5.
Why convert salt to grams before scaling a recipe?
Grams are easier to multiply or divide than spoons. Convert the original teaspoons first, then apply your batch or serving multiplier to the gram result, and the salt stays in proportion.
When should I weigh the salt instead of converting it?
When exact sodium, a fermentation percentage or a nutrition label depends on the amount. In those cases weigh it on a calibrated kitchen scale and check the product label, because salts differ by volume.
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/salt-tsp-to-grams \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"teaspoons":1.5}'const res = await fetch("https://api.kit.forhosting.com/cook/salt-tsp-to-grams", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"teaspoons": 1.5
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/cook/salt-tsp-to-grams",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"teaspoons": 1.5
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/cook/salt-tsp-to-grams", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"teaspoons":1.5}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"teaspoons":1.5}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/cook/salt-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.5
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "cook.salt_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.
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
Scale recipes and automate repeatable calculations
A given number therefore returns the same result in the browser and through the API. The API price is $0.002 per request, while the page can run the same core calculation locally. When exchanging data between systems, send teaspoons as a JSON number rather than formatted text, and handle invalid_input responses for missing, non-numeric, infinite, or negative quantities.
Technical questions
What inputs return an error?
Missing values, strings, non-numeric values, infinity, NaN, and negative numbers return an invalid_input error.
What does the API conversion cost?
Each API request costs $0.002. The browser version can run the same deterministic calculation locally.