Chicken Thigh Protein Per 100g: Raw vs Cooked, Explained

Chicken thigh protein per 100g is about 20g when weighed raw and roughly 26g when weighed cooked, using representative database entries for edible thigh meat. The difference is mainly water lost during cooking: it concentrates the protein in each 100g but does not create more protein in the piece. For accurate tracking, match the value to the weight you actually recorded and whether the thigh is boneless, skinless and cooked.

What the number means

A protein figure “per 100g” describes the amount of protein in 100g of a specified food, in a specified state. It is not a fixed property of every chicken thigh. A database value can refer to raw meat, cooked meat, meat with skin, or a serving that includes bone. Those are different entries, so the number is only useful when its description matches your food.

For a practical reference, USDA FoodData Central entries put raw thigh meat at around 19.7g protein per 100g and cooked roasted thigh meat at around 25.9g per 100g. Treat these as representative values, not a guarantee for every product: breed, trimming, preparation and the database entry selected can affect the result. You can compare entries in USDA FoodData Central’s chicken-thigh search; Australian shoppers can also check foods in the Australian Food Composition Database.

The useful rule is: raw weight needs a raw entry, and cooked weight needs a cooked entry. Weigh the edible portion, not bone, and use the food description that most closely matches what you ate. A skin-on entry is a better match for skin eaten than a skinless entry, even though protein is usually the main macro people are trying to count.

Why raw and cooked values differ

Water changes the amount per 100g

Chicken loses water as it cooks. If a piece starts at 100g and finishes lighter, much of its protein remains in the meat while the total weight falls. The cooked portion therefore has more protein per 100g—not because cooking added protein, but because each 100g now contains a more concentrated share of the original food.

This distinction matters most when you switch between weighing raw and cooked. If you log 150g cooked using the raw value of 19.7g per 100g, you would record about 30g protein. Using the cooked reference of 25.9g gives about 39g. That gap is large enough to distort a meal or a day’s macro total.

Cooking yield connects the two entries

Yield is the cooked weight divided by the raw weight. It varies with cooking time, temperature, cut size and method, so it is better to measure your own batch than assume a universal conversion. The protein total for the batch should remain broadly similar, while the weight changes through moisture loss and, depending on preparation, drippings or discarded pieces.

• Illustrative example: 600g raw edible thigh meat at 19.7g protein per 100g contains about 118g protein in total.
• Illustrative yield: If that batch finishes at 450g cooked, it averages about 26.2g protein per 100g cooked (118g divided by 450g, then multiplied by 100).
• Portion example: A 150g cooked serving from that batch contains about 39g protein, assuming the batch is mixed and portioned evenly.
• Bone-in warning: If a 200g raw bone-in thigh includes 40g of bone, calculate from the 160g edible portion—not the full scale weight.

The worked yield is an illustration, not a promise that every batch loses one-quarter of its weight. If your cooked batch weighs 480g instead, divide the batch’s estimated protein by 480g to find its own protein per 100g. This approach is more consistent than applying a generic cooked number to an unusually dry or juicy batch.

How to calculate a portion for macro tracking

Once the food state and entry match, the arithmetic is simple: protein in portion = weight in grams × protein per 100g ÷ 100. For 180g raw thigh meat at 19.7g per 100g, that is about 35.5g protein. For 180g cooked meat at 25.9g per 100g, it is about 46.6g.

Choose one weighing method and stick to it

For meal prep, either weigh portions raw and log a raw entry, or weigh portions cooked and log a cooked entry. Mixing the two methods within one batch is where errors creep in. If you cook a large tray and divide it into meals, a reliable batch calculation is:

1. Weigh the edible raw meat, excluding packaging and bone.
2. Multiply that weight by the raw entry’s protein per 100g and divide by 100.
3. Weigh the cooked batch after removing anything you will not eat.
4. Divide the batch’s estimated protein total by its cooked weight, then use that cooked rate for portions from the batch.

For example, if the 600g raw batch above yields 450g cooked and you split it into three equal portions, each portion is 150g cooked and contains about 39g protein. If you add sauce or vegetables, log those separately unless your nutrition entry specifically describes the combined dish. That keeps the chicken estimate distinct from the rest of the meal.

For packaged products, the nutrition information panel can be a better match than a generic database entry when it describes the exact product. Read the serving size and whether values refer to the food as sold or prepared; Australian label guidance explains how to read a nutrition information panel. If the panel reports protein per serve, scale it to the amount you actually ate rather than assuming one pack or one serve equals your portion.

Use protein per 100g to compare grocery value

Protein density alone does not tell you which pack is the better buy. For budget comparisons, use the edible weight, the pack price and a consistent protein value. This is especially important when comparing boneless thighs with bone-in pieces: the cheaper price per kilogram may apply to weight you cannot eat.

Here is an illustrative comparison method, not a current Coles price claim. Suppose a boneless pack costs $12 and contains 600g edible raw thigh meat. At 19.7g protein per 100g, the pack contains about 118g protein. Its cost is about $2.54 per 25g protein: $12 divided by 118g, multiplied by 25g. Replace the example price and weight with the figures on the pack to get a useful estimate for your shop.

• Compare like with like: use raw edible weight and a raw protein value for each raw pack.
• Include waste: for bone-in or heavily trimmed meat, estimate edible yield or weigh the meat after deboning.
• Calculate cost per protein amount: divide pack price by total protein, then multiply by your chosen comparison amount, such as 25g.
• Check the meal, not just the meat: include rice, vegetables, oil, marinade and other ingredients when estimating meal cost.

A lower cost per 25g of protein does not automatically make a pack the best choice. Consider whether you will use the full pack, whether the portion fits your meal plan, and whether the cut’s fat content suits your macro target. A deal that leads to unused food can cost more in practice than a slightly dearer pack that fits the week’s planned meals.

Where the estimate can break down

Bone and skin change the match. A scale does not distinguish edible meat from bone. Skin also contributes weight and changes the food description, while trimming changes how much of the purchased weight ends up in the meal. When precision matters, weigh the edible portion or select a database entry that matches the product and what you ate.

Cooking methods do not produce identical yields. Roasting, pan-frying and stewing can leave different amounts of moisture in the meat. Sauces and cooking liquids create another decision: if you eat them, they may contribute nutrients that are not captured by a plain-thigh entry; if you discard them, the final dish may differ from an entry that includes them. For repeatable meal prep, calculate a batch-specific cooked rate rather than treating every method as interchangeable.

Labels, apps and databases can disagree. A packaged product’s panel may describe a particular formulation, while a generic database describes a broader food category. Values can also be rounded on labels. Australian reference values are useful for local foods, but the closest match still depends on the product and preparation. If your goal is consistency rather than laboratory precision, use the same appropriate entry and weighing routine each time.

Finally, a protein number is not a personal target. The Australian Nutrient Reference Values set population reference amounts by age and life stage; an individual training plan may need a different target based on its purpose and personal circumstances. Use chicken’s protein figure to count what is in a portion, not to infer how much you personally should eat. The Australian protein reference values explain the population context.

A practical routine for weekly planning

For a household planning several dinners, the simplest reliable routine is to choose a weighing point before cooking and keep it consistent for the batch. Record the raw edible amount, estimate the batch’s protein from a matching raw entry, then divide that total across the cooked portions. If you prefer to log each portion as cooked, weigh the finished batch and calculate its batch-specific cooked rate once.

• At the shop: compare pack price per edible protein, not just dollars per kilogram.
• At prep: record whether weights are raw or cooked, and whether the meat includes skin or bone.
• At serving: portion the batch evenly or weigh each serving, then log using the corresponding rate.
• When plans change: update the meal estimate if you leave skin, bones or cooking liquid uneaten.

For a starting policy, a household could log raw pack weights during meal prep and use raw database values throughout; that is an illustrative workflow, not a universal best method. Choose whichever point in the process is easiest to repeat. Macronomics is designed for Australian Coles shoppers who want to plan meals alongside estimated whole-pack grocery costs and the cost of protein. If that fits your weekly routine, Macronomics is worth exploring as its beta develops.

Authored with NotFair SEO