ScanDish
RU Open the bot

Home · Counting

Per 100 g, not by eye

USDA FoodData Central gives guides per 100 g and does not promise that every brand will match a database row. The weight you actually have is written on its own, not replaced with the words “about a pack.”

A guide per 100 g · 9 min · a calm pattern

Per 100 g, not by eye

Which question a row answers

A database row answers a narrow question: what guide applies to 100 g of the food in the state the row is labeled for. It does not answer how many grams are in the spoon until the spoon is weighed. One hundred grams in the table is the unit of the guide, not an assumed lunch. Lunch can be lighter or heavier, and that weight is yours, not the row’s.

If you weighed exactly 100 g of the food in the same state, the row is read directly as a guide. If you weighed some other amount, you start from the per-100 g guide and use your own weight, without substituting a guess for the scale. The proportion does not create new properties of the food. It only carries a guide you already have onto another mass.

Why brands do not match

The database says outright that brands differ. Two packs with similar names may match neither each other nor a row chosen “by the sound of it.” The row is therefore a guide, not the passport of the package in your hand. The passport of the package, if one is printed, is its own label.

An FDA label states energy per serving of that package, and a serving is not always 100 g. Confusing a database row with the panel on the pack mixes two sources. When the panel is in your hand, the diary can lean on it and on the number of servings in the container. When there is no panel, what remains is the per-100 g guide and a measured weight, with the brand caveat kept.

Why the eye does not replace a scale

The eye recognizes a food well and names grams poorly. “A mug,” “a handful,” and “the usual” are not a FoodData Central row. Until there is a weight, there is no multiplier for the per-100 g guide. It is more honest to keep the name and a note that the weight was not measured than to enter confident grams from memory.

A kitchen scale closes that particular hole: it supplies the mass the per-100 g row knows how to work with. A picture of a pile, without a scale, does not create a mass. A brand name does not create one either, until you have read a labeled serving or weighed the food. The database guide starts after the mass, not in place of it.

What the guide does not promise

A guide does not become more accurate by rounding it to a handsome number. The facts do not permit replacing a database row with a round figure you did not take from a source. Brands may already differ, and a second homemade rounding only moves the log away from both sources. The guide stays a guide, and the weight stays a weight.

The database does not prescribe how often to eat a food, and it does not declare the food good or bad. It answers a question about 100 g of the chosen row. A label beside it answers a different question: energy per serving of that package, and the package may contain several servings. Both sources are useful so long as they are not passed off as the same answer.

What this text draws on

  • USDA FoodData Central: guides per 100 g; brands differ. A dry-food row is not a cooked portion, because water changes the weight. Do not use a “rice triples” factor.
  • FDA Nutrition Facts: energy is stated per labeled serving; a package can contain several servings. A labeled serving is not always 100 g.

A short paraphrase of open guides and reviews (WHO, national recommendations, peer‑reviewed summaries). Not a quotation and not a treatment protocol.

Short answers

If the portion is exactly 100 g, can the database row be copied as it stands?

Yes, as a guide, if the state of the food matches the row’s label. Brands can still differ, so the guide is not the passport of every pack.

Do similar names on different brands mean the same figures?

No. FoodData Central states that brands differ. A similar name on the shelf does not prove a match with the database row.