Baking pan size converter
Changing a baking pan is easier when the comparison is based on usable area rather than a single side length.
Run — free
Enter the original pan area, the target pan area, and the recipe's stated baking time. The calculator returns the factor to apply to every ingredient, the corresponding percentage increase or decrease, and a baseline time estimate. Because proportional ingredient scaling keeps batter depth approximately constant, the estimated time does not change automatically, while normal doneness checks remain essential.
Compare pans by usable area
A pan conversion starts with area because batter spreads across a surface, not along one isolated dimension. A 9 by 13 inch rectangular pan has 117 square inches of area, while an 8 by 8 inch square pan has 64 square inches. The calculator divides the target area by the original area to produce the scale factor. In that example, the result is about 0.547, so each ingredient should be multiplied by 0.547. The unit itself does not matter as long as both values use the same square unit: square inches may be compared with square inches, and square centimeters with square centimeters. Do not mix the two without converting first. For circular pans, calculate usable area as pi times the radius squared; remember that the radius is half the diameter. For rectangular and square pans, multiply the inside length by the inside width. Measuring the inside dimensions is usually more useful than relying on a nominal label because rims and sloped walls can change actual capacity.
Scale every ingredient consistently
Apply the returned scale factor to every scalable ingredient quantity, including flour, sugar, fat, liquids, leavening, salt, and flavorings. If the factor is below one, the target pan is smaller and the recipe should be reduced; if it is above one, the target pan is larger and the recipe should be increased. Small quantities require judgment. For example, a result of 1.5 eggs can be handled by beating two eggs together and weighing or measuring three quarters of the mixture. Very tiny amounts of leavening or spice are often easier to measure by weight than with spoons. The percentage change is another expression of the same factor: a factor of 1.25 means 25 percent more of each ingredient, while 0.75 means 25 percent less. Use the unrounded factor for important production calculations when possible, even though the displayed factor is rounded for readability. Scaling all ingredients together preserves the recipe's ratios; selectively rounding several ingredients in different directions can gradually change structure, sweetness, hydration, or rise.
Understand the baking-time estimate
The baseline estimate keeps the original baking time unchanged because area-based ingredient scaling is intended to preserve approximately the same batter depth. Similar depth means heat travels roughly the same distance toward the center, making the recipe's stated time a more defensible starting point than multiplying time by the area ratio. This is an estimate, not a promise. Pan material and color affect browning, convection changes heat transfer, and shapes with corners or center tubes bake differently. An oven's calibration and the starting temperature of the batter also matter. Begin checking at the recipe's normal early-check point, or several minutes before the stated finish when the bake is delicate. Use the recipe's actual doneness cues: a clean or crumb-coated tester, a set center, edge behavior, internal temperature, color, or spring-back response. If you change pan area without scaling the ingredients, batter depth changes and this time estimate no longer applies. In that case, a shallower layer generally finishes sooner and a deeper layer generally needs longer, with increased risk of an overbrowned exterior before the center is done.
What you can do with it
Move a sheet cake into a smaller pan
Reduce every ingredient by the same area-based factor while retaining the original batter depth and a practical starting time.
Increase a recipe for a larger tin
Calculate how much more batter is needed before shopping, mixing, or pricing a larger batch.
Standardize bakery production
Use one repeatable factor when adapting a tested formula across pans with different usable areas.
FAQ
What does the scale factor mean?
Multiply every original ingredient quantity by the scale factor. A factor below 1 reduces the recipe, while a factor above 1 increases it.
Why does the baseline baking time stay the same?
Scaling ingredients in direct proportion to pan area preserves approximately the same batter depth, so the original time is the most reasonable starting estimate.
Can I enter square inches or square centimeters?
Yes. Use any area unit, but both pan areas must use the same unit. The ratio is unitless.
How do I find the area of a round pan?
Square the inside radius and multiply by pi. The radius is half of the inside diameter.
Does this account for pan material or oven differences?
No. Material, color, shape, oven calibration, and batter temperature can change baking behavior, so follow the recipe's doneness cues.
What does the API request cost?
Each API request costs $0.002. The same deterministic calculation can run in the browser on this page.
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/cook/baking-pan-size-convert \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"original_pan_area":117,"target_pan_area":64,"original_baking_time_minutes":40}'const res = await fetch("https://api.kit.forhosting.com/cook/baking-pan-size-convert", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"original_pan_area": 117,
"target_pan_area": 64,
"original_baking_time_minutes": 40
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/cook/baking-pan-size-convert",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"original_pan_area": 117,
"target_pan_area": 64,
"original_baking_time_minutes": 40
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/cook/baking-pan-size-convert", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"original_pan_area":117,"target_pan_area":64,"original_baking_time_minutes":40}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"original_pan_area":117,"target_pan_area":64,"original_baking_time_minutes":40}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/cook/baking-pan-size-convert", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"original_pan_area": 117,
"target_pan_area": 64,
"original_baking_time_minutes": 40
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "cook.baking_pan_size_convert",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |