Why the Recipe Scaler Skipped That Line: How Your Paste Actually Gets Read

You paste a recipe in, tap 2×, and most of it doubles perfectly — but one line sits there unchanged. The flour doubled, the stock doubled, and “5 mushrooms” is still five mushrooms. Nothing errored, nothing turned red; the line just quietly came back the way it went in.

That isn’t randomness, and it isn’t a failure of the arithmetic. The multiplier math itself is settled — our guide to scaling a recipe up or down covers where the factor comes from and which numbers should never be multiplied. This post is about the layer underneath: how the Recipe Scaler reads a pasted line in the first place, what makes it decide a number is a quantity, and how to lay out a paste so nothing gets silently left behind.

One line, one number

The single most important rule: the scaler scans each line for the first number and stops. Everything after that first match is copied through untouched.

So a line that holds two ingredients only ever gets one of them scaled:

2 cups flour, 1 tsp salt   →   4 cups flour, 1 tsp salt

The flour doubled. The salt did not, and nothing told you so. Pasted from a blog where the ingredient list is comma-separated, or from a note where you crammed two things onto one row, this is the most common way a scaled recipe comes out wrong — and it’s the easiest to miss, because the line did change, just not enough.

The fix is mechanical: one ingredient per line. If you’re pasting from somewhere that runs quantities together, break them up before you scale. It takes ten seconds and it’s the difference between a correct output and a batch with half the salt it should have.

The same rule explains a stranger result. Paste a numbered list and the numbers themselves are the first thing on each line:

1. 2 cups flour   →   2. 2 cups flour

At 2×, the list index doubled from 1 to 2 and the flour didn’t move at all. The scaler has no idea “1.” is a step number rather than a quantity — it’s just the first number on the line. Use dashes or plain lines, never 1. 2. 3. Bullets work fine, because - 2 cups flour puts the first number where it belongs.

The word right after the number decides everything

Once the scaler has a number, it looks at the very next word and uses it to classify the line. That one token controls three separate decisions: whether the line is a time or temperature that must be protected, whether the result is formatted as a whole number or a kitchen fraction, and whether a unit conversion applies.

Protection is the important one, and it works by pattern-matching that word against a list of time and length terms — minutes, hours, inches, centimetres, the degree symbol. Match it, and the line passes through completely untouched, which is exactly what you want for “bake for 25 minutes.”

The catch is that the match is a substring test, not a whole-word one. Any ingredient whose name happens to contain one of those fragments gets treated as a time or a length and is silently skipped:

5 mushrooms          →   5 mushrooms        ("mushrooms" contains "hr")
3 minced garlic      →   3 minced garlic    ("minced" contains "min")
1 pinch salt         →   1 pinch salt       ("pinch" contains "inch")
12 shrimp, peeled    →   12 shrimp          ("shrimp" contains "hr")
2 mint sprigs        →   2 mint sprigs      ("mint" contains "min")
1 gelatin sheet      →   1 gelatin sheet    ("gelatin" ends in "in")
6 mini peppers       →   6 mini peppers     ("mini" contains "min")

Every one of those lines comes back exactly as pasted. Meanwhile 2 chicken breasts, 2 sprigs rosemary and 2 cloves garlic, minced all scale normally — note that last one especially, because moving “minced” after the ingredient is enough to make the line work.

That’s the practical workaround, and it costs nothing: put the preparation word last. 3 cloves garlic, minced scales; 3 minced garlic cloves does not. 3 sprigs mint scales; 3 mint sprigs does not. Same ingredient, same amount, different word order — and the word order is what the parser is reading.

For the handful that can’t be reworded around — mushrooms, shrimp, gelatin, pumpkin — just scale those by hand. Knowing which lines need it is the whole point; a skipped line you know about is a non-problem.

How temperatures are protected, and when they aren’t

Times and temperatures are meant to survive scaling untouched, and mostly they do. Bake at 350°F for 25 minutes comes back identical at any multiplier, because the degree symbol immediately after 350 flags the line as a temperature.

Take the symbol away and the protection goes with it:

Bake at 350°F      →   Bake at 350°F      (protected)
Bake at 350 degrees →   Bake at 700 degrees
Preheat to 180C     →   Preheat to 360C

“Degrees”, a bare F, and a bare C aren’t on the protected list — and c can’t safely be added, since it’s also a legitimate abbreviation for cup. So the habit worth forming is simply: write oven temperatures with the degree symbol. 350°F and 180°C are safe; 350 degrees and 180C are not.

Ranges break protection too, for the same first-number-only reason. In Bake for 25-30 minutes, the word straight after 25 is -30, not minutes, so the line never gets flagged:

Bake for 25-30 minutes   →   Bake for 50-30 minutes

That applies to ingredient ranges as well — 1-2 cloves garlic at 2× becomes 2-2 cloves garlic. Pick a single number before you scale. Write 2 cloves garlic, not 1-2.

One more interaction worth knowing: the metric toggle changes which lines are protected. With Convert imperial → metric switched on, method lines are no longer held back, so a multiplier applies to oven temperatures and bake times as well as ingredients. Bake at 350°F for 25 minutes at 2× with the toggle on comes out as Bake at 371°C for 25 minutes — a number that looks entirely plausible in Celsius and is nothing of the sort. If you want both a resized recipe and metric units, do it as two passes: scale with the toggle off, then convert the scaled output at 1×.

What the output rounds to

Two formatting rules explain most surprises in the numbers themselves.

Weights round to whole units. Anything in grams, kilos, ounces or pounds comes back as an integer, which is right for 200 g → 300 g but destructive at the small end. Quarter a recipe and 1 g instant yeast becomes 0 g instant yeast; 2 g salt becomes 1 g. When you’re scaling down, check every gram-level line by hand — yeast, salt, spices and leavening are exactly the ingredients where rounding to the nearest whole gram matters most.

Volumes snap to kitchen fractions — the reasoning behind that is covered in the scaling guide, but there’s a floor worth knowing: below about a sixteenth, the fraction list runs out and you get a decimal instead. 1/8 tsp cayenne halved comes back as 0.06 tsp, which is the honest answer and a useless instruction. Read it as “a pinch.”

Also note that the multiplier box wins outright. Type a multiplier — or tap any of the ½×, 2×, 3×, ¼× presets, which write into that box — and the servings fields stop having any effect at all until you clear it. If you set servings and the output doesn’t match, an old multiplier is almost certainly still sitting in that field.

A paste that works every time

Everything above reduces to five habits:

• One ingredient per line, no commas joining two quantities.
• No numbered lists — dashes or bare lines only.
• Preparation words last: garlic, minced, not minced garlic.
• Single numbers, not ranges, in both ingredients and times.
• Degree symbols on temperatures, and scale and convert in separate passes.

Format the paste that way and the Recipe Scaler will hit every quantity in a normal ingredient list. Then give the output one read-through before you cook, paying attention to gram-level amounts when scaling down and to any ingredient whose name contains “min”, “in”, “hr” or “inch”. If you’re also moving between cups and grams, the Cups to Grams converter handles ingredient-specific densities that a flat multiplier can’t, and the Oven Temperature Converter is the safer way to move a bake temperature between scales — precisely because it never multiplies anything.