Per Serving vs Per 100g: Which Comparison Should You Use?

Comparison method · Updated 2026-08-15 · AptBite

Per serving describes the portion you will actually eat. Per 100g describes the food itself, independent of portion. Both are correct — for different questions — and because U.S. labels only print per-serving values, the per-100g view is one you have to calculate yourself.

A clean split view showing per-serving context beside a 100 gram reference
Per serving answers “what will I eat?” Per 100g answers “what is this food, gram for gram?”

Per serving answers an eating question

Per serving tells you what the package's reference portion contributes: what one bar, one cup, or one bowl adds to your day. It is the better view when you are planning a snack, logging a meal, or checking what a realistic portion delivers. Its weakness is structural: serving sizes differ between products, so two per-serving numbers can describe unequal amounts of food. A 150-calorie serving and a 200-calorie serving are not comparable until you know the grams behind each.

Per 100g answers a product question

Per 100 grams puts every food on the same weight denominator, stripping out serving-size differences entirely. It is the right view when you want to know which of two cereals is denser in sugar, which cheese is saltier, or which cracker is leaner — questions about the food, not the portion. The conversion is one line:

value per 100g = value per serving × 100 ÷ serving weight in grams

If the label's serving is already 100g, no work is needed. Otherwise keep the original grams in the arithmetic and only round at the end.

Example: a serving can win while density loses

Imagine Food A has 150 calories per 30g serving and Food B has 200 calories per 50g serving. Per serving, A looks lower. Per 100g, A is 150 × 100 ÷ 30 = 500 calories, and B is 200 × 100 ÷ 50 = 400 calories. So Food A is lighter as labeled, while Food B is the less calorie-dense food by weight. Neither result is wrong; they answer different questions. The right choice depends on the amount you plan to eat — which is exactly why the two views belong side by side rather than in competition.

Second example: two cereals by sugar density

Cereal X lists 12g of total sugar per 40g serving; Cereal Y lists 14g per 55g serving. Per serving, X looks sweeter... per 100g, X is 12 × 100 ÷ 40 = 30g of sugar, and Y is 14 × 100 ÷ 55 ≈ 25.5g. Cereal Y's serving is bigger, which is why its printed number is bigger; the food itself is less sugar-dense. If you pour 60g of either, X delivers 18g of sugar and Y about 15g. That is the sequence in miniature: the per-100g view describes the products, and the scaled-to-your-bowl view describes your breakfast.

Why the math is on you in the U.S.

Shoppers from the EU, UK, or Australia are used to a per-100g column printed on every label. U.S. Nutrition Facts panels do not include one: the panel shows per-serving values (plus a per-container column on dual-column packages), and that is all. If you want a weight-normalized comparison of two American products, you compute it from the serving line. That makes the serving weight — printed in grams right beside the household measure — the most important number on the panel for comparison work, and it is worth copying down exactly as printed rather than rounding it to a tidy number first.

When per serving is the right basis

When per 100g is the right basis

Where per 100g misleads

A 100-gram comparison can be mathematically clean and practically absurd. Nobody eats 100g of salt, hot sauce, or protein powder at once, and normalizing concentrated foods to 100g inflates differences that never occur on a plate. Liquids add a unit trap: beverages are labeled per mL serving, and 100mL is not 100g except for water-density liquids. Use per 100g as a research lens to understand the food, then return to per serving — or to the amount you actually pour — for the real decision.

A two-view workflow that holds up

  1. Copy both labels' serving weights and the nutrient you care about, exactly as printed.
  2. Compute per 100g for both products to see which food is denser.
  3. Compute the amount you will actually eat for both, to see which portion is heavier in practice.
  4. If the two views disagree, report the trade-off — “lower per bowl, denser per gram” — instead of forcing a single winner.

The serving-size converter does step two mechanically if you do not want to do the division in the aisle.

What neither basis can tell you

Both are descriptions of numbers on a panel. Neither accounts for ingredient quality, satiety, price, taste, or your medical needs, and a calculated per-100g value is not an official label claim — it is your arithmetic on the label's data. Label rounding also sets a floor on precision: values are declared to the nearest gram or 10 calories, so differences of a few percent between two products are often inside the rounding noise. For allergies, medically required diets, pregnancy, or conditions affected by sodium, sugar, or protein, use the label together with advice from a qualified clinician.

Saving your future self some arithmetic

If you buy the same few products regularly, record each one's serving weight once — in a note or in a comparison app — and the per-100g math becomes a one-time cost rather than a per-trip chore. It also makes reformulations visible: when a label quietly changes its serving weight, your saved per-100g figure shows whether the product itself changed or only the portion did.

The bottom line

Use per serving for portion decisions and per 100g for product comparisons — and in the U.S., expect to compute the per-100g view yourself from the serving weight. For the underlying label rules, consult the FDA's overview of the Nutrition Facts label and the FDA serving-size guidance. AptBite preserves the source serving size while showing normalized comparisons side by side, so you can check both views without doing the arithmetic in your head. This article is general label education, not medical or dietary advice.

A clearer way to compare

See the numbers before you choose.

Scan a barcode or nutrition label, compare products on the same target, and keep the trade-off visible in AptBite.

Download on the App Store