How to Scale a Recipe Up or Down (and Where the Recipe Scaler Math Breaks)

Almost every recipe is written for a number of people that isn't the number you're feeding tonight. The braised chicken serves 4, but it's just you and one other person. The cake makes one layer, and the birthday needs two. So you start doing kitchen arithmetic in your head, and somewhere around "okay, two-thirds of 350 grams" you give up and eyeball it.

Most of scaling is genuinely just multiplication, and you can hand that off to a tool in two seconds. But a few ingredients refuse to obey the multiplier, and if you don't know which ones, you end up with a dinner that's too salty or a cake that bakes through on the outside while staying raw in the middle. This post covers both halves: the boring math you should automate, and the four or five places where you still have to use your head.

The one number that does everything: the scale factor

Every scaling decision starts from a single ratio:

scale factor = desired servings ÷ original servings

That's it. If a recipe serves 4 and you want 6, the scale factor is 6 ÷ 4 = 1.5. If it serves 4 and you want 2, it's 0.5. Cooking for one off a 4-serving recipe? 0.25.

Once you have that number, you multiply each measured ingredient by it:

600 g chicken × 1.5 = 900 g
2 tbsp soy sauce × 1.5 = 3 tbsp
250 ml stock × 1.5 = 375 ml

Doubling is just a scale factor of 2; halving is 0.5. Those two are easy enough to do by hand, but the moment your factor is 1.5 or 0.75 or 1.33, the fractions get ugly fast, and that's where a recipe scaler earns its keep — paste the ingredient list, type the original and target servings, and every line is recomputed at once with the unit kept on the right line.

A worked example: 4 servings up to 6

Let me run a real one. Here's a simple pasta sauce written for 4:

400 g canned tomatoes
3 cloves garlic
2 tbsp olive oil
1 tsp salt
1/2 tsp chili flakes
a handful of basil
Simmer 25 minutes

Scale factor: 6 ÷ 4 = 1.5. Apply it to each measurable line:

400 g tomatoes → 600 g
3 cloves garlic → 4.5, which rounds to 4 or 5 cloves (you can't mince half a clove cleanly, so pick one)
2 tbsp olive oil → 3 tbsp
1 tsp salt → 1.5 tsp on paper — but hold that thought
1/2 tsp chili flakes → 0.75 tsp, on paper
"a handful of basil" → there's no number, so it passes through untouched
"Simmer 25 minutes" → also untouched, because time doesn't scale this way

Four of those seven lines came out clean. The garlic needed rounding because you can't buy 4.5 cloves. And the salt, chili, and simmer time are flagged because they're the ones that lie to you. Notice the scaler leaves the no-number lines ("a handful of basil") and the time line alone on purpose — it only touches lines that actually look like a measured quantity.

Why salt and spices don't scale linearly

Here's the part the calculator can't do for you. Salt, chili, strong spices, garlic, and anything you'd describe as "to taste" do not scale on a straight line, because flavor perception isn't linear and because the cook's tolerance for error shrinks as the dish gets smaller.

Two reasons it goes wrong:

Seasoning is to taste, not to formula. A 1.5× batch of sauce has 1.5× the volume but doesn't necessarily need a full 1.5× the salt to taste right — bigger batches concentrate differently as they reduce. Multiply seasonings as a starting point, then taste and adjust at the end. Always under-salt the calculated amount, then climb up; you can add salt, you can't remove it.

Small batches punish over-spicing. Scale a recipe down to a quarter and a "rounded 1/4 teaspoon" of cayenne is suddenly the difference between mild and inedible. When you scale down, treat strong spices as the absolute ceiling and start below it.

My own rule, after ruining one too many half-batches of curry: I let the tool compute the exact multiplied amount for salt and spices, then I deliberately use about 80% of it and correct at the end. The scaler gives me the right ballpark; my tongue makes the final call. For the rest — flour, liquid, sugar, fat — the straight multiplication is exact and I trust it completely.

Why bake time and oven temperature are different again

Time and temperature follow their own rules, and neither one tracks the scale factor.

Oven temperature does not change at all. Halve a cake and 180 °C is still 180 °C; double it and it's still 180 °C. Temperature sets the rate of the chemistry, not the quantity. Scaling it would be flatly wrong.

Time scales sub-linearly, not by the factor. A half-size loaf does not bake in half the time — heat penetrates by depth and thickness, not by total mass, so a smaller bake might need 70–80% of the original time, and a bigger one only 10–15 minutes more. The honest move is to set a timer for the short end of the estimate and check early. A countdown timer plus a thermometer or a toothpick beats trusting any multiplied number. Check doneness by internal temperature or a clean skewer, never by the clock alone.

There's a quieter trap underneath this: the pan. If you double a batter and pour it into the original tin, it bakes half-raw in the middle and dries at the edges. Pan area should roughly track the recipe — doubling a 9×13 tray means two trays, not one giant one. The math on your ingredients can be perfect and the cake still fails if the tin didn't scale with it.

Keeping your units straight while you scale

One last friction point: scaling and unit conversion are different jobs, and mixing them mid-recipe is how mistakes creep in. Scale first in whatever units the recipe is written in, then convert if you need to. If you try to do both at once — "1.5 cups times 1.33, and also that's how many millilitres?" — you'll drop a factor somewhere.

Scale the recipe to your serving count, get a clean ingredient list, and only then run anything that needs converting through a cooking unit converter. Two clean steps beat one tangled calculation every time, and you'll be able to see at a glance whether the scaled amount is sane before you start measuring.

The short version

Scaling a recipe comes down to one ratio and a short list of exceptions. Compute desired ÷ original, multiply every measured ingredient by it, and round countable things — eggs, cloves, slices — to whole numbers. Then stop trusting the multiplier for the four things that lie: salt and spices (taste and adjust, lean under), garlic and aromatics (round, don't fractionate), bake time (check early, go by doneness), and oven temperature (don't touch it at all). Let the arithmetic be automatic so your attention is free for the parts that actually need a cook.

Made by Toolora · Updated 2026-06-13