Mori: AI Calorie Counter and macro tracker for iPhone

Track macros by chatting.

Mori is an AI calorie counter for iPhone that works from a sentence. Tell it what you ate in plain language, skip the food database hunt, then review editable protein, carbs, fat, and calorie estimates.

Download on theApp Store iOS 26 or later. Subscription required; eligible annual plans include a 3-day trial.
Natural meal logging Plain language → clear macros
Mori logging eggs and sourdough toast in a conversational daily macro journal
Today
52gprotein
144gcarbs
15gfat
Nutrition is estimated honestly and stays editable.
See how it flows

No database hunt

Conversation first

Macros stay legible

Every estimate is editable

History becomes visual

Start with the real blocker

What is making
tracking hard today?

The right starting point depends on what broke down: memory, portions, trust in an estimate, protein visibility, or the app workflow itself. Pick the closest problem and start there.

00 / Why Mori

When normal calorie trackers
feel too heavy.

Mori is for people who want useful calorie and macro context without turning every meal into a database search project.

01

Start with the meal you remember.

Type “chicken bowl with rice, salsa, cheese, and half left” instead of searching duplicate entries. The no-database calorie tracker guide explains when that workflow helps.

02

Review the estimate before trusting it.

AI can miss oil, sauce, brands, cooked weight, and portions. Mori keeps the first estimate editable. Use the AI calorie estimate checker to compare macro math and hidden extras, then read the AI macro tracking guide for the deeper review order.

03

Choose the smallest workflow that sticks.

Text is not always the answer. Barcode, photo, voice, or a verified database can be better for some meals. Use the calorie tracker app fit checker before downloading another app.

01 / How it works

One sentence in.
A useful day out.

Mori turns the way you naturally describe food into a journal you can trust, understand, and correct.

01
You

Two eggs, sourdough toast, and a black coffee.

Logged: 17g protein, 26g carbs, and 11g fat.

Say what you ate.

No database syntax. No exact product hunt. Describe the meal like you would to a training partner.

02
17gProtein
26gCarbs
11gFat

See the estimate.

Protein, carbs, and fat lead. Calories stay available as useful context, without taking over the whole experience.

03
Portion 1.25×
Day recalculated

Make it yours.

Correct portions or ingredients whenever Mori’s first guess does not match the plate in front of you.

A more human way to log

Say it the way you remember it.

Food rarely arrives as a perfect database entry. Mori starts with your words, gives you useful context, and leaves the final say with you.

Try a sentence Live example
Mori’s first estimate

Two eggs, sourdough toast, and a black coffee.

17gProtein
26gCarbs
11gFat
278kcal
A thoughtful starting point. Always editable.
02 / Inside Mori

Built like a journal.
Not a dashboard.

The estimates stay legible. The experience stays calm enough to use every day.

Macro-first detail

The numbers that matter stay visible.

Protein, carbs, and fat sit at the center of the day. Progress is readable at a glance, with calories in their proper place.

  • Clear daily totals
  • Goal-based starting targets
  • Optional journal photos, not used to estimate nutrition
  • Quiet progress cues
Mori daily macro view showing protein, carbs, fat, and a meal conversation
Honest by design

Adjust any meal.

Portions, ingredients, and nutrition estimates remain under your control.

Mori meal detail view with portion adjustment and ingredient breakdown
A calmer vocabulary
No “good” foods.
No “bad” foods.
Just useful context.

Mori avoids moral labels and spreadsheet energy. It helps you see the day clearly, then lets you move on.

03 / Visual history

Your week,
remembered.

Pull back from the daily thread and meals become a visual atlas, an image-led record that is easier to scan, remember, and return to.

7days in view
14meals remembered
Mori visual meal atlas with image-led weekly food history
Tap any meal to return to its exact day.
04 / See it in motion

A food journal
that moves gently.

From a plain-language meal to an editable card and a visual week, the real Mori experience in thirty seconds.

05 / Learn and calculate

Useful before
you download.

Clear guides and free calculators for the questions that show up between meals.

You have not started tracking yet.

Log what you already eat for a week before changing anything, weigh only the dense foods, then set a target from your own baseline.

Read the starting guide

Work out what maintenance means for you.

Where the formula comes from, why the activity category moves the number so much, and how to treat the result as a starting assumption.

Read the maintenance guide

Get a starting estimate, and its range.

Mifflin-St Jeor resting energy plus an activity assumption, with the nearby category range so one dropdown click does not look like a fact.

Estimate TDEE

Check the formula against your own log.

Use 14 to 28 days of intake and a weight trend to see the maintenance your data implies, then compare it with the formula estimate.

Compare the two

Convert a calorie target into grams.

Enter calories per 100g from a label and see how many grams equal 100 Calories, 50 Calories, 200 Calories, or your own target.

Calculate grams for 100 Calories

Compare foods by calorie density.

See calories per gram, calories per 100g, and grams per 100 Calories so apples, rice, nuts, oil, and packaged snacks are easier to compare.

Compare calorie density

Convert a kilojoule label, then scale it.

Divide by 4.184 for kcal, then scale a per-100g or per-serving value to the amount you actually ate.

Convert kilojoules

Use kilojoules when the label does.

Estimate daily energy in kJ, compare it with Calories, and keep the Australian or New Zealand label basis visible before logging.

Estimate daily kilojoules

Convert food weight before logging.

Switch between ounces and grams for solid food weights, keep fluid ounces out of the math, and scale the nutrition entry cleanly.

Convert food weight

Find the higher-protein choice.

Compare foods by protein per 100 Calories and protein share of total calories, then copy a clearer Mori log note.

Compare protein density

Count the oil that left the bottle.

Grams, teaspoons, spray oil, measured pan leftovers, and servings, so a home-cooked batch does not quietly drift.

Calculate cooking oil

Split a homemade batch honestly.

Add ingredients, oil, and toppings, then divide by servings or by cooked weight when the portions are uneven.

Calculate recipe macros

Check the first estimate.

See where portion and hidden-ingredient errors enter, then use a quick review order before accepting the result.

Review AI estimates

Check the number before you save it.

Compare AI calories with macro math, then review portion, oil, sauce, drinks, toppings, labels, and uncertainty.

Open the estimate checker

Test the AI number against a better one.

Compare an AI estimate with a corrected or weighed reference and see the gap before reusing it as a repeat meal.

Test the estimate

Do not trust the photo alone.

Check a photo app or chatbot estimate for portion depth, hidden oil, sauce, mixed meals, and macro consistency.

Review the photo estimate

Ask for a better estimate.

Build a prompt that asks for assumptions, ranges, hidden ingredients, and a copyable Mori log sentence.

Build the prompt

Type the details AI cannot see.

Use portion, preparation, oil, sauce, label, restaurant, and uncertainty details before saving an AI estimate.

Write a better meal log

Choose the AI calorie tracker that fits.

Compare photo, text, voice, barcode, pricing, privacy, and editable estimates before downloading another tracker.

Read the app checklist

Find the protein workflow before you subscribe.

Test whether you need protein-only logging, macro context, labels, saved meals, or a lighter journal.

Run the protein fit checker

Weigh a meal once, then save it.

Turn one measured breakfast, bowl, coffee, or meal-prep lunch into a reusable Mori entry.

Save a repeat meal

Know what to type before you log.

Use meal-description examples, AI estimate review steps, and barcode/database fallback rules before choosing a text-based tracker.

Read the text-based guide

Pick a vacation tracking mode.

Choose full logging, rough estimates, a protein anchor, or a clean pause before the trip gets messy.

Plan the trip log

Find the hidden weekend gap.

Compare weekdays with weekends and check restaurants, drinks, snacks, late nights, and missing logs.

Audit the weekend

Went over calories today?

Log the day, compare the weekly context, avoid harsh compensation, and restart at the next meal.

Recover calmly

The deficit is not showing up yet.

Audit log completeness, scale averages, restaurant estimates, water-weight context, and maintenance assumptions.

Troubleshoot the plateau

Skip the food database hunt.

Use meal examples, edit checks, and app-fit questions for AI or text logging without scrolling duplicate entries.

Read the no-database guide

Do the quick math.

Convert macros to calories, resize a portion, or see an evidence-labeled protein range.

Open the calculators

Save the breakfast you keep rebuilding.

Calculate oats, yogurt, milk, protein powder, fruit, seeds, and toppings once, then edit the parts that change.

Calculate overnight oats

Track the bowl, toppings included.

Calculate yogurt, powder, fruit, granola, cereal, nut butter, seeds, honey, and other extras from your labels.

Calculate a yogurt bowl

Split the stack fairly.

Add mix, oats, yogurt, eggs, protein powder, oil, syrup, fruit, and toppings before saving the batch.

Calculate protein pancakes

Meal prep the tray.

Split eggs, egg whites, dairy, cheese, meat, vegetables, and oil into bites or breakfast servings.

Calculate egg bites

Wrap the batch math.

Add tortillas, eggs, egg whites, meat, beans, potatoes, cheese, oil, and sauce before freezing.

Calculate burritos

Split the bowl prep.

Calculate chicken, cooked rice, vegetables, beans, oil, sauce, and toppings per meal-prep bowl.

Calculate chicken bowls

Estimate the restaurant bowl.

Start with official menu defaults, then adjust rice, protein, beans, queso, guac, cheese, sour cream, and chips.

Calculate a Chipotle bowl

Log the Harvest Bowl clearly.

Use Sweetgreen's official nutrition default, then adjust leftovers, portion eaten, dressing, and add-ons.

Calculate Harvest Bowl calories

Split the cookie math.

Calculate a Crumbl whole cookie, half, quarter, weighed bite, leftover piece, or sampled box.

Calculate Crumbl calories

Make protein coffee easier to log.

Add powder, milk, creamer, syrup, sweetener, and toppings before saving a cleaner drink entry in Mori.

Calculate protein coffee

Estimate a 7 Brew drink honestly.

7 Brew publishes no nutrition. Build the cup from base, dairy, and syrup pumps, and get a range instead of false precision.

Estimate a 7 Brew drink

Compare the fall drink board.

Pick a 2026 Starbucks fall drink, then scale calories, sugar, macros, portion, and custom changes.

Compare fall drinks

Scale the Pumpkin Spice Latte.

Use the Starbucks PSL order-screen calories, then adjust the amount you drank and known custom changes.

Calculate a PSL

Log Pumpkin Spice Chai clearly.

Start with the current Starbucks value, then scale portion, count, sugar, macros, and custom changes.

Calculate pumpkin chai

Keep the cold foam visible.

Start with Starbucks' Pumpkin Cream Cold Brew value, then scale the cup, syrup, foam, and portion.

Calculate cold brew

Log the new fall espresso.

Use the Starbucks value, then scale oatmilk, brown sugar, pumpkin cold foam, and the amount finished.

Calculate shaken espresso

Make the next entry smaller.

Use repeat meals, honest estimates, and scheduled reviews so food logging stays useful after a missed day.

Reduce logging friction

Keep protein visible without a diet scoreboard.

See when a protein-only log is enough, when calories still matter, and how to keep tracking calm.

Read the lighter workflow

Creatine moved the scale.

Separate an early water-related change from fat gain, training progress, and the longer trend.

Read the scale clearly

Your cycle changed the number.

Put the weigh-in beside body water, bloating, digestion, appetite, and your own repeated pattern.

Track the pattern
06 / Clear by default

Estimates,
not magic.

Mori makes a thoughtful first estimate, tells you what it means, and keeps correction close at hand.

Read the privacy policy Use the private tracker checklist Check what no account means See the method and sources
01

Your journal is stored on your device.

Meal history is stored locally. When you ask Mori to analyze a meal, your text plus current and recent journal context is securely processed off-device to produce the response.

02

No account or password.

Mori does not ask for your name or email. It uses a random install identifier to associate onboarding preferences with your installation.

03

No moral labels.

Nutrition is context, not judgment. Mori is a wellness journal, not a medical device.

Mori Pro

More room
for the whole picture.

Mori Pro is required to use the journal after onboarding. It includes AI meal analysis, generated meal artwork, and the complete visual atlas.

Your next meal can be the easy one

Say the meal. Keep the day.

Open Mori, describe what you ate, and get back to living. Requires iOS 26 or later.

No account required Local journal with disclosed AI processing Every estimate stays editable
Get MoriAvailable on iPhone