Key takeaways
- There is no single calorie count for every steak.
- Compare entries in the same cooked and trimmed state.
- Weigh edible cooked meat rather than bone-in package weight.
- Sauce, butter and sides belong in the complete meal calculation.
What Steak Calories Really Means
Steak calories are the food energy in a defined amount of a defined beef cut. A 100-gram cooked ribeye entry that includes separable fat is not directly comparable with a raw lean-only sirloin entry, even when both are casually called steak.
A useful answer begins by naming the exact cut and the state in which it is measured. Raw and cooked weights are not interchangeable because cooking usually removes water and some rendered fat. A cooked 100-gram sample therefore represents a different starting amount of beef than 100 grams raw. Bone, separable exterior fat, marinades and sauce create additional differences that a single restaurant estimate cannot resolve.
This guide uses practical kitchen measurements and identifies where a number is sourced rather than presenting one universal value. For example, USDA FoodData Central lists cooked Choice top sirloin with lean and fat at about 219 kcal per 100 g, while cooked Choice strip with lean and fat is about 275 kcal per 100 g. Treat the figures as comparison tools for planning; use the package label or a verified database entry for the exact product you actually eat.

The Useful Comparison
| Cooked beef reference | kcal per 100 g | Protein per 100 g | What the entry includes |
|---|---|---|---|
| Top sirloin, Choice, broiled | 219 | 29.0 g | Lean and separable fat |
| Tenderloin, Choice, grilled | 217 | 30.2 g | Lean and separable fat |
| Top loin strip, Choice, grilled | 275 | 25.7 g | Lean and separable fat |
| Flank, Choice, broiled | 194 | 27.8 g | Lean only |
| Ribeye, Choice, grilled | 285 | 23.9 g | Lean and separable fat |
Choose the cut you enjoy, then control the variable that changes the plate most directly: the edible cooked portion. The table is a starting point, not permission to ignore the steak in front of you. Fine marbling, the amount of separable fat eaten, final doneness and any oil or butter retained on the surface can move a real serving away from a reference entry.
When comparing cuts, hold the serving weight constant. When comparing meals, include the complete plate. Rice, potatoes, dressing, sugary glaze, butter and restaurant portions may contribute more variation than the difference between two lean steak cuts. For anatomy and buying terminology, begin with the steak-cuts directory before choosing a cooking method.
Record the cooked weight
Weigh the edible cooked portion after bone and discarded hard fat are removed. That creates a repeatable denominator and prevents package weight from masquerading as the amount served.
A Repeatable Planning Method
For home tracking, choose a matching FoodData Central description, note whether separable fat is included, cook normally and weigh the edible result before sauce. Build the plan before the pan gets hot. Portion the raw steak, prepare the sides, decide which ingredients will be stored separately and label containers if more than one meal is being assembled.
- Match the cut: Select a database entry with the same muscle, grade when known, cooked method and lean-only or lean-and-fat state.
- Measure edible meat: Remove bone and anything not eaten, then weigh the cooked serving in grams.
- Scale the value: Divide grams by 100 and multiply by the database value; round to a useful whole number.
- Add the plate: Account separately for retained oil, butter, sauce, potatoes, rice, bread and dressing.
- Keep uncertainty visible: Restaurant steaks and mixed dishes justify a range rather than a falsely exact number.
Dry cooking can concentrate calories per 100 grams because the steak loses water; it does not create energy from nothing. Added cooking fat counts only to the extent it remains in the served food. Time-per-side charts cannot account for thickness, starting temperature, cookware or burner output. For whole steaks, insert an instant-read thermometer from the side toward the coolest lean center, avoiding bone, large fat pockets and the cooking surface.
Keep culinary preference and safety distinct
USDA FSIS advises 145°F followed by at least a three-minute rest for whole beef steaks. A recipe may describe another culinary target, but it should not present preference as the official safety endpoint. See the steak temperature guide for probe placement and carryover context.
Serving, Storage and Reheating
A three-ounce cooked serving is about 85 grams; multiply a per-100-gram value by 0.85. A six-ounce cooked portion is about 170 grams, so multiply by 1.70. Slice only what will be eaten immediately when possible. A larger intact piece loses less moisture in storage than a pile of thin slices, while a strongly grained cut still needs to be carved across its fibers before serving.
Store the steak and calorie-dense finishing sauce separately when practical so the next portion can be weighed and dressed deliberately. Cool cooked food promptly in shallow containers and keep wet sauce away from crisp greens, toasted toppings and roasted potatoes. Reheat only the portion needed. Gentle covered heat, a brief warm sauce bath or adding thin steak slices to an already-hot bowl usually protects the center better than repeating the original hard sear.

For a complete cooking workflow, continue with the how-to-cook-steak guide. If the plan is built around composed dinners, the steak dinner ideas hub connects bowls, salads, skillet meals and make-ahead options without turning closely related searches into competing pages.
Common Mistakes and Better Decisions
| Mistake | Why it fails | Better decision |
|---|---|---|
| Using bone-in package weight | Bone is not eaten | Weigh the edible cooked portion |
| Mixing raw and cooked values | Water loss changes the per-100-g concentration | Use one state consistently |
| Ignoring separable fat | Lean-only and lean-and-fat records answer different questions | Match what was actually eaten |
| Counting the steak but not the sauce | The plate total becomes incomplete | Track major additions separately |
Most disappointing results come from an undefined measurement or a sequencing problem. Decide whether the goal is a nutrition comparison, a dry rub, a pan sauce or a stored meal; then measure the variables that actually control that result. Adding more seasoning cannot correct an overcooked center, and a precise database number cannot repair an unweighed restaurant portion.
Keep a short cooking note with cut, raw and cooked weight, thickness, cooking surface, pull temperature and final yield. On the next attempt, change one variable rather than all of them. This is faster than chasing a new minute-per-side rule and produces information that belongs to your own equipment and preferred portion size.
The Bottom Line
Steak calories change with cut, trim, cooked yield and portion size. The sound comparison uses the same cooked state and weighs the edible serving. Choose the cut you enjoy, then control the variable that changes the plate most directly: the edible cooked portion.
Use exact labels, measured edible portions and controlled cooking as the foundation. Keep claims narrow enough to support with visible evidence, and treat sauce, sides and storage as part of the result rather than afterthoughts. That framework remains useful even when a product, cut or serving size differs from the examples on this page.
Continue Through This Steak Topic
Build the full picture: Ribeye Steak Calories, and Steak Protein cover the closely related cuts, methods, buying decisions and recipes that support this guide.
When you need to compare across families or techniques, continue with Lean vs Fatty Steak, Best Steak for Meal Prep, and steak cuts. These pages answer adjacent questions without forcing every detail into one overgrown article.
Frequently Asked Questions
How many calories are in 100 grams of steak?
The examples in this guide range from about 194 to 285 kcal per 100 g cooked, but the correct value depends on cut, trim and database description.
Does cooking steak add calories?
Cooking commonly removes water and may render fat, changing calories per 100 g. Added oil or butter contributes only if retained and eaten.
Should I weigh steak raw or cooked?
Either can work if the database entry matches that state. Cooked weight is often easiest for portioning the edible serving.
Sources & further reading
- USDA FoodData Central — Beef top sirloin, Choice, cooked, broiled, lean and fat — Foundation food record used for the 219 kcal and 29.0 g protein per 100 g comparison.
- USDA FoodData Central — Beef tenderloin, Choice, cooked, grilled, lean and fat — Foundation food record used for the 217 kcal and 30.2 g protein per 100 g comparison.
- USDA FoodData Central — Beef top loin strip, Choice, cooked, grilled, lean and fat — Foundation food record used for the 275 kcal and 25.7 g protein per 100 g comparison.
- USDA FoodData Central — Beef flank, Choice, cooked, broiled, lean only — Foundation food record used for the 194 kcal and 27.8 g protein per 100 g comparison.
- USDA FoodData Central — Beef ribeye, Choice, cooked, grilled, lean and fat — Foundation food record used for the 285 kcal and 23.9 g protein per 100 g comparison.
- USDA FSIS — Safe Minimum Internal Temperature Chart — Official guidance for whole beef steaks: 145°F followed by at least a three-minute rest.




