Dunkin' Iced Coffee with Oatmilk Calories by Size

Which Dunkin' preparation does this page cover?

This page covers Iced Coffee with Oatmilk in the three source-listed sizes: Small, Medium, and Large. It keeps iced coffee, oatmilk, and cup size together so a generic coffee, latte, cold brew, or different milk preparation is not mistaken for the requested drink. Small and Large are neighboring source records, not substitutes for the Medium answer.

The source name matters more than a generic coffee label because the PDF treats different milks, sweeteners, flavors, and sizes as separate recipes. A result for plain iced coffee cannot answer an oatmilk query, and a result for iced latte with oatmilk cannot answer an iced coffee query. The page therefore uses the exact “Iced Coffee with Oatmilk” family and does not merge any similarly named latte, cold brew, or flavored coffee rows.

How many calories are in a Medium Iced Coffee with Oatmilk?

Iced Coffee with Oatmilk - Medium (Medium) lists 30 calories, 1g protein, 5g carbohydrate, 1g fat, 40mg sodium, 1g total sugar, and 1g added sugar. Those fields all come from record dunkin-0802. The Medium label is preserved independently from the product name even though the source name also contains “Medium,” because the duplicate specification makes the row easier to audit against the PDF extraction rather than implying that an unmarked coffee happens to use a medium cup.

The number is not calculated from the Small or Large entry. Restaurant beverage recipes may use size-specific amounts, and scaling one cup mathematically would introduce an estimate that the JSON does not publish. A Medium order therefore uses the Medium row directly, while a different cup must use its corresponding record without converting ounces or multiplying the nutrition values.

Small stays attached to its own nutrition row

Iced Coffee with Oatmilk - Small (Small) lists 15 calories, 1g protein, 3g carbohydrate, 0g fat, 25mg sodium, 1g total sugar, and 0g added sugar. This is record dunkin-0803, and its Small serving label is part of the evidence. The page does not call it a reduced Medium because that phrase would suggest a proportional recipe decision that is not present in the source data.

A user comparing cups should read the complete Small row rather than looking only at calories. Carbohydrate, fat, sodium, total sugar, added sugar, and protein all remain visible because a size decision can change several fields at once. The comparison table keeps them on one line so no value is detached from the exact preparation that produced it.

Large is a third published preparation

Iced Coffee with Oatmilk - Large (Large) lists 45 calories, 1g protein, 8g carbohydrate, 1.5g fat, 60mg sodium, 2g total sugar, and 1g added sugar. The evidence pointer is record dunkin-0801. Large is presented after Medium because the page follows the searcher's likely decision path: answer the queried size first, then allow an explicit comparison with the two other source sizes.

Nothing on the page assumes that a larger cup is ordered or consumed in full, and nothing converts these figures into a daily allowance. The purpose is narrower: preserve the restaurant's three exact cup labels, expose the extracted nutrition fields, and prevent a generic oatmilk or coffee value from being mistaken for this specific iced preparation.

Oatmilk is an ingredient qualifier, not a category shortcut

The Dunkin' JSON contains other drinks that mention oatmilk, including hot coffee, cold brew, latte, and macchiato preparations. Those rows are deliberately absent from this table. Their shared ingredient word does not make their recipes interchangeable, just as “iced” does not make an iced latte identical to an iced coffee.

The same boundary applies to dairy and other plant-based choices. An almond milk row, whole milk row, skim milk row, cream row, or cream-and-sugar row may sit near this product in the full dataset, but it answers a different order. This page makes no subtraction for removing oatmilk and no addition for syrups, cold foam, sugar, or flavor because those transformations would create nutrition values that are not attached to the three selected records.

Calories should be read beside sugar and macros

The query uses the word calories, yet the source row supplies a wider nutritional identity. For each cup, the page keeps protein, carbohydrate, total fat, sodium, total sugar, and added sugar beside calories. That layout prevents a low calorie figure from silently standing in for every other field and lets a reader confirm whether the selected preparation includes a source-listed sugar amount.

Total sugar and added sugar are separate fields in the Dunkin' file, so the table does not relabel one as the other. It also does not invent caffeine, fluid ounces, allergens, ingredient quantities, or a glycemic measure because none of those values is established by these JSON records. The product name and serving size identify the preparation; the displayed nutrient columns define the scope of the claim.

Record ids make each displayed value auditable

The first column is not decorative metadata. Records dunkin-0803, dunkin-0802, and dunkin-0801 are the exact objects read from data/dunkin.json when this static page is generated. The HTML table, page schema, and prose facts all draw from those objects, so the page does not maintain a second hand-entered nutrition table.

An audit can start with a visible record id, locate the same object in the JSON, then verify the source name, serving label, source page, source table row, and nutrient fields. This chain is especially important for a large beverage dataset where a one-word difference can select a different milk or sweetener. The visible id turns that risk into a checkable lookup rather than relying on a loosely similar name.

Use the page by matching the complete order

First verify that the order is Iced Coffee rather than Cold Brew Coffee, Iced Latte, or Iced Macchiato. Next verify oatmilk rather than another milk or cream. Finally select Small, Medium, or Large. If all three qualifiers match, the corresponding row is the relevant frozen source record; if any qualifier differs, return to the full Dunkin' table and search for the exact preparation.

This order-matching method is more reliable than treating a menu word as a broad category. The specification names a concrete decision with a directly matching record, and the page serves that decision without turning it into a claim about every Dunkin' iced coffee.

Source date and restaurant confirmation still matter

The page reflects the frozen nutrition PDF retrieved on August 17, 2026. Availability, recipes, serving procedures, and published nutrition can change after that retrieval date. A matching record shows what the archived source reported; it does not prove that every location currently prepares the drink the same way or that a customized order retains the listed result.

For a current purchase, confirm the product name, size, milk, sweetener, flavors, and other additions with the restaurant's current materials. For allergens, ingredients, caffeine, or personal dietary needs, use the appropriate current source or professional guidance. This independent reference remains useful because it keeps the archived row transparent, not because it replaces the restaurant's live menu.

Frequently asked questions