Ingredient research, culinary education, checking broad food-composition differences, identifying an FDC record, comparing basic foods on the same reference basis and finding the official UK CoFID dataset.
RecipeWanted Resources
Official food composition data · source-first reference
Food Data
Search and compare reported nutrients from USDA FoodData Central. Check the source and measurement basis, or follow the separate UK CoFID reference. These records are not personalised nutrition advice.
Official source data100 g / 100 ml basis-awareSource provenanceNo personalised advice
Food Data Sub-PillarOfficial-source reference infrastructure with source, provenance and limitation boundaries kept visible.
Quick start
Before you start
Locate official food-composition records, compare selected nutrient values only when their provider reference bases are compatible, and understand exactly which source/data type produced each number.
A food or ingredient name. For branded products, include the brand or product description and enable the Branded data type deliberately.
Source-labelled search results, key nutrients, full returned nutrient table, up-to-four-food comparison, FDC identifiers/publication metadata and official source links.
Official-source search resultsBasis-labelled key nutrient referenceFull returned nutrient tableUp-to-four compatible-basis comparisonSource/data-type provenanceUK CoFID source directory
Examples for home cooking and teaching
Choose a relevant example and check the assumptions before using it in your kitchen or lesson.
Compare ingredients on one reference basis
Select up to four records. Only compare records whose provider basis matches (for example 100 g with 100 g); 100 g and 100 ml are never presented as the same numeric basis.
Distinguish source types
Foundation Foods, FNDDS, SR Legacy and Branded Foods were built for different purposes. The data type stays visible because the records are not all collected in the same way.
Check a branded record carefully
Search branded products only when useful. Branded nutrient data originate from product-label information supplied through the FoodData Central partnership and can change when products or submissions change.
Use this againReturn when comparing another food, revisiting an official record or checking whether the provider/source release has changed.
Food Data intentionally stores no visitor search history. Pinning stores only a browser-local shortcut back to the route.
Trust & safety at a glance
Use the result for the decision it was built to support
Displayed values are provider records on the provider-declared basis. Missing values remain not reported; analytical LOQ information remains distinguishable from a true zero where supplied.
Official/provider-sourced food-composition reference8 subject references · Reference register provided below; no current review date is asserted for this route.
Search official food-composition records, inspect reported nutrients/components and compare selected records while keeping provider, data type and reference basis visible.
Not personalised nutrition advice, medical/dietetic assessment, recipe nutrition calculation, food-safety decision, allergen guarantee, health ranking or regulatory label determination.
Food composition sources are source- and country-specific. USDA FoodData Central and UK CoFID remain separate authorities and are not blended into one RecipeWanted value.
Provider credentials remain server-side. Public food queries use bounded server-side provider/cache infrastructure; Resources analytics does not receive the query text or provider key. Commercial state cannot change provider choice, returned values, source labels, data-type interpretation or result order.
When to stop and verify:Use the current official provider record and qualified professional guidance for clinical, regulatory, labelling or high-consequence decisions instead of treating this reference layer as advice.
Privacy scope: this describes the working-data behaviour of this Resources tool only. Site-level cookies, analytics, consent and other storage/access technologies remain governed by RecipeWanted’s wider privacy/CMP configuration and applicable law.
Source scope: external authorities and specialist references support specific information; linking to them does not mean they have reviewed, approved or endorsed RecipeWanted.
How this Resource reaches its result
MethodProvider-sourced food-composition reference with provenance
Server-side provider adapters return official food-composition records, which RecipeWanted normalises for display while preserving provider/data-type identity, units, missingness and available analytical context.
Can it be reproduced?Deterministic under this version
The same provider record/version and normalisation contract produce the same displayed reference values; provider updates can legitimately change future records.
Evidence8 registered references · RecipeWanted review UNREVIEWED
USDA FoodData Central remains the numeric provider under V16.25 Source/Request Contract 1.1, with UK CoFID maintained as a separate official reference boundary and no mixed 100 g/100 ml comparison.
IndependenceNo paid or analytics influence over the result
Commercial and analytics state cannot change provider data, source labels or result order. No runtime AI invents missing nutrient values or food records.
Uncertainty stays explicit: Food composition varies by sample, product, preparation and provider methodology; not every nutrient is measured or reported for every record.
Evidence reference: RWRES-55171E5E1C707C1F — a RecipeWanted integrity/reference fingerprint for this release evidence set, not certification or third-party endorsement.
Report a factual or method concern if a source conflicts with the tool, a calculation appears wrong, or a boundary needs review.
RecipeWanted Resources · Food Data
Search official food-composition data without losing the source context
Look up reported nutrients in USDA FoodData Central and check the food description, preparation and measurement basis before comparing records. UK CoFID is linked separately as an official UK reference; its values are not blended with USDA data.
Reference data, not personal advice. Food composition can vary by food, preparation, sample, brand and data method. RecipeWanted does not turn these values into a diagnosis, diet target or guarantee.
Live lookup providerUSDA FoodData Central readyMode: demo key
Local upstream guard0 this hour · 0 todayDemo fallback cap 20/hour · 40/day
Latest provider checkNot yet probedUse Tool admin for an explicit probe.
Choose the source before the number
Food composition databases are not interchangeable buckets
FoodData Central itself contains multiple data types built for different jobs. RecipeWanted keeps that provenance visible so the user can decide whether the record actually answers the question.
Foundation
Analytical data and metadata on commodity or minimally processed foods, with underlying sample context. Not every nutrient has necessarily been analysed.
Survey (FNDDS)
Food and Nutrient Database for Dietary Studies records used for foods/beverages reported in What We Eat in America / NHANES dietary studies.
SR Legacy
Historical USDA Standard Reference composition data. The final SR Legacy release is from 2018 and is no longer updated.
Branded
Product-label data supplied by food-industry data providers and standardised/published through FoodData Central. Reported nutrient values can use a 100 g or 100 ml basis depending on the provider unit, and product values can change as records are updated.
Experimental
Food data published in peer-reviewed research supported by or in collaboration with USDA; interpretation depends on the experimental context.
How to read the numbers
Useful reference data needs the right interpretation
The reference basis must match
Most non-Branded FoodData Central nutrient values use a 100 g reference basis. Branded records can use 100 g or 100 ml depending on provider unit. V16.25 labels the basis per record and blocks mixed/unknown-basis numeric comparisons.
Missing does not mean zero
Foundation Foods does not necessarily report every nutrient for every food. V16.25 writes “Not reported” when the provider did not return a value instead of creating a zero.
Zeros can need source context
FoodData Central documents limits of quantification. Where LOQ metadata is returned, RecipeWanted displays a less-than value rather than hiding that context behind a plain zero.
Preparation state matters
Raw, boiled, roasted, drained, fortified or otherwise prepared versions can be separate food records. Compare descriptions before comparing values.
Branded records can change
Branded values originate from product-label information supplied through the FoodData Central partnership. Reformulation or provider corrections can change a product record.
UK CoFID stays distinct
McCance and Widdowson’s CoFID is a UK food-composition source. V16.25 links it separately rather than averaging a UK record with a USDA record and presenting the result as authoritative.
Official source directory
Open the underlying authority
Use these links when you need deeper methodology, release dates, downloads or the UK source dataset itself.
USDA FoodData CentralAPI Guide
Official REST access, API-key, rate-limit and CC0 licensing authority. V16.25 keeps credentials server-side and applies lower local request budgets.
Open official source →USDA FoodData CentralData Type DocumentationDefines Foundation, Experimental, FNDDS, Branded and SR Legacy data and their different purposes/update models.
Open official source →USDA FoodData CentralDownloadable DataOfficial downloadable-release register. RecipeWanted does not hard-code a downloadable file as permanently current; this source remains the authority for release state.
Open official source →USDA FoodData CentralUpdate LogOfficial change log used to verify ongoing FoodData Central releases, including monthly Branded database updates.
Open official source →USDA FoodData CentralDownload Field DescriptionsDefines provider fields used by the provenance layer. The final UI keeps each returned record’s reference basis explicit instead of assuming every record is 100 g.
Open official source →USDA FoodData CentralFoundation Foods DocumentationExplains analytical Foundation Food values, sample variability, missing nutrients and the relationship between 100 g values and portions.
Open official source →USDA FoodData CentralGlobal Branded Food Products Database DocumentationExplains industry-supplied Branded data and USDA standardisation to a 100-unit basis: 100 g or 100 ml depending on the provider unit.
Open official source →GOV.UK / Public Health EnglandComposition of foods integrated dataset (CoFID)Official UK food-composition dataset directory and 2021 user guide. CoFID remains a distinct source rather than being silently reconciled with USDA records.
Open official source →What RecipeWanted deliberately does not infer from food data
No calories, sodium, sugar, protein or other nutrient target is generated for an individual.
A higher or lower nutrient value is not automatically labelled healthier, safer or more suitable.
This sub-pillar does not calculate the nutritional profile of a RecipeWanted recipe or portion from ingredient data.
It does not determine label compliance, school/care standards, medical suitability or legal nutrition claims.
USDA and UK composition data remain separate authorities with different records and methods.
Affiliate, sponsor and analytics state cannot modify a food record, provider choice, nutrient value or comparison.
Food data questions
Is this a calorie or nutrition calculator?
No. This is a food-composition reference tool. It displays source records and selected reported nutrients; it does not calculate a personal intake target or recipe nutrition total.
Why can two records for the same food look different?
Preparation state, variety, sampling, analytical method, survey use, branded formulation and update date can differ. Check the full description and data type before assuming two records represent the same food.
Why does the page sometimes say 100 g and sometimes 100 ml?
FoodData Central Branded values can use a 100 g or 100 ml provider basis. RecipeWanted labels that basis from the returned provider unit and will not present mass- and volume-based records as a like-for-like numeric comparison.
Why does RecipeWanted show “Not reported”?
Because missing data should not be turned into zero. Some FoodData Central records do not contain every nutrient/component.
What is Foundation Foods?
Foundation Foods provides analytical food-component data plus underlying metadata for basic/minimally processed foods and is updated as new data become available.
Why is Branded Foods optional?
Branded records are useful for a specific commercial product, but their values originate from product-label data supplied by food-industry data providers. That evidence model is different from analytically sampled Foundation Foods.
What is SR Legacy?
It is the final release of USDA’s historic Standard Reference data type. It remains useful reference material but stopped updating after its final 2018 release.
Can RecipeWanted combine USDA data with UK CoFID?
No automatic merging is performed. The two sources have their own food codes, records, methods and release histories. RecipeWanted keeps provenance separate rather than manufacturing one blended value.
Does RecipeWanted save what I search for?
The raw food term is sent to the configured FoodData Central provider for the lookup. The Resources plugin does not intentionally store that raw term in its aggregate analytics or provider-status options; server-side cache keys use a hash.
What should I do if a number matters for a medical or regulatory decision?
Open the official provider record/documentation and use the appropriate qualified professional or regulatory authority. This Resource is not a medical, dietetic or legal decision system.
Continue across RecipeWanted
Use the next route for the next question
Related Resources handle the next practical job. The ecosystem handoffs add another useful format when a visual, video, current update, longer article or wider recipe browse answers something different. Cooking Education remains the deeper teaching layer.
01Cooking Converters
Convert kitchen measurements deliberately after you have identified the actual food or ingredient record.
Open related Resource → 02Recipe Cost CalculatorKeep food composition and pricing separate: costing uses prices you supply rather than nutrient data.
Open related Resource → 03Cook With What You Have FinderMove from ingredient identity into real RecipeWanted recipes without using food-composition numbers to generate a recipe.
Open related Resource → 04Ingredient Substitution FinderUse the substitution tool for culinary-function decisions; similar nutrient values do not prove two ingredients are functional substitutes.
Open related Resource → 05Ingredient GuidesOpen the related Cooking Education route for deeper method and explanation.
06Measurements & ConversionsOpen the related Cooking Education route for deeper method and explanation.
07Search RecipesApply the tool or decision inside a complete RecipeWanted dish.
Legal, privacy & fair-use notice
Free Resources, with clear limits and clear data boundaries.
RecipeWanted Resources provides general cooking information, deterministic calculations, planning aids and reference tools. It is not legal, medical, dietetic, allergy, regulatory or other professional advice, and it does not replace product labels, manufacturer instructions, competent-authority guidance or qualified professional advice where those are needed.
Each tool explains how it handles your entries. This Resources analytics dataset does not retain recipe or ingredient names, pantry lists, allergy, dietary or health information, other free text, exact quantities, visitor/session/account IDs, IP addresses, user-agent strings or referrer URLs.
This Resources statistics layer is currently enabled and records only allowlisted aggregate interaction and coarse workflow/build-shape counters. Daily aggregate buckets are retained for up to 730 days. Aggregate results are for RecipeWanted/QHE internal RecipeWanted service improvement only; they are not sold or used by this layer for advertising measurement, individual profiling or cross-site tracking.
Any reasonable fair-use or availability rules for free tools are separate from privacy law. Access is not conditional on participating in Resources analytics, and “fair use” is not treated as consent or as a legal basis for collecting personal data. On instrumented Resources pages, the usage-statistics panel provides a simple, free objection control.
Wider site/infrastructure scope: ordinary hosting, security, caching, firewall, consent-management or server-log systems may process technical request information outside the Resources aggregate dataset. Those systems remain governed by RecipeWanted’s wider privacy/CMP arrangements and published privacy information. This Resources notice does not claim that every web request is anonymous.
External authorities linked elsewhere in Resources support specific facts or methods; their inclusion does not mean they approve or endorse RecipeWanted. If a higher-consequence decision is uncertain, stop and verify it with the appropriate current source.First-party usage statistics
Help RecipeWanted learn what is actually useful
Resources records aggregate usage statistics such as qualified tool views, whether a working surface is started, route-level value actions, coarse read depth, broad workflow/build-shape buckets and which non-commercial RecipeWanted handoffs are used. Build-shape signals are deliberately coarse (for example, a small/medium/large row-count bucket or a selected calculator mode): RecipeWanted does not send the recipe name, ingredient list, pantry items, allergen/dietary choices, free text or exact quantities to this analytics dataset; it does not create a visitor/session ID; and it does not store IP addresses, user-agent strings or referrer URLs in the analytics dataset.
Purpose: help RecipeWanted/QHE decide which free tools, workflows, supporting content and first-party integrations to improve next. Aggregate statistics may be reviewed internally across QHE only for that same RecipeWanted service-improvement purpose. They are not sold and are not used by this layer for advertising measurement, cross-site tracking or individual profiling. Free access is not conditional on this measurement: opting out does not disable or reduce any Resource tool.
What is counted and retained?
Allowed counters include 5-second qualified views, 30 seconds of visible engagement, 50%/90% read depth, first working-surface use, selected non-commercial feature/export/continuity actions, hub task choices, broad allowlisted workflow/build-shape buckets and RecipeWanted internal/ecosystem handoffs. Counts are merged directly into UTC daily buckets and retained for up to 730 days under the current admin setting. The only browser preference this layer writes is the first-party objection cookie after you choose to opt out; removing the objection deletes that preference. This describes the Resources aggregate dataset only; ordinary hosting, security, caching, firewall, consent-management or server-log systems remain governed separately by RecipeWanted’s wider privacy/CMP arrangements.
Privacy informationYou can object simply and free of charge at any time. The preference applies only to this first-party Resources statistics layer.
Next step
Use the tool, then get back to cooking.
Resources should remove friction around the task rather than become another layer to manage.
