Sodium claims are some of the most tightly regulated on a food label, with specific numeric thresholds behind each phrase — which makes them genuinely useful once you know what each one actually promises.

The four common claim thresholds

These sodium claims generally follow set thresholds per serving, not gut feel:

  • Sodium free: less than 5 mg per serving.
  • Very low sodium: 35 mg or less per serving.
  • Low sodium: 140 mg or less per serving.
  • Reduced or less sodium: at least 25% less than the regular version of the product.

"Reduced" and "less sodium" are relative claims

A "reduced sodium" soup can still be high in sodium overall — the claim only means it's 25% lower than that brand's regular soup, which might have started very high. Relative claims describe a comparison, not an absolute amount.

"Per serving" is the catch

All of these thresholds apply to the serving size printed on the label, which is sometimes smaller than what people actually eat in one sitting. A "low sodium" cracker at 140 mg per six crackers adds up fast if a real portion is fifteen.

"Light in sodium": a less common fifth claim

A fifth, less commonly used claim, "light in sodium" or "lightly salted," requires at least a 50% sodium reduction compared to the standard version of the product, a stricter cut than the 25% required for "reduced" or "less." It's worth recognizing this claim specifically, since it promises meaningfully more than "reduced sodium" despite the two phrases sounding similar on a shelf.

These same regulated thresholds apply consistently whether a product is a cracker, a canned soup, a frozen meal, or a condiment, which means the claim itself is comparable across very different food categories even though the realistic serving size, and therefore the real-world sodium impact, varies enormously between them. A "low sodium" condiment used a tablespoon at a time and a "low sodium" frozen dinner eaten as an entire meal are both technically meeting the same 140 mg threshold, but they occupy very different places in a day's overall sodium total.

Restaurant and prepared-food sodium claims, when they appear at all, generally follow a looser, less consistently enforced standard than packaged retail food, since restaurant menus aren't subject to the same nutrition-labeling requirements everywhere. A "lightly salted" description on a restaurant menu is a chef's characterization rather than a regulated claim tied to a specific milligram threshold, which is worth keeping in mind when eating out is a regular part of your routine, and it's a good reason to ask directly about preparation, rather than relying on descriptive language alone, if sodium is a closely managed part of your diet.

How these claims compare to your daily target

Against the Dietary Guidelines for Americans' general limit of 2,300 mg a day, or the American Heart Association's stricter 1,500 mg target commonly recommended for people managing blood pressure, even a "low sodium" product at 140 mg per serving can represent a meaningful share of the day's total if several servings are eaten, or if it's one of several sodium-containing foods across a day's meals. The claim tells you the product is comparatively low; it doesn't tell you whether your overall day, across every food and condiment combined, is landing under your personal target.

What to actually check

The claim on the front is a decent quick filter, but the milligram number on the nutrition panel, multiplied by how much you'll actually eat, is the number that matters for a daily sodium target. Two products can both say "low sodium" and still differ by a factor of three once you account for realistic portion size.

A useful habit is picking two or three high-sodium categories you buy regularly — bread, canned soup, deli meat, condiments — and actually comparing the milligrams-per-serving across a few brands the next time you're at the store, rather than relying on the front-of-package claim across every purchase. Once you've identified the lower-sodium option in each category you buy often, that becomes your default choice going forward, and you don't need to re-run the comparison every single trip.

It's also worth checking a food's sodium claim against how it's actually going to be used in a dish rather than in isolation. A "low sodium" broth is genuinely useful if it's the only sodium source in a soup, but far less of a win if the same soup also includes salty bacon, a seasoned bouillon cube, and a heavily salted canned vegetable — the individual claim on the broth doesn't account for the sodium contributed by everything else in the pot, which is exactly why a whole-recipe view matters as much as any single ingredient's label.

Taken together, the regulated claim thresholds, the serving-size caveat, and the whole-recipe view form a reasonably complete toolkit for making sodium decisions quickly at the shelf without needing to run a full calculation for every product. Most of the value comes from applying it consistently to the handful of high-sodium categories that make up the bulk of a typical week's shopping, rather than trying to apply it with equal rigor to every single item in the cart.