How to Scale a Recipe for a Different Size Cast-Iron Pan
Two completely different problems get lumped together under "scaling a recipe," and cast iron is where the mix-up actually costs you a good dinner. One problem is feeding more or fewer people the same dish. The other is fitting a recipe written for one pan into a pan of a different size, while still feeding the same number of people. They call for different math, and using the wrong one is how you end up with a skillet cornbread that's a thin, dry disc or a pan that overflows the moment it hits the oven.
Both cases boil down to a single multiplier — a scaling factor you apply to every ingredient amount — but the factor is calculated differently depending on which problem you're actually solving. Get the factor right and the rest is arithmetic.
Servings mode: when you need more or less food
If your only goal is to feed a different number of people with the same pan, the scaling factor is the ratio of servings you want to the servings the recipe was written for: factor = desired servings / original servings. This is the classic recipe-scaling math that has nothing to do with pan geometry at all — it assumes you're either using a bigger pan to hold more food or simply making more of a dish that isn't pan-size-constrained.
A few worked examples make the pattern obvious:
| Original amount | Original servings | Desired servings | Factor | Scaled amount |
|---|---|---|---|---|
| 2 cups | 4 | 6 | 1.5 | 3 cups |
| 1.5 cups | 4 | 2 | 0.5 | 0.75 cups |
| 3 cups | 6 | 10 | ~1.667 | 5 cups |
Notice the second row: scaling down is exactly as valid as scaling up, and the factor works the same way. Halving a recipe that serves 4 down to a servings target of 2 gives a factor of 0.5, and every ingredient in the recipe gets multiplied by that same 0.5 — 1.5 cups becomes 0.75 cups, and a tablespoon of an ingredient becomes half a tablespoon, and so on down the ingredient list. The third row shows a less tidy factor, roughly 1.667, but the arithmetic still resolves cleanly: 3 cups times 1.667 lands almost exactly on 5 cups.
Servings mode is the right tool whenever the pan itself isn't changing — you're using the same skillet, just making more or less of what goes into it, or the recipe naturally fills a variable amount of pan space (like a stew or a batch of pancake batter portioned onto a griddle) rather than being sized specifically to one pan's footprint.
Pan-size mode: when the pan itself is different
The more cast-iron-specific problem is different: you still want to feed the same number of people, but the recipe was written for a pan you don't own. A cornbread recipe calling for a 10-inch skillet, made instead in a 12-inch skillet, isn't a servings problem — it's a surface-area problem, and it needs its own factor.
Here's the part that trips people up: a 12-inch pan is not "20% bigger" than a 10-inch pan in the way that matters for a recipe, even though 12 is 20% more than 10. What matters is the cooking surface — the area of the pan's base — and area doesn't scale with diameter. It scales with the square of the diameter, because the area of a circle is pi times the radius squared, and the radius is just half the diameter. So the correct scaling factor for a pan-size change is:
factor = (new diameter / old diameter)^2
Run the 10-to-12-inch example through that formula: 12 divided by 10 is 1.2, and 1.2 squared is 1.44. That 12-inch pan doesn't need 20% more batter — it needs 44% more, because its cooking surface is 44% larger, not 20% larger. Skip the squaring step and every dish you scale by "eyeballing the size difference" comes out thinner than it should, spread too sparse over a surface that grew faster than your instinct expected. If you'd rather look up a size's actual cooking-surface area than compute it by hand, the skillet size reference lists it for every common diameter alongside servings, oil, and preheat time.
Worked pan-size examples
Here's how that squared-ratio factor plays out across a few common resizing moves, including the rounding step covered below:
| Original amount | Old pan | New pan | Factor | Scaled (rounded) |
|---|---|---|---|---|
| 2 cups | 10 in | 12 in | 1.44 | 2.875 cups (2 7/8 cups) |
| 1 cup | 8 in | 12 in | 2.25 | 2.25 cups (2 1/4 cups) |
| 4 cups | 12 in | 10 in | ~0.694 | 2.75 cups (2 3/4 cups) |
| 0.5 cup | 10 in | 14 in | 1.96 | 1 cup exactly |
The third row shows the same math running in reverse: moving a recipe down from a 12-inch pan to a 10-inch pan gives a factor under 1, because you're covering less surface, not more. Ten divided by twelve is about 0.833, and squared that comes out to roughly 0.694 — so 4 cups of batter scales down to about 2.78 cups before rounding, landing at 2.75 cups afterward. It's the identical formula as the upsizing cases; the factor just falls below 1 because the new pan is the smaller one.
The last row is worth a second look because the rounding pushes it to a clean number. A 10-inch recipe moved to a 14-inch pan has a factor of 1.96 — nearly double, since the diameter grew by 40% and 1.4 squared is 1.96. Half a cup times 1.96 comes out to 0.98 cups, just shy of a full cup, and the nearest-eighth rounding step (covered next) rounds that up to exactly 1 cup.
Why the rounding step matters
Both modes finish with the same rounding rule: the scaled amount is rounded to the nearest eighth of a unit. That's not an arbitrary choice — it's the finest increment most kitchen measuring cups and spoons actually have gradations for. A calculator can spit out "2.88 cups" or "0.98 cups" with as many decimal places as you like, but no one owns a measuring cup marked in hundredths, and pretending otherwise is false precision that just makes a recipe harder to follow at the counter.
Rounding to the nearest eighth turns those decimal outputs into numbers you can actually measure: 2.875 cups reads as 2 and 7/8 cups, a mark most standard cup sets include or can be approximated with a 1/8-cup measure. 0.98 cups rounds to a full cup, which is both easier to measure and close enough that the difference disappears in normal cooking variance anyway. The rounding doesn't fight the math — it just meets it where your kitchen tools actually live.
One practical note: rounding happens once, on the final scaled amount, not on each intermediate step. If you're scaling several ingredients in the same recipe, work out each ingredient's exact scaled amount first using the full factor, and only round at the very end for each one. Rounding a factor itself (say, treating 1.44 as "about 1.5" before you multiply) compounds error across every ingredient in the recipe and can leave a dish measurably off from what the pan actually needs.
Choosing the right mode for the job
The two modes answer two different questions, and it's worth pausing before you scale anything to ask which one you're actually facing:
- Use servings mode when the pan isn't changing and you simply need to feed more or fewer people — a dinner party instead of a weeknight meal for two, using the same skillet either way.
- Use pan-size mode when the headcount is staying the same but you're working with a pan the recipe wasn't written for — you only own a 12-inch skillet and the recipe calls for a 10-inch, or you inherited an 8-inch pan and want to try a recipe sized for something larger.
- If both apply — a different pan and a different number of servings — pan-size mode takes precedence when a diameter change is specified, since it's the more specific, cast-iron-relevant calculation; adjust for servings separately by scaling the pan-corrected result again, rather than trying to fold both changes into one factor.
It's also worth noticing what pan-size mode assumes: that the dish is meant to fill the pan to roughly the same depth regardless of diameter, which is true for things like cornbread, frittatas, skillet cookies, and baked dips, where the pan's footprint largely determines the finished thickness. It's a poor fit for dishes that don't care about pan footprint at all — a pot of chili or a pan sauce doesn't need "44% more" just because you're using a bigger pan; it needs however much you're actually trying to make, which is a servings question, not a geometry one.
Putting it together
The underlying idea is simple once it's named: servings scaling is about how much food you want, and pan-size scaling is about how much surface you're covering. The first uses a plain ratio of people; the second squares a ratio of diameters, because area grows faster than length does. Mixing them up — treating a bigger pan like it just needs a bit more batter in proportion to how much bigger it looks — is the single most common reason a recipe moved to a new skillet comes out too thin, too thick, or overflowing the rim. Work out which question you're actually answering, apply the matching factor, round to the nearest eighth so the number matches what your measuring cups can actually do, and the recipe travels cleanly to whatever pan you've got on the stove.