Sugars vs total carbohydrate: which number belongs in a food log?

Read the lines as related quantities, not extra ingredients

A nutrition label can show total carbohydrate, dietary fibre, total sugars and added sugars close together. Those rows provide different views of the food composition. They are not a recipe list whose numbers should all be summed. Read the row name together with the serving basis before moving a value into a diary.

The FDA explains that total sugars on the US label include naturally present and added sugars, while sugars form part of total carbohydrate. Keeping that relationship clear prevents an entry from counting a subset as an additional amount. The same care is needed when another app displays several nutrient fields on one screen.

Sources: [1], [3]

Work through one serving before scaling it

Hypothetical US label: one serving contains 32 g total carbohydrate, including 12 g total sugars, of which 7 g are added sugars. A carbohydrate record for the full serving is 32 g. It is not 32 plus 12 plus 7, or 51 g, because those numbers overlap.

For 1.5 servings, total carbohydrate is 48 g, total sugars are 18 g and added sugars are 10.5 g. Those remain three related descriptions of the same portion. If you record a sugar field separately, use its matching value without adding that value to the carbohydrate total again.

Do not use the sugars line as the complete carbohydrate amount

A food can have carbohydrate beyond its sugars, so copying only the sugar line into a field asking for carbohydrate can describe the wrong quantity. The label relationship is especially useful when a product front highlights a sugar number while the full nutrition table supplies a larger carbohydrate value.

A statement about no added sugars also does not establish that a product has no naturally present sugars, no other carbohydrate or no calories. Use the complete matching nutrition information for logging rather than converting a front-of-pack phrase into a numerical value for several different fields.

Sources: [3]

Keep included sugars and separate additions inside the right boundary

If you use the label for a complete flavoured yoghurt, its nutrition describes that product, including ingredients already mixed into it. Separately adding all of the product sugars as another food would count an included part again. A spoon of sweetener you add afterwards is a different ingredient outside that package value.

For a homemade recipe, calculate the known ingredients and then allocate the recipe portion. Do not add both a complete recipe total and every included sweetener separately. The distinction is the boundary of the source, rather than whether an ingredient was visible in a finished photograph.

Check the particular label instead of transferring a convention blindly

This explanation refers to the US Nutrition Facts relationships described by the FDA. Labels and terminology can differ between markets, so read the product information in front of you. If moving values between tools, confirm what the receiving field calls for rather than assuming every similarly named line is equivalent.

Check the amount too. A correct sugar value for a 100 g basis is still wrong for a 60 g portion if entered without scaling. The NCI distinguishes measured amounts from estimates: a label can supply nutrition for a reference amount while your consumed amount remains estimated. Keep those two facts separate in the record.

1. Find the product serving or per-100 amount.
2. Identify total carbohydrate, total sugars and any added-sugar line.
3. Scale each value to the same consumed portion.
4. Do not add a subset to its parent total.
5. Check separate ingredients added outside the labelled product.

Sources: [2]

Use matching nutrition fields in CalQuest

For a known package calculation, enter calories and the listed macros in CalQuest on one portion basis. Use total carbohydrate information appropriate to the source and intended field, rather than replacing it with only a highlighted sugars figure. Review the saved numbers together after adjusting a serving.

A photo estimate cannot read the exact sugar content or package recipe from appearance. Add known details in the optional note or use manual known nutrition. CalQuest does not scan nutrition labels or barcodes. Photo scans use limited free energy, with ads and optional PRO; no clinical sugar-monitoring workflow is promised by this guide.

Frequently asked questions

Should I add sugars to total carbohydrate?

Not on the US Nutrition Facts basis described here. Sugars are already included in total carbohydrate, so adding them again would duplicate that part of the total.

Are added sugars separate from total sugars?

They are reported separately as information, but the added-sugar amount is included within total sugars on the US label. Do not sum the two as independent totals.

Does no added sugar mean zero carbohydrate?

No. The product can contain naturally present sugars or other carbohydrate. Use the matching nutrition table rather than assigning zero from the marketing phrase.

Can a photo show the grams of sugar in a meal?

No. Appearance does not establish the exact recipe or nutrient grams. Use matching known information when available and keep an image-based nutrition result as an estimate.

Keep exploring

• Total carbs vs net carbs in a food log: compare the same definition
• Sodium vs salt on food labels: convert the amount and unit correctly
• Read the food label before choosing a field
• Account for separately added drink ingredients
• Check definitions and amounts when totals differ