Macros, Explained for People Who Just Want Dinner

What protein, carbs and fat actually do, why the numbers are always estimates, and how much precision is worth chasing.

Macro tracking has picked up a lot of cultural baggage — spreadsheets, digital scales, a certain kind of intensity. Underneath that, the actual concept is simple and genuinely useful, and you can get most of the benefit without any of the intensity.

Here is the plain version.

What the three things are

"Macros" is short for macronutrients: the three components of food that supply energy.

MacroEnergy per gramMainly doesFound in
Protein~4 kcalBuilds and repairs tissue; keeps you fullMeat, fish, eggs, dairy, pulses, tofu
Carbohydrate~4 kcalPrimary quick energy sourceGrains, bread, pasta, rice, fruit, potatoes
Fat~9 kcalHormones, absorbing vitamins, satiety, flavourOils, butter, nuts, cheese, oily fish

Calories are not a fourth thing. They are the total of the other three. If you know the grams, the calorie figure is arithmetic.

That relationship is the main reason tracking macros tells you more than tracking calories alone. Two 600-calorie dinners can behave completely differently depending on how those calories split. The one with forty grams of protein will keep you full in a way the one with six will not.

Why the numbers are always estimates

This is the part most guides skip, and skipping it is what makes people chase a precision that does not exist.

Every macro figure you have ever seen — on a packet, in a cookbook, in an app — is built the same way: match each ingredient to a food composition database, scale by quantity, add up. The databases are good. The quantities are where it falls apart.

  • A recipe says "1 onion". Onions differ in weight by a factor of three.
  • It says "a drizzle of oil". How much ended up in the food rather than left in the pan is unknowable.
  • Two chicken breasts of identical weight can differ meaningfully in fat.
  • Cooking drives off water and renders out fat, changing the per-gram figures.

None of this is a flaw in tracking. It is just the actual resolution of the instrument. Anyone quoting your dinner to the nearest calorie is quoting noise. This applies equally to any app that computes macros for you, ours included.

The numbers are a compass, not a tape measure. Useful for direction. Not for millimetres.

How much precision is worth it

It depends entirely on what you are doing, and most people aim far higher than their goal requires.

If you want to eat a bit better

You do not need to track at all. You need to notice. Log for a week or two, look at the pattern, stop. Almost everyone finds the same two things: less protein than expected, and one or two meals doing most of the work. That is the insight. It does not require a fourth week of logging.

If you have a specific body composition goal

Consistency matters more than accuracy. If you estimate the same way every day, your errors are roughly constant, and the trend is still correct — which is the thing you are actually steering by. A consistently-wrong number that moves in the right direction is more useful than an occasionally-perfect one.

If you are managing a medical condition

Follow the guidance you have been given by a professional. Carbohydrate counting for diabetes, for instance, has requirements that general advice does not cover, and this article is not a substitute for it.

The one number worth attention

If you only look at one macro, make it protein. It is the one most people are short on, it is the most satiating per calorie, and it is the hardest to accidentally over-eat.

A practical check without any arithmetic: does every meal have an obvious protein source? Not a trace — an actual component. Eggs, meat, fish, dairy, pulses, tofu. A surprising number of meals that feel balanced turn out to be carbohydrate with a garnish.

Carbohydrate and fat mostly take care of themselves once protein is anchored, because there is only so much room left on the plate.

Practical habits

  • Log the meal, not the ingredient. Once a dish is in the system, reuse it. Most people rotate through a small number of dinners.
  • Estimate consistently. Pick a mental size for "a portion of rice" and use it every time.
  • Weigh the dense things if you weigh anything. Oil, nuts, cheese, peanut butter. Errors there cost far more than errors on vegetables.
  • Do not chase the daily number. Look at the week. A single day tells you almost nothing.
  • Stop when it stops teaching you. Tracking is a measuring exercise, not a permanent condition.
Where Gurt fits

Gurt AI computes the macro breakdown for every recipe it generates, so the arithmetic disappears. The numbers are estimates, for exactly the reasons above — we would rather say that plainly than imply a precision the underlying data does not support.

What they are good for is noticing patterns across a week, which is where the useful information actually lives.

The short version

  • Three macros: protein, carbohydrate, fat. Calories are their total, not a separate thing.
  • Every number is an estimate. The databases are fine; the quantities are the problem.
  • Consistency beats accuracy for any goal you are steering by trend.
  • Protein is the one worth watching.
  • Track to learn something, then stop.

None of this needs to be complicated, and it should not take over your cooking. If deciding what to cook is the harder problem, that is a separate method.