A recipe for six servings can become a useful starting point for nine servings by multiplying its measured ingredients by 9 ÷ 6, or 1.5. That calculation preserves the numerical proportions in the ingredient list.
It does not tell you how long the food should cook, which equipment will work, or whether every instruction still fits the new batch. Keep the calculation and the cooking method visible together so you can review both.
Use one multiplier for the measured rows
The serving multiplier is the target number of servings divided by the original number. Apply it to each confirmed numeric quantity, using the original recipe as the starting point. Do not make a new base recipe from values that were already rounded for display.
For the six-to-nine example, 180 g of flour becomes 270 g, 90 g of butter becomes 135 g, and 1 teaspoon becomes 1½ teaspoons. These are scaling calculations within the original units; no density is needed merely to multiply them.
| Original | For nine servings |
|---|---|
| 180 g flour | 270 g flour |
| 90 g butter | 135 g butter |
| 1 tsp baking powder | 1½ tsp baking powder |
Keep time and temperature as written
If the recipe says “Bake for 25–30 minutes,” that instruction remains text. BatchLadle does not turn it into 37½–45 minutes when the ingredients are multiplied by 1.5. The numerical appearance of a time does not make it an ingredient quantity.
The same principle applies to resting, chilling, and fermentation instructions, as well as oven settings. A serving ratio is not a model of those processes. Review the original recipe’s guidance for changes in batch size or equipment rather than treating a copied number as a new recommendation.
Resolve uncertain lines before relying on a total
Some lines do not contain a single amount. “Salt to taste” is an instruction, while “1–2 tablespoons milk, if needed” describes a range and a condition. Keep that information. An empty or uncertain quantity should never become zero just because the parser needs a number.
You can choose a definite amount, retain a confirmed range, or keep the line as a note. Make the choice explicit and preserve the original text. The shopping list then has a clear basis for what it totals and what remains outside the quantified amount.
Treat packages and pieces deliberately
A line such as “1 can (400 g)” includes more than one possible quantity. It may refer to a package count, its stated weight, or an amount used from the package. The presence of 400 does not establish which number should be scaled.
Check the recipe and packaging, then enter the quantity you intend to use. Keep any remaining package information in the notes. This is also a good moment to confirm whether the recipe describes an ingredient before or after draining, peeling, or another preparation.
Review the container as a separate step
If the recipe uses a baking pan, compare the inside dimensions and intended fill depth. The pan tool can provide a geometric capacity ratio for supported shapes. That ratio answers a size question; it does not establish a new baking time.
Choose whether servings or a pan comparison should determine the final multiplier, then apply that choice once. Multiplying by a serving factor and accidentally applying an unrelated pan factor again can produce a batch you did not intend.
Check the result before saving
Read the original and new quantities side by side. Look for an unexpected unit, an unresolved line, or a preparation note that was dropped. Switch between fractions and decimals if it helps you read the amount, while retaining the underlying calculation.
Save the recipe when the review is complete, and keep a JSON backup if you need to restore the editable project elsewhere. A printed recipe is useful in the kitchen; its original quantities and notes are what make the calculation traceable later.