-
Notifications
You must be signed in to change notification settings - Fork 691
Tutorial Importing Nutrition
Your strap tells you what you spent — calories out, strain, recovery. Nutrition CSV import lets you put what you took in right next to it. Export a simple daily CSV from your food tracker, import it into NOOP, and your calories-in sits beside your calories-out in Explore and Compare — so you can finally see how the two move together over weeks.
Like everything in NOOP, it's a local file you import once. Nothing is uploaded, and you don't need an account anywhere.
Once imported, your nutrition becomes a first-class set of metrics:
- Calories in lines up against calories out (active + basal energy) in Explore and Compare.
- Macros — protein, carbohydrate, fat — become their own series you can plot and correlate.
- The correlation tools can then answer questions like: do higher-carb days track with better next-day recovery? or does an energy surplus show up in my weight trend?
NOOP doesn't judge your diet or set targets — it just makes nutrition another honest signal you can interrogate alongside the rest.
- A food tracker that exports CSV — Cronometer and MacroFactor are the tested ones, and any tracker (or a spreadsheet you keep by hand) works as long as the columns match the layout below.
- A daily CSV — one row per day. (Per-entry exports with many rows per day also work; NOOP totals them per day on import.)
- NOOP on macOS, iOS, or Android.
- Open Cronometer on the web (cronometer.com — the export lives there, not always in the mobile app).
- Go to Settings → Account → Export Data (sometimes under a Data or Export menu).
- Choose the Daily Nutrition / Daily Summary export (the per-day totals), pick your date range, and download the
.csv.
Cronometer's daily export already has a Date column and totals for Energy (kcal), Protein (g), Carbs (g), and Fat (g) — exactly what NOOP needs.
- Open MacroFactor.
- Go to Settings / Profile → Export Data (look for a Data export option).
- Export your daily log as
.csvand save it somewhere you can reach from NOOP (Downloads, Files, iCloud Drive).
MacroFactor's export includes a date and daily calorie and macro totals, which map straight onto NOOP's columns.
If your tracker can output a CSV — or you keep your own — just make sure it has a date column and a calories column, with optional macro columns. See the accepted headers next.
NOOP is flexible about header names so it works with different trackers. It needs a date and calories; macros are optional but recommended.
| Field | Accepted column headers (case-insensitive) | Required? |
|---|---|---|
| Date |
Date, Day, Timestamp
|
Yes |
| Calories in |
Calories, Energy (kcal), Energy, kcal, Calories (kcal)
|
Yes |
| Protein |
Protein, Protein (g)
|
Optional |
| Carbohydrate |
Carbs, Carbohydrate, Carbs (g), Carbohydrate (g)
|
Optional |
| Fat |
Fat, Fat (g), Total Fat
|
Optional |
Notes:
-
Dates should be recognisable calendar dates —
2026-06-12(ISO) is safest; commonDD/MM/YYYYandMM/DD/YYYYstyles are handled too. ISO removes any day/month ambiguity, so prefer it if your tracker offers it. - Multiple rows for the same day (per-meal or per-entry exports) are summed into a daily total automatically.
- Missing macro columns are fine — you'll get calories-in without the macro series.
- Blank cells are treated as no data for that day, not zero.
Date,Energy (kcal),Protein (g),Carbs (g),Fat (g)
2026-06-10,2180,142,201,78
2026-06-11,2460,138,255,86
2026-06-12,1990,150,160,71
Even this works (calories only):
Date,Calories
2026-06-10,2180
2026-06-11,2460
The nutrition import lives in Data Sources, the same hub you use for WHOOP and Apple Health.
- Open NOOP and go to Data Sources.
- Find the Nutrition (CSV) card.
- Click / tap Choose CSV… and pick the file you exported.
- NOOP reads it on-device and totals each day. When it's done you'll see a confirmation — days imported and the date span covered.
- Open NOOP and go to Data Sources.
- Tap Choose CSV under the Nutrition card.
- Select your exported
.csv. - NOOP ingests and stores it locally; a count of days appears when it finishes.
Re-importing: importing an updated CSV is safe — NOOP keys nutrition by day, so re-importing overwrites a day's totals rather than stacking duplicates. Export fresh from your tracker whenever you want to top up, and re-import.
This is the payoff. Your nutrition is now a set of metrics like any other.
- Open Explore.
- Under the Activity / nutrition grouping, pick Calories In (or a macro).
- You get the full detail dossier — trend chart, average/min/max, and a "What correlates" scan that compares calories-in against every other metric over the window.
- Open Compare.
- Add Calories In, then add Active Energy (or Total Calories Out) — and optionally Weight or Recovery.
- The normalized overlay puts them on one timeline, and "How They Move Together" gives each pair a plain-English read — e.g. "When calories in rise, weight tends to rise — a moderate positive link."
Worth trying:
- Calories In vs Calories Out — your energy balance over time, at a glance.
- Carbs vs next-day Recovery / HRV — does fuelling track with readiness?
- Calories In vs Weight — does a surplus or deficit show up where you'd expect?
As always, NOOP shows what moves together, not cause and effect — these are prompts for your own judgement, not instructions.
"Import failed" or "no rows found". Open the CSV and confirm the first row is the header and that it has a recognisable date column and a calories column (see the accepted headers above). Exports wrapped in extra preamble rows can confuse the parser — delete any rows above the header.
Calories imported, but no macros.
Your CSV probably lacks protein/carbs/fat columns, or they're named in a way NOOP doesn't recognise. Rename them to one of the accepted headers (e.g. Protein (g)) and re-import.
Dates look shifted by a few days.
Likely a DD/MM vs MM/DD ambiguity. Re-export in ISO format (YYYY-MM-DD) if your tracker offers it — it's unambiguous.
Totals look doubled. You may have imported the same file twice in a way that didn't overwrite, or you have a per-entry export and a daily export of the same period. Stick to one export style; NOOP sums per-day, so don't combine a per-meal file with an already-totalled one for the same dates.
- Local file, local import. Your nutrition CSV is read on-device and stored in NOOP's local database. Nothing is uploaded.
- No account. NOOP never connects to Cronometer, MacroFactor, or anywhere else — you export the file, you hand it to NOOP.
- Yours to remove. Clear it by wiping NOOP's local data (see Importing History) or uninstalling.
- Importing History — WHOOP CSV, Apple Health, and the full import hub.
- Explore & Compare — plotting and correlating calories-in against calories-out.
- Features — what each screen shows.
- Troubleshooting — general import help.
Reminder: NOOP is an independent, unofficial interoperability tool for a device you own — not affiliated with WHOOP, Inc., and not a medical device. Nutrition correlations are informational, not dietary or medical advice. See Privacy and Security and the Disclaimer.
NOOP is an independent, unofficial, non-commercial interoperability project — not affiliated with, endorsed by, or sponsored by WHOOP, Inc. "WHOOP" is a trademark of WHOOP, Inc., used nominatively. Works only with a device you own; not a medical device; every metric is an approximation, not medical advice. · Privacy and Security · Donations · Releases