About

Nutritional Values answers one question: what is actually in the thing I am about to cook?

Paste a recipe, tell it how many servings you get, and it breaks the recipe into ingredients, matches each one to USDA FoodData Central, and gives you the numbers per serving. Then it lets you change things — the amounts, the servings, or the ingredients themselves — and shows you what moved.

Who it is for

Home cooks who want to understand a recipe rather than track a diet. It leads with the numbers that change decisions — calories, protein, fibre, saturated fat, added sugars and salt — and keeps the full vitamin and mineral table one click away for when you want it.

What it does not do

• No accounts. Nothing to sign up for.
• No tracking. No analytics, no cookies, no third-party scripts of any kind.
• Nothing personal stored. Recipe text is sent to a server to be read into ingredients, and the structured result is cached by a hash of the text so the same recipe isn’t re-read — but the text itself is not stored, and nothing is tied to a session, cookie or account. Your servings, edits and saved recipes never leave your browser. The privacy page is specific about exactly what is sent where, and how to run it with no network calls at all.
• No health claims. It reports what the food contains. It does not tell you what to eat, and it is not medical or dietary advice.

Data and honesty

Nutrient values come from USDA FoodData Central. Where a figure is an estimate — a volume converted to a weight, an unmatched ingredient, a fallback value from the built-in table — the interface says so on the row rather than presenting everything with equal confidence.

The honest summary of the accuracy is on the accuracy page: typically within 10–15% on calories, more reliable for comparing two versions of a recipe than for any single absolute number.

Built with

A Jekyll static site on Cloudflare Pages, with all CSS inlined and no render-blocking resources, no web fonts and no framework. The whole interactive calculator is plain ES modules, and it should load in well under a second on a phone.

Ingredient extraction uses Claude Haiku 4.5 — it reads the recipe text and maps each line onto the vocabulary the USDA database uses. It never calculates anything: every nutrition figure on the page comes from multiplying a database value by a weight, in ordinary code that is covered by tests. Nutrition data is served from this site’s own mirror of FoodData Central, so lookups are fast and don’t depend on an upstream rate limit.