To scale a recipe, multiply every ingredient by a conversion factor (new yield ÷ original yield). But that simple math is where most people stop — and where dishes fall apart. Salt, leavening, spices, cooking time, and pan size do not scale linearly. Here's how to do it properly so a doubled batch tastes like the original, not a watered-down or over-salted version of it.
The conversion factor is the foundation of every scaled recipe:
Conversion factor = desired yield ÷ original yield
Multiply each ingredient amount by this number. That gives you a starting point — not a finished recipe.
This is the single biggest fix for scaling failures. Volume measurements (cups, tablespoons) compound error as you scale. Three cups of flour scooped loosely can vary by 20% from three cups packed — and at 4x batch size, that error becomes a brick.
Convert flour, sugar, butter, and other bulk ingredients to grams before applying your conversion factor. Weight scales perfectly and predictably. A kitchen scale is the cheapest reliability upgrade you can buy.
For liquids, milliliters work the same way. Keep a quick reference handy:
Some ingredients punch above their weight. Multiplying them straight will ruin the dish.
Salt and spices — Scale to about 75–90% of the math at first, then taste and adjust. Flavor perception isn't linear; a doubled batch rarely needs exactly double the salt to taste right. Under-season, then correct upward — you can always add more.
Leavening (baking soda, baking powder, yeast) — Scale these proportionally, but cap it. For large jumps (3x and beyond), reduce leavening slightly, around 10–15%. Too much leavening in a big batch causes over-rising, collapse, and a metallic or soapy taste.
Strong aromatics (garlic, chili, cloves, vanilla, alcohol) — Start at 75% of the scaled amount and adjust to taste. These intensify in larger quantities.
Thickeners (cornstarch, flour roux, gelatin) — Scale proportionally, but expect to fine-tune. Larger volumes hold heat differently and may set firmer.
Cooking time and temperature follow physics, not multiplication.
For stovetop cooking, a bigger batch in the same pot means crowding — which steams instead of sears. Use a wider pan, cook in batches, or accept longer reduction times.
Scaling math assumes your gear can handle it. It often can't.
If your equipment can't keep up, make multiple smaller batches instead of one oversized one. It's more reliable.
Eggs don't divide neatly. If halving a recipe calls for 1.5 eggs, beat one egg, measure it (a large egg is about 50g of liquid), and use half. For scaling up, round to whole eggs and adjust liquid slightly if needed.
The same logic applies to anything sold in fixed units — one can of tomatoes, one packet of yeast. Round sensibly and adjust surrounding ingredients to compensate.
Scaling is iterative. Season conservatively, taste, and bring it up to where it should be. Then write down what actually worked — the corrected salt, the real bake time, the pan you used. A scaled recipe you don't record is a problem you'll solve from scratch next time.
1. Calculate conversion factor (new yield ÷ old yield)
2. Convert bulk ingredients to weight
3. Multiply everything by the factor
4. Reduce salt, spices, and strong aromatics to ~75–90%, then taste
5. Cap leavening on large jumps
6. Keep temperature the same; adjust time by doneness
7. Check equipment and pan depth
8. Record your final, working version
The failures are almost always the same three things: scaling by volume instead of weight, multiplying salt and leavening blindly, and assuming time scales with quantity. Fix those three and most recipes scale cleanly.
---
If you'd rather not run the math by hand — especially when you're also tracking what each portion costs — that's exactly the problem PrepSheet is built for. It turns any recipe into a scalable, costed prep sheet with one-tap batch scaling, cost per portion, and a printable sheet for the kitchen, no signup required. If that sounds useful, you can join the waitlist and try it free here.