Scale a recipe to a package size
Recipe needs 300 g, but the pack contains 500 g? Resize the whole recipe around one or more complete packages instead of leaving an awkward remainder.
PackageFit math
If a recipe uses 300 g of an ingredient and your package is 500 g, one complete package gives a factor of 500 ÷ 300 = 1.667×. FOOGG applies that factor to the leading quantity on each recognized ingredient line.
Compare package counts before choosing a batch
For a recipe that originally serves 4 and uses 300 g of the packaged ingredient, a 500 g pack produces these planning options:
| Packages used | Ingredient available | Batch factor | Estimated servings |
|---|---|---|---|
| 1 | 500 g | 1.667× | about 6.7 |
| 2 | 1,000 g | 3.333× | about 13.3 |
| 3 | 1,500 g | 5× | 20 |
The calculator uses the exact package size and package count you enter. It does not assume a standard retail pack because sizes vary by brand and market.
Before you commit to a large batch
- Check equipment capacity: a mathematically valid 3× or 5× batch can exceed your bowl, pot or baking pan.
- Check pan fit separately: for baking, use PanFit rather than assuming a larger ingredient batch belongs in the same pan.
- Review taste-sensitive ingredients: salt, strong spices, leaveners and thickeners may need recipe-specific judgment rather than blind rounding.
- Plan storage before scaling up: make sure the larger cooked quantity fits your intended storage and handling plan.
When this tool is the right fit
Use PackageFit when the package itself determines the target batch: for example, using a whole block of tofu or a complete tub of cream. If you are short on one ingredient, use the single-ingredient scaler. If several ingredients could run out, use Use What I Have.
What remains unchanged
FOOGG changes recognized leading numeric quantities. It does not infer ingredient density, rewrite cooking instructions, choose container sizes or decide whether the larger batch needs a different process. Those decisions remain visible instead of being hidden behind a single “scale” number. The parsing rules are documented in the methodology.