Dunkin' Dunkalatte Calories and Sugar by Size

Which Dunkalatte preparations does this page cover?

This page covers six plain Dunkalatte source records rather than selecting one unexplained total: Hot and Iced, each in Small, Medium, and Large. A Dunkalatte name alone does not choose temperature or cup size, so the reader must match both qualifiers before using a value.

This structure answers the query without pretending that “Dunkalatte” is a single nutrition row. The reader must still match the temperature and size printed on the order. Flavored names such as Marshmallow Cloud Dunkalatte, Peanut Butter Dunkalatte, Strawberries N’ Creme Cloud Dunkalatte, or Toasted Almond Iced Dunkalatte remain outside the table because they are separate products in the source file.

Hot Small keeps its own serving identity

Hot Dunkalatte - Small (Small) lists 210 calories, 8g protein, 30g carbohydrate, 6g fat, 170mg sodium, 29g total sugar, and 18g added sugar. Its evidence pointer is dunkin-0208. The word Hot appears in the source item name, while Small is retained as the serving label; both qualifiers are needed to select this row correctly.

The page does not scale this entry from Medium or treat it as a generic small latte. A differently named hot latte, a flavored Dunkalatte, or another milk preparation must use its own record. The narrow product match prevents a broad calorie query from flattening distinct recipes into one convenient number.

Hot Medium is one direct answer to an unqualified query

Hot Dunkalatte - Medium (Medium) lists 310 calories, 11g protein, 45g carbohydrate, 10g fat, 250mg sodium, 43g total sugar, and 27g added sugar. Record dunkin-0207 supplies every displayed field for this row. Medium can answer a reader who confirms a Hot Medium order, but it is not presented as the default for all Dunkalattes.

A search snippet often drops the context around a value. This page keeps temperature, size, product name, total sugar, added sugar, macros, and sodium together so the number cannot be copied honestly without its serving identity. The visible record id provides a second check when two names appear nearly identical.

Hot Large is a third published hot preparation

Hot Dunkalatte - Large (Large) lists 410 calories, 15g protein, 60g carbohydrate, 13g fat, 330mg sodium, 58g total sugar, and 36g added sugar. The associated object is dunkin-0206. Large is not a mathematical multiple of Small within this page; it is an independently extracted record carrying its own nutrition fields.

That record-level treatment is important for drinks because recipe components do not have to scale in a simple ratio. Even when several values appear orderly across cup sizes, the site uses the source rows rather than inferring a formula. A future source change can therefore update one size without requiring an invented scaling rule.

Iced Small starts the cold group

Iced Dunkalatte - Small (Small) lists 210 calories, 8g protein, 30g carbohydrate, 6g fat, 170mg sodium, 29g total sugar, and 18g added sugar. The record id is dunkin-0238. Iced is a preparation qualifier, not a styling choice in the page heading, and it must be matched before using the row.

The table places Hot rows before Iced rows so the two temperature groups remain easy to scan. It does not imply that one temperature is nutritionally preferable. The goal is to let a reader select the actual order and see the source values without crossing into another product family.

Iced Medium must be distinguished from Hot Medium

Iced Dunkalatte - Medium (Medium) lists 310 calories, 11g protein, 45g carbohydrate, 10g fat, 260mg sodium, 43g total sugar, and 27g added sugar. This row maps to dunkin-0237. Several nutrient fields may match the Hot Medium object in the frozen file, but the source still publishes two named records and the page preserves both rather than collapsing them.

Where the two records differ, the table keeps the distinct value visible; where they match, it shows the matching source values without claiming that temperature can never matter. This distinction separates evidence from inference. The page reports the archived rows and does not generalize beyond them to later recipes or customized drinks.

Iced Large completes the six-row comparison

Iced Dunkalatte - Large (Large) lists 410 calories, 15g protein, 60g carbohydrate, 13g fat, 350mg sodium, 58g total sugar, and 36g added sugar. Its traceable identifier is dunkin-0236. A Large Iced order should use this row only when the product name remains plain Iced Dunkalatte rather than a separately flavored variant.

Showing all six objects on one page avoids two opposite errors: returning only a generic Dunkalatte value, or creating a thin page for every temperature-size combination. The consolidated table is still exact because each line preserves one source name, one serving, one id, and its own nutrient fields.

Sugar content needs the source field label

The phrase “Dunkalatte sugar content” does not say whether the reader means total sugar or added sugar. The Dunkin' JSON provides both fields, so the page displays both and refuses to guess which one was intended. Each amount stays on the same line as its source record rather than being summarized as a product-wide sugar claim.

Carbohydrate is also kept separate from sugar, while fat, protein, sodium, and calories remain alongside it. No caffeine, ingredient quantity, fluid-ounce volume, allergen status, or personalized daily percentage is added because those claims are not supplied by the six selected objects. The table answers only the evidence the page actually has.

Flavor variants are explicit negative scope

The frozen dataset includes other names containing Dunkalatte, but a shared suffix does not make them the same beverage. Marshmallow, peanut butter, strawberry-and-cream, or toasted almond wording signals a different source record. Their nutrition values do not enter this page, and the plain rows are not offered as a base from which flavor can be added or subtracted.

This boundary is useful when a current menu or receipt shortens the display name. Before using a row, verify whether the drink was plain Hot Dunkalatte or plain Iced Dunkalatte and whether any named flavor was part of the recipe. If the preparation differs, search the full overview for the exact source name instead of editing a plain value.

Six record ids anchor the nutrition claims

The Hot objects are dunkin-0208, dunkin-0207, and dunkin-0206; the Iced objects are dunkin-0238, dunkin-0237, and dunkin-0236. The generator reads these records from data/dunkin.json for the visible table, structured data, and facts in the explanatory copy.

An auditor can locate an id, confirm the name and serving, then compare the source page and table-row location captured in the JSON. This explicit chain is preferable to maintaining another handwritten matrix because it makes accidental cross-linking between plain and flavored drinks detectable. It also proves that no new menu item or cup size was invented for the landing page.

Use the frozen page as a precise reference

The source PDF was retrieved on August 17, 2026. Later recipes, regional availability, serving practice, or menu names may differ, and the page does not claim otherwise. Match the current order to the archived product, temperature, and size before using a value, then confirm current information with the restaurant when the decision is consequential.

Ingredient, allergen, caffeine, and medical questions extend beyond the displayed fields. ChainMenu is an independent reference rather than an ordering service or restaurant publication. Its value here is the exact mapping from two observed search needs to six transparent source records, with uncertainty left visible instead of filled by estimates.

Frequently asked questions