How to Scale a Recipe Up or Down Without Wrecking It

A recipe serves four and you’re cooking for six. Or it serves twelve and there are two of you. The instinct is to wing it — “I’ll just add a bit more flour” — and that’s exactly how a cake comes out flat or a sauce ends up thin. Scaling a recipe is genuinely simple arithmetic, but it has one big subtlety and a couple of small landmines. Here’s the whole method, including the numbers you must leave completely alone.

Everything rides on one multiplier

Scaling a recipe is not “add more of each thing.” It’s multiplying every quantity by the same factor, so the proportions that make the dish work stay locked. That factor comes straight from servings:

multiplier = target servings ÷ original servings

Going from 4 to 6 servings, the multiplier is 6 ÷ 4 = 1.5. Every ingredient quantity gets multiplied by 1.5 — full stop. 2 cups of flour becomes 3; 1 teaspoon of salt becomes 1½; 200 g of sugar becomes 300. Because the same number touches everything, the ratios between ingredients never move, which is what keeps the chemistry and the taste intact. The Recipe Scaler takes your original and target servings, computes that multiplier, and applies it to every line you paste — or you can override the multiplier directly when you’d rather just say “double it.”

Servings vs. a raw multiplier

There are two honest ways to set the factor, and good tools support both. The servings approach (4 → 6) is best when you’re cooking for a known headcount. The direct-multiplier approach (½×, 2×, 3×) is better when you think in batches: halve the cookies, triple the chili for the freezer. They’re the same operation — a multiplier — just entered from different ends. Presets like ½×, ¼×, 2× and 3× exist because those are the jumps people actually make, and typing “0.5” is slower than tapping a button.

The numbers you must never multiply

Here’s the landmine that ruins naïve scaling: not every number in a recipe is a quantity. A line like “bake at 350°F for 25 minutes” contains two numbers that have nothing to do with how much you’re making. Double the recipe and the oven is still 350°F. It might need longer, but it absolutely is not 700°F, and the time doesn’t simply double either — a cake in a bigger pan bakes at its own pace, governed by depth and heat transfer, not by a multiplier.

This is why a smart scaler looks for units. It multiplies numbers attached to measurements — cup, tbsp, tsp, g, kg, ml, oz, lb — and leaves bare numbers, temperatures and times untouched. The recipe scaler scans each line for the first real quantity and its unit, scales that, and deliberately ignores oven temperatures and minute counts. So “2 cups flour” becomes “3 cups flour” while “bake at 350°F for 25 minutes” passes through unchanged. That single distinction is the difference between a tool that helps and one that hands you a 700-degree disaster.

Friendly fractions, because kitchens don’t do decimals

Multiply 3/4 cup by 1.5 and the literal answer is 1.125 cups. Nobody owns a 1.125-cup measure. Raw scaling produces ugly decimals constantly, and an unrounded scaled recipe is technically correct and practically useless. The fix is to snap results to the fractions a kitchen actually has — ¼, ⅓, ½, ⅔, ¾ — whenever the quantity is small enough that the fraction matters.

1.125 cups → 1⅛ cups (the nearest real measure)

The scaler rounds to those friendly fractions for small cup/tbsp/tsp amounts (below about 10), and switches to whole numbers for larger or weight-based quantities where a fraction of a gram is noise. The result reads like a recipe a person wrote, not a spreadsheet dump — which means you can actually follow it without doing mental rounding at the counter.

A note on what scales cleanly and what doesn’t

Most ingredients scale linearly and forgivingly: flour, sugar, liquids, fats. A few are touchier. Salt and strong spices scale by the multiplier mathematically, but taste is not perfectly linear — doubling a stew rarely needs exactly double the cayenne, so scale them by the math and then taste. Leavening (baking soda, baking powder, yeast) does scale with the rest, but very large multiples can behave unexpectedly because rise depends on pan size and surface area too. And cooking times never scale by the multiplier — they track pan depth and oven behaviour, so treat a scaled recipe’s original time as a starting point and check for doneness rather than trusting the clock. None of this breaks the multiplier method; it just means the math gets you 95% of the way and your senses cover the last 5%.

Optional: scale and convert units at the same time

If your source recipe is in cups and you’d rather work in grams and millilitres, you can fold a unit conversion into the same pass — cups ×240 ml, tbsp ×15 ml, tsp ×5 ml, oz ×28 g, lb ×454 g, and °F → °C. The scaler has a toggle for exactly this, so a US recipe can come out both resized and metric in one step instead of two error-prone rounds of arithmetic.

Put it together

Scaling a recipe is one multiplier — target servings over original — applied to every real quantity, with temperatures and times left strictly alone and the results rounded to fractions a measuring cup can actually hold. Do that and a recipe stretches or shrinks without losing the proportions that make it work. Paste your ingredient list into the recipe scaler, set your servings or tap a preset, and it multiplies the quantities, skips the oven numbers, rounds to friendly fractions, and can even hand you the metric version — so you cook the right amount the first time.