Side dish quantity per person calculator
Twelve guests at half a cup of coleslaw each need 6 cups in total. Enter the headcount and the portion you serve per person, in cups, grams, ounces or scoops, and get the amount to buy or prep. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Guests
- 12 cup
- Portion per person
- 0.5
- Total quantity
- 6 cup
Planning mashed potatoes, roasted vegetables, rice, or a salad for a crowd usually starts with one simple product: how many guests times how much each person is meant to receive. Hosts, caterers, and meal-prep apps need that total before they shop or write a prep sheet, without inventing a recipe or scaling a full ingredient list. This side dish quantity per person calculator multiplies a positive guest count by a fixed per-person portion and returns the total quantity in the same unit you used for the portion.
How guest count and portion become a total side dish quantity
Side dishes are almost always planned with a fixed scoop, cup, or weight per diner rather than a full multi-ingredient recipe rewrite. If each guest should get half a cup of coleslaw and twelve people are coming, you need six cups total; if each person gets one hundred fifty grams of roasted carrots and the table seats twenty-four, you need three thousand six hundred grams before peeling waste and second helpings.
The calculator does not convert cups to grams or ounces to millilitres; whatever unit you assign to the portion is the unit of the total. An optional unit label (for example cup, g, oz, or scoop) is echoed for display so a prep sheet can say six cup total without changing the math. This method is the right tool when the serving standard is already known—from a house chart, a dietitian rule of thumb, or last year’s successful Thanksgiving—and you only need the product for the new guest list.
What it guarantees is a deterministic product so two shifts, two apps, and a printed shopping list never disagree on how much side dish the guest count implies.
Where a side dish per-person calculator earns its keep
Home hosts planning a holiday table can multiply a known scoop size by RSVP count and buy the right bags of potatoes or trays of vegetables without reopening a full cookbook. Catering kitchens and school cafeterias keep house portion standards—one hundred grams of rice, three ounces of green beans—and need a deterministic total when the headcount changes the morning of service. Culinary and hospitality classes teach portion math by showing that doubling guests doubles the side; a pure oracle lets students check homework in seconds without a spreadsheet.
Prefer this capability when the question is simply guests times a fixed side portion; use a general recipe scaler when you must expand a full ingredient list, and use main-protein tools when the question is pounds of meat rather than scoops of a side.
What you can do with it
Holiday and dinner-party shopping lists
Multiply RSVP headcount by your house scoop (cups of mashed potatoes, grams of salad) to get a single total for the grocery run.
Catering and cafeteria prep sheets
Apply a fixed side-dish standard per diner when the morning headcount changes so two shifts buy and plate the same quantity.
Apps, homework, and meal-kit builders
Power a guest × portion field in a planning app, or let students verify side-dish portion arithmetic against a deterministic oracle.
FAQ
What happens if guests is zero or negative?
Guest count must be a finite number greater than zero; non-positive values are not billed.
Does the calculator convert cups to grams?
Optional unit is a display label only and does not convert quantities.
How much side dish do I need for 12 people?
Multiply 12 by the portion each guest gets. At half a cup per person that is 6 cups. A house standard such as 100 grams of rice each works the same way, and the total comes out in that unit.
Does the total include extra for second helpings or waste?
No. It is exactly guests times portion, with no allowance for peeling waste, seconds or leftovers. Add your own margin on top if your table usually goes back for more.
Can I use this to work out how much meat to buy?
It is meant for sides served by the scoop, cup or weight. For pounds of a main protein use a main-dish tool, and to expand a full ingredient list use a recipe scaler.
Related tools
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/side-per-person \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"guests":12,"portion_per_person":0.5}'const res = await fetch("https://api.kit.forhosting.com/cook/side-per-person", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"guests": 12,
"portion_per_person": 0.5
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/cook/side-per-person",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"guests": 12,
"portion_per_person": 0.5
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/cook/side-per-person", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"guests":12,"portion_per_person":0.5}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"guests":12,"portion_per_person":0.5}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/cook/side-per-person", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"guests": 12,
"portion_per_person": 0.5
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "cook.side_per_person",
"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. |
Technical notes
Non-positive guests fail with invalid_input so a zero or negative headcount never produces a fake shopping number. The same pure parse logic powers the free browser path and the prepaid API, so party planners, kitchen dashboards, and automation scripts always agree on total_quantity = guests × portion_per_person.
How guest count and portion become a total side dish quantity
The arithmetic is intentionally linear: guests is the positive headcount, portion_per_person is the positive amount each person receives in any single consistent unit, and total_quantity equals guests times portion_per_person. It is not a multi-ingredient recipe scaler, not a main-course meat weight estimator, and not a buffer model for waste or leftovers; those concerns live outside this endpoint.
Input contract, response shape, and error behaviour
POST a JSON body with two required positive finite numbers: guests (aliases guest_count, people, headcount, diners, party_size, n) and portion_per_person (aliases portion, per_person, serving_size, amount_per_guest, side_portion). Optional unit (aliases portion_unit, qty_unit, measure) is a short string label for display only and is omitted from the response when not provided. Missing fields, empty strings, non-finite values, zero guests, negative guests, zero portion, and negative portion fail with invalid_input naming the problem and are not billed. On success the body echoes guests and portion_per_person, returns total_quantity, includes formula and method strings for UI copy, returns a one-line English message, and includes unit only when you supplied it. Example: twelve guests at half a cup each yields total_quantity six; twenty-four guests at zero point seven five yields eighteen. Failed validation does not consume prepaid balance. Keep requests small, pin total_quantity in tests, and treat the unit field as a label never a converter—if you need grams from cups, convert before you call this endpoint.
Where a side dish per-person calculator earns its keep
Party-planning and meal-kit apps can expose a guest field and a portion field, call this parse endpoint, and fill a shopping-list line with total_quantity in the unit the user already chose. Always account for dietary restrictions, second helpings, and waste in your own kitchen rules—those sit outside the numeric scope of this endpoint but matter on the plate.
Technical questions
How do I calculate side dish quantity from guests?
Send positive guests and positive portion_per_person (same unit for the portion you want). The API returns total_quantity = guests × portion_per_person.
Can I use this for more than one side dish?
Call once per side dish with that dish’s portion_per_person. Each request returns one total_quantity for one portion standard.
What does the side dish quantity per person calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.