Pizza dough ratio calculator
Plan dough by the ball: 4 balls of 250 g make 1000 g of dough, split by baker's percentages into flour, water, salt and yeast, with 62% hydration and 2.5% salt as defaults. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Balls
- 4
- Ball weight
- 250
- Hydration
- 62
- Salt pct
- 2.5
- Yeast pct
- 0.2
- Total dough
- 1,000
Pizza dough formulas are almost always written in baker's percentages, but home cooks and small pizzerias usually plan service by how many dough balls they need and how heavy each ball should be. A pizza dough ratio calculator turns that service plan into scale weights: total dough equals balls times ball weight, flour is recovered as the one-hundred-percent baseline from the baker sum, and water, salt, and yeast follow as flour times each percentage. Defaults match a lean Neapolitan-style mix—sixty-two percent hydration, two and a half percent salt, two-tenths percent instant dry yeast—while every percentage stays editable for Roman, New York, or long cold-ferment styles.
How ball count and baker's percentages become flour, water, salt, and yeast
Professional pizza dough is planned in two layers that must stay consistent. The first layer is service: how many dough balls you need and the target weight of each ball after bulk fermentation and division. Four balls at two hundred fifty grams means one thousand grams of finished dough on the bench.
The second layer is the formula card written in baker's percentages, where flour always equals one hundred percent and every other ingredient is a percent of that flour mass. Hydration is simply the water percentage; salt is usually two to three percent; yeast depends on temperature, preferment, and ferment length and is often a fraction of a percent for overnight cold proofing.
Combining the layers is pure algebra: total dough mass is balls times ball weight; the baker total is one hundred plus hydration plus salt percent plus yeast percent; flour equals total dough times one hundred divided by that baker total; water, salt, and yeast each equal flour times their percentage divided by one hundred. Because salt and yeast are small, flour is a bit under total dough and water is a large share of the remainder.
Changing ball count or ball weight scales the batch linearly while percentages stay fixed, so the same formula card works for a weeknight test pie and a Friday rush.
When planning by dough balls pays off
Home pizza makers who buy flour by the bag and plan for a fixed number of dinner pies need flour and water weights that match the ball size their peel and oven can handle, without reverse-engineering a percentage card by hand. Culinary classes teach baker's math by showing that raising hydration from sixty-two to seventy percent changes water and flour for the same total dough mass; a deterministic oracle lets students check homework in seconds.
Recipe apps and commissary backends store style presets as percentage maps and call a tiny convert when rendering a scale ticket or shopping list. Prefer this capability when you already know ball count, ball weight, and the three baker percentages; it is not a cups-to-grams density tool, not a single-ingredient baker percent reverse (see the baker's percentage to weight calculator for that), and not a fermentation timer.
What you can do with it
Weeknight pizza ball plan
Pick how many pies and a ball weight for your pan or peel, then weigh flour, water, salt, and yeast from default or custom baker percentages.
Prep sheets from order forecasts
Convert tomorrow's dough-ball count into a mix ticket so production flour and salt match service portion weights.
Teach baker's percentage with live checks
Show students how hydration and salt percent change absolute weights when total dough is fixed by balls times ball weight.
FAQ
What are the default pizza dough ratios?
Hydration 62% water, salt 2.5%, and yeast 0.2% of flour (instant dry yeast style). Override any percentage for New York, Roman, or long cold-ferment formulas.
What units does the calculator use?
Any consistent mass unit, typically grams. Ball weight and all returned ingredient weights share the same unit; only ratios are unitless baker percentages.
How much flour goes into 4 dough balls of 250 g?
About six hundred and seven grams of the 1000 g total, with the default 62% hydration, 2.5% salt and 0.2% yeast. Most of the rest is water, plus a little salt and yeast.
Why is the flour less than the total dough weight?
Because flour counts as 100% and everything else is added on top. With the defaults the formula totals 164.7%, so the dough weight is divided by that total to find the flour.
Can I leave out the yeast or the salt?
Yes, both can be set to zero. Zero yeast suits a dough you will inoculate with a separate preferment; zero salt works for a test, but it weakens flavour and gluten strength.
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/pizza-dough-ratio \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"balls":4,"ball_weight":250}'const res = await fetch("https://api.kit.forhosting.com/cook/pizza-dough-ratio", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"balls": 4,
"ball_weight": 250
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/cook/pizza-dough-ratio",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"balls": 4,
"ball_weight": 250
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/cook/pizza-dough-ratio", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"balls":4,"ball_weight":250}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"balls":4,"ball_weight":250}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/cook/pizza-dough-ratio", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"balls": 4,
"ball_weight": 250
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "cook.pizza_dough_ratio",
"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
Invalid ball counts, non-positive ball weights, and negative percentages fail with invalid_input instead of inventing a batch.
Input contract, defaults, response shape, and errors
Zero yeast is allowed if you will inoculate with a preferment outside this mix; zero salt is allowed for testing but not recommended for flavour or gluten strength. Values are rounded to twelve decimal places for byte-stable goldens without changing gram-scale kitchen precision. Example: four balls at two hundred fifty grams with defaults yields one thousand grams total dough and flour near six hundred seven grams with water, salt, and yeast in the expected ratios. POST a JSON body with two required finite numbers: balls (aliases ball_count, count, n_balls, pizzas, n)—a positive integer count of dough balls—and ball_weight (aliases ball_wt, weight_per_ball, dough_ball_g, portion_g, ball_g)—the target mass of each ball in grams or any unit you keep consistent across the batch. Optional finite non-negative numbers control the formula: hydration (aliases water_pct, hydration_pct, h2o_pct, water_percent) defaults to sixty-two; salt_pct (aliases salt, salt_percent, salt_baker) defaults to two point five; yeast_pct (aliases yeast, yeast_percent, yeast_baker, idy_pct) defaults to zero point two for instant dry yeast on a moderate ferment. Negative percentages, non-integer or sub-one ball counts, zero or negative ball weight, missing fields, empty strings, and non-finite values fail with invalid_input naming the field and are not billed. On success the body echoes balls, ball_weight, hydration, salt_pct, and yeast_pct; returns total_dough, flour, water, salt, yeast, and baker_total_pct; and includes formula as the closed-form identity plus message as a one-line English summary for UI copy.
Where a pizza dough ratio API earns its keep
Pop-up and small pizzerias write prep sheets from tomorrow's order forecast: balls times ball weight sets the dough bucket, then this endpoint expands salt and yeast so mixers do not guess. Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when you deliberately send zero balls to verify error handling.
Technical questions
How do I calculate pizza dough flour and water from dough balls?
Send balls (positive integer) and ball_weight (positive mass). Optional hydration, salt_pct, and yeast_pct default to 62, 2.5, and 0.2. Flour = total_dough × 100 / (100 + hydration + salt_pct + yeast_pct); water, salt, and yeast = flour × each percent / 100.
What input is rejected?
Non-integer or sub-one balls, non-positive ball_weight, negative hydration/salt_pct/yeast_pct, missing fields, and non-finite values fail with invalid_input and are not billed.
What does the pizza dough ratio calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.