Recipe Scaling Calculator
Take any recipe up or down without the mental arithmetic. Enter your ingredients, then scale by a plain multiplier, target servings, pan count, or a finished batch weight — every amount is recalculated together.
2 doubles the recipe, 0.5 halves it.
Servings, pieces, or portions — any unit, as long as both boxes use the same one.
Number of identical pans, tins, or trays.
Total finished (or raw) batch weight the original recipe produces, and your target.
Formula & how it works
Everything reduces to one scale factor. By multiplier it is the number you type; by servings, pans, or batch weight it is target ÷ original.
Each ingredient's new amount is original amount × factor, keeping every ratio in the recipe identical.
Worked example
A loaf uses 500 g flour, 350 g water, 10 g salt and 7 g yeast, and serves 8. To serve 20 the factor is 20 ÷ 8 = 2.5, giving 1,250 g flour, 875 g water, 25 g salt and 17.5 g yeast. Prefer to fill three tins instead of one? Switch to pan count, enter 1 and 3, and every amount triples.
Scaling a recipe the smart way
Pick the target that matches your goal
All four modes end in the same place — a single factor — but starting from the number you actually know saves errors. If you want a specific yield, scale by servings or batch weight; if you are filling more tins, scale by pans; if you just want "a bit more", use the multiplier. The ingredient list updates the moment you change any of them.
Weigh, don't spoon, when you scale big
Volume measures drift as amounts grow — three cups of flour scooped loosely can vary by a lot. Working in grams keeps a scaled recipe faithful to the original ratios, which matters most for bread and cake where hydration and structure depend on precise proportions. Enter grams here where you can.
Some things resist a straight multiply
Leavening, salt, and spice often taste stronger in a bigger batch, and very large scales can change mixing and baking behaviour. Treat the scaled numbers as an accurate starting point, then trust your palate. Bake time in particular follows pan size, not batch size, so pair this with a pan conversion before you commit.