How to Scale a Recipe Up or Down Without Guessing

Scaling a recipe up for a crowd or down for a smaller household seems like it should be simple multiplication, and for most ingredients, it is. The part that trips people up is knowing which measurements convert cleanly, which units to actually use for precision, and which parts of a recipe (cooking time, pan size, leavening) refuse to scale in a straight line no matter how carefully you do the arithmetic.

Start with a clean scaling factor

The first step is figuring out your scaling factor: target servings divided by the recipe's original servings. If a recipe serves 4 and you need to feed 6, your factor is 6 divided by 4, or 1.5. If you need to feed 10, your factor is 10 divided by 4, or 2.5. If you're cooking for 3 instead of a full 4-person batch, your factor is 0.75.

Once you have that factor, every ingredient quantity in the original recipe gets multiplied by it. A recipe calling for 2 cups of flour at the original 4 servings becomes:

That mL column matters more than it looks. Converting to milliliters, using the National Institute of Standards and Technology's (NIST) official cooking measurement equivalencies, lets you check your scaled total against a kitchen scale or a metric measuring cup, which is more accurate than stacking multiple imprecise cup or tablespoon measurements on top of each other.

The official NIST conversions worth memorizing

NIST's Office of Weights and Measures publishes a reference table of approximate equivalents between U.S. customary kitchen measures and metric units, specifically for home cooking use. The core figures, straight from that reference:

These are the values NIST itself labels as approximate, meant for everyday home cooking rather than laboratory precision, which is exactly the level of accuracy a scaled recipe needs. NIST's companion publication, SP430, Household Weights and Measures, maintained by the agency's Office of Weights and Measures, presents the same kind of household-friendly weights and measures tables for general consumer use, confirming that these approximate equivalents are the standard reference NIST itself points to for everyday kitchen conversions, not a simplified version aimed only at beginners.

Why scaling by weight beats scaling by volume

When you're scaling a recipe by a factor like 1.5 or 2.5, volume measurements (cups, tablespoons) start accumulating small errors, because each scoop of flour or sugar you measure by volume already carries some variability depending on how packed it is. Multiplying that small inconsistency by 1.5x or 2.5x multiplies the error too.

Converting to grams using the NIST weight equivalents and then multiplying by your scaling factor avoids compounding that error, because you're working with one consistent unit instead of stacking multiple cup or spoon measurements. This matters most for baking, where the ratio between flour, fat, and liquid is what determines whether the final texture holds together, and least for something forgiving like a soup or stew, where small ingredient variances barely register in the final dish.

What does not scale linearly

The ingredient quantities scale cleanly with simple multiplication. Several other things in a recipe do not:

• Cooking and baking time generally does not scale linearly with volume. Doubling a cake batter and pouring it into a single larger pan usually needs a longer bake time than double the original time, because heat has to penetrate a thicker mass; the right approach is to check for doneness using the recipe's visual or temperature cues, not just a doubled clock time.
• Pan size and shape change how a scaled batter or dough bakes. The same total volume of batter spread thinner in a wider pan bakes faster than that volume poured into a smaller, deeper pan.
• Leavening agents (baking powder, baking soda, yeast) do not always scale in exact proportion, especially at large multiples, because their effect depends partly on surface area and gas distribution within the batter, not purely on total mass.
• Seasoning, particularly salt and strong spices, is often safer to scale at a slightly lower ratio than the main ingredients and adjusted to taste afterward, since perceived saltiness and spice intensity don't always track a straight multiplication the way bulk ingredients do.

A practical scaling workflow

1. Calculate your scaling factor: target servings divided by original servings.
2. Convert each core ingredient to grams or milliliters using the NIST equivalents, then multiply by the factor.
3. Choose a pan or pot sized for the new total volume, not just a scaled-up version of the original pan.
4. Use the recipe's doneness cues (color, internal temperature, texture) rather than a straight-multiplied cooking time.
5. Scale seasoning conservatively and adjust to taste at the end, especially for salt and potent spices.

Key takeaways

• Scaling factor equals target servings divided by original servings; multiply every core ingredient quantity by that factor.
• NIST's official kitchen conversions (1 cup equals 240 mL, 1 tablespoon equals 15 mL, 1 pound equals 454 g) let you verify a scaled recipe with a scale or metric measuring cup instead of stacking volume measurements.
• Scaling by weight in grams introduces less compounding error than scaling by volume, especially for baking.
• Cooking time, pan size, and leavening agents do not scale in a straight line with ingredient volume; rely on doneness cues rather than a multiplied clock time.
• Scale seasoning like salt and strong spices conservatively, then adjust to taste after cooking.

Get the math right on the ingredients and treat time, pan size, and seasoning as separate judgment calls, and a scaled recipe comes out tasting like the original instead of just a bigger or smaller version of it.