Skip to content
Guides10 min read

MacroFactor vs Cronometer: Recipe Changes and Past Logs

Compare MacroFactor and Cronometer recipe edits, copies, retirement and deletion, with practical examples of what changes in past food logs.

k

kcalm editorial team

Prepared with AI assistance

Food being prepared in a kitchen
Food being prepared in a kitchen

MacroFactor vs Cronometer recipe changes have different consequences for past food logs. MacroFactor preserves previously logged entries when you edit a saved recipe. Cronometer documents ways to copy, retire and delete recipes, while its staff guidance describes an option to update past entries when editing an original. The useful first distinction is whether you are recording a new batch or correcting an old mistake. [1] [2] [3]

This public-documentation review is dated 16 November 2026 (Australia/Sydney). It is not a hands-on account test. kcalm publishes this comparison and makes a competing calorie-tracking app. The recipe numbers below are hypothetical arithmetic, not measured app outputs, dietary targets or laboratory results.

How do MacroFactor vs Cronometer recipe changes affect history?

MacroFactor recipe edits apply to future logging while preserving existing entries. Cronometer offers several recipe-management actions with different consequences, including a documented distinction between retiring a recipe and deleting its diary history. Its older staff replies also describe a choice about updating previous entries. [1] [2] [3]

ActionMacroFactorCronometer
Edit a saved recipeExisting logged entries remain unchanged [1]Staff guidance describes an option to update past entries [3]
Keep two variationsDuplicate the recipe [4]Create a copy from recipe settings [5]
Correct an already logged recipe compositionEdit the base recipe, then remove and relog the affected entry [1]Historical-update option described by staff; check the scope before saving [3]
Remove an obsolete recipe from the libraryRetire behaviour not established by the sources reviewedRetire removes it from the foods list and keeps diary entries [2]
Delete the saved recipeHistorical effect not established by the sources reviewedDeletion removes the recipe and its diary history [2]
“Not established” means this review has no verified answer for that action. It does not mean the app lacks it. In particular, an editing rule is not evidence of what a deletion command does.

The Cronometer mobile and web recipe manuals were updated in June 2026. Both describe retirement and deletion. The historical-update explanation comes from named Cronometer staff replies dated 2020 and 2021; the current manuals reviewed do not spell out that save-dialogue behaviour. Treat the exact current wording and platform coverage as unverified. [2] [3] [5]

Is your recipe change a new batch or a correction?

A new batch represents food made differently today; a correction repairs information that was wrong when you logged an earlier meal. That distinction determines which dates you intend to change, even before you choose an app command.

Imagine you make a lentil bake every Sunday. This week you use a different yoghurt topping and more tomato sauce. Last week's entry can still be an accurate description of last week's bake. Renaming today's version “Lentil bake, 16 November” gives you a clear way to recognise it later.

Now imagine you discover that the original recipe listed 100 g of an ingredient when you actually used 200 g. That is a historical recording error if the same mistake affected the earlier batch. You may want to revisit those particular entries, using the original package or cooking notes where available.

The distinction also applies to portions. NIDDK defines a portion as the amount you choose to eat and a serving as the amount listed on a food label. Your portion can differ from that reference amount. A smaller bowl today does not necessarily require a new recipe: it can simply mean a different amount of the same food. [6]

For ingredient-import problems, our recipe importer comparison covers matching and serving corrections before a recipe reaches your diary.

Food being prepared in a kitchen
Food being prepared in a kitchen

What does a recipe revision change in calorie terms?

A recipe revision changes the calculated energy for a portion when the batch energy, portion count or weight relationship changes. In this hypothetical example, increasing a four-portion batch from 1,600 to 1,800 kcal changes each equal portion from 400 to 450 kcal, a 12.5 percent increase.

These are invented totals chosen to make the arithmetic visible. Both batches are assumed to weigh 1,200 g, approximately 42.3 oz. Each equal portion weighs 300 g, approximately 10.6 oz. Kilojoules are calculated as kcal multiplied by 4.184 and rounded to whole numbers.

Hypothetical recordBatch energyEqual portionsEnergy per portion
Original batch A1,600 kcal / 6,694 kJ4400 kcal / 1,674 kJ
New batch B1,800 kcal / 7,531 kJ4450 kcal / 1,883 kJ
Difference, B minus A200 kcal / 837 kJSame portion count50 kcal / 209 kJ
Batch B divided into five1,800 kcal / 7,531 kJ5360 kcal / 1,506 kJ
The final row changes the meaning of “one portion”. Five equal portions of the same 1,200 g batch weigh 240 g each, approximately 8.5 oz. It does not describe the same 300 g bowl suddenly containing less energy.

Here is the history consequence as arithmetic: if three old 400 kcal entries were replaced with 450 kcal entries, the recorded total would rise by 150 kcal, or 628 kJ. Spread across a seven-day average, that is approximately 21 kcal, or 90 kJ, per day. Nothing about the food already eaten changes; only the record does.

This calculation does not reproduce either app's algorithm or predict a target adjustment. It shows why an old total can move after a data correction. For a separate portion-entry calculation, see our serving size error guide.

How can you keep both recipe versions available?

Keeping two named recipe versions lets you choose the batch you actually ate without relying on memory. MacroFactor documents a Duplicate command, and Cronometer's web recipe manual documents creating a copy through the settings menu. [4] [5]

MacroFactor's route depends on the food logger layout. In the speed layout, open the recipe and select Duplicate. Its context layout reaches duplication through the plate's recipe details. The duplicate opens in the creation workflow, where you can change ingredients and give it a distinct name. [4]

Cronometer's web settings menu offers a recipe copy, and its mobile diary menu lists Edit a Copy of Recipe alongside Edit Recipe, Adjust Recipe and Explode Recipe. Those are separate actions; a similar-looking menu label is not a guarantee that they have identical effects. [5] [7]

A practical naming system can be very simple: “Lentil bake, original” and “Lentil bake, yoghurt topping”. Dates help when ingredients vary every batch. You can use the same names on freezer labels so the food container and the recipe list tell the same story.

Consider this sequence for a new batch:

  1. Identify the saved recipe that most closely matches what you are making.
  2. Create a duplicate or copy when you want both versions available.
  3. Give the new version a name you can distinguish at a glance.
  4. Check the ingredient amounts and the serving definition.
  5. Compare the displayed total with your notes before logging your portion.
  6. Reopen one earlier entry if preserving that record was your intention.

This is an organisational workflow, not a claim that every batch needs meticulous versioning. Two names may be enough for a regular breakfast; more detail can help when several freezer batches coexist.

Which details are worth checking before saving?

The most useful recipe checks are the ingredient identity, quantity, label basis and portion definition. Preserving a historical entry keeps the information you entered; it does not independently verify the food composition or the amount you ate.

For a packaged ingredient, check whether the figures refer to one serving or the whole package. The FDA's example shows 280 kcal for one serving of lasagne and 560 kcal for two servings, approximately 1,172 and 2,343 kJ respectively. Its serving-size guidance also explains that a label serving is not an instruction about how much to eat. [8]

Database identity matters too. USDA FoodData Central distinguishes analytically derived Foundation Foods from manufacturer-supplied Branded Foods label information. Those are different kinds of evidence behind an ingredient entry. A familiar name alone is not proof that a result matches the product in your kitchen. [9]

For example, consider a hypothetical yoghurt label listing 120 kcal per 150 g serving. Entering those 120 kcal as though they applied to 100 g changes the calculated value of a 150 g portion to 180 kcal. That is a 60 kcal, or 251 kJ, difference created entirely by the reference amount. No recipe-history feature can identify that mistake just from the final total.

Keep the task bounded: compare the ingredient you changed, the batch total and the portion you logged. If all three match your intention, there is little value in repeatedly rewriting unrelated old meals. Our homemade meal calorie guide explains oil and cooking-yield questions separately.

A person using a smartphone
A person using a smartphone

What can you do if an old total changes unexpectedly?

An unexpected old total calls for checking the affected entry, its amount and the action you saved. Start with one identifiable meal and any notes you already have, rather than assuming every previous day changed in the same way.

Write down the date, recipe name, serving unit and visible energy total. Compare these with a screenshot or previous record if available. A changed quantity, a different recipe version and a changed ingredient are separate explanations to investigate.

Cronometer's older staff advice describes restoring a recipe's previous values and updating past entries again. That only offers a plausible reconstruction when you actually know the earlier values. It is not documentation of a universal undo button, and this review has not verified a current automatic version-history restore feature. [3]

If several batches had different compositions, one reconstructed recipe may not represent all of them. Consider asking support about the affected dates and action before making another broad edit. A short factual description is useful: “I changed this recipe on this date; these earlier entries now show a different total.”

Frequently Asked Questions

These frequently asked questions distinguish recipe-library changes from changes to individual diary entries. The answers reflect the documentation reviewed on 16 November 2026 (Australia/Sydney), with older support evidence identified where relevant.

Does editing a MacroFactor recipe change yesterday's entry?

MacroFactor says editing the base recipe leaves existing logged entries unchanged. Its documented method for applying a composition correction to an old entry is to remove that entry and log it again after editing the recipe. [1]

Can I hide a Cronometer recipe while keeping old meals?

Cronometer documents retiring a recipe for that purpose. Retirement removes it from the foods list while retaining diary entries. Deleting the saved recipe has a different documented result: removal of its diary history too. [2]

Does Cronometer ask before updating past entries?

Named Cronometer staff described a choice when saving recipe changes in older support replies. The current recipe manuals reviewed do not fully document the dialogue across platforms, so this guide does not promise exact wording on your device. [3]

Where is MacroFactor's recipe edit control?

MacroFactor's help directs you through the plus button and Recipes. The speed layout uses an Edit button; the context layout uses a swipe and pencil icon. Saving the edit updates future uses of that recipe. [10]

Is a changed calorie total evidence that I ate differently?

A changed record alone cannot establish that. In our hypothetical example, replacing three 400 kcal entries with 450 kcal entries adds 150 kcal to the diary even though the meals are already in the past. Check what changed in the record before interpreting the total.

Do I need a new recipe for every portion size?

A new portion size can be recorded as a different quantity of an existing recipe. Cronometer's mobile diary instructions include editing an entry's amount and serving size. Separate recipe versions are more useful when you want to distinguish different ingredient combinations. [7]

Sources

Sources include primary app documentation, identified vendor staff guidance and three government references for the nutrition-recording context. Government sources do not establish either app's software behaviour. All links were retrieved for this review on 16 November 2026 (Australia/Sydney).

  1. MacroFactor: recipe edits and food log history.
  2. Cronometer: mobile custom recipes, retirement and deletion.
  3. Cronometer staff replies: updating past recipe entries, 2020 and 2021.
  4. MacroFactor: duplicate a custom food or recipe.
  5. Cronometer: web custom recipe controls.
  6. NIDDK: food portions and recording what you eat.
  7. Cronometer: mobile diary editing.
  8. FDA: serving size on the Nutrition Facts label.
  9. USDA FoodData Central: data type documentation.
  10. MacroFactor: edit a custom recipe.

Ready to track smarter?

Log a meal with a photo or a few words. kcalm estimates calories and nutrients, so you can review the foods, portions and daily totals in one place.

Download on the App StoreGet it on Google PlayEligible trial offers and renewal terms appear before purchase.

Related articles