Calorie Tracker Apps That Sync With Apple Health

The words “Works with Apple Health” are sitting under two calorie trackers. You connect both, log lunch once, and now have to answer the question the badge skipped: which app is allowed to write?

That is the real Apple Health decision. Start by deciding whether your calorie tracker should write nutrition to Health, read nutrition already stored there, or do both. Treat calories and macros as separate fields. When possible, give nutrition write access to one primary app so the same meal does not arrive from two sources.

The comparison baseline was checked against official documentation on July 30, 2026. MyFitnessPal’s replacement Apple Health page was rechecked on August 23 after its August 5 update, and Amy’s App Store listing was rechecked at version 1.74. Foodnoms publishes a clear free-write/paid-read split. Lose It! describes food moving in both directions, but not historical imports. MyFitnessPal documents one-way food export and says meal timestamps do not sync. MacroFactor imports daily calorie and macro totals rather than rebuilding meals. Cronometer documents granular read/write controls and manual backfill. Amy advertises an Apple Health connection, but its public materials still do not provide enough detail for a sync-first recommendation.

This guide is based on current Apple documentation, app help centers, and US App Store pages. We did not install these apps or inspect the Health samples they produce. The app descriptions below are documented support, not hands-on results.

The short answer

There is no honest overall winner without testing current builds on the same iPhone. The table is a documentation-based shortlist, not a test result.

If you need…	Documented candidate	What the official documentation says	What remains untested
An explicitly documented Apple-first nutrition workflow	Foodnoms	Free plan exports; Foodnoms+ imports; only nutrients present in the entry are written	Exact current fields, timestamps, and edit/delete behavior
Food moving both ways without importing old history	Lose It!	Core Apple Health syncing is available to iOS users; third-party Dietary Energy can appear in the Lose It! log	The exact outbound fields and how overlapping meals are handled
A one-way MyFitnessPal food export	MyFitnessPal	Meal-summary calories and some nutrients go to Health; food does not come back; timestamps do not sync	Tier access, current field list, and meal lifecycle
Daily totals feeding a coaching workflow	MacroFactor	Apple Health nutrition imports appear as daily calories and macros, not foods or meals	Exact export fields and the current authorization sheet
Granular controls and a manual backfill option	Cronometer	Its help page shows selectable read/write access and a manual backfill flow	Current nutrition matrix, tier, sample shape, edits, and deletion
Notes-like food logging with Health as a secondary connection	Amy Food Journal	The product page shows Apple Health syncing; App Store history mentions Health reliability and duplicate-prevention changes	Direction, fields, tier, timestamps, history, and lifecycle

Notice what the table does not say. An App Store install button does not prove the relevant sync is free. A permission toggle does not prove a sample arrived. An app that tracks 95 nutrients internally does not necessarily write all 95 to Health.

If Dietary Energy itself is unfamiliar, first read what Apple Health stores as calories eaten. That guide owns the manual Health path; this one owns the product-documentation comparison.

Read And Write Are Different Permissions

Apple says Health access is granted separately for reading and writing, and separately for each data type. A tracker can therefore have permission to write Dietary Energy while being unable to read Dietary Energy from another app. It can read weight and workouts while never reading nutrition. It can write calories without writing protein.

Write access lets an app save a supported data type to the HealthKit store. This is the direction you want when Health is your archive or when another app will consume the nutrition later.

Read access lets an app request data stored by other sources. Apple’s current developer documentation also allows a person to grant only a recent window of history rather than full history. Read permission is not necessarily permission to every old record.

There is a privacy wrinkle: an app cannot conclusively tell whether you denied read access or whether there simply is no readable data. Apple deliberately makes both situations look empty to the app. If an import appears blank, check the permission and the date range before deciding the integration is broken.

This is why “two-way sync” needs four follow-up questions:

1. Which nutrition types can the app write?
2. Which nutrition types can it read from other sources?
3. How much history can it read or backfill?
4. Where does imported nutrition appear inside the app?

MacroFactor provides a good example of the fourth question. Its documentation says imported nutrition appears on the Nutrition page as daily calorie and macronutrient totals, not as foods or meals in the timeline. That can be exactly right for its coaching calculations and exactly wrong for someone expecting a reconstructed breakfast.

Dietary Energy Is Not A Macro Bundle

In HealthKit, calories eaten are stored as Dietary Energy. Protein, carbohydrates, and total fat are separate quantity types measured by mass. Apple also defines separate types for fiber, sugar, sodium, vitamins, minerals, water, caffeine, and more.

The practical consequence is simple: a 620-calorie meal in Health does not prove that protein arrived. A complete set of macros does not prove the app wrote sodium. Check each field you care about.

Apple gives developers a food correlation type that can group nutrition samples into one food object and carry a food name. That is a platform capability, not a promise that every tracker uses it or that the consumer Health app will show a rich meal record. MyFitnessPal’s own FAQ, for example, describes meal-summary export and explicitly says food timestamps do not sync.

Do not mix Dietary Energy with Active Energy or Resting Energy. Dietary Energy is energy consumed. Active and Resting Energy concern calories burned. A fitness app reading your Watch activity is not evidence that it can read your lunch. For the burned side of the equation, use our guide to Apple Watch calorie tracking and its limits.

What Each App Currently Documents

Every app section below has the same evidence status: Documented, not hands-on tested. A vendor page can support a shortlist. Only a current permission capture and resulting Health record can establish what a particular build did on a particular phone.

MyFitnessPal: A Documented One-Way Food Export

MyFitnessPal’s Apple Health connection page, updated August 5, 2026 and rechecked August 23, documents food moving from MyFitnessPal to Apple Health as meal summaries with most nutrients. It says caffeine and Vitamin A do not sync, food timestamps do not sync, and food does not move from Apple Health into MyFitnessPal. It also says MyFitnessPal cannot pull historical Apple Health data; only data logged after the connection can sync in supported inbound categories.

That documented direction may fit when MyFitnessPal remains your primary food log and Health is simply a destination. It does not support expecting a meal created elsewhere to appear in the MyFitnessPal diary, preserving meal time downstream, or importing old Health history. The page does not establish the current subscription requirement, edit/delete lifecycle, or the exact Health records produced, so verify those in the current app before subscribing.

Lose It!: Food In Both Directions, No Historical Import

Lose It!‘s current support page says Apple Health syncing is available to all iOS users. Lose It! sends food, weight, and exercise to Health. It can also receive food from other apps when you grant permission to read Dietary Energy; imported food receives a heart icon in the log.

The important limit is history. Lose It! says it cannot import past entries or backdate the connection. Its page also puts some custom-goal categories, including protein, fat, and carbohydrates, behind Premium. The documentation does not spell out the exact structure of an outbound meal or what an edit does to an existing Health sample.

Cronometer: Broad Controls, But Do Not Assume All 95+ Nutrients

Cronometer documents selectable Apple Health read and write permissions. Its official permission image shows a long list of individual types, while the app settings include a switch for writing to Health. The same guide documents a calendar-based manual backfill when imported Health data is missing from the Cronometer diary.

That makes Cronometer worth inspecting when detailed nutrition is the goal. It does not justify the claim that every nutrient Cronometer tracks is exported in the current version or tier. Check Dietary Energy and the specific macro or micronutrient toggles you need, then inspect the resulting Health records.

MacroFactor: Daily Nutrition, Not A Second Food Log

MacroFactor’s integration guide says it can use Apple Health as an inbound source and export nutrition for another app to consume. It draws up to 30 days of history when an integration is connected.

Its model is deliberately summary-first. Imported nutrition is daily calories and macros on the Nutrition page, not food or meal entries. MacroFactor’s own manual estimate and food log also take priority over Apple Health nutrition for that day. The US App Store currently describes MacroFactor as a paid app with a trial and no permanent free tier.

This documented model may fit when a daily total is the useful input. It does not support expecting Apple Health to rebuild a detailed MacroFactor timeline.

Foodnoms: An Explicit Published Tier Split

Foodnoms says it writes nutrition from logged foods to Apple Health, but only writes nutrients that exist on the entry. A food with no sodium value cannot produce a sodium record. Entries made on Mac reach Health only after they sync to an iPhone, because the Mac cannot access Health directly.

The free plan is documented as export-only. Reading nutrition from other apps requires Foodnoms+. Imported entries appear beside foods in the Food Log, but Foodnoms says they must be deleted in the source app or Health, not from Foodnoms.

That is unusually clear documentation. It still does not establish current timestamps, every exported field, or how a changed source meal is replaced. Those remain five-minute-test questions.

Amy Food Journal: The Publisher’s App, With Less Public Detail

Disclosure: I created Amy Food Journal and have a financial interest in it.

Amy’s public site shows an Apple Health connection, and its App Store listing was at version 1.74 when rechecked August 23, 2026. The version history includes earlier notes about water syncing, Health reliability, and duplicate-prevention changes. Those are product claims, not independent results. The public pages do not currently publish a read/write field matrix, history policy, or tier-specific Health contract.

That means Amy cannot be the sync-first recommendation in this guide. Consider it when plain-language, Notes-like food logging is your primary need, then inspect its current Health authorization sheet and run the same test below. Ownership earns Amy more disclosure, not a lower evidence bar.

How Duplicate Nutrition Data Starts

Suppose Foodnoms and MyFitnessPal both have permission to write Dietary Energy. You log or copy the same lunch through both. You have now created the condition for two sources to contribute overlapping calorie samples.

Apple lets you inspect and reorder sources for a data type. Health prioritizes the source at the top when multiple sources contribute the same data type. That setting is not a documented command to delete the lower source’s records, and Apple does not promise automatic meal deduplication on that page.

Use this safer setup:

• Pick one primary nutrition writer.
• Let downstream apps read when they need the shared total.
• Turn off nutrition write access for an app that is only consuming data.
• Inspect Show All Data and Data Sources & Access before deleting anything.
• Treat calories, protein, carbohydrates, fat, water, weight, and activity as separate permission decisions.

Changing source priority can change which source Health uses first. It does not tell you whether an old sample survived an edit, whether deletion propagated, or whether two apps wrote the same meal with different timestamps.

Run This Five-Minute Test Before You Commit

Official documentation should narrow your shortlist. Your phone should make the final decision.

1. Name the job. Write down “app to Health,” “Health to app,” or “both,” plus the exact fields you need.
2. Grant the minimum access. Start with Dietary Energy and the macros you actually use. Leave unrelated activity, weight, sleep, and clinical categories off.
3. Create one distinctive test entry. Use a real food entry with an easy-to-recognize calorie value and meal time. Save the app version and tier.
4. Inspect Health, not just the graph. Open Dietary Energy, choose Show All Data, and open the individual record. Check value, time, and source. Repeat for protein, carbohydrates, and fat.
5. Edit, then delete. Confirm whether the old value is replaced, left beside the new value, or remains after deletion. Do not assume a changed daily total means the individual record disappeared.
6. Test reading separately. If you need Health-to-app import, add one temporary manual Dietary Energy record in Health. See whether it appears as a food, a daily total, an adjustment, or nothing.
7. Check a second writer. Before connecting another food app, turn off its nutrition write access unless you intentionally want it to contribute records.

Use a temporary entry and remove only the records you created. Do not experiment by deleting a real Health history.

Build A Shortlist From The Documentation

Investigate Foodnoms when you want a clearly documented Apple-first split: free export and paid import. Investigate Lose It! when documented food transfer in both directions matters more than historical import. Keep MyFitnessPal on the shortlist when one-way meal-summary export is enough and you do not need synced meal timestamps.

Investigate MacroFactor when daily calories and macros are the useful coaching input, not meal reconstruction. Put Cronometer on the shortlist when granular nutrition controls and manual backfill matter, but verify its current field toggles before assuming nutrient breadth. Consider Amy for its plain-language logging workflow only after its less-specific public Health claims pass the same test.

If Health integration is secondary, compare the broader calorie tracker guide. If a permanent free workflow matters more than bidirectional sync, use the free calorie tracking apps with no subscription guide.

The Real Decision

A dependable Apple Health setup is usually not the app with the longest permission sheet. It is the setup with one clear nutrition writer, only the read access a second app needs, and records you can identify later.

Pick the data job first. Read the vendor’s contract. Then test one meal before trusting a month of history.

Frequently Asked Questions

Which calorie tracker syncs best with Apple Health?

There is no defensible overall winner here because this guide did not run current device tests. Foodnoms publishes an explicit free-write/paid-read contract. Lose It! documents core food transfer in both directions. The right choice depends on whether you need export, import, historical data, detailed nutrients, or daily totals.

Does Apple Health calculate macros from Dietary Energy?

Do not assume it does. HealthKit defines Dietary Energy, protein, carbohydrates, and fat as separate data types. Confirm that the app writes each field you need.

Can Apple Health send food to MyFitnessPal?

MyFitnessPal’s official FAQ currently says no: food goes from MyFitnessPal to Health, not from Health to MyFitnessPal.

Can two calorie apps duplicate calories in Apple Health?

Two apps with write access can contribute records to the same nutrition type. Apple’s source-priority controls do not document automatic meal deduplication. Use one primary writer and inspect individual records when totals look wrong.

Does Apple Health preserve meal names and times?

HealthKit supports food objects and food-name metadata, but each app chooses what to write. MyFitnessPal explicitly says food timestamps do not sync. Verify the individual Health record for every app where meal identity matters.

Is Apple Health nutrition sync free?

It depends on the app and direction. Foodnoms documents export on its free plan and import with Foodnoms+. Lose It! says core Health syncing is available to all iOS users, with some custom data categories requiring Premium. Other help pages reviewed here do not publish a complete current tier contract, so check the in-app entitlement screen.