How Often Does USDA Update FoodData Central?

USDA FoodData Central updates on different schedules depending on the data type: Branded Foods monthly, Foundation Foods roughly every April and October, and Survey/FNDDS only once every two years alongside a new national dietary survey cycle. This site runs on the Foundation Foods release published April 30, 2026 — USDA's own numbering puts it at version 15.0.

How often does USDA actually release new Foundation Foods data?

According to USDA FoodData Central's own Update Log, major Foundation Foods versions have landed roughly every six months: version 15.0 on April 30, 2026, version 14.0 on December 18, 2025, version 13.0 on April 24, 2025, and version 12.0 on October 31, 2024. This project's own data independently matches that pattern: querying this site's food table shows its 469 Foundation Foods carry 15 distinct publication_date values, running from April 1, 2019 to April 30, 2026, and the large majority of those dates fall in April or October of a given year. A dataset built from USDA's downloads, read on its own, shows the same twice-a-year rhythm USDA's release log states directly.

Does every food in a release actually get reanalyzed, or just a few new ones?

Just a few, and the size varies a lot release to release. The earliest batch in this database, published April 1, 2019, brought 92 of the 469 Foundation Foods currently here — including Hummus, commercial and Tomatoes, grape, raw. The most recent batch, published April 30, 2026, added 33 more, including Alaska Pollock, raw and Grapefruit, raw. In between, this project's own publication-date counts show releases as small as 13 foods (April 2021) and as large as 58 (December 2019). A release date means USDA published a new batch of analyzed commodities that cycle — not that every food already in the system was retested.

What about Branded Foods and Survey/FNDDS — do they run on the same schedule?

No, and the gap is wide. The same USDA update log states Branded Foods are on "ongoing monthly updates," far more frequent than Foundation Foods' twice-yearly cadence — new branded-product versions appear in essentially every month of the log. Survey/FNDDS runs the other direction: per USDA's data type documentation, FNDDS is updated "every two years in concert with WWEIA, NHANES release" — tied to a full national dietary survey cycle, not a fixed calendar. This site does not currently include any Branded Foods data, so the monthly cadence doesn't apply to anything in this database yet. The 1,882 Survey/FNDDS ingredients this site does carry show their own sign of that slower rhythm: their underlying sr_addmod_year values span 1976 to 2018, clustering heavily in 2001–2009, meaning a large share of this site's Survey ingredient data was locked in well over a decade before today, independent of how recently FNDDS itself was last repackaged as an edition.

Why does the update schedule differ so much by data type in the first place?

Because each data type is produced a completely different way. Per USDA FoodData Central's own About Us page, the whole system is maintained by USDA's Agricultural Research Service (ARS), but Branded Foods specifically runs through "a public-private partnership" that includes organizations like GS1 US, 1WorldSync and Euromonitor International — industry data feeds that can hand over new packaged-product label data continuously, which is exactly why that type can update monthly. Foundation Foods, by contrast, depends on ARS's own laboratories physically acquiring and analyzing market or agricultural samples, a slower process that only clears a new batch for release a couple of times a year. Survey/FNDDS sits on a third timeline entirely, because it isn't an independent data-collection effort at all — it's built from existing FDC sources to match whatever foods the current two-year National Health and Nutrition Examination Survey (NHANES) cycle happened to capture, so a new FNDDS edition can't exist until a new survey cycle finishes.

Does SR Legacy update on any of these schedules?

No — it's the one FoodData Central type that doesn't update at all anymore. USDA's data type documentation states SR Legacy's "final release" came in "April 2018," and the same source notes that any changes since then have been limited to occasional corrections rather than new data. That matters for this site indirectly: because roughly 95% of this project's own Survey/FNDDS nutrient values trace back to an SR Legacy source rather than a fresh Foundation analysis, a meaningful share of what displays as "Survey" data on this site is, underneath, built on a dataset that has not been updated since 2018 regardless of how recently FNDDS itself was last repackaged as an edition.

What release is this site actually running on right now?

This project's own USDA_RELEASE constant — the value shown in freshness stamps across the site — names "USDA FoodData Central — Foundation Foods," version "2026-04-30." That matches USDA's own update log entry for version 15.0, released April 30, 2026, exactly. When this site states a release date, it's citing the same version number USDA itself assigned, not an internal estimate.

Does a twice-a-year or once-every-two-years cadence mean the underlying data goes stale in between releases?

Not necessarily in the way a release date alone suggests. A release date marks when USDA packaged and republished a dataset — it doesn't mean every sample behind it was collected that same month. This project's own market_acquisition table, which records when a Foundation Food's physical market sample was actually bought, spans acquisition dates from November 1999 to January 2026 — a 26-year range sitting underneath the 15 narrower publication-date batches discussed above. A food published in this year's April release can still be built from older underlying lab work; the release date and the sample date are two different facts, and only one of them is what "last verified" on this site actually tracks.

How should I decide whether a number on this site is current?

Check the page's own "last verified" stamp rather than assuming a recent-sounding release date covers everything on it. This project tracks a last_verified_date separately from the underlying USDA publication_date for exactly this reason — a food can carry an older publication date while still being the current, unretracted figure USDA publishes for it today, since Foundation Foods doesn't re-test a commodity on every cycle just because a new version shipped. The practical rule holds regardless of nutrient: a twice-yearly Foundation Foods release and a once-every-two-years FNDDS edition both mean "USDA repackaged and republished," not "every value was just reanalyzed."

If I'm citing a number from this site elsewhere, what should I actually say about its age?

Name the release, not just "USDA FoodData Central." Because the five data types update on entirely different clocks, "USDA FoodData Central, accessed today" tells a reader nothing about whether the underlying figure is a month old or ten years old. This site's own freshness stamps are built to answer that more precisely: the sitewide release constant names the exact Foundation Foods version and date (April 30, 2026) this build was imported from, and each individual food or ingredient page carries its own last_verified_date on top of that. If you're pulling a number from here into your own work, citing both — which USDA release the figure traces to, and when this site last confirmed it — is a more honest citation than either one alone, especially for a dataset where, as the batch sizes above show, a "new" release can mean as few as 13 newly analyzed foods rather than a full refresh of everything already published.