Recipe scaler
Scale ingredient quantities while retaining units.
How to use Recipe scaler
The recipe scaler multiplies every ingredient quantity by the ratio of target servings to original servings and keeps each unit unchanged. Enter one ingredient per line as name, quantity and unit separated by commas, such as Flour,250,g, for up to 500 lines. Servings can be fractional, and results appear as a table of ingredient, scaled quantity and unit.
- Paste the source into the input editor, or load the built-in example.
- Set original servings, target servings.
- Run recipe scaler, review the output, then use the available copy or download controls.
What this tool supports
Scale ingredient quantities while retaining units.
- Original servings
- Range: 0.01 to 1000000000000
- Target servings
- Range: 0.01 to 1000000000000
Limits and processing
Local bounded calculations. Numeric inputs must be finite and within the visible ranges. Lists and tables have operation-specific limits. Models, estimates and supplied rates must be checked against your intended use.
Example source
Flour,250,g Milk,300,ml Eggs,2,count
Frequently asked questions
How do I double or halve a recipe?
Set Target servings to twice or half the Original servings, for example 4 to 8 or 4 to 2. Every quantity is multiplied by the same factor, so 250 g of flour becomes 500 g or 125 g.
Does the recipe scaler convert units?
No. Units are copied from your input unchanged, so 300 ml stays in milliliters after scaling. Convert between cups, grams or ounces separately if you need a different unit in the scaled recipe.
Do cooking times scale with the recipe?
No. Ingredient quantities scale linearly, but cooking time and pan dimensions may not. Check doneness and choose a suitable pan when you make a much larger or smaller batch than the original.
Where is my input processed?
This operation processes its source in your browser. Copy and download are explicit actions; source input is not saved in an account or history.
What are the input limits?
Local bounded calculations. Numeric inputs must be finite and within the visible ranges. Lists and tables have operation-specific limits. Models, estimates and supplied rates must be checked against your intended use.