How to Scale a Recipe Without Ruining It
Doubling a recipe by doubling every number is how you end up with something too salty, over-risen, and still raw in the middle. Most ingredients scale. Several do not.
By Rohit Sharma, Founder, SEOShouts
Multiply the quantities by the factor you want and you have scaled a recipe. That works for perhaps 80 per cent of what is on the list. The remaining 20 per cent is what separates a doubled recipe that works from one that does not.
What scales cleanly
Bulk ingredients scale linearly without complaint. Flour, sugar, milk, stock, butter, most vegetables, most meats. If a recipe calls for 200 g of flour and you want half again as much, 300 g is correct and there is nothing further to think about.
factor = desired servings ÷ original servings
A recipe for 4 that you want to serve 6 has a factor of 1.5. Multiply each bulk ingredient by that.
What does not
Salt and strong spices
Perception of saltiness and heat does not rise in step with quantity. Doubling a recipe and doubling the chilli usually produces something noticeably hotter than the original, not equally hot in twice the volume. Scale seasoning by around 1.5 when doubling, then taste and correct at the end. This is the single most common scaling mistake.
Raising agents
Baking powder and bicarbonate of soda are the other frequent failure. Doubling them produces too much gas for the batter structure to hold, so the cake rises fast, then collapses, and often carries a soapy or metallic aftertaste. Scale raising agents by about 1.5 when doubling.
Alcohol, vanilla, and other volatiles
These reduce and evaporate at rates set by surface area and time, not by the amount present. A doubled batch in a wider pan loses proportionally more. Scale to roughly 1.5 and adjust to taste.
| Ingredient | When doubling | Why |
|---|---|---|
| Flour, sugar, liquid, fat | × 2 | Bulk ingredients scale linearly |
| Salt and spices | × 1.5, then taste | Perceived intensity is not linear |
| Baking powder, bicarbonate | × 1.5 | Excess gas collapses the structure |
| Yeast | × 1.5 to 1.75 | Larger dough retains more heat and ferments faster |
| Vanilla, alcohol, extracts | × 1.5 | Volatiles evaporate by surface area, not volume |
| Gelatine and setting agents | × 2 exactly | Set strength depends strictly on ratio |
Cooking time does not scale at all
This catches people out more than any ingredient. Doubling a casserole does not double its cooking time. Heat travels from the outside in, so what matters is the depth of the food and the surface area exposed, not the total mass.
- Same depth, wider pan: cooking time is roughly unchanged.
- Same pan, deeper food: time increases substantially, often by half again or more.
- Baked goods: keep the depth the same and use two tins rather than one deeper one.
- Always judge by internal temperature or a skewer, never by the original recipe clock.
Scaling down has its own trap
Halving a recipe that calls for one egg leaves you needing half an egg. Beat the egg, weigh it, and use half by weight; a large egg is around 50 g out of shell. The same applies to any ingredient that arrives in indivisible units. Below about a third of the original quantity, most recipes stop working reliably because pan contact and evaporation no longer match what the method assumed.
Frequently asked questions
Can I just double every ingredient?
For bulk ingredients, yes. Salt, spices, raising agents and extracts should be scaled by about 1.5 rather than 2, then adjusted to taste, because their effect is not proportional to quantity.
Does cooking time double when I double a recipe?
No. Heat penetrates by depth, not by total mass. If you keep the depth the same and use a wider pan or two tins, the time barely changes. If the food gets deeper, allow significantly longer and test the internal temperature.
How do I use half an egg?
Beat a whole egg, then weigh out half of it. A large egg is roughly 50 g without the shell, so 25 g is your half.
Calculators from this guide
About the author
Rohit Sharma is the founder of SEOShouts, a search consultancy in India, and has worked in technical SEO and content strategy since 2014. He builds and maintains Calcshark.