What FoodData Central is
Use USDA FoodData Central to look up measured nutrient values for ingredients — not marketing claims from blogs. Search Foundation or SR Legacy foods for produce and legumes, note the serving weight, and add numbers only when you actually checked them. That keeps recipe pages honest.
USDA describes FoodData Central as an integrated, research-focused data system with expanded nutrient and food-component information. The public search is at https://fdc.nal.usda.gov/ The FAQ and help pages explain how the data types differ and how a search works. Those pages, not a recipe blog, are the instructions this note follows.
The FAQ lists five data types. Foundation Foods and Experimental Foods are newer. The other three are SR Legacy (the final Standard Reference release), the Food and Nutrient Database for Dietary Studies (FNDDS), and the USDA Global Branded Food Products Database. For a home cook checking a vegetable or a bean, Foundation Foods and SR Legacy are the usual places to start. FNDDS supports survey research. Experimental Foods are produced or studied under special conditions, and USDA says they may not be appropriate as a reference for consumers or for diet planning.
Values are a snapshot. USDA notes that foods and methods change, so a number reflects particular samples, places, and times. Copy the date and the data type with the number. Do not treat an old screenshot as permanent.
Foundation Foods versus Branded Foods
Foundation Foods are values from analysis of foods and ingredients, with metadata such as sample counts, locations, dates, and analytical methods when that information is available. USDA's goal for this data type is a growing set of basic foods and ingredients. The search defaults to Foundation Foods, which is helpful when you type a produce name and want a generic food rather than a packaged product.
SR Legacy was the main U.S. food-composition set for decades. The FAQ says the April 2018 release is the final one and will not be updated. It is still a wide list of nutrient values derived from analyses, calculations, and published literature. If Foundation Foods does not yet include the exact ingredient you need, SR Legacy is the other generic set the FAQ points to. For more recent data, USDA says to search the other data types.
Branded Foods are different. They are nutrient values from the labels of branded and private-label products, supplied by industry data partners. USDA standardizes how they are presented. The FAQ says branded data are updated monthly in the application and the API. Use Branded Foods when you cooked with a specific carton, can, or bag and you want the numbers printed for that product. Do not use a branded record as if it were a generic cup of spinach. A flavored bean pouch and plain black beans are not the same food.
FoodData Central's own categories are not the MyPlate food groups. The FAQ says the database does not use the Dietary Guidelines food groups. Looking up a nutrient is not the same task as building a MyPlate week. Use MyPlate for the shape of the plate. Use FoodData Central when you want a measured number for an ingredient.
Look up spinach, black beans, and olive oil
The FAQ describes a basic search in four steps. Step one: use the search box on the site. You can search by food name or by an identifier such as an NDB number. Step two: open the tab for the data type you want. Result counts appear next to each type, and the search defaults to Foundation Foods. The branded tab has extra filters. Step three: click the item that actually matches the food, including the form. Raw and cooked are different. Canned and dried are different. Oil is not the vegetable it was pressed from. Step four: read the nutrient values, the portion information, and the notes on how the data were derived.
Try that sequence with three ingredients that show up in vegetable recipes. Search spinach, then choose a Foundation or SR Legacy record that matches the form you used, such as raw spinach or cooked spinach, not a frozen branded entrée that happens to contain spinach. Search black beans, and choose a plain bean record in the form you used, such as canned or boiled, rather than a seasoned packaged meal. Search olive oil, and choose an oil record, then read the amount basis before you write anything down.
This article does not print calorie or nutrient figures for those foods. Numbers change when the record, the form, or the amount changes, and a copied figure from memory would be a guess. Open the record and use the figure on the screen. If you cannot find a close match, leave the number off the recipe. A missing number is more honest than a borrowed one.
While you are on the record, write down four things: the food name as USDA prints it, the data type, the identifier on the page, and the amount the values refer to. Those four details let you check the number later. A blog that lists calories with no food name and no amount is not a source you can audit.
Portion weights and per 100 grams
FoodData Central does not automatically resize a portion for you. The FAQ says there is currently no way in the search to customize portion size and have the nutrients recalculate. Most Foundation Foods are shown on a 100-unit basis, often per 100 grams. Branded foods use the serving size from the package label. A survey food may list household measures such as a cup, with a gram weight beside it.
Match the basis to the recipe. If the record is per 100 grams, weigh the ingredient you used or convert with a scale, then scale the nutrients only with arithmetic you can show. If you do not weigh the food, do not invent a gram weight. A heaping cup and a level cup are not the same, and drained beans are not the same as beans plus canning liquid. Note drained or undrained when the record makes that distinction.
Household measures on a record are clues, not permission to skip the gram weight. If both a serving and a per-100-gram column are visible, record which column you used. Mixing them is how recipe cards end up with impossible plates. USDA's help pages also describe dates on a record, including when a food was published and, for some data types, when a sample was acquired. If you publish a number, the date belongs next to it.
How to present nutrition on a recipe card
Nutrition on a home recipe card should be optional and clearly approximate. A fair card names the ingredient, the amount, the FoodData Central record you used, and the words estimated or approximate. It does not present a rounded total as a laboratory assay of the finished dish. Cooking, draining, and what you leave on the plate all change what someone actually eats.
Add a nutrient only when you opened the record and copied that nutrient for that amount. Energy, protein, carbohydrate, fat, and fiber are common fields. Vitamins and minerals are appropriate only when they appear on the record you checked. Do not upgrade a number into a benefit claim. A milligram figure is a measurement. It is not a promise about health, and it is not a reason to call the recipe a therapy.
If several ingredients are estimated, say so once at the top of the card. If you skipped an ingredient because you could not find a close record, say that too. Readers can tolerate an incomplete card. They cannot audit a card that looks official and is not. On this site, treat any nutrition line as kitchen context, not as medical guidance and not as a substitute for the USDA record itself.
What FoodData Central does not tell you
FoodData Central does not tell you that a food is an alkaline therapy, and it does not score foods by body pH. A nutrient table is not a medical instruction. It will not tell you whether a recipe is right for a specific person, and it will not turn a vegetable dish into care for a condition. This site's opinion, labeled as opinion, is that pH talk does not belong on a recipe card. The card can hold ingredients, steps, and checked numbers. The word alkaline, when we use it, remains a lifestyle and recipe label for vegetable-forward cooking.
The database also will not write your recipe. It will not know the brand you used unless you search Branded Foods, and it will not know how your household measures a cup. Experimental foods and supplement databases linked from the system are outside a normal vegetable recipe. Stay with the food you cooked.
Linking out correctly
When you publish a number, link the FoodData Central record or, at minimum, name the food, the data type, and the identifier so a reader can find it. Link the public site, the FAQ, and the help page when you describe the method, so the instructions stay attached to USDA rather than to a paraphrase that might go stale. Those three addresses are listed below.
Do not link a nutrient claim to a sales page, and do not cite another recipe blog as if it were USDA. If you want plate-pattern context, use MyPlate and the Dietary Guidelines, which are a different job from a nutrient lookup. If you want a personal plan, talk with a registered dietitian or another qualified clinician. A database search is a checking step. It is not personal advice.
Medical disclaimer
Medical disclaimer: this article is general education about how to read a public food-composition database. It does not provide medical advice, diagnosis, or treatment. It does not claim that any nutrient, food, or recipe prevents, treats, or cures any disease or condition. Alkaline, on this site, is a lifestyle and recipe label, not a therapy. Nutrition figures belong on a recipe only when you have checked them. Please read the full disclaimer on this site before you use any number here as guidance for your own diet.
Sources
USDA FoodData Central: https://fdc.nal.usda.gov/
USDA FoodData Central FAQ: https://fdc.nal.usda.gov/faq/
USDA FoodData Central help: https://fdc.nal.usda.gov/help/
A thoughtful note: This article is for general education and inspiration. It does not provide medical advice, diagnosis, or treatment. Please see our full disclaimer.
