Health · Community report
Turn a food photo into logged macros
@Damien_Ducate says Muse helped build an iOS Shortcut that turns a food photo into calories and macros logged in Apple Health, and debugged it with them step by step when it broke. How accurate the estimates were is not said, so check a few against labels before relying on it.
What you can get
What it is
iOS Shortcut build and Apple Health logging
A working iOS Shortcut that takes a food photo and logs estimated calories and macros into Apple Health, with you reviewing the setup and any estimate before relying on it.
It came back right when
- The Shortcut takes a photo and produces calorie and macro estimates.
- Those estimates are logged into Apple Health correctly.
- You've tested it against at least one known food.
- Apple Health permissions match only what the Shortcut needs.
The checks are editorial, not from the source.
- Choose the estimation service
Agreed and explained before building starts.
- Build the Shortcut
Photo capture, estimate, and Apple Health logging chained together.
- Test against known foodsStops for your approval
Compare estimates to labels or a trusted tracker.
- Review permissionsStops for your approval
Apple Health access scoped to what's needed.
Editorial, not from the source
Works when
- You already log food in Apple Health and want the photo step automated.
- You're willing to test and calibrate the estimate rather than trust it blindly.
- You're comfortable debugging a Shortcut with the agent if something breaks.
Does not work when
- You need clinically accurate macro counts; a photo estimate won't give you that.
- You don't use Apple Health or a compatible tracker.
- You want it working perfectly on the first try with no testing.
Turn a food photo into logged macros: review template
| Item | What it is based on | Status |
|---|---|---|
| [Estimation service] | [Agreed with you before building] | [Confirmed] |
| [Test results] | [Comparison against known foods] | [Pass / needs calibration] |
| [Apple Health access] | [Shortcut's permissions request] | [Reviewed and scoped] |
The source case
On X, @Damien_Ducate reports, among several other uses, that Muse helped them build an iOS Shortcut that takes a food photo and turns it into calories and macros logged straight into Apple Health, and that when the shortcut broke, Muse debugged it with them step by step until they found the bug. The post doesn't say which service estimates the calories and macros from the photo, how accurate the estimate was, or how long the shortcut took to build. It is an individual report, checked on 2026-10-09, not evidence that this shortcut will work the same way for another reader's phone or diet-tracking setup.
A public report by someone outside this library. Not independently reproduced here.
From the source
Source excerpt
It helped me build an iOS Shortcut that goes from a food photo → calories and macros → straight into Apple Health. And when it broke, it debugged it with me step by step until we found the bug.
Quoted from the original posts. Not written by this guide, and not a result produced here.
Suggested prompt
Bring An iPhone with the Shortcuts app and Apple Health, A sense of which foods you'll use to test accuracy. Acts Builds an iOS Shortcut that connects a photo-to-macro estimate with Apple Health. Debugs the Shortcut with you if it breaks. Does not log estimates into Apple Health beyond what the Shortcut's reviewed permissions allow. Source community report, checked 2026-10-09.
Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.
Other ways to ask
Editorial rewrites of the brief above, for a different emphasis. Copy them separately.
What you need
Editorial, not from the source
You supply
- An iPhone with the Shortcuts app and Apple Health
- A sense of which foods you'll use to test accuracy
Connected
- Shortcuts app
- Apple Health
- Whatever photo-to-macro estimation service the agent proposes, for you to approve
Approved by you
- Your review of what the Shortcut can read and write in Apple Health
- Your approval of the estimation service it proposes to use
How to try it
Editorial, not from the source
- Tell the agent you want an iOS Shortcut that takes a food photo, estimates calories and macros, and logs the result into Apple Health.
- Have it build the Shortcut, including whatever service it uses to estimate the macros from the photo, and explain that choice to you.
- Test it on a few known foods and compare the logged numbers against labels or a tracking app you trust.
- If it breaks, as happened in the report this page is built on, work through the debugging with it rather than rebuilding from scratch.
- Review the final Shortcut's permissions in Apple Health before relying on its logs.
Decide what the Shortcut should connect
This task links three things: a photo taken on your phone, a service that estimates calories and macros from that photo, and Apple Health, where the result gets logged. Before any building starts, have the agent name which service it plans to use for the estimate and explain, in plain terms, how that service turns a photo into numbers. Different services vary in how they handle mixed plates, portion size guessing, and branded packaged foods, and knowing which one is in use matters if the numbers ever look wrong later. Treat the choice of estimation service as a decision you're making, not a detail to skip past, since swapping it out later could shift your logged history in ways that are hard to untangle afterward.
Test before you trust it
A photo-based macro estimate is a guess, and guesses need calibration. Once the Shortcut is built, run it on a few foods you already know the numbers for, such as something with a nutrition label or a meal from an app that already tracks macros accurately, and compare the Shortcut's output against those known values. If the estimate is consistently off in one direction, that's useful to know going forward, and it's better to find that out on a test case than to discover it weeks into relying on the log for your eating decisions. This step is the difference between a fun automation and one you can actually use for tracking.
Debugging is part of the deal
The report this page is built on describes the Shortcut breaking at some point and being debugged step by step rather than scrapped and rebuilt. iOS Shortcuts that chain a camera, a third-party estimation service, and Apple Health have several points where something can go wrong, from a permissions prompt to a service's response format changing. When that happens, work through it with the agent rather than assuming the whole approach has failed. Before any of this, though, review exactly what access the Shortcut has in Apple Health, since a shortcut that can write data should be scoped to only the categories it actually needs, such as dietary energy and macros, not your full health record.
Open Muse to try it. That is the product's own site; this guide is not part of it.
Limits and confirmation points
Limits to confirm
- One attributed report. It names no estimation method, accuracy, or build time, and does not show the Shortcut will work the same way on another phone or account.
- Macro estimates from a photo are approximate. This isn't medical or nutritional advice, and the numbers should be checked, not trusted outright.
- Apple Health permissions need to be reviewed by you; the agent can set up the Shortcut but shouldn't be given broad access without your review.
- The report describes one bug found by debugging together; other issues may need the same back-and-forth rather than a one-shot fix.
Stop and check
Editorial, not from the source
- Before building: agree on which estimation service or app it will use.
- Before relying on it: test against known foods and compare the numbers.
- Before granting access: review what the Shortcut can read and write in Apple Health.
If it goes wrong
Editorial, not from the source
- The Shortcut breaks or stops logging
- Debug it step by step with the agent, as described in the report this page is built on, rather than assuming it's unfixable.
- The macro estimate looks off
- Compare it against a label or a tracking app you trust, and treat the photo estimate as a starting point, not a final number.
- Apple Health asks for more access than expected
- Review the permissions request and limit it to what the Shortcut actually needs to log calories and macros.
Common questions
Can Muse build a Shortcut that logs food photos as macros?
One user reports it built one that turns a food photo into calories and macros logged in Apple Health, and debugged it with them when it broke. This is an individual report and this directory has not reproduced it.
How accurate is the macro estimate?
Not stated in the report. Treat any photo-based estimate as approximate and test it against known foods before relying on it.
What happens if the Shortcut breaks?
In the report this page is built on, the agent debugged it step by step with the user until the bug was found. Expect some back-and-forth rather than a guaranteed one-shot fix.
Does this require any special health knowledge?
No, but this isn't nutritional or medical advice either. It's a build-and-log task; what to do with the numbers is up to you.
What access does the Shortcut need in Apple Health?
Only what it needs to log calories and macros. Review the requested permissions before approving them.
Next
Related to this task
More in Health
Similar tasks
Get recurring task recommendations — ask your own agent to check for relevant updates.