Corned beef cure calculator
1 kg of beef takes 50 g of salt, 25 g of sugar, 2.5 g of Prague Powder #1 and 1,000 ml of cover water at the standard rates. Enter the meat weight in grams, kilograms, pounds or ounces and every ingredient scales with it. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Meat weight
- 1,000
- Weight unit
- g
- Meat weight g
- 1,000
- Salt percent
- 5
- Sugar percent
- 2.5
Corned beef starts with a wet brine: pickling or kosher salt, sugar, and a measured dose of Prague Powder #1 (pink curing salt, cure #1) dissolved in enough water to cover the brisket or other cut. Home cooks and deli-style meal preppers often copy a single recipe written for one fixed weight and then guess when the next pack is heavier or lighter, which throws salt level, sweetness, and nitrite rate off the mark. This corned beef cure calculator accepts meat weight in grams, kilograms, pounds, or ounces, applies standard mass-percent rates for salt, sugar, and cure, and returns each ingredient in grams plus cover water in millilitres. Optional percent overrides let you match a house formula while keeping the same pure math.
What a corned-beef wet brine is scaling when weight changes
A traditional wet corn for beef is not a fixed cup of salt in a fixed pot of water independent of the meat; professional and serious home formulas treat salt, sugar, and curing salt as fractions of the meat mass so that larger and smaller pieces receive proportional dissolved solids.
The defaults used here follow common wet-brine practice: five percent salt by meat weight (fifty grams of pickling or kosher salt per kilogram of meat), two and a half percent sugar (twenty-five grams per kilogram), and zero point two five percent Prague Powder number one (two and a half grams per kilogram), which matches the widely taught zero point two five percent rate for nitrite cure number one on meat.
Cover water defaults to one thousand millilitres per kilogram of meat so the cut can sit fully submerged; you may still top up with plain water in the vessel if the geometry of the pan needs more liquid, because dissolved solids were already set from meat mass rather than from a fixed gallon recipe. When you change only the meat weight, every solid and the suggested water volume scale linearly.
What to enter and what you get back
Numeric strings are accepted for numeric fields. Example: one thousand grams of meat at defaults yields fifty grams salt, twenty-five grams sugar, two and a half grams cure number one, and one thousand millilitres of cover water. Use only Prague Powder number one (cure number one) for a short wet corn intended to be cooked; cure number two is for long dry-cured products and is outside this calculator.
Always measure curing salt by weight when possible and follow local food-safety guidance for refrigeration time and cooking temperature.
Where a corned beef cure calculator earns its keep
Home cooks planning St. Patrick’s Day or year-round deli-style leftovers need a quick scale when the butcher packs a three-pound flat one week and a six-pound point the next, without rewriting a gallon-and-cup recipe by hand. Meal-prep and small catering kitchens batch several briskets and want a deterministic gram sheet for salt, sugar, and pink salt that matches the free browser tool staff already trust.
Failed validation does not consume balance.
What you can do with it
Home brisket wet brine by weight
Enter brisket weight in pounds or grams to get salt, sugar, Prague Powder #1, and cover water for a classic corned-beef wet brine.
Deli and catering batch sheets
Scale the same house salt, sugar, and cure percents across mixed bag weights so every flat and point gets proportional dissolved solids.
FAQ
How do I calculate corned beef brine salt, sugar, and cure from meat weight?
Defaults use 5% salt, 2.5% sugar, and 0.25% Prague Powder #1 by meat mass, plus 1000 ml water per kg.
What happens if meat weight is zero or negative?
Non-positive meat weight cannot scale a brine and is not billed.
Can I use cure #2 instead of Prague Powder #1?
No. Use only Prague Powder #1 for a short wet corn that will be cooked. Cure #2 is meant for long dry-cured products and is outside this calculator. Weigh curing salt rather than measuring it by volume.
What if the brine does not cover the meat?
Top up the pot with plain water. The salt, sugar and cure were already set from the meat weight, not from a fixed volume of water, so the amounts in the result stay the same.
Can I use my own house brine percentages?
Yes. Enter your own salt, sugar or cure percentage of the meat weight and it replaces the default for that calculation only, so a milder or saltier house brine still scales correctly.
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/corned-beef-cure \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"meat_weight":1000}'const res = await fetch("https://api.kit.forhosting.com/cook/corned-beef-cure", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"meat_weight": 1000
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/cook/corned-beef-cure",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"meat_weight": 1000
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/cook/corned-beef-cure", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"meat_weight":1000}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"meat_weight":1000}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/cook/corned-beef-cure", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"meat_weight": 1000
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "cook.corned_beef_cure",
"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
Non-positive meat weight is rejected as invalid_input because a brine cannot be scaled from zero or negative mass.
What a corned-beef wet brine is scaling when weight changes
When you pass custom salt_percent, sugar_percent, or cure_percent, those rates replace the defaults for that call only, which is how a shop that runs a milder or saltier house brine keeps one calculator for every bag of brisket without rewriting code.
Input contract, response shape, and error behaviour
POST a JSON body with meat_weight as a required finite number strictly greater than zero. weight_unit is optional and defaults to grams; accepted values are g, kg, lb, and oz (case-insensitive synonyms such as pounds and ounces are normalised). salt_percent, sugar_percent, and cure_percent are optional non-negative percentages of meat mass and default to five, two and a half, and zero point two five respectively. water_ml_per_kg is optional, non-negative, and defaults to one thousand. Missing meat_weight, non-finite values, unknown units, negative percents, and non-positive meat weight fail with invalid_input naming the problem; those failures are not billed. On success the body echoes meat_weight and weight_unit, reports meat_weight_g after conversion, echoes the effective salt_percent, sugar_percent, cure_percent, and water_ml_per_kg, and returns salt_g, sugar_g, cure_g, and water_ml rounded to twelve decimal places for stable goldens across runtimes, plus a formula string restating the mass-percent identities.
Where a corned beef cure calculator earns its keep
Teaching kitchens and culinary courses use the API to show why cure number one is a mass fraction of the meat rather than a random teaspoon count that drifts when the cut size changes. Keep one mass unit per request, pin salt_g sugar_g and cure_g in tests, and you get reproducible brine solids for notebooks, deli software, and edge workers without standing up a full production ERP of your own.
Integration use cases
Recipe and CMS widgets
Power a live corned beef cure calculator on a food site with the free browser path matching the API for published gram lines.
Technical questions
Which curing salt does cure_g refer to?
Prague Powder #1 (pink curing salt / cure #1) at the default 0.25% of meat mass. Do not substitute cure #2 for a short wet corn; that product is for long dry-cured meats.
Can I change the salt, sugar, or cure percentages?
Yes. Pass salt_percent, sugar_percent, and cure_percent as non-negative numbers to override the defaults for that call while still scaling from meat weight.
What does the corned beef cure calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.