How Many Calories Are In A 7 Oz Steak? | The Real Count

A 7-oz cooked steak lands around 350–600 calories, with lean cuts on the lower end and ribeye on the higher end.

“7 ounces of steak” sounds precise, yet calorie totals can swing a lot. A lean sirloin that’s trimmed well and grilled can sit hundreds of calories below a buttery ribeye seared in oil. Add a pat of butter, a creamy sauce, or a heavy restaurant baste and the number climbs again.

This article gives you a clean way to pin down your best estimate, plus a realistic range you can use when logging food. You’ll also see why two steaks that weigh the same can be far apart on calories.

What 7 ounces actually means on your plate

Seven ounces can describe either the raw weight you measure on a kitchen scale or the cooked weight you see on the menu. Those are not the same. Steak loses water as it cooks, so the cooked piece usually weighs less than the raw piece you started with.

If your steak is listed as “7 oz” at a restaurant, it often means the raw weight before cooking. If you weigh at home after cooking, your “7 oz” is the cooked weight. That difference alone can shift your calorie math, since nutrition databases list foods in specific forms (raw, cooked, broiled, pan-fried, and so on).

Raw vs cooked: a fast sanity check

A common home pattern looks like this: a steak that starts at 7 oz raw can drop to something closer to 5–6 oz after cooking, depending on doneness and how much fat renders out. If you only know the cooked weight, you can still estimate, you just need to match your database entry to “cooked” rather than “raw.”

Why steak calories vary so much

Steak calories come from protein and fat. Protein stays fairly steady cut to cut. Fat does not. A lean cut can be mostly protein and water. A marbled cut carries more fat, and fat packs more calories per gram than protein.

Cut and marbling

Ribeye, strip, and some chuck steaks are famous for marbling. Sirloin and tenderloin tend to be leaner. Two 7-oz steaks can look similar in size while hiding different fat levels inside the muscle.

Trim level and edge fat

Some steaks are sold with a thick fat cap. Some are trimmed close. If you eat the fat cap, you’re eating the most calorie-dense part of the steak. If you trim it off before cooking or leave it on the plate, your calories drop.

Cooking method and added fat

Grilling and broiling let rendered fat drip away. Pan-searing keeps more rendered fat in the pan, and many cooks add oil or butter for browning. Even one tablespoon of cooking fat can add a noticeable calorie bump to the final plate.

Doneness and moisture loss

As steak cooks longer, it loses more water. That makes the steak denser in calories per ounce even if the total calories in the whole piece stay close. So a well-done steak can show a higher “calories per 100 g” value than the same cut cooked rare, since there’s less water left.

How Many Calories Are In A 7 Oz Steak? Real-world ranges

If you want one practical number, start with this: a typical 7-oz cooked steak sits in the mid-hundreds of calories. Lean cuts often land in the mid-300s to mid-400s. Rich, well-marbled cuts can land in the 500s and can push higher with added fat.

The calorie ranges below are built from USDA FoodData Central calorie densities for cooked beef cuts, then scaled to a 7-oz (198 g) cooked portion. FoodData Central is the USDA’s public nutrient database used widely in nutrition analysis. USDA FoodData Central is the source base for the per-100-gram values used here.

One more detail: if you’re tracking from a packaged label or a chain menu, the printed calorie number can be rounded. U.S. rules allow calories to be declared in set increments, which can make two items look closer than they are. 21 CFR 101.9 nutrition labeling rules lays out how calories can be rounded for labels and labeling.

Use the table as a starting point, then adjust based on what you actually ate: fat cap, cooking fat, sauces, and sides.

Calories by cut for a 7-oz cooked steak

This table is meant for quick logging. It assumes you’re eating the steak itself, not the oil left in the pan, not a butter baste, not a creamy topping. If you add those, treat them as separate items and add them on.

Steak type (cooked)	Calories for 7 oz	Why it lands there
Tenderloin / filet, lean	340–430	Lower marbling, less fat eaten per bite
Top sirloin, trimmed	360–470	Lean-leaning cut, calories rise with remaining edge fat
Flank or skirt, trimmed	420–520	Moderate fat, often cooked hot, sometimes served with extra drippings
Top loin / strip	470–600	More marbling than sirloin, fat cap can add more
Ribeye	520–700	High marbling, fat renders yet a lot is still eaten
T-bone / porterhouse (edible meat only)	450–650	Mix of strip and tenderloin, bone changes the served weight math
Chuck eye or flat iron	480–650	Flavorful, often more fat than it looks
“Steakhouse” steak with butter baste	+100–250 add-on	Butter or oil clings to the surface and gets eaten

How to estimate your steak calories at home

You can get a close estimate in under two minutes with a scale and a simple method. The goal is not perfection. The goal is a number that is close enough to guide your daily intake without turning dinner into math class.

Step 1: Decide if your 7 oz is raw or cooked

If you weighed the steak before cooking, use raw entries in your tracking app. If you weighed it after cooking, use cooked entries. If you only have a restaurant menu weight, treat it as raw weight unless the menu says “cooked weight.”

Step 2: Pick the closest cut entry you can

Most apps let you choose “sirloin steak, cooked” or “ribeye, cooked.” Pick the cut first, then the cooking style if it’s listed. If you can only find one cooked entry, use it and move on. Getting the cut right usually matters more than micro-details like grill vs broil.

Step 3: Add what you cooked with

If you brushed the steak with oil, add the oil. If you basted with butter, add the butter. If you made a pan sauce with cream, add the cream. This is where tracking gets honest. Steak itself can be lean. The extras can be the bigger calorie source.

Step 4: Adjust if you left fat behind

If you trimmed a thick fat cap and did not eat it, you can shave your estimate down a bit. If you ate every crispy edge, keep the full estimate. This is the main reason two people can share “the same steak” and log different calories.

Restaurant steaks: why the number can jump

Restaurants are built on flavor, and flavor often comes from fat and salt. Steaks are commonly finished with butter, brushed with oil, or served with a rich topping. The menu may call it “garlic butter,” “herb butter,” or “au poivre sauce.” Those add-ons can add more calories than you’d guess by looking.

Portion naming can add confusion too. A menu may list a “7 oz filet” that is the raw weight. After cooking, you might get a smaller piece than you expect. Your calories are tied to the raw portion if you trust the menu spec, but your eye is judging the cooked piece. That mismatch makes people under-log.

Three quick cues that your steak is on the higher end

• It shines with a glossy layer on the surface after slicing.
• There’s a pool of buttery drippings on the plate that tastes like the steak.
• The cut is ribeye, strip, or a “chef’s cut” known for marbling.

Protein and fat: what a 7-oz steak brings

Calories are only one part of the story. A 7-oz cooked steak can bring a large hit of protein, plus iron, zinc, and B vitamins. Protein content tends to be high across cuts. The swing is mostly fat. If you’re trying to keep calories lower while keeping protein high, lean cuts with smart cooking tend to fit better.

If you’re buying steak for a calorie target, look for words like “lean,” “trimmed,” and “sirloin,” then cook it in a way that doesn’t soak it in extra fat. If you’re buying steak for a richer meal, ribeye and strip are famous for a reason. Just log them honestly.

Food safety basics for steak

Calories are not worth much if you get sick. Use a thermometer, especially with thicker steaks. For whole cuts of beef, a common minimum internal temperature guidance is 145°F with a rest time. USDA FSIS safe minimum internal temperature chart lists recommended minimums for meats and poultry.

Resting matters for two reasons: safety and juiciness. Pulling the steak at the right temperature and letting it rest keeps more moisture inside. That can also keep the cooked weight a bit higher, which can slightly lower the calories per ounce when you compare the same cut cooked longer.

Second table: a fast way to log a 7-oz steak without guessing

Use this as a repeatable routine. Once you do it twice, it feels automatic.

What you have	What to log	Small check to stay on track
7 oz raw weight at home	Raw steak entry for that cut	Log any oil or butter used
7 oz cooked weight at home	Cooked steak entry for that cut	Trim left on plate means lower calories
Menu lists “7 oz filet”	Raw filet portion, restaurant style	Add butter topping if it arrives with one
Steak is bone-in	Edible meat estimate, not total weight	Bone can be 15–25% of the listed weight
Pan-seared with visible drippings eaten	Cooked entry plus added fat	Count what you spoon over the steak
Grilled, no added fat	Cooked entry only	Pick a “broiled/grilled” style if listed

A simple range you can trust when you have no details

Sometimes you’re at a friend’s house or a work dinner and you can’t weigh anything. In that case, pick a range based on the cut and how rich it tasted.

• Lean cut, light cooking fat: log 380–450 calories for the steak.
• Medium marbling or fatty edges eaten: log 450–600 calories.
• Ribeye or butter-finished steak: log 600–800 calories.

If you want to tighten that range next time, bring one habit: weigh raw steaks before cooking at home. After a few meals, you’ll learn what your usual “7 oz” looks like and how your favorite cut lands for calories.

References you can use to verify numbers

All calorie ranges in this article are grounded in publicly available nutrient databases and labeling rules. If you want to go deeper, you can use the same sources below to cross-check your own cut and cooking method.

FoodData Central dataset listing on Data.gov also explains how the USDA organizes food composition data and how updates are published.