Scale Recipe Ingredient Quantities by Serving Count

This recipe serving scaler recalculates every ingredient quantity when the number of people, portions, or batches changes. Enter the recipe's original serving count, the serving count you need, and a structured list of ingredients. The calculator applies one proportional factor to every quantity, keeps ingredient names and units attached, and returns both the original and scaled values. It is deterministic, requires no network access, and rejects zero or negative serving counts before doing any arithmetic.

Scale a recipe without changing its proportions

A recipe is a set of proportions tied to an expected yield. If a soup written for four servings must feed ten people, increasing only the stock or only the vegetables changes the dish rather than resizing it. This calculator uses one scale factor for the entire ingredient list: target servings divided by original servings.

Every supplied quantity is multiplied by that same factor, so the relationship among flour, water, salt, oil, spices, and other ingredients remains mathematically consistent. Enter quantities as numbers and keep each unit in its own optional unit field. The result repeats the ingredient name, original quantity, scaled quantity, and unit, which makes it straightforward to display a before-and-after list or pass the records into another workflow.

Zero quantities are permitted because a recipe record may intentionally include an optional ingredient at none, but negative quantities are rejected as invalid recipe data. The calculation changes amounts only; it does not convert grams to cups, choose package sizes, or infer the density of an ingredient. Use consistent units in the input, and interpret the output in those same units.

Understand the serving factor and numeric result

Moving from four servings to ten produces a factor of 2.5, while moving from eight servings to two produces a factor of 0.25. Each original quantity is then multiplied by the factor. For example, 300 grams of flour in a four-serving recipe becomes 750 grams for ten servings, and two eggs become five.

Results are normalized to a stable numeric precision to avoid distracting floating-point artifacts such as a long trail of binary decimal digits. Both serving fields must be finite numbers greater than zero. Ingredient quantities must be finite, non-negative numbers.

The bounded list and quantity limits prevent accidental oversized requests while still allowing large catering recipes and detailed commercial formulas. No rounding to whole packages, spoon measures, or eggs is imposed; the caller decides whether practical kitchen rounding is appropriate.

Use scaled quantities in kitchens and software

For home cooking, enter the yield printed on the recipe and the number of diners expected, then copy the scaled list into a shopping note or preparation plan. For catering, the same response can become a production worksheet while retaining the units chosen by the kitchen. Preserve the unrounded numeric result until the presentation layer if your application has ingredient-specific display rules.

Liquids may be shown to one decimal place, spices to a smaller measure, and indivisible items such as eggs may require a deliberate operational decision. Those choices are outside proportional scaling and should not silently alter the calculation. A useful validation pattern is to confirm that the ingredient array is non-empty, each name is meaningful, every quantity uses the intended unit, and both serving counts are positive before submission.

When shrinking a recipe, also consider equipment constraints: mathematically correct quantities do not guarantee that a different pan size, cooking time, or mixer capacity will behave identically.