Macro tracker app: protein, carbohydrate, and fat without a cult

Published: 2026-08-25 · Updated: 2026-08-25 · 6 min read

Macros are grams of protein, carbohydrate, and fat that add up to energy. A tracker is useful when it sits on top of food you cook. Cook EZ builds those grams from USDA FoodData Central, Open Food Facts, and the recipes you generate, then lets you aim at splits from the macro calculator. This guide is the kitchen version: what to log, what to ignore, and how Cook Mode dinners become diary numbers.

Energy first, then the split

Protein and carbohydrate provide about 4 kcal per gram. Fat provides about 9 kcal per gram. Alcohol is about 7 kcal per gram and is not a macro people plan as carefully, which is how Friday disappears. If your calorie calculator puts TDEE at 2400 kcal (Mifflin-St Jeor plus activity, PubMed 2305711), a 30/40/30 protein/carb/fat split is a gram target, not a personality. The Dietary Guidelines for Americans still want a pattern with vegetables, fruit, grains, and protein foods. Hitting fat grams with fried snacks can satisfy the tracker and miss the pattern.

Protein gets the most internet noise. For a general adult, the Recommended Dietary Allowance is 0.8 g per kilogram of body weight, which is a minimum to prevent deficiency, not an athletic target. Many people who lift aim higher, often in the 1.6 to 2.2 g/kg range in sports-nutrition literature. Cook EZ will not pick your number. The macro calculator will let you set one. The diary will show whether dinner helped.

Carbohydrate is a bucket that includes fiber and sugars. The FDA Nutrition Facts label splits dietary fiber and added sugars on packaged food. A plate photo of a fruit bowl will not split added honey from fruit. Scan the granola. Weigh the banana. Be precise where the label exists.

Creatine, fiber supplements, and cooking spray still belong in the day if you care about the total. Spray oil is fat. Two seconds of spray is not zero. Weigh a spray on a plate once if you are arguing with the diary.

How Cook EZ gets the grams

A generated recipe lists ingredients with quantities. Nutrition on the card is a summed estimate from FDC-style entries plus any packaged items. Log servings eaten. If you cooked a four-serving dal and ate one serving, that is 25 percent of the pot, including the coconut milk that went in. If you skimmed the cream off the top and ate extra, edit the log. The card cannot see your spoon.

Barcodes attach OFF or cache data. Free to log. Fat in a yogurt varies by 0 percent, 2 percent, 5 percent, and Greek strained styles. Pick the row that matches the cup. The FDA label on the foil lid is the tie-breaker.

Plate photos assign items, then you slide grams. Fat error is usually oil. Protein error is usually the meat or the beans. Carbohydrate error is usually the rice, the tortilla, or the hidden sugar in the sauce. Put the effort on those three.

Weekly protein average beats a 9 p.m. scramble to hit a number with a powder you do not like. Generate tomorrow's dinner with 10 g more tofu instead. The tracker should change the grocery list.

Cooking changes the food, not the physics

Water leaves meat as it cooks toward a safe temperature. Poultry to 165 °F, per USDA Keep Food Safe. The cooked FDC entry already reflects typical yield. Logging raw grams as cooked food double-counts water or undercounts protein depending on the row. Match the state.

Oil enters the food. A tablespoon of olive oil is about 14 g of fat and about 120 kcal. Stir-fries, roasted vegetables, and pan sauces pick up oil that a "steamed broccoli" FDC row does not include. If the generate specified 15 ml of oil and you used 45 ml, the card is lying and you know it. Add 30 ml in the diary or edit the recipe for next time.

Carryover cooking after you pull a roast does not add macros. Resting redistributes juice. The FSIS leftover reheat to 165 °F also does not add macros. Reheating can drive off a little water, concentrating grams per bite. For home logging, ignore that concentration unless you are weighing freeze-dried backpacking food.

Setting targets you can cook toward

Use the calorie calculator for TDEE, then the macro calculator for a split that matches how you already eat. If you hate drinking protein shakes, do not set a protein target that requires two scoops. Generate high-protein dinners: chicken thighs, tofu, lentils, fish, Greek yogurt sauces. FoodData Central will show cooked lentils at a useful protein-per-kcal ratio. Use them.

Keto-style very low carbohydrate is a medical-adjacent pattern for some people and a fad for others. If you set carbs under 50 g, the generator must know that. Hidden carbohydrate in sauces and in "just a little rice" will blow the day. Read labels. The FDA added-sugars line matters. A keto generate that still includes honey in the marinade is a failed generate. Edit or reroll.

Guardrails: the app should not encourage extreme deficits. If a clinician set macros for diabetes, CKD, or sport, those numbers win. Cook EZ's tracker is a log. It is not a prescription.

Weeknight tactics that move the diary

Anchor protein on the board during mise en place. 150 to 200 g cooked meat, 200 g extra-firm tofu, or 250 g cooked lentils is a dinner-sized move for many adults. Then add a carbohydrate you can portion (rice, potato, tortilla) and a vegetable that takes oil you will measure. That plate is loggable without a philosophy.

Cook Mode timers keep the protein from drying out while you chase the vegetable. Dry chicken makes people add sauce. Sauce adds sugar and sodium. The better fix is a brine, a marinade, or pulling on temperature. A thermometer is a macro tool because it prevents the compensatory butter.

Leftovers: chill within 2 hours, 3 to 4 days in the fridge, per FSIS. Logging Tuesday's chicken on Thursday is still the same macros if the portion is the same. The tracker does not care about the day. Salmonella does. Reheat to 165 °F.

What people overfit

They weigh the spinach and eyeball the peanut butter. Reverse it. They log a banana and skip the latte. They argue about whether a fruit is "clean" while pouring 40 g of oil into a sheet pan. FoodData Central is calm about this. Oil is energy-dense. Spinach is not. Track the dense foods.

They copy a stranger's 40/30/30 split into a 5-foot-2 office worker body. TDEE does not care about the split until energy is in the right neighborhood. Get the calorie calculator close, then layer macros.

They trust a restaurant "macro bowl" PDF that assumes 4 oz of chicken when the kitchen served 8 oz. Photograph the plate. Slide the chicken. Ignore the PDF unless you have evidence.

Allergens and macros are different jobs

A whey protein that helps the protein target can be a milk-allergy emergency. A soy-based meat that helps the protein target can be a soy-allergy emergency. Generate with the allergy list on. Do not add a powder to hit a number if the powder is an allergen. The tracker will happily log a food that can harm you. That is not a software bug. It is a category error. You still read labels.

Wheat in soy sauce does not show up as a carbohydrate crisis. It shows up as an allergy crisis. AI can miss wheat in sauces. The macro line for "2 tbsp soy sauce" might be 10 kcal. The medical line might be an epinephrine story. Keep the banner on the recipe and the bottle in your hand.

If you use Open Food Facts via barcode, check the allergen tags on the product as well as the macros. Crowdsourced allergen data can lag a reformulation. The package in the kitchen is current.

Alcohol still counts on a macro day even when it does not sit in the protein column. Log the wine. The calorie calculator TDEE does not have a weekend exemption. Friday is included.

Weigh the oil into the measuring spoon before it hits the sheet pan. Generate a dinner that already lists 180 g of cooked tofu. Log the plate from the recipe's serving control. The tracker should follow the pan, not the other way around.

Questions

Do I need to hit macros exactly every day?

No. Weekly averages on protein and energy teach more than a 2 g miss at 10 p.m. Use the diary to steer the next generate, not to punish a banana.

Where do Cook EZ's macro numbers come from?

Recipe cards and search from USDA FoodData Central-style entries. Packaged food from Open Food Facts and labels. Your gram edits override the first guess.

Is barcode logging free?

Yes. Scanning a product into the diary does not spend a generate credit.

How do I set the split?

Use the macro calculator after you have a TDEE from the calorie calculator (Mifflin-St Jeor). Then cook toward the protein number with real food.

Sources

Cook it in Cook EZ

Photograph the dish or type the name. The app writes the recipe for your allergies, equipment, and time, then logs the plate if you want the calories.