Diary Exporter for MyFitnessPal

EXPORT YOUR ENTIRE MYFITNESSPAL FOOD DIARY. NOT JUST THE LAST 12 MONTHS. MyFitnessPal's built-in export stops at one year. If you've been logging meals for two, five, or ten years, everything older than 365 days is locked away behind a date picker that won't go back any further. Diary Exporter for MyFitnessPal removes that limit. Pick any start date, from the day you created your account to yesterday, and get every food entry you've ever logged in a single CSV file. WHY THIS EXTENSION EXISTS MyFitnessPal's "Printable Diary" and data export features cap each request at 365 days. There is no official way to pull a multi-year history in one go, and stitching together a dozen separate one-year exports by hand is tedious and error-prone. This extension does the stitching for you. It walks your chosen date range in short windows, requests each window from MyFitnessPal using the login session already open in your browser, and merges everything into one clean, consistent CSV. A ten-year diary comes out as one file with one row per food entry, ready for Excel, Google Sheets, Numbers, Python, R, or whatever tool you use to make sense of your data. WHAT YOU GET Any date range Your account's estimated creation date is prefilled as the start date, so the default export is your full history. Narrow it to a single month or widen it to a decade. The 365-day ceiling does not apply. One row per food entry, 33 columns of detail Every logged food becomes one row containing: • date, meal_name, meal_position • brand_name, description • servings, serving_value, serving_unit, gram_weight • calories, carbohydrates, fat, protein • fiber, sugar, added_sugars, sugar_alcohols • sodium, cholesterol, potassium, calcium, iron • saturated_fat, trans_fat, monounsaturated_fat, polyunsaturated_fat • vitamin_a, vitamin_c, vitamin_d • food_id, entry_id, created_at, logged_at Nutrient values are for the serving you actually logged (already multiplied by the number of servings), so you can sum a column and get real daily totals without any extra math. Live progress you can walk away from A progress bar in the popup shows how many day-windows have been fetched and how many food entries have been collected so far. Close the popup, switch tabs, go make a coffee. The export keeps running inside the MyFitnessPal tab, and reopening the popup picks up right where it is. A Cancel button stops it cleanly at any time. Built for long exports Multi-year histories mean dozens of requests, and any one of them can hiccup. The extension automatically retries transient failures with a growing back-off delay, and if a window keeps failing it splits that window in half and tries the smaller pieces. Permanent errors (for example a wrong username, or a session that has logged out) are recognised immediately and reported instead of being retried forever. Sensible defaults, adjustable if you need them Out of the box it requests 90 days at a time with a short pause between requests. An Advanced section lets you change both: anywhere from 7 to 180 days per request, and a pause of 0 to 5 seconds. Smaller windows are gentler on very dense diaries; larger windows finish faster on sparse ones. A tidy output file The CSV lands in your Downloads folder as mfp_food_diary_<from>_to_<to>.csv, with the date range in the filename so multiple exports never get mixed up. HOW TO USE IT 1. Log in at myfitnesspal.com and stay on any www.myfitnesspal.com page. 2. Click the extension icon. Your username and estimated account-creation date are prefilled. Adjust the From and To dates if you want a narrower range. 3. Click "Export food diary to CSV". 4. Watch the progress bar, or close the popup and come back later. 5. When it finishes, open the CSV from your Downloads folder. Don't navigate away from or reload the MyFitnessPal tab while an export is running, since the exporter lives inside that tab. PRIVACY: EVERYTHING STAYS IN YOUR BROWSER This extension has no server, no account system, no analytics, and no tracking code. It makes the same requests to MyFitnessPal that the MyFitnessPal website itself makes when you view your diary, using the login session you already have. The data comes back to your browser, is turned into a CSV there, and is saved to your computer through Chrome's download manager. Nothing is transmitted to the extension's author or to any third party at any point. The only things the extension stores are the username and start date you last typed, kept in the extension's local storage so the form is prefilled next time. Removing the extension removes them. Permissions, and why each one is needed: • activeTab and scripting: run the exporter inside the MyFitnessPal tab you are viewing, and only after you click the extension icon. No standing access to any website is requested, and the extension cannot see any tab you don't invoke it on. • downloads: save the finished CSV to your computer. That's the full list. There is no "read and change all your data on all websites" permission here. The source code is published under the MIT license at https://github.com/rodmhgl/mfp-diary-exporter so you can read exactly what it does. WHAT PEOPLE USE THE EXPORT FOR • Year-over-year comparisons of calories, macros, and micronutrients across an entire logging history • Building personal dashboards in Google Sheets, Excel, Power BI, or Grafana • Feeding a complete diet history into a spreadsheet or notebook alongside weight, training, or lab data • Keeping a permanent local backup of years of logging effort • Moving to a different tracking app without losing your history • Reviewing long-term patterns before a conversation with a doctor, dietitian, or coach GOOD TO KNOW Username must match exactly The Username field must match your MyFitnessPal profile name (case does not matter). If the export fails immediately with "MyFitnessPal does not recognise the username", check that field first. Missing dates mean nothing was logged MyFitness…